The user must login to the CCM before any M5X programming can be started. Refer to Operation and Maintenance Manual, SEBU6874, "Communication Protocol for Customized Systems" for more specific information.
Create a Broadcast List
In the following example a broadcast list will be created. The list will also be activated. The list will contain PID $00 $40 (engine rpm) and PID $00 $54 (engine oil pressure). The information will be requested in 2 second intervals from the EMCP II GSC. The list will then be deactivated.
- Create a Broadcast List - IID 13: 500013150258040020004000540000000000 0000000000000086
IID 13 - Used to create a broadcast list. A total of eight lists is allowed by the CCM. This example assumes list number 2.
Show/hide tableTable 1 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $00 User's PC is the sending module 3 $13 IID 13 4 $15 Number of bytes 5 $02 List number 6 $58 GSC number 1 7 $04 Response will be sent every 2 seconds (increments of 0.5 seconds) 8 $00 These bits are unused (always = 0) 9 $20 Programming Options: no separator, message terminated by carriage return, in ASCII form. 10, 11 $00 $40 1st PID - Generator Set Engine RPM 12, 13 $00 $54 2nd PID - Engine Oil Pressure (kPa) 14, 15 $00 $00 Filter for unused PID 16, 17 $00 $00 Filter for unused PID 18, 19 $00 $00 Filter for unused PID 20, 21 $00 $00 Filter for unused PID 22, 23 $00 $00 Filter for unused PID 24, 25 $00 $00 Filter for unused PID 26 $86 Checksum
- IID 15 is the response from the CCM that confirms that the list has been successfully created: 500115010099
IID 15 - The CCM's reply to IID 11, IID 12, or IID 13.
Show/hide tableTable 2 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $01 CCM is the sending module 3 $15 IID 15 4 $01 Number of bytes 5 $00 IID data is OK 6 $99 Checksum
- Activate the Broadcast List - IID 11: 50001101029C
IID 11 - Used to activate a broadcast list.
Show/hide tableTable 3 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $00 User's PC is the sending module 3 $11 IID 11 4 $01 Number of bytes 5 $02 List number 6 $9C Checksum
- IID 15 is the response from the CCM confirming that the list has been activated: 500115010099
IID 15 - The CCM's reply to IID 11, IID 12, or IID 13.
Show/hide tableTable 4 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $01 CCM is the sending module 3 $15 IID 15 4 $01 Number of bytes 5 $00 IID data is OK 6 $99 Checksum
- IID 10 is the broadcast response from the CCM: 5001100602580BB800C8B4
IID 10 - The data will now start flowing from the GSC to the CCM and then to the user's PC at the rate of once every two seconds. The entire broadcast list will not be returned if any of the following conditions are met:
- The GSC number is not available.
- The GSC does not support the PID.
- The PID contains more than 2 bytes of data.
Show/hide tableTable 5 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $01 CCM is the sending module 3 $10 IID 10 4 $06 Number of bytes 5 $02 List number 6 $58 GSC number 1 7, 8 $0BB8 1500 rpm 9, 10 $00C8 100 kPa 11 $B4 Checksum - The GSC number is not available.
- IID 12 will deactivate the list: 50001201029
IID 12 - Used to deactive a list.
Show/hide tableTable 6 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $01 CCM is the sending module 3 $12 IID 12 4 $06 Number of bytes 5 $02 List Number 6 $9B Checksum
- IID 15 is the response from the CCM confirming that the list has been successfully deactivated: 500115010099
IID 15 - The CCM's reply to IID 11, IID 12, or IID 13.
Show/hide tableTable 7 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $01 CCM is the sending module 3 $15 IID 15 4 $01 Number of bytes 5 $00 IID data is OK 6 $99 Checksum
Reading Faults from EMCP II GSC
The following example shows how to read faults from the EMCP II GSC.
- Use IID 24 to send PID $0082 to the GSC: 5000240400580082AE
IID 24- Single parameter Read Request
Show/hide tableTable 8 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $01 CCM is the sending module 3 $24 IID 24 4 $04 Number of bytes 5 $00 IID data is OK 6 $58 GSC number 1 7, 8 $00 $82 PID $0082 GSC Fault Log Codes, Status, And Number of occurrences 9 $AE Checksum
- IID 25 is the response from the CCM: 5001250758008200BEC30424
IID 25 - Single Parameter Read Response
Show/hide tableTable 9 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $01 CCM is the sending module 3 $25 IID 25 4 $07 Number of bytes 5 $58 GSC number 1 6, 7 $00 $82 PID $0082 GSC Fault Log Codes, Status, And Number of occurrences 8, 9 $00 $BE CID 190 (engine speed sensor fault) 10 $C3 Count included, inactive fault, logged fault, standard FMI (3) 11 $04 Occurrence count of 4 12 $24 Checksum
- IID 00 is used to request additional information on a fault 500000070058008300BEC34D
IID 00 - Special parameter Command
Show/hide tableTable 10 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $01 CCM is the sending module 3 $00 IID 00 4 $07 Number of bytes 5 $00 Reply in ASCII format 6 $58 GSC number 1 7, 8 $00 $83 PID $0083 GSC Fault Log Request For Additional Data 9, 10, 11 $00 $BE $C3 More information requested on CID 190 FMI 3 12 $4D Checksum
- IID 25 will contain the reply as PID $0084 5001250B58008400BEC303000C001102
IID 25 - Single Parameter Read Response
Show/hide tableTable 11 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $01 CCM is the sending module 3 $25 IID 25 4 $0B Number of bytes 5 $58 GSC number 1 6, 7 $00 $84 PID $0084 GSC Fault Log Response For Additional Data 8, 9 $00 $BE CID 190 10 $C3 More information on FMI 3 11 $03 Three occurrences of this fault 12, 13 $00 $0C First occurrence at 12 hours 14, 15 $00 $11 Last occurrence at 17 hours 16 $02 Checksum
Monitoring Generator Phase
The following example shows how to select which generator phase the GSC monitors.
- Use IID 34 to write the parameters of PID $F0B0: 500034050048F0B0007F
IID 34 - Single Parameter Write Request
Show/hide tableTable 12 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $00 User's PC is the sending module 3 $34 IID 34 4 $05 Number of bytes 5 $00 Reply in ASCII format 6 $58 GSC number 1 7, 8 $F0 $B0 PID $F0B0 Generator Phase Select 9 $00 Phase A-B Voltage, Phase A Current 10 $7F Checksum
- IID 35 is the response from the CCM: 5001350458F0B0007E
IID 35 - Single Parameter Write Response
Show/hide tableTable 13 Byte(s) Byte Contents Detailed Description 1 $50 Indicates M5X protocol 2 $01 CCM is the sending module 3 $35 IID 35 4 $04 Number of bytes 5 $58 GSC number 1 6, 7 $F0 $B0 PID $F0B0 Generator Phase Select 8 $00 Phase A-B Voltage, Phase A Current 9 $7E Checksum
Retrieving CCM Diagnostic Codes
The CCM allows the diagnostic codes to be read from the CCM and the Engine Controller. This is accomplished by using IID 24. Use IID 24 with PID 0082 to retrieve the codes for the CCM. The format for the message is given below.
5000240400610082cs
The CCM will respond with two data bytes.
Clearing CCM Diagnostic Codes
The diagnostic codes on the CCM can be cleared. The codes are cleared by using IID 34 with PID 000D. The codes on the CCM can be cleared at any time. By sending the following message to the CCM, all of the diagnostic codes will be cleared.
500034050061000DFFcs
The CCM will respond with IID 35, if the message is received properly.