2,556
edits
Changes
mLine 45:
Line 45: − + Line 59:
Line 59: + − + − + − + − − '''Note:''' This information is provided only as an example and Teltonika takes no responsibility for information accuracy or damage that may be done to the vehicle or {{{model|FMB640}}} module while integrating it. − − '''Example:'''+ − + Line 77:
Line 75: − + − Line 143:
Line 140: + +
no edit summary
==Configuration==
==Configuration==
{{{module|FMB640}}} has 70 configurable Manual CAN elements. Manual CAN data can be configured using “Manual CAN” in the CAN tab.
[[{{{model|FMB640}}}]] has 70 configurable Manual CAN elements.
{{{image1|[[Image:FMB640_Manual_CAN.png|700px|none]]}}}
{{{image1|[[Image:FMB640_Manual_CAN.png|700px|none]]}}}
'''Example:'''
'''Example:'''
A sample CAN message has the following structure: <code>X18FEE9018FFFFFFFF23840300</code>, where essential parts are <code>FEE9</code> – identifier and <code>FFFFFFFF23840300</code> – data bytes.
A sample CAN message has the following structure: <code>X18FEE9018FFFFFFFF23840300</code>, where essential parts are <code>FEE9</code> – identifier and <code>FFFFFFFF23840300</code> – data bytes.
CAN messages are configured like any other I/O parameters. They consist of 4 identifier bytes and 8 data bytes. Below you will find a sample configuration for fuel consumption parameter:
CAN messages are configured like any other I/O parameters. They consist of 4 identifier bytes and 8 data bytes. Below you will find a sample configuration for fuel consumption parameter:
* ID type – is always 29 bits.
* '''ID type''' – is always 29 bits.
Output data mask – defines which data bytes are sent to the server (sometimes not all data bytes are necessary).
* '''Output data mask''' – defines which data bytes are sent to the server (sometimes not all data bytes are necessary).
* CAN ID – this is 4 byte identifier. Messages use 4 bytes, but the first and last bytes may differ in different vehicle models while the middle four bytes are the same for all vehicles. The first and last bytes may have any value. Because of this reason, it is recommended to write <code>FF</code> in the first byte and the same in the last byte.
* '''CAN ID''' – this is 4 byte identifier. Messages use 4 bytes, but the first and last bytes may differ in different vehicle models while the middle four bytes are the same for all vehicles. The first and last bytes may have any value. Because of this reason, it is recommended to write <code>FF</code> in the first byte and the same in the last byte.
==Example==
All Mercedes Benz Actros 2 models with Vehicle Identification Number (VIN) starting with WDB93 have a possibility to connect {{{model|FMB640}}} module to the CAN bus. This can be done by connecting to a special PSM module (which may or may not be included in the truck) or ground module of the vehicle. For the CAN signal to be available, parameter 520 must be enabled in “kommunikationsschnittstelle” in the vehicle with Mercedes Stardiagnose.
All Mercedes Benz Actros 2 models with Vehicle Identification Number (VIN) starting with WDB93 have a possibility to connect [[{{{model|FMB640}}}]] module to the CAN bus. This can be done by connecting to a special PSM module (which may or may not be included in the truck) or ground module of the vehicle. For the CAN signal to be available, parameter 520 must be enabled in “kommunikationsschnittstelle” in the vehicle with Mercedes Stardiagnose.
CAN wires can be found on the X5 connector located in the fuse box:
CAN wires can be found on the X5 connector located in the fuse box:
{{{image4|[[Image:FMB630_manual_CAN4.png|500px|none]]}}}
{{{image4|[[Image:FMB630_manual_CAN4.png|500px|none]]}}}
In the example {{{model|FMB640}}} will filter all CAN messages with identifier FFFEE9FF (fuel consumption).
In the example [[{{{model|FMB640}}}]] will filter all CAN messages with identifier FFFEE9FF (fuel consumption).
{{{image5|[[Image:FMB640_Manual_CAN5.png|600px|none]]}}}
{{{image5|[[Image:FMB640_Manual_CAN5.png|600px|none]]}}}
'''Note:''' Averaging constant cannot be used with CAN data, because this information comes in digital format. So in order to prevent data loss, set Averaging constant parameter to 1.
'''Note:''' Averaging constant cannot be used with CAN data, because this information comes in digital format. So in order to prevent data loss, set Averaging constant parameter to 1.
Most parameters have a certain resolution. <code>FEE9</code> parameter has 0.5L/bit gain, so the value that is sent to the server has to be multiplied by 0.5.
Most parameters have a certain resolution. <code>FEE9</code> parameter has 0.5L/bit gain, so the value that is sent to the server has to be multiplied by 0.5.
SPN
SPN
|}
|}
'''Note:''' This information is provided only as an example and Teltonika takes no responsibility for information accuracy or damage that may be done to the vehicle or [[{{{model|FMB640}}}]] module while integrating it.
[[Category:FMB640 Configuration]]
[[Category:FMB640 Configuration]]