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.png|300px|center]]}}} | + | {{{image1|[[Image:FMB630_manual_CAN1.png|700px|center]]}}} |
| | | |
| 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_CAN3.png|300px|center]]}}} | + | {{{image2|[[Image:FMB630_manual_CAN3.png|200px|center]]}}} |
| | | |
| | | |
Line 54: |
Line 54: |
| | | |
| | | |
− | {{{image3|[[Image:FMB630_manual_CAN2.png|300px|center]]}}} | + | {{{image3|[[Image:FMB630_manual_CAN2.png|500px|center]]}}} |
| | | |
| Example | | Example |
Line 75: |
Line 75: |
| {{{image4|[[Image:FMB630_manual_CAN4.png|300px|center]]}}} | | {{{image4|[[Image:FMB630_manual_CAN4.png|300px|center]]}}} |
| | | |
− | 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). |
| | | |
− | {{{image5|[[Image:FMB630_manual_CAN5.png|300px|center]]}}} | + | {{{image5|[[Image:FMB630_manual_CAN5.png|500px|center]]}}} |
| | | |
| CAN parameter configuration example | | CAN parameter configuration example |
Line 114: |
Line 114: |
| SPN | | SPN |
| | | |
− | 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. |
| | | |
− | {{{image6|[[Image:FMB630_manual_CAN6.png|300px|center]]}}} | + | {{{image6|[[Image:FMB630_manual_CAN6.png|400px|center]]}}} |
| | | |
| 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 147: |
Line 147: |
| | | |
| | | |
− | {{{image7|[[Image:FMB630_manual_CAN7.png|300px|center]]}}} | + | {{{image7|[[Image:FMB630_manual_CAN7.png|400px|center]]}}} |
| | | |
| 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. |