Line 12: |
Line 12: |
| | | |
| FMS, or Fleet Management Systems Interface, is a sector to configure and manage events based on vehicle data of commercial vehicles. Vehicle data comes through CAN lines. Event configuring isn’t different from those in LVCAN and I/O sectors. The only difference is IDs. | | FMS, or Fleet Management Systems Interface, is a sector to configure and manage events based on vehicle data of commercial vehicles. Vehicle data comes through CAN lines. Event configuring isn’t different from those in LVCAN and I/O sectors. The only difference is IDs. |
| + | |
| + | ===DM1 and DM2=== |
| + | |
| + | Diagnostic messages reading – DM1, DM2 |
| + | |
| + | '''This feature will be available with the firmware 03.01.01 which should be released till the 2024 Q2 end.''' |
| + | |
| + | Unexpected vehicle maintenance causes many challenges for logistic companies, especially for heavy duty vehicles. |
| + | With professional device lineup like FMC650 – Tell Tale information (dashboard lights) can be read remotely indicating various issues with heavy duty vehicles. |
| + | New feature of Diagnostic Trouble Code (DTC) reading will help to narrow down the specific faults happening in vehicles – receive DTC information remotely. |
| + | |
| + | With FMC650/FMM650/FMB641 you can read 2 types of DTC messages based on J1939 protocol: |
| + | DM1 – Active codes |
| + | DM2 – Previously Active codes |
| + | |
| + | FMC650/FMM650 is able to read DM codes and pass them to the server in IO element. When active DM1 or DM2 messages appear on CAN line it is broadcasted very often – FMC650 device save the codes into internal memory and does not spam the server with irrelevant information – only new DTC codes are sent to the server. |
| + | |
| + | |
| + | '''ACTIVE DIAGNOSTIC TROUBLE CODES (DM1)''' |
| + | * Memory array of 100 elements (4B each) is reserved for DM1 group messages. Memory will be cleared when device will reset or after Ignition OFF. |
| + | * When record is saved with previously active DTC code, this code is saved in device memory. |
| + | * Only active DTC Code not present in device memory will be saved as record (for each unique code separate record will be created if FMS IO element “Active DTC error Codes” is enabled). |
| + | * If memory array is full, oldest code will be overwritten with the new DTC code detected |
| + | |
| + | |
| + | '''PREVIOUSLY ACTIVE DIAGNOSTIC TROUBLE CODES (DM2)''' |
| + | * Memory array of 100 elements (4B each) is reserved for DM2 group messages. Memory will be cleared when device will reset or after Ignition OFF. |
| + | * When record is saved with previously active DTC code, this code is saved in device memory. |
| + | * Only previously active DTC Code not present in device memory will be saved as record If memory array is full, oldest code will be overwritten with the new DTC code detected |
| + | * If memory array is full, oldest code will be overwritten with the new DTC code detected |
| + | |
| + | |
| + | '''Functioning of DM1 and DM2 happens simultaneously''' |
| + | |
| + | Active Diagnostic Trouble Codes DM1 Group: |
| + | {| class="wikitable" |
| + | |+ |
| + | ! style="width: 150px; background: black; color: white;" | Description |
| + | ! style="width: 175px; background: black; color: white;" | Values |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | PGN |
| + | | style="text-align: left; vertical-align: top;" | 65226 (0xFECA) |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | Data Bytes |
| + | | style="text-align: left; vertical-align: top;" | 03 FF 00 00 00 00 FF FF |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | lampMalfunctionIndicatorStatus_1213 |
| + | | style="text-align: left; vertical-align: top;" | 0 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | lampRedStopStatus_623 |
| + | | style="text-align: left; vertical-align: top;" | 0 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | lampAmberWarningStatus_624 |
| + | | style="text-align: left; vertical-align: top;" | 0 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | lampProtectStatus_987 |
| + | | style="text-align: left; vertical-align: top;" | 3 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | flashMalfunctionIndicator_3038 |
| + | | style="text-align: left; vertical-align: top;" | 3 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | flashRedStop_3039 |
| + | | style="text-align: left; vertical-align: top;" | 3 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | flashAmberWarning_3040 |
| + | | style="text-align: left; vertical-align: top;" | 3 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | flashProtect_3041 |
| + | | style="text-align: left; vertical-align: top;" | 3 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | DTC |
| + | | style="text-align: left; vertical-align: top;" | 0 |
| + | |} |
| + | |
| + | Active Diagnostic Trouble Codes DM2 Group: |
| + | {| class="wikitable" |
| + | |+ |
| + | ! style="width: 150px; background: black; color: white;" | Description |
| + | ! style="width: 175px; background: black; color: white;" | Values |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | PGN |
| + | | style="text-align: left; vertical-align: top;" | 65226 (0xFECA) |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | Data Bytes |
| + | | style="text-align: left; vertical-align: top;" | 00 FF 6F F2 E4 01 FF FF |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | lampMalfunctionIndicatorStatus_1213 |
| + | | style="text-align: left; vertical-align: top;" | 0 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | lampRedStopStatus_623 |
| + | | style="text-align: left; vertical-align: top;" | 0 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | lampAmberWarningStatus_624 |
| + | | style="text-align: left; vertical-align: top;" | 0 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | lampProtectStatus_987 |
| + | | style="text-align: left; vertical-align: top;" | 0 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | flashMalfunctionIndicator_3038 |
| + | | style="text-align: left; vertical-align: top;" | 3 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | flashRedStop_3039 |
| + | | style="text-align: left; vertical-align: top;" | 3 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | flashAmberWarning_3040 |
| + | | style="text-align: left; vertical-align: top;" | 3 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | flashProtect_3041 |
| + | | style="text-align: left; vertical-align: top;" | 3 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | DTC |
| + | | style="text-align: left; vertical-align: top;" | 0 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | SPN |
| + | | style="text-align: left; vertical-align: top;" | 0 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | FMI |
| + | | style="text-align: left; vertical-align: top;" | 4 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | OC |
| + | | style="text-align: left; vertical-align: top;" | 1 |
| + | |- |
| + | ! style="text-align: left; vertical-align: top;" | CM |
| + | | style="text-align: left; vertical-align: top;" | 0 |
| + | |} |
| + | |
| + | ==EV FMS== |
| + | |
| + | Heavy duty logistics vehicle manufacturers are swiftly moving towards a more sustainable logistic supply chain by providing electric heavy duty trucks. |
| + | Most of the main manufacturers are already offering electric versions of their most successful traditional truck lineup. |
| + | |
| + | This change opens up new possibilities and new challenges for telematics companies. |
| + | |
| + | Fortunately, the market remains in agreement for standardized telematics communication protocol – [https://wiki.teltonika-gps.com/view/FMC650_LVCAN_I/O,FMS_IO_and_Tachograph_data_elements#FMS FMS Standard]. |
| + | |
| + | This standard implies same communication protocol and same [https://teltonika-gps.com/products/accessories/data-cables/fms-cable connection practices]. |
| + | |
| + | Relative information about AVL IDs can be found in this [https://wiki.teltonika-gps.com/view/FMB641_Teltonika_Data_Sending_Parameters_ID link]. |
| + | |
| + | The protocol is expanded to support electric vehicle information which can be read with FMC650/FMM650: |
| + | Battery voltage/temperature, coolant information and many new electric FMS related information can be found in new tab “EV FMS IO”: |
| + | |
| + | [[File:FMC650 EV FMS1.gif]] |
| | | |
| ==Tachograph Data== | | ==Tachograph Data== |
Line 316: |
Line 459: |
| | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" |Driver2 current daily driving time | | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" |Driver2 current daily driving time |
| | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - | | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - |
− | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | +
| |
| | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - | | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - |
− | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | + | + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - |
| | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - | | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - |
| |- | | |- |
Line 330: |
Line 473: |
| | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" |Driver2 current weekly driving time | | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" |Driver2 current weekly driving time |
| | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - | | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - |
− | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | +
| |
| | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - | | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - |
− | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | + | + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - |
| | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - | | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | - |
| |- | | |- |