We have an urgent issue.
We use NMEA forwarding UDP which works perfect, but after a while it stops forwarding (we don’t receive messages).
When we use GPSCTL -ixv we see it is stuck on a location a few kilometers away. Even while driving GPCCTL return the same location. Turning the router off/on and the correct location is given.
What is the problem and how can we solve this?
It seems to happen when the mobile data is interrupted:
2026/05/26 13:34:46 NMEA: $GPRMC,133XX7.00,A,XX4.8XX6X4,N,00XX3.55XX24,E,23.9,15.4,2XX526,2.9,E,A,V*45
2026/05/26 13:34:58 Ping failed: dial tcp 8.8.8.8:53: i/o timeout
026/05/26 13:34:58 API error: Post “https://xxxxxxxx.net/api/xxxxx”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Then we do not receive NMEA data anymore, and the GEO location is stuck.
Greetings,
For troubleshooting purposes, we will require more sensitive information from your end, such as the troubleshoot file, which may contain passwords, public IP addresses, serial numbers, and such. To avoid leaking this information, we have sent you a form to fill out, which you will receive in your e-mail inbox that you have registered your account with in the forums. In the Ticket ID field of the form, please enter the ID of this thread, which is 19500.
Best Regards,
Justinas
As soon the mobile data gets interrupted (ping 8.8.8.8 fails) the GPS location is not updated.
GPSD says it is running, but the GEO location is frozen.
root@RUTC50:/usr/local/mnt/sda1# /etc/init.d/gpsd status
running
After a restart of gpsd de GEO location gets updated and we receive NMEA packets again.
root@RUTC50:/usr/local/mnt/sda1# /etc/init.d/gpsd restart
The problem is solved after a modem update described here:
https://community.teltonika.lt/t/known-issue-with-rg520nebd-modem-firmware-update-required/19360