AVL05

loloski7 years ago

Hi Everyone,

Good day i'm fairly new to traccar, I've seen in the documentation that traccar support AVL05 which is a totem based protocol, so what I did is I point the tracker to public_ip_server:5007 I could see that the tracker could send data to traccar but it won't save the DB? does traccar support acknowledgement ? because i believed traccar can't send the acknowledgement, thanks!

2015-08-20 12:08:52 DEBUG: [979982CB: 5007 < x.x.x.x] HEX: 242442453836333737313032343339323131327c4141244750524d432c3034343730342e3030302c412c313433392e333333342c4e2c31323035392e313431372c452c302e30302c302e30302c3230030303831352c2c2c412a36377c30312e377c30302e387c30312e347c3030303030303030303030307c32303135303832303034343730347c31343239313236357c30303030303030307c344545434246384233317c303030307c302e303030307c303030327c30303030307c3536453a32

2015-08-20 12:10:52 DEBUG: [979982CB: 5007 < x.x.x.x] HEX: 242442453836333737313032343339323131327c4141244750524d432c3034343730342e3030302c412c313433392e333333342c4e2c31323035392e313431372c452c302e30302c302e30302c3230030303831352c2c2c412a36377c30312e377c30302e387c30312e347c3030303030303030303030307c32303135303832303034343730347c31343239313236357c30303030303030307c344545434246384233317c303030307c302e303030307c303030327c30303030307c3536453a32

2015-08-20 12:12:56 DEBUG: [979982CB: 5007 < x.x.x.x] HEX: 242442453836333737313032343339323131327c4141244750524d432c3034343730342e3030302c412c313433392e333333342c4e2c31323035392e313431372c452c302e30302c302e30302c3230030303831352c2c2c412a36377c30312e377c30302e387c30312e347c3030303030303030303030307c32303135303832303034343730347c31343239313236357c30303030303030307c344545434246384233317c303030307c302e303030307c303030327c30303030307c3536453a32
loloski7 years ago

To follow up this post, does somebody know what's the acknowledgement string that traccar send to the device, based on the documentation it should be the CRC16 Modbus checksum right minus 4 bytes?

$$BExxxxxxxxxxxxxx|AA$GPRMC,044704.000,A,1439.3334,N,12059.1417,E,0.00,0.00,200815,,,A*67|01.7|00.8|01.4|000000000000|20150820044704|14291265|00000000|4EECBF8B31|0000|0.0000|0002|00000|
Anton Tananaev7 years ago

It looks like Totem protocol, but I think messages are corrupted because they can't be converted to text.

loloski7 years ago

Hi Anton,

I deliberately put some error in HEX, because there are some sensitive data on that sorry but I just want to say I think it's either the device doesn't acknowledge the traccar acknowledgement.

I believed this device has a custom firmware on it it's not a standard AVL05 so to speak, In any case could you please confirm one thing for me, your insight is pretty much appreciated.

What's the device String in byte array you send to the device as an acknowledgement based on your code base?

I believed the string should be looked like CRC16 MOdbus (Checksum) e.g or do I get it wrong based on the specs?

0xDB25 + "\r\n"

Thanks

loloski7 years ago

Hi Anton,

To answer your question this is the string should look like I just sanitise some text IMEI and the CRC16 Modbus Checksum, by the way could you please merge my other post on this I'm really sorry for messing up :(

$$BExxxxxxxxxxxxxx|AA$GPRMC,044704.000,A,1439.3334,N,12059.1417,E,0.00,0.00,200815,,,A*67|01.7|00.8|01.4|000000000000|20150820044704|14291265|00000000|4EECBF8B31|0000|0.0000|0002|00000|
Anton Tananaev7 years ago

Can you please send me original HEX message to email. Address is at the bottom of the page (letter icon).

loloski7 years ago

Hi Anton,

Done send it on your gmail account, thanks a lot for the help

Anton Tananaev7 years ago

Message was slightly different from what server expected. I have fixed the problem. Let me know if you want me to provide a new build for testing.

loloski7 years ago

Hi Anton,

Please close this issue now, I can concur that this change fix the issue, please let the ack function intact because I believed it won't hurt the other avl05/totem variant without their ack function being enabled, many thanks!!