Difference between revisions of "FMS Tell Tale Status"
From Wiki Knowledge Base | Teltonika GPS
| (32 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
__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. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | ==What parameters should be enabled== | + | == What parameters should be enabled == |
| − | + | Configurable parameters via SMS/GPRS commands can be found at [[FMB640_Device_Family_Parameter_list#FMS]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[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 ID0<br> | + | * Tell Tale ID1<br> |
| − | *Tell Tale ID1<br> | + | * Tell Tale ID2<br> |
| − | *Tell Tale ID2<br> | + | * Tell Tale ID3<br> |
| − | *Tell Tale ID3<br> | ||
Each ID represents Block ID of Tell Tale. | Each ID represents Block ID of Tell Tale. | ||
| Line 42: | Line 26: | ||
| − | #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> | ||
| Line 59: | Line 42: | ||
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 == |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Received data:<BR> | Received data:<BR> | ||
Block ID = 0| 0xFF8F88FFBFFFFFF0<BR> | Block ID = 0| 0xFF8F88FFBFFFFFF0<BR> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | 5 Byte BF | Binary 1011 1111 | Status 8 | + | 1 Byte FF | Binary 1111 1111 | Status 1 <BR> |
| − | 6 Byte FF | Binary 1111 1111 | Status 10 | + | 2 Byte 8F | Binary 1000 1111 | Status 2;3<BR> |
| − | 7 Byte FF | Binary 1111 1111 | Status 12 | + | 3 Byte 88 | Binary 1000 1000 | Status 4;5<BR> |
| − | 8 Byte F0 | Binary 1111 | + | 4 Byte FF | Binary 1111 1111 | Status 6;7<BR> |
| + | 5 Byte BF | Binary 1011 1111 | Status 8;9<BR> | ||
| + | 6 Byte FF | Binary 1111 1111 | Status 10;11<BR> | ||
| + | 7 Byte FF | Binary 1111 1111 | Status 12;13<BR> | ||
| + | 8 Byte F0 | Binary 1111 0000 | Status 14;15<BR> | ||
| Line 84: | Line 60: | ||
Block ID = 1| 0xFFFFFFFFFFFF8FF1<BR> | Block ID = 1| 0xFFFFFFFFFFFF8FF1<BR> | ||
| + | Block ID = 2| 0xFFFF8FFFFFF8FFF2<BR> | ||
| + | Block ID = 3| 0xFFFFFFFFFFFFFFF3<BR> | ||
| − | + | Received data: | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | Block ID = 0| 0xFF8F88FFBFFFFFF0 | ||
| + | |||
| + | 1 Byte FF | Binary 1111 1111 | Status 1 | ||
| + | 2 Byte 8F | Binary 1000 1111 | Status 2;3 | ||
| + | 3 Byte 88 | Binary 1000 1000 | Status 4;5 | ||
| + | 4 Byte FF | Binary 1111 1111 | Status 6;7 | ||
| + | 5 Byte BF | Binary 1011 1111 | Status 8;9 | ||
| + | 6 Byte FF | Binary 1111 1111 | Status 10;11 | ||
| + | 7 Byte FF | Binary 1111 1111 | Status 12;13 | ||
| + | 8 Byte F0 | Binary 1111 0000 | Status 14;15 | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | Block ID = | + | Block ID = 1| 0xFFFFFFFFFFFF8FF1 |
| − | + | Block ID = 2| 0xFFFF8FFFFFF8FFF2 | |
| − | + | Block ID = 3| 0xFFFFFFFFFFFFFFF3 | |
| − | 2 | ||
| − | 3 | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=='''Quick links'''== | =='''Quick links'''== | ||
| − | [ | + | [http://www.fms-standard.com/Truck/down_load/fms%20document_v_04_vers.13.10.2017.pdf FMS-Standard Description Document] |
| Line 138: | Line 99: | ||
{| | {| | ||
| − | |[[File:Alert.png|left|link=|50px]]||<b>Note: FMS Tell Tale status is supported on | + | |[[File:Alert.png|left|link=|50px]]||<b>Note: FMS Tell Tale status is supported on [[FMB640]] [[FMC640]] [[FMM640]] [[FMB630]] [[FM6300]] devices. Also please check firmware errata table to see from which firmware version this feature is available.</b> |
|} | |} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 15:56, 4 December 2020
Main Page > EOL Products > FMB640 > FMB640 Manual > FMS Tell Tale StatusFMS 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. 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.
What parameters should be enabled
Configurable parameters via SMS/GPRS commands can be found at FMB640_Device_Family_Parameter_list#FMS
How does it work?
IO element describes Tell Tale Block ID message received from Block ID 0,1,2,3 in Hexadecimal format.:
- Tell Tale ID0
- Tell Tale ID1
- Tell Tale ID2
- Tell Tale ID3
Each ID represents Block ID of Tell Tale.
IO elements store information that is received from FMS Tell Tale Status message (CAN ID - 0x00FD7D).
Status message sends Data Block information in Data Byte 1. Block ID is determined by Data Byte 1 first 4 Bits. Example in hexadecimal first 4 bits where X – random byte value.
- X016 – Block ID 0 - FMS IO element Tell Tale ID0
- X116 – Block ID 1 - FMS IO element Tell Tale ID1
- X216 – Block ID 2 - FMS IO element Tell Tale ID2
- X316 – Block ID 3 - FMS IO element Tell Tale ID3
Once Block ID is captured all 8 bytes of Tell Tale message are saved to corresponding Tell Tale IO element.
Example of FMS Tell Tale status data:
When device is powered up all elements are be updated to the first corresponding message.
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.
How to parse Tell Tale message
Received data:
Block ID = 0| 0xFF8F88FFBFFFFFF0
1 Byte FF | Binary 1111 1111 | Status 1
2 Byte 8F | Binary 1000 1111 | Status 2;3
3 Byte 88 | Binary 1000 1000 | Status 4;5
4 Byte FF | Binary 1111 1111 | Status 6;7
5 Byte BF | Binary 1011 1111 | Status 8;9
6 Byte FF | Binary 1111 1111 | Status 10;11
7 Byte FF | Binary 1111 1111 | Status 12;13
8 Byte F0 | Binary 1111 0000 | Status 14;15
Block ID = 1| 0xFFFFFFFFFFFF8FF1
Block ID = 2| 0xFFFF8FFFFFF8FFF2
Block ID = 3| 0xFFFFFFFFFFFFFFF3
Received data:
Block ID = 0| 0xFF8F88FFBFFFFFF0
1 Byte FF | Binary 1111 1111 | Status 1 2 Byte 8F | Binary 1000 1111 | Status 2;3 3 Byte 88 | Binary 1000 1000 | Status 4;5 4 Byte FF | Binary 1111 1111 | Status 6;7 5 Byte BF | Binary 1011 1111 | Status 8;9 6 Byte FF | Binary 1111 1111 | Status 10;11 7 Byte FF | Binary 1111 1111 | Status 12;13 8 Byte F0 | Binary 1111 0000 | Status 14;15
Block ID = 1| 0xFFFFFFFFFFFF8FF1
Block ID = 2| 0xFFFF8FFFFFF8FFF2
Block ID = 3| 0xFFFFFFFFFFFFFFF3
Quick links
FMS-Standard Description Document
 |
Tell Tale only available on vehicles that support FMS standard |
|
Tell Tale examples are provided in FMS-Standard Description document that is publicly available |
|
Availability of parameter depends on vehicle’s model and configuration of the FMS interface of the truck. |
|
Note: FMS Tell Tale status is supported on FMB640 FMC640 FMM640 FMB630 FM6300 devices. Also please check firmware errata table to see from which firmware version this feature is available. |
