Hello,
I am encountering an issue with decoding messages from a Teltonika FMC125 device configured to send data via GSM with satellite backup through an Iridium Edge modem. While messages sent over GSM are perfectly decoded and interpreted by Traccar, messages sent via Iridium are not processed or displayed correctly. Below is an example of a message received via Iridium:
2024-12-04 15:38:36 INFO: [T12345678] connected
2024-12-04 15:38:36 INFO: [T12345678: teltonika < 192.168.1.100] 01003e01001c5875a44833303030303030303030303030303000011100006750777b03000b020b9af51b6dab0000000602000e6750768b9387436f6c580000ffff
2024-12-04 15:38:36 INFO: [T12345678] disconnected
Configuration Details:
Device: Teltonika FMC125.
Backup Communication: Satellite via Iridium Edge.
IMEI (anonymized): 300000000000000.
IP Address (anonymized): 192.168.1.100.
Observations:
Messages sent via GSM are fully decoded and processed by Traccar.
Messages sent via Iridium establish a connection, but the data is not decoded or displayed in the platform.
Key differences in the Iridium message:
The Codec ID appears as 01, which might not align with the expected 0C (Codec8) or 08 (Codec8 Extended).
The Checksum value is 0000ffff, which may not be calculated correctly, potentially leading to rejection.
GPS and I/O data fields seem to be present but are not interpreted by Traccar.
Questions:
Is the Codec ID 01 valid for messages sent via the Iridium Edge? If not, how can this be corrected or configured for compatibility with Traccar?
Can the Checksum value be recalculated? How critical is this for Traccar to accept the message?
Does this message fully conform to the Teltonika AVL protocol for satellite communication, or are there specific adjustments needed for messages sent through Iridium?
Are there known limitations in Traccar or Teltonika devices when using Iridium as a backup communication channel?
Additional Notes:
The issue seems specific to messages sent over Iridium, as GSM messages are processed without issues.
Any guidance on validating and debugging messages sent through Iridium, or on tools to parse and validate the Teltonika protocol, would be greatly appreciated.
Thank you for your assistance!
Do you have the documentation for Teltonika Iridium protocol?
Have you tried T622 Iridium port?
Hello,
I am encountering an issue with decoding messages from a Teltonika FMC125 device configured to send data via GSM with satellite backup through an Iridium Edge modem. While messages sent over GSM are perfectly decoded and interpreted by Traccar, messages sent via Iridium are not processed or displayed correctly. Below is an example of a message received via Iridium:
Configuration Details:
Device: Teltonika FMC125.
Backup Communication: Satellite via Iridium Edge.
IMEI (anonymized): 300000000000000.
IP Address (anonymized): 192.168.1.100.
Observations:
Messages sent via GSM are fully decoded and processed by Traccar.
Messages sent via Iridium establish a connection, but the data is not decoded or displayed in the platform.
Key differences in the Iridium message:
The Codec ID appears as 01, which might not align with the expected 0C (Codec8) or 08 (Codec8 Extended).
The Checksum value is 0000ffff, which may not be calculated correctly, potentially leading to rejection.
GPS and I/O data fields seem to be present but are not interpreted by Traccar.
Questions:
Is the Codec ID 01 valid for messages sent via the Iridium Edge? If not, how can this be corrected or configured for compatibility with Traccar?
Can the Checksum value be recalculated? How critical is this for Traccar to accept the message?
Does this message fully conform to the Teltonika AVL protocol for satellite communication, or are there specific adjustments needed for messages sent through Iridium?
Are there known limitations in Traccar or Teltonika devices when using Iridium as a backup communication channel?
Additional Notes:
The issue seems specific to messages sent over Iridium, as GSM messages are processed without issues.
Any guidance on validating and debugging messages sent through Iridium, or on tools to parse and validate the Teltonika protocol, would be greatly appreciated.
Thank you for your assistance!