Technologies

[fanam77]

Hi Earlson,

Using the Parameter Translation Editor program, you have to add two new translations (Active Diagnostics and Active Events) from the Engine ECM to the Modbus ECM.

Then refer to the Events and Diagnostics section of publication RENR8091 for interpretation.

Hope this helps

[fanam77]

@QuadSurfer's post:

This problem was resolved by flashing the PL1000E with the latest file.

[earlson]

Hi fanam77,

Thanks for your reply.

After some verification on both ECM and PL-1000E device, we have concluded there was something wrong with ECM device. We discovered that the CAT "NPD" display panel was showing the correct  value (e.g. RPM value) after the engine started, but the PL-1000E modbus output was showing incorrect value (e.g. very huge values) after the data translation from ECM device.

Could advise the connection link between ECM - CANJ1939 - Cat datalink for PL-1000E and CAT "NPD" display panel. As I would like to know the output link from CANJ1939/ECM translating data to CAT display panel and PL-1000E.

FYI, despite several attempt to reflash ECM configuration and check the harness/wiring connection, this problem still presist giving an invalid data in modbus translation for third party device to poll (e.g. PLC).

Is the symptom described above giving you any clue on this issue more to ECM hardware failure or software failure ?

Hopefully, we would not need to change the ECM considering the lead time and extra cost it will incur.

Please feedback if possible.

Thanks.

[BlackCat1]

The data path will depend on how the PL1000E is configured.  The PL1000E can be configured for J1939 or CDL.  CDL is most commonly used for twin engines applications.  So for CDL the path would be ECM -> CDL -> PL1000E -> Your display software

The "MPD" Marine Power Display data path is ECM -> J1939 -> MPD

Each Modbus parameter has scaling that needs to be applied by the system integrator to get the correct value to display.  You should have a copy of the parameters, Modbus registers and scaling from the PL1000E Parameter Translation Editor configuration.

Example:

• Parameter = engine speed
• Modbus Register = 40001
• Data Type = Float
• Data Length = 2
• Resolution = 0.5

Your engine ECM is working perfectly.  Apply a scale factor to your display software and you will have the correct values.

[earlson]

Thanks for swift reponse.

I am aware on this scalling resolution to be applied of this engine parameter. Initially, my ECM and PL-1000E was working perfectly, I am able to poll the required data at no issue. However, recently I discovered that the polled data from PL-1000E via CAT data link giving us very huge value after scaled.

Example :

Desired Engine Speed (RPM) : 16,385

Engine Speed (RPM) : 32,753

We also noticed if we were to swap PL-1000E to the same engine on the left, it was ok and the modbus data display from PL-1000E was accurate. Therefore, I am suspecting there is something not right on CAT data link connection or ECM device had failed.

[BlackCat1]

You can easily confirm the data on the CDL is correct by connecting CatET and monitoring each parameter.  This will be the same data that the PL1000E uses to convert to Modbus.  Also, you can use a low level program like ModScan32 to view the raw data coming out of the PL1000E. 

[earlson]

After the verification, it is confirmed that CDL connecting to CATET was giving us the correct data, but the same data that uses PL1000E to convert to Modbus proved otherwise. I have used Modpoll, a similar program like ModScan32 to poll the raw data, it showed some very huge values (e.g. Engine Speed : 16,385). Nevertheless, the "MPD" Marine panel display still give us the correct value.

Would the symptoms mentioned here enable you to classify the problem ?

Please advise.

Thanks!

[BlackCat1]

It sounds like one pieces of the PL1000E configuration is not correct.

1. Verify the PL1000E has the latest flash file 376-4410.FLS installed

2. Verify the configuration of the PCL file and PTE file used for the engine ECM

3. Print out the Parameter List Report.

4. Copy the PCL file to the PL1000E by placing it in the NEW folder by using FTP

5. Reset the PL1000E

6. Verify the PL1000E is using the current file by looking in the CURRENT folder for the file.  Example: "MyFile_20110817133638.pcl"  The date code is appended to your file name.

[earlson]

It doesn't seem to be PL1000E configuration issue, as I swapped the left problematic PL1000E device to the right ECM, I was able to poll the modbus raw data with correct value. Therefore, the Pl-1000E configuration and hardware, I think has no issue. I am anticipating there might be some thing wrong with LEFT ECM hardware device.

LEFT ECM connecting to LEFT PL1000E - Modbus raw data issue

RIGHT ECM  connecting to LEFT PL1000E - Working OK

[earlson]

Just to add on to my findings, as we have verified both PL1000E devices on the left and right side. It is confirmed that both PL1000E hardwares have no issue. Reason being, we have tried to swap a few units of good working condition PL1000E on the problematic LEFT ECM device, it still give us an invalid modbus data.

Therefore, we're quite certain the root cause of this invalid modbus data was caused by ECM hardware device.

I think we have no choice but to replace a new ECM device.

Anyway, Thanks for your help.