RUT955 with $GPRMC no more running

G.S.3 years ago

After a pause of half a year I tried to connect the RUT955 (with new firmware 07.00 from Teltonika) to traccar, running on a Synology NAS via synology.me url.
It was working once with port 5027 (55027 on NAS), but now I find in the log:

2021-10-06 13:56:46 DEBUG: [b7603efc: 55027 < 178.26.155.202] HEX: 
244750524d432c3132333134322e30302c412c343832342e3836333536342c4e2c30313132382e3136313638342c452c302e302c302e302c3036313032312c302e342c452c412a33340d0a00

which is (checksum failure, because I changed my location, don't mind):

$GPRMC,123142.00,A,5224.863564,N,01228.161684,E,0.0,0.0,061021,0.4,E,A*34

which is a correct $GPRMC line, but on the display the status stays 'offline'.

I also tried port 5055 ((old?) traccar protocol, but the same result)

My question is: How and where do I know and find that the IMEI is correctly received and accepted by traccar, so that it is correlated with the display?
It was working once, so there is some manmade(?) error, perhaps....
Thanks

Anton Tananaev3 years ago

Looks like your device is not sending using Teltonika protocol, so it won't work on port 5027.

I suspect you misconfigured something on the device if it worked fine before.

G.S.3 years ago

Thanks for your answer. You are right: Misconfigured!

For all Teltonika-Devices the port is 5027 or 55027 on a synology NAS.
But that means, that NMEA-forwarding with $GPMRC is not the correct way, because, as I estimated, no IMEI is transferred.
So, the only way to get it done, is to enable AVL Server and NOT NMEA Server.
With AVL, the IMEI is also transferred and can be correlated to the traccar map.