1,583
edits
Changes
→How to parse Tell Tale message
__TOC__
__TOC__
== FMS Tell Tale Status Introduction ==
==FMS Tell Tale Status Introduction==
Tell Tale was created in order to receive all available dashboard indication events that are available on truck via FMS protocol according to J1939 standard.
Tell Tale was created in order to receive all available dashboard indication events that are available on truck via FMS protocol according to J1939 standard.
SAE J1939 is the vehicle bus standard used for communication and diagnostics among vehicle components. Based on the same architecture FMS protocol dedicated to telematics systems is available. It has certain standardized parameters available, such as fuel consumption, engine work-hours, etc. Please visit http://www.fms-standard.com/ for more information and message structure.
SAE J1939 is the vehicle bus standard used for communication and diagnostics among vehicle components. Based on the same architecture FMS protocol dedicated to telematics systems is available. It has certain standardized parameters available, such as fuel consumption, engine work-hours, etc. Please visit http://www.fms-standard.com/ for more information and message structure.
== Is there any Tell Tale parameters available on my vehicle? ==
==Is there any Tell Tale parameters available on my vehicle?==
<br>
<br>
To check if any Tell Tale parameters are available via FMS on your vehicle '''scanfms''' SMS/GPRS command can be used. If there is any parameters available on FMS this means that Tell Tale status is available as well. Response will show parameters that are available on vehicle, but it does not include all Tell Tale statuses - only MIL indication is implemented see [[FMB640_Teltonika_Data_Sending_Parameters_ID#FMS_elements|FMS elements]]. How to parse scanfms response can be found in wiki [[FMB_scanfms]] page.
To check if any Tell Tale parameters are available via FMS on your vehicle '''scanfms''' SMS/GPRS command can be used. If there is any parameters available on FMS this means that Tell Tale status is available as well. Response will show parameters that are available on vehicle, but it does not include all Tell Tale statuses - only MIL indication is implemented see [[FMB640_Teltonika_Data_Sending_Parameters_ID#FMS_elements|FMS elements]]. How to parse scanfms response can be found in wiki [[FMB_scanfms]] page.
<br>
<br>
== What parameters should be enabled ==
==What parameters should be enabled==
<br>
<br>
FMBX640 have CAN1 and CAN2 BUS lines that are already configured.
FMBX640 have CAN1 and CAN2 BUS lines that are already configured.
<br>
<br>
* FMB640 CAN1 connected to vehicle's FMS(J1939) BUS line
* FMB640 CAN2 connected to vehicle's Tachograph
*FMB640 CAN1 connected to vehicle's FMS(J1939) BUS line
*FMB640 CAN2 connected to vehicle's Tachograph
<br>
<br>
More information in [[FMB640_CAN_%5C_Tachograph|CAN\Tachograph paragraph]]
More information in [[FMB640_CAN_%5C_Tachograph|CAN\Tachograph paragraph]]
[[File:Tell Tale configuration.gif]]
[[File:Tell Tale configuration.gif]]
== How does it work? ==
==How does it work?==
<br>
<br>
IO element describes Tell Tale Block ID message received from Block ID 0,1,2,3 in Hexadecimal format.:<br>
IO element describes Tell Tale Block ID message received from Block ID 0,1,2,3 in Hexadecimal format.:<br>
* Tell Tale ID0<br>
* Tell Tale ID1<br>
*Tell Tale ID0<br>
* Tell Tale ID2<br>
*Tell Tale ID1<br>
* Tell Tale ID3<br>
*Tell Tale ID2<br>
*Tell Tale ID3<br>
Each ID represents Block ID of Tell Tale.
Each ID represents Block ID of Tell Tale.
# X0<sub>16</sub> – Block ID 0 - FMS IO element Tell Tale ID0<br>
#X0<sub>16</sub> – Block ID 0 - FMS IO element Tell Tale ID0<br>
# X1<sub>16</sub> – Block ID 1 - FMS IO element Tell Tale ID1<br>
#X1<sub>16</sub> – Block ID 1 - FMS IO element Tell Tale ID1<br>
# X2<sub>16</sub> – Block ID 2 - FMS IO element Tell Tale ID2<br>
#X2<sub>16</sub> – Block ID 2 - FMS IO element Tell Tale ID2<br>
# X3<sub>16</sub> – Block ID 3 - FMS IO element Tell Tale ID3<br>
#X3<sub>16</sub> – Block ID 3 - FMS IO element Tell Tale ID3<br>
<br>
<br>
After 4 seconds (1000 ms per Block ID) all values will be captured again. Device checks last saved value of Tell Tale IO elements and if it is changed – values are updated.<BR>
After 4 seconds (1000 ms per Block ID) all values will be captured again. Device checks last saved value of Tell Tale IO elements and if it is changed – values are updated.<BR>
== How to parse Tell Tale message ==
==How to parse Tell Tale message==
Bytes should be read from Right <<< To left. <BR> 4th and 8th Bytes are <span style="background:grey">not defined</span><br>
Bytes should be read from Right <<< To left. <BR> 4th and 8th Bytes are <span style="background:grey">not defined</span><br>
Block ID = 0| 0xFF8F88FFBFFFFFF0<BR>
Block ID = 0| 0xFF8F88FFBFFFFFF0<BR>
1 Byte FF | Binary <span style="background:grey"> 1</span><span style="background:green"> 111</span> <span style="background:grey">1</span><span style="background:orange">111</span> | <span style="background:green"> Status 1 -Not avail. </span><span style="background:orange"> Block</span> <BR>
1 Byte FF | Binary <span style="background:grey"> 1</span><span style="background:green"> 111</span> <span style="background:grey">1</span><span style="background:orange">111</span> | <span style="background:green"> Status 1 -Not avail.; </span><span style="background:orange"> Block</span> <BR>
2 Byte 8F | Binary 1000 1111 | Status 2- Not avail.;3 - reserved| <BR>
2 Byte 8F | Binary 1000 1111 | Status 2- Not avail.;3 - reserved| <BR>
3 Byte 88 | Binary 1000 1000 | Status 4- Reserved;5 - Reserved| <BR>
3 Byte 88 | Binary 1000 1000 | Status 4- Reserved;5 - Reserved| <BR>
Block ID = 1| 0xFFFFFFFFFFFF8FF1<BR>
Block ID = 1| 0xFFFFFFFFFFFF8FF1<BR>
1 Byte FF | Binary 1111 1111 | Status 1;Block |<BR>
1 Byte FF | Binary 1111 1111 | Status 1-not avail;Block |<BR>
2 Byte FF | Binary 1111 1111 | Status 2- Not avail;3- Not avail |<BR>
2 Byte FF | Binary 1111 1111 | Status 2- Not avail;3- Not avail |<BR>
3 Byte FF | Binary 1111 1111 | Status 4- Not avail;5- Not avail |<BR>
3 Byte FF | Binary 1111 1111 | Status 4- Not avail;5- Not avail |<BR>
Block ID = 2| 0xFFFF8FFFFFF8FFF2<BR>
Block ID = 2| 0xFFFF8FFFFFF8FFF2<BR>
<BR>
<BR>
1 Byte FF | Binary 1111 1111 | Status 1; Block<BR>
1 Byte FF | Binary 1111 1111 | Status 1-not avail; Block<BR>
2 Byte FF | Binary 1111 1111 | Status 2-not avail;3-not avail<BR>
2 Byte FF | Binary 1111 1111 | Status 2-not avail;3-not avail<BR>
3 Byte 8F | Binary 1<span style="background:green">000</span> 1111 | <span style="background:green">Status 4-OFF, Engine Emission system failure (Mil indicator)</span>;5- reserved<BR>
3 Byte 8F | Binary 1<span style="background:green">000</span> 1111 | <span style="background:green">Status 4-OFF, Engine Emission system failure (Mil indicator)</span>;5- reserved<BR>
<BR>
<BR>
5 Byte FF | Binary 1111 1111 | Status 8-not avail;9-not avail<BR>
5 Byte FF | Binary 1111 1111 | Status 8-not avail;9-not avail<BR>
6 Byte F8 | Binary 1111 1111 | Status 10-reserved;11-not avail<BR>
6 Byte F8 | Binary 1111 1111 | Status 10-not avail;11-not avail<BR>
7 Byte FF | Binary 1111 1111 | Status 12-not avail;13-not avail<BR>
7 Byte FF | Binary 1111 1111 | Status 12-not avail;13-not avail<BR>
8 Byte F3 | Binary 1111 0<span style="background:orange">011</span> | <span style="background:orange">Status 14-Condition Info, ESC switched off</span>;15-not avail<BR>
8 Byte F3 | Binary 1111 0<span style="background:orange">011</span> | <span style="background:orange">Status 14-Condition Info, ESC switched off</span>;15-not avail<BR>
