Line 44: |
Line 44: |
| Manual CAN data can be configured using “Manual CAN” in CAN tab. | | Manual CAN data can be configured using “Manual CAN” in CAN tab. |
| | | |
| + | {{{image1|[[Image:FMB630_manual_CAN1]]}}} |
| | | |
| CAN message ID type: Message ID type two types according to SAEJ1939 standard: Standard ID (value: 0 to 0x7FFh) and Extended ID (value: 0 to 0x1FFFFFFFh). | | CAN message ID type: Message ID type two types according to SAEJ1939 standard: Standard ID (value: 0 to 0x7FFh) and Extended ID (value: 0 to 0x1FFFFFFFh). |
| | | |
| + | {{{image2|[[Image:FMB630_manual_CAN2]]}}} |
| | | |
− | CAN message ID types
| |
| | | |
| Message ID value is entered in hex format. This parameter is used to configure hardware message filter (Figure 90). All messages contain 8 bytes of data, to select particular data/bytes “Output Data Mask” is used, it’s done by ticking required bytes, only selected bytes are sent to server. | | Message ID value is entered in hex format. This parameter is used to configure hardware message filter (Figure 90). All messages contain 8 bytes of data, to select particular data/bytes “Output Data Mask” is used, it’s done by ticking required bytes, only selected bytes are sent to server. |
| | | |
− | CAN message filter configuration
| + | |
| + | {{{image3|[[Image:FMB630_manual_CAN3]]}}} |
| | | |
| Example | | Example |
Line 71: |
Line 73: |
| Pin 2: CAN High signal (blue wire) | | Pin 2: CAN High signal (blue wire) |
| | | |
− | X5 plug on Mercedes Benz
| + | {{{image4|[[Image:FMB630_manual_CAN4]]}}} |
| | | |
| In the example {{{model|FMB630}}} will filter all CAN messages with identifier FFFEE9FF (fuel consumption) (Figure 92). | | In the example {{{model|FMB630}}} will filter all CAN messages with identifier FFFEE9FF (fuel consumption) (Figure 92). |
| | | |
| + | {{{image5|[[Image:FMB630_manual_CAN5]]}}} |
| | | |
| CAN parameter configuration example | | CAN parameter configuration example |
Line 113: |
Line 116: |
| The example indicates how fuel consumption message is selected and how configuration impacts this selection (Figure 93). | | The example indicates how fuel consumption message is selected and how configuration impacts this selection (Figure 93). |
| | | |
− | Example
| + | {{{image6|[[Image:FMB630_manual_CAN6]]}}} |
| | | |
| When certain message is filtered, {{{model|FMB630}}} checks which data bytes should be sent to server. Document indicates that 5-8 bytes are used in FMS standard. | | When certain message is filtered, {{{model|FMB630}}} checks which data bytes should be sent to server. Document indicates that 5-8 bytes are used in FMS standard. |
Line 144: |
Line 147: |
| | | |
| | | |
− | Example
| + | {{{image7|[[Image:FMB630_manual_CAN7]]}}} |
| | | |
| Data bytes are filtered by selecting the checkboxes in Output data mask. Note, that configurator has them listed starting with MSB. | | Data bytes are filtered by selecting the checkboxes in Output data mask. Note, that configurator has them listed starting with MSB. |
| After message is filtered it is attached to the data packet and sent to the server. Values are returned in HEX. 00 03 84 23(HEX) = 230435(DEC). Notice, that data resolution is 0.5L/bit gain – value has to be multiplied by 0.5, therefore vehicle used a total 115217,5 liters of fuel. | | After message is filtered it is attached to the data packet and sent to the server. Values are returned in HEX. 00 03 84 23(HEX) = 230435(DEC). Notice, that data resolution is 0.5L/bit gain – value has to be multiplied by 0.5, therefore vehicle used a total 115217,5 liters of fuel. |