IID 00 - Special Parameter Command
IID 00 is used to read or write special parameters. IID 00 is used when IID 24 or IID 25 cannot be used. The response to an IID 00 will be an IID 25 Single Parameter Read Response. An example of the IID 00 message is: $500000zz00580083ddddddcs. This example contains three bytes of data.
IID 00 - Special Parameter Command | ||
---|---|---|
Bytes(s) | Description | |
1 - 4 | Standard Preamble | |
5 | Reply Format | |
$00 = ASCII | ||
6 | Unit Number Data is being written to | |
3500B Marine Engine Unit Number
$21 = Electronic engine controller (Port) $22 = Electronic engine controller (Starboard) $24 = Electronic engine controller (Single of Center) |
||
3500B Generator Set Unit Number
$21 - $26 = Electronic engine controller $28, $29 (number 1-8) |
||
EMCP II Generator Set Unit Number
$58 - $5F = GSC (number 1-8) |
||
Customer Communication Module Unit No.
$61 = CCM |
||
7, 8 | PID | |
9 - 11(1) | Data value of parameter. | |
12 | Checksum of message followed by an ASCII carriage return ($0D) |
(1) | The number of bytes will depend on the PID. |
This IID is used to broadcast data from the CCM to the host device. The CCM will send this message if the time to broadcast data has elapsed. In order to send an IID 10 message, ALL of the parameters must be present on the CAT data link. When IID 10 is used, the data will be two bytes in length. If a parameter only has one data byte, zeros will be added in front of the data. An example of the IID 10 message is: $500110zz0124ddd120ddd220ddd320ddd420 ddd520ddd620ddd720ddd8cs.
IID 10 - Broadcast Response | |
Byte(s) | Description |
1-4 | Standard preamble (50 xxyyzz) |
5 | Parameter List Number
$01 - $08 show which list 1 through 8 is being sent. |
6 | Unit Number Data is being written to
3500B Marine Engine Unit Number $21 = Electronic engine controller (Port) $22 = Electronic engine controller (Starboard) $24 = Electronic engine controller (Single of Center) |
3500B Generator Set Unit Number
$21 - $26 = Electronic engine controller $28, $29 (number 1-8) |
|
EMCP II Generator Set Unit Number
$58 - $5F = GSC (number 1-8) |
|
Customer Communication Module Unit No.
$61 = CCM |
|
7 | Separator(1) |
8,9 | Data for 1st PID |
10 | Separator(1) |
11, 12 | Data for 2nd PID |
13 | Separator(1) |
14, 15 | Data for 3rd PID |
16 | Separator(1) |
17, 18 | Data for 4th PID |
19 | Separator(1) |
20, 21 | Data for 5th PID |
22 | Separator(1) |
23, 24 | Data for 6th PID |
25 | Separator(1) |
26, 27 | Data for 7th PID |
28 | Separator(1) |
29, 30 | Data for 8th PID |
31 | Checksum of message |
(1) | A separator may or may not be present depending on bytes 8 and 9 of IID 13. |
IID 10 can will be either binary or ASCII. The message format is determined by bytes 8 and 9 of IID 13. The entire broadcast list will not be returned if any of the following conditions are met:
- The GSC number or the ECM number is not available.
- The GSC or the ECM does not support any of the PID in IID 13.
- The PID contains more than 2 bytes of data.
Refer to PID $00 $80 for information on the device ID. Refer to IID 13 for information on creating broadcast lists. Refer to Operation and Maintenance Manual, SEBU6874, "Programming Examples for M5X Protocol".
IID 11 - Activate a Broadcast List
This IID is used in order to activate a broadcast list that has been programmed. When a list is programmed into the CCM, the list is set to deactivated. The list will stay deactivated until a valid IID 11 message is received. After receiving an IID 11 message, the CCM responds with an IID 15 message. The IID 15 message is for verification of the IID 11 message. If the IID 11 message is valid and the list is programmed, broadcasting of the data will start. Lists can be activated and deactivated at any time without being reprogrammed. A typical IID 11 example is: $5000110101cs
IID 11- Activate a Broadcast List | |
Byte(s) | Description |
1-4 | Standard preamble (50 xxyyzz) |
5 | Parameter List Number
$01 - $08 show which list 1 through 8 is being sent. |
6 | Checksum of message |
IID 12 - Deactivate a Broadcast List
This IID is used in order to deactivate a broadcast list that has been programmed. A list will stay activated until a valid IID 12 message is received. Upon receiving an IID 12 message, the CCM responds with an IID 15 message. This is used to indicate the validity of the message. If the IID 12 message is valid, the broadcasting of the data will stop. Lists can be activated and deactivated at any time without being reprogrammed. A typical IID 12 example is: $5000120101cs.
IID 12 - Deactivate a Broadcast List | |
Byte(s) | Description |
1-4 | Standard preamble (50 xxyyzz) |
5 | Parameter List Number
$01 - $08 show which list 1 through 8 is being sent. |
6 | Checksum of message |
IID 13 - Create a Broadcast List
This IID is used in order to program a broadcast list. After receiving an IID 13 command, the CCM responds with an IID 15 message. If the command message is valid, the list will be programmed in the CCM. This IID has several parameters that need to be programmed with the IID.
The message must contain eight parameters. If the number of desired parameters is only four, the remaining four parameters must be filled with zeros (0). The broadcast response (IID 10) will only contain data for the nonzero parameters. A typical IID 13 example is: $500013150124010000ddd1ddd2ddd3 ddd5ddd6ddd7ddd8cs
IID 13 - Deactivate a Broadcast List | ||
Byte(s) | Description | |
1-4 | Standard preamble (50 xxyyzz) | |
5 | Parameter List Number
$01 - $08 show which list 1 through 8 is being sent. |
|
6 | Unit Number Data is being written to | |
3500B Marine Engine Unit Number
$21 = Electronic engine controller (Port) $22 = Electronic engine controller (Starboard) $24 = Electronic engine controller (Single of Center) |
||
3500B Generator Set Unit Number
$21 - $26 = Electronic engine controller $28, $29 (number 1-8) |
||
EMCP II Generator Set Unit Number
$58 - $5F = GSC (number 1-8) |
||
Customer Communication Module Unit No.
$61 = CCM |
||
7 | Update Rate (between list or parameters) | |
Resolution: 0.5 second per bit
Data range: 0 to 127.5 ($00 to $FF) |
||
8, 9 | Programming Options | |
Bit 1 | 0 = ASCII
1 = Binary |
|
Bit 3, 2 | 00 = Message terminated by carriage return
01 = Message terminated by carriage return and line feed |
|
Bit 4 | 0 = Always | |
Bit 6, 5 | 00 = Comma separator
01 = Space separator 10 = No separator |
|
Bit 7-16 | Reserved for future use | |
10, 11 | Data for 1st PID(1) | |
12, 13 | Data for 2nd PID(1) | |
14, 15 | Data for 3rd PID(1) | |
16, 17 | Data for 4th PID(1) | |
18, 19 | Data for 5th PID(1) | |
20, 21 | Data for 6th PID(1) | |
22, 23 | Data for 7th PID(1) | |
24, 25 | Data for 8th PID(1) | |
26 | Checksum of message |
(1) | If a PID is not used, 0000 must be entered for that PID. The CCM will ignore any PID's after the first PID entered as 0000. Therefore all unused PID's must be at the end of the broadcast list. |
Note: Each CCM will support up to a total of eight lists for all GSC's and ECM's. Each list may contain up to eight PID's. The CCM will support up to 64 parameters. However, the total number of PID's able to be broadcast is limited to 48 per controller. Refer to Operation and Maintenance Manual, SEBU6874, "Programming Examples for M5X Protocol".
Note: For the older version of CCM, 117-6170 System Communication Module, the total number of PID's able to be broadcast is limited to 31 per module.
IID 15 - Status Reply to IID 11, IID 12, and IID 13
This IID is used in order to indicate the validity of a command message that was just sent to the CCM. A typical IID 15 example is: $5001150100cs.
IID 15 - Status Reply to IID 11, IID 12, and IID 13 | |
Byte(s) | Description |
1-4 | Standard preamble (50 xxyyzz) |
5 | IID sent in response to (11, 12, or 82) |
6 | Status Reply
$00 = IID data is OK $10 = Invalid list number (greater than 8 or less than 1) $20 = List is not programmed $30 = Faulty checksum or command format |
7 | Checksum of message followed by an ASCII carriage return ($0D) |
IID 24 - Single Parameter Read Request
This IID is used to request data for an individual parameter. The parameter can be sent one time per second. Another IID 24 request cannot be sent until one second has elapsed and/or an IID 25 message has been received for the previous request. A typical IID 24 example is: $500024040024F515cs
IID 24 - Single Parameter Read Request | |
Byte(s) | Description |
1-4 | Standard preamble (50 xxyyzz) |
5 | Reply format
$00 = ASCII |
6 | Unit Number Data is being written to
3500B Marine Engine Unit Number $21 = Electronic engine controller (Port) $22 = Electronic engine controller (Starboard) $24 = Electronic engine controller (Single of Center) |
3500B Generator Set Unit Number
$21 - $26 = Electronic engine controller $28, $29 (number 1-8) |
|
EMCP II Generator Set Unit Number
$58 - $5F = GSC (number 1-8) |
|
Customer Communication Module Unit No.
$61 = CCM |
|
7, 8 | PID |
9 | Checksum of message followed by an ASCII carriage return ($0D) |
IID 25 - Single Parameter Read Response
This IID is used to indicate a response to a single parameter read request (IID 24). The number of bytes for this IID will vary. The number of bytes is dependent on the parameter that was requested. A typical IID 25 example is: $500125zz24F515ddddcs
Note: In this example, parameter F515 has two data bytes.
IID 25 - Single Parameter Read Response | |
Byte(s) | Description |
1-4 | Standard preamble (50 xxyyzz) |
5 | Unit Number Data is being written to
3500B Marine Engine Unit Number $21 = Electronic engine controller (Port) $22 = Electronic engine controller (Starboard) $24 = Electronic engine controller (Single of Center) |
3500B Generator Set Unit Number
$21 - $26 = Electronic engine controller $28, $29 (number 1-8) |
|
EMCP II Generator Set Unit Number
$58 - $5F = GSC (number 1-8) |
|
Customer Communication Module Unit No.
$61 = CCM |
|
6, 7 | PID |
8 | Data value of requested parameter. Data value may be from 1 through 27 bytes. This example shows two bytes. |
9 | Checksum of message followed by an ASCII carriage return ($0D) |
IID 34 - Single Parameter Write Request
This IID is used to write data for an individual parameter. The data can be sent one time per second. Another IID 34 request cannot be sent until one second has elapsed and/or an IID 35 message has been received for the previous request. A typical IID 34 example is: $500034zz0024F515ddddcs
IID 34 - Single Parameter Write Request | |
Byte(s) | Description |
1-4 | Standard preamble (50 xxyyzz) |
5 | Reply format
$00 = ASCII |
6 | Unit Number Data is being written to
3500B Marine Engine Unit Number $21 = Electronic engine controller (Port) $22 = Electronic engine controller (Starboard) $24 = Electronic engine controller (Single of Center) |
3500B Generator Set Unit Number
$21 - $26 = Electronic engine controller $28, $29 (number 1-8) |
|
EMCP II Generator Set Unit Number
$58 - $5F = GSC (number 1-8) |
|
Customer Communication Module Unit No.
$61 = CCM |
|
7, 8 | PID |
9, 10 | Data value of requested parameter. Data value may be from 1 through 27 bytes. This example shows two bytes. |
11 | Checksum of message followed by an ASCII carriage return ($0D) |
IID 35 - Single Parameter Write Response
This IID is used to indicate a response to a single parameter write request (IID 34). The number of bytes for this IID will vary depending on the parameter that was written. A typical IID 35 example is: $500135zz24F515ddddcs.
IID 35 - Single Parameter Write Response | |
Byte(s) | Description |
1-4 | Standard preamble (50 xxyyzz) |
6 | Unit Number Data is being written to
3500B Marine Engine Unit Number $21 = Electronic engine controller (Port) $22 = Electronic engine controller (Starboard) $24 = Electronic engine controller (Single of Center) |
3500B Generator Set Unit Number
$21 - $26 = Electronic engine controller $28, $29 (number 1-8) |
|
EMCP II Generator Set Unit Number
$58 - $5F = GSC (number 1-8) |
|
Customer Communication Module Unit No.
$61 = CCM |
|
6, 7 | PID |
8, 9 | Data value of requested parameter. Data value may be from 1 through 27 bytes. This example shows two bytes. |
10 | Checksum of message followed by an ASCII carriage return ($0D) |