|
|
| (40 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. |
| − | ==Is there any Tell Tale parameters available on my vehicle?==
| |
| − | <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.
| |
| − | <br>
| |
| | | | |
| − | ==What parameters should be enabled== | + | == What parameters should be enabled == |
| − | <br>
| + | Configurable parameters via SMS/GPRS commands can be found at [[FMB640_Device_Family_Parameter_list#FMS]] |
| − | FMBX640 have CAN1 and CAN2 BUS lines that are already configured.
| |
| − | <br>
| |
| − | | |
| − | *FMB640 CAN1 connected to vehicle's FMS(J1939) BUS line
| |
| − | *FMB640 CAN2 connected to vehicle's Tachograph
| |
| | | | |
| − | <br>
| |
| − | More information in [[FMB640_CAN_%5C_Tachograph|CAN\Tachograph paragraph]]
| |
| − | <br>
| |
| − |
| |
| − | Configurable parameters via SMS/GPRS commands can be found at [[FMB640_Device_Family_Parameter_list#FMS]]
| |
| − | <br>
| |
| | [[File:Tell Tale configuration.gif]] | | [[File:Tell Tale configuration.gif]] |
| | | | |
| − | ==How does it work?== | + | == How to parse Tell Tale data == |
| − | | + | Example of FMS Tell Tale status data: |
| − | <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 ID2<br>
| |
| − | *Tell Tale ID3<br>
| |
| − | | |
| − | Each ID represents Block ID of Tell Tale.
| |
| − | <bR>
| |
| − | | |
| − | IO elements store information that is received from FMS Tell Tale Status message (CAN ID - 0x00FD7D).<br>
| |
| − | 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.<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>
| |
| − | #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>
| |
| − | | |
| − | <br>
| |
| − | | |
| − | Once Block ID is captured all 8 bytes of Tell Tale message are saved to corresponding Tell Tale IO element.<br>
| |
| − | | |
| − | | |
| − | Example of FMS Tell Tale status data:<br> | |
| | [[File:Tell Tale.PNG]] | | [[File:Tell Tale.PNG]] |
| | | | |
| − | When device is powered up all elements are be updated to the first corresponding message.
| + | Test |
| − | | |
| − | 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==
| |
| − | Bytes should be read from Right <<< To left. <BR> 4th and 8th Bytes are <span style="background:grey">not defined</span><br>
| |
| | | | |
| − | Statuses are described in [[FMS_Tell_Tale_Status#Quick_links|FMS document]]. <br>
| |
| − | See Table for Tell Tale statuses, page 27 (60) <br>
| |
| − | Binary table to determine indication status can be found in 1.1.16 FMS Tell Tale Status: FMS1, Page 26 (60)<br>
| |
| | | | |
| − | Received data:<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>
| |
| − | 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>
| |
| − | 4 Byte FF | Binary 1111 1111 | Status 6- Not avail.;7- Not avail.| <BR>
| |
| − |
| |
| − | 5 Byte BF | Binary 1011 1111 | Status 8- Not avail.;9- Reserved<BR>
| |
| − | 6 Byte FF | 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>
| |
| − | 8 Byte F0 | Binary 1111 <span style="background:orange">0000</span> | Status <span style="background:orange">14- OFF (Position lights,side lights)</span> ;15- Not avail.<BR>
| |
| − |
| |
| − |
| |
| − |
| |
| − |
| |
| − | Block ID = 1| 0xFFFFFFFFFFFF8FF1<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>
| |
| − | 3 Byte FF | Binary 1111 1111 | Status 4- Not avail;5- Not avail |<BR>
| |
| − | 4 Byte FF | Binary 1111 1111 | Status 6- Not avail;7- Not avail |<BR>
| |
| − | 5 Byte FF | Binary 1111 1111 | Status 8- Not avail;9- Not avail |<BR>
| |
| − | 6 Byte FF | Binary 1111 1111 | Status 10- Not avail;11- Not avail|<BR>
| |
| − | 7 Byte 8F | Binary 1<span style="background:green">000 </span> 1111 | Status 12- Not avail;<span style="background:green">13-OFF Engine oil level </span>|<BR>
| |
| − | 8 Byte F1 | Binary 1111 0<span style="background:orange">001</span> | <span style="background:orange">14- Condition Red Engine coolant level </span>;Status 15- Not avail |
| |
| − |
| |
| − |
| |
| − | <BR>
| |
| − |
| |
| − | Block ID = 2| 0xFFFF8FFFFFF8FFF2<BR>
| |
| − | <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>
| |
| − | 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>
| |
| − | 4 Byte FF | Binary 1111 1111 | Status 6-not avail;7-not avail<BR>
| |
| − | <BR>
| |
| − | 5 Byte FF | Binary 1111 1111 | Status 8-not avail;9-not avail<BR>
| |
| − | 6 Byte F8 | Binary 1111 1<span style="background:orange">000</span> | <span style="background:orange">Status 10-OFF, Bus stop brake</span> ;11-not avail<BR>
| |
| − | 7 Byte FF | Binary 1111 1111 | Status 12-not avail;13-not avail<BR>
| |
| − | 8 Byte F2 | Binary 1111 0<span style="background:orange">010</span> |<span style="background:orange"> Status 14-Condition Yellow, Kneeling</span>;15-not avail<BR>
| |
| − |
| |
| − |
| |
| − | Block ID = 3| 0xFFFFFFFFFFFFFFF3<BR>
| |
| − | <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>
| |
| − | 3 Byte 8F | Binary 1111 1111 | Status 4-not avail;-not avail<BR>
| |
| − | 4 Byte FF | Binary 1111 1111 | Status 6-not avail;7-not avail<BR>
| |
| − | <BR>
| |
| − | 5 Byte FF | Binary 1111 1111 | Status 8-not avail;9-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>
| |
| − | 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>
| |
| | | | |
| | =='''Quick links'''== | | =='''Quick links'''== |
| − | [https://fms-standard.com/Truck/down_load/fms%20document_v_05_vers.24.11.2023.pdf FMS-Standard Description Document] | + | [http://www.fms-standard.com/Truck/down_load/fms%20document_v_04_vers.13.10.2017.pdf FMS-Standard Description Document] |
| | | | |
| | | | |
| Line 136: |
Line 32: |
| | |[[File:Alert.png|left|link=|50px]]||<b>Availability of parameter depends on vehicle’s model and configuration of the FMS interface of the truck.</b> | | |[[File:Alert.png|left|link=|50px]]||<b>Availability of parameter depends on vehicle’s model and configuration of the FMS interface of the truck.</b> |
| | |} | | |} |
| − |
| |
| | {| | | {| |
| − | |[[File:Alert.png|left|link=|50px]]||<b>Note: FMS Tell Tale status is supported on [[FMC650]] [[FMM650]] [[FMB640]] [[FMC640]] [[FMM640]] [[FMB630]] [[FM6300]] devices. Also please check firmware errata table to see from which firmware version this feature is available.</b> | + | |[[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> |
| | |} | | |} |
| − | [[Category:FMB640 Manual|3]]
| |
| − | [[Category:FMC640]]
| |
| − | [[Category:FMM640]]
| |
| − | [[Category:FMM640 Manual]]
| |
| − | [[Category:FMC650 Manual]]
| |
