ITS Protocol - Exception?

Hi,
Below is a sample message that is being sent via the ITS protocol. (I'm encoding this as HEX and sending the message. I have created the device in Traccar already). This message isn't getting parsed. The server doesn't show any error, which, in my opinion indicates that the message and protocol are correct.

NOTE: The placeholder for deviceid (XXXXXXX) is IMEI number in the standard ITS protocol. This device is sending its 7-digit serial number instead. The XXXXXXX in the message below is the serial number.

Any suggestions? Is the protocol correct?

I wasn't able to find anything on the forums ...

$$CLIENT_1NS,XXXXXXX,1,17.12345,79.123456789,2023-08-31 18:29:50.000,A,0,0,26411,0,15,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,15,0,0,0,0,0,0,0,0,0,0,0,0,0,2,15,193,0

Thank you for your help!

Logs?

By the way, no errors does not necessarily means that the message and the protocol are correct.

This is what I get in the logs

2023-10-16 19:33:09  INFO: Started Server@1aa5ea58{STARTING}[10.0.15,sto=0] @29588ms
2023-10-16 19:33:32  INFO: [T42cb01a8] connected
2023-10-16 19:33:32  INFO: [T42cb01a8: gps103 < 127.0.0.1] 2424434c49454e545f314e532c323438353039362c312c31342e34323334333636362c37352e39343033343030302c323032332d30382d33312031383a32393a35302e3030302c412c302c302c32363431312c302c31352c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c31352c302c302c302c302c302c302c302c302c302c302c302c302c302c322c31352c3139332c30
2023-10-16 19:33:32  INFO: [T42cb01a8] disconnected
2023-10-16 19:35:18  INFO: [T4118be8a] connected
2023-10-16 19:35:18  INFO: [T4118be8a: its < 127.0.0.1] 2424434c49454e545f314e532c323438353039362c312c31342e34323334333636362c37352e39343033343030302c323032332d30382d33312031383a32393a35302e3030302c412c302c302c32363431312c302c31352c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c31352c302c302c302c302c302c302c302c302c302c302c302c302c302c322c31352c3139332c30
2023-10-16 19:35:18  INFO: [T4118be8a] disconnected

I don't see the delimiter at the end of the message.

The delimiter doesn't seem to matter. I tried with and without the delimiter.

Here is the log with the delimiter.

2023-10-16 19:39:34  INFO: [T9ac21b45] connected
2023-10-16 19:39:34  INFO: [T9ac21b45: its < 127.0.0.1] 2424434c49454e545f314e532c323438353039362c312c31342e34323334333636362c37352e39343033343030302c323032332d30382d33312031383a32393a35302e3030302c412c302c302c32363431312c302c31352c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c302c31352c302c302c302c302c302c302c302c302c302c302c302c302c302c322c31352c3139332c302c2a
2023-10-16 19:39:35  INFO: [T9ac21b45] disconnected

Maybe there's something with the message format then.

Exactly my point. Do you / anyone know if this is a different protocol?

I don't think it's a different protocol. Probably just a variation of the same protocol that's not supported yet.

Ok thanks