So what HEX messages can you show from the log for this device ?
This is not the standard Teltonika protocol, so this won't work on port 5027. You have to ask them for the protocol documentation.
Thanks both
Track-trace - I am cautious about showing potentially personally identifiable data in a public forum , but I acknowledge it may be the
only way to obtain debug. I am however, intrigued by Anton's comment which points back to a Teltonika issue..
Anton - So If I understand you correctly, the NMEA-0183 formatted data captured above in my wireshark traces is not the correct data structure for port 5027 is that correct ?
In which case the problem is clearly with the Teltonika router sending the wrong message string formats which needs to be addressed by teltonika themselves . I will raise it with them over on their forum, and see what they have to say .
Many thanks again guys
regards
BB
Correct, it's not correct :)
It will either have to be addressed by Teltonika, or it's their new format, it would need to be implemented in Traccar.
Thanks Anton,
I have been looking into the situation deeper on the Teltonika side and now have a much more accurate picture of what happened.
No explanation (yet) however, and no resolution.
In summary (in case anyone else ever finds themselves in the same situation) :
I logged into the X11 router and turned off the NMEA service - it continued to send data. I reset the port and IP address
in the NMEA service and applied the config - it STILL sent data (verified in Wireshark on the traccar VM) so I rebooted the
X11. this stopped all data to the server.
With nothing coming out of the X11, I logged into the gui to check the status of the AVL service. it wasnt listed at all (?).
I logged into the router CLI (as root) and did a service status command
The AVL service showed as stopped.
I manually started it ( service avl start).
It did not activate.
I then set it to auto boot (service avl enable) and rebooted
this got the service to start , but no data is being forwarded on port 5027 still from the router.
I have put the matter into the hands of Teltonika and see what they have to say . but nevertheless it is
the router that is at fault !
is there a port that traccar can accept NMEA0183 messages please ? I looked through the devices list and didnt see it mentioned specifically
but I seem to remember having previously used traccar for AIS.
Regards
BB
T55 port should be able to accept NMEA, but your samples are not pure NMEA, so I'm not sure it's going to work.
Keep us posted if you receive a response from Teltonika.
Hi Guys,
Running a Teltonika RUT X11 into a self hosted traccar server on virtual debian12 build
The X11 has been off air for some months due to vehicle engine failure and I reconnected it on Sunday
I am using an OpenVPN connection to get to the server ruling out a connectivity issue and Wireshark
traces taken on the Traccar server VM confirm that:
Below is a snapshot of the data from wireshark at my traccar server:
I went to the length of reinstalling debian 12 from scratch (no pun intended!) and updated to the latest traccar
server build
Traccar is running , I have registered as a user and added my device with its correct IMEI (copy pasted) but it simply reports that I am offline
The fact that GPS data is arriving at the server, has the correct IMEI, and is recoverable as ASCII points to either:
A) Formatting of the data is wrong by Teltonika after a firmware upgrade, or
B) Traccar is no longer listening on 5027 (checked the devices page - still says 5027 for teltonika, or
C) Traccar isn't processing the data submitted to it on 5027 correctly
Any of the devs here able to advise from my message ASCII whether the issue is in the teltonika data formatting
or the processing by Traccar please ?
(yes I have given the server and device a reboot and yes I have waited for several hours to get the data through - overnight in fact)
Many thanks in advance
Regards
BB