VIN not showing for TOPFLYtech TorchX 110

Darkking 16 hours ago

I am using a TOPFLYtech TorchX 110 OBD-II tracker, which communicates via the t800x protocol on port 5047.

The tracker is successfully sending GPS and standard telemetry (Type 02 messages), but I've noticed an issue with how the VIN is handled. The device sends its diagnostic/OBD data using Message Type 09, but it alternates between two different packet structures. Because of these mixed payloads, the full VIN does not seem to parse or display correctly in the device state.

Here are the exact logs from my server showing the behavior:

  1. The Full VIN Packet (Length: 002f)
    When the device boots up or periodically, it sends a dedicated packet containing the full 17-character VIN:
2026-02-27 13:16:37  INFO: [Tc2438797: t800x < 110.225.88.56] 262609002f001a086728406271613126022707463155aa801441054d4248435a434233535045433339363135810d0a

Hex Segment: 4d 42 48 43 5a 43 42 33 53 50 45 43 33 39 36 31 35

ASCII Translation: MBHCZCB3SPEC39615 (The correct, full 17-character VIN)

  1. The Partial VIN / Diagnostic Packet (Length: 005b)
    Shortly after, the device sends a longer diagnostic packet that only contains the first 8 characters of the VIN, followed by a pipe | separator (7c):
2026-02-27 13:16:34  INFO: [Tc2438797: t800x < 110.225.88.56] 262609005b0019086728406271613126022707462855aa70404801410a7c333230377c334343467c010042010101007c06100b00007c000000107cffffffff7c00007c0100fe0042007c334d4248435a4342337c0000007c900d0a

Hex Segment: 4d 42 48 43 5a 43 42 33 7c

ASCII Translation: MBHCZCB3| (Missing the last 9 characters)

Could you please check the T800xProtocolDecoder to ensure it is correctly extracting the vin attribute from the 002f packet and show the VIN data.

Anton Tananaev 15 hours ago

Do you have the protocol documentation for your device?

Darkking 15 hours ago

Yes. I have

Darkking 15 hours ago

I have mailed you the documents.

Anton Tananaev 4 hours ago

From what I can tell, Traccar doesn't decode message type 0x09 is not decoded currently. Are you sure you're using the official Traccar?

Darkking 3 hours ago

Yes. I am using Traccar 6.11.1 currently. I have installed it from official Traccer Git.

Anton Tananaev 2 hours ago

Please provide full log session.

Darkking 2 hours ago

I will email you the full log from my server.

Darkking 2 hours ago

The log file from the server was too big to post here. I mailed you the log file. I am just putting partial log here.

2026-02-28 00:03:34  INFO: Event id: 867284062716131, time: 2026-02-28 00:01:17, type: deviceMoving, notifications: 0
2026-02-28 00:45:45  INFO: [Td305deae: t800x < 223.228.193.220] 262609005b002a086728406271613126022719154155aac0404801410b7c333230377c334343467c010042010101017c06100b00007c000000107c4223420c7c00007c0100fe0042007c334d4248435a4342337c0000007c0f0d0a
2026-02-28 00:45:45  INFO: [Td305deae: t800x > 223.228.193.220] 262609000f002a0867284062716131
2026-02-28 11:18:40  INFO: [T26e9dc37: t800x < 106.194.113.194] 262609005b002b086728406271613126022805483655aa50404801410a7c333230377c334343467c010042010101007c06100b00007c000000107cffffffff7c00007c0100fe0042007c334d4248435a4342337c0000007cb00d0a
2026-02-28 11:18:40  INFO: [T26e9dc37: t800x > 106.194.113.194] 262609000f002b0867284062716131
2026-02-28 11:18:43  INFO: [T26e9dc37: t800x < 106.194.113.194] 262609002f002c086728406271613126022805483855aa601441054d4248435a434233535045433339363135610d0a
2026-02-28 11:18:43  INFO: [T26e9dc37: t800x > 106.194.113.194] 262609000f002c0867284062716131
2026-02-28 11:20:39  INFO: Event id: 867284062716131, time: 2026-02-28 11:18:44, type: deviceMoving, notifications: 0
2026-02-28 11:53:16  INFO: [T15b547c3: t800x < 106.194.113.194] 262609005b002d086728406271613126022806231255aae0404801410b7c333230377c334343467c010042010101017c06100b00007c000000107c4223420c7c00007c0100fe0042007c334d4248435a4342337c0000007c2f0d0a
2026-02-28 11:53:16  INFO: [T15b547c3: t800x > 106.194.113.194] 262609000f002d0867284062716131