Question

Hi, when I bought the RUTX12 some time ago I could set up all the key functionalities needed. After a problem I had to reset to factory setting. In doing so I applied the latest firmware. Since then my GPS services stopped working. With various firmware updates the error messages changed but still not working. 

These are the error messages I have right now in the log files with firmware RUTX_R_00.02.06. GPS is of course enabled but just showing position N/A. One thing that never worked, even while the GPS service worked, was showing the map. But I don‘t care about that as long as it generates the coordinates. 

daemon.info procd: Instance gpsd::gpsd s in a crash loop 6 crashes, 5 seconds since last crash

daemon.err uhttpd[4064]: /usr/lib/lua/luci/controller/gps.lua:80: attempt to concatenate field '?' (a nil value)

daemon.err uhttpd[4064]: stack traceback:

daemon.err uhttpd[4064]:  /usr/lib/lua/luci/controller/gps.lua:80: in function </usr/lib/lua/luci/controller/gps.lua:74>

Thanks for your help.

Regards,

Michael

Answer 1

Hello,

It seems that something wrong happened while you were resetting your router to the factory default configuration and that results in messed up GPS or other services. I suggest reflashing the firmware to the latest via the bootloader menu. Please follow these instructions: https://wiki.teltonika-networks.com/view/RUTXxx_Firmware_via_The_Bootloader_Menu

Regards.

Comments

Thanks! Will give it a go and let you know if it helped. :-)

---

I tried what you suggested. Got though the procedure until it says installing update. It‘s not showing the screen but the browser tap says „installing firmware“. However, nothing happens. Router does not reboot. Tried it a couple of times, same result. Any additional advise?

Did a reboot and it works as before. Setup is still correct, most tings work, except GPS.

Many thanks for additional advise.

---

Hello,

I think I had an issue similar to yours with an older firmware, as a workaround I ended up with a "minimal" config:

 - no NMEA support,

 - nothing NMEA related (forwarding, cache ...)

 - no HTTP server, TAVL, AVL AVLIO geofencing...

This is good enough for me as I use it to have the coordinates and to be sure to have a backup time synchronization.

I can send you my config file if you need.

Regards,

---

Thanks, I have exactly the same situation. Tested without any NMEA and all the other ones you‘ve mentioned. Then it works. Pretty much pointless, however, as my use case is to use a HTTP server to track and record the location.

Reflashed the firmware with the latest version. No change in error messages when I active any of the services mentioned above. Only activating GPS without any other services works.

---

Looks like it works in version 02.06.1 with NMEA forwarding enabled and http enabled. I can see the incoming packets on the remote server:

12:03:30.073271 IP (tos 0x0, ttl 64, id 5695, offset 0, flags [DF], proto UDP (17), length 82)
    192.168.8.1.35039 > 192.168.8.199.8500: isakmp 3.1 msgid 32342c32:
	0x0000:  4500 0052 163f 4000 4011 9243 c0a8 0801
	0x0010:  c0a8 08c7 88df 2134 003e c024 2447 5047
	0x0020:  5341 2c41 2c32 2c30 322c 3130 2c31 322c
	0x0030:  3234 2c32 352c 3239 2c33 322c 2c2c 2c2c
	0x0040:  2c31 2e34 2c31 2e31 2c30 2e38 2a33 350d
	0x0050:  0a00

Regards,

---

Thanks, good to know that it works for you. It still does not work with my device. Flashed the firmware with exactly this version. Only changed the mobile network and WIFI configuration and switched on GPS. In the Map view it then shows the correct coordinates although it does not show the map, which doesn‘t matter. 

If I switch on https (only, nothing else) it stops working.  The log continues to show these error messages. 

Sun Mar 21 06:27:31 2021 daemon.err uhttpd[4146]: /usr/lib/lua/luci/controller/gps.lua:80: attempt to concatenate field '?' (a nil value)

Sun Mar 21 06:27:31 2021 daemon.err uhttpd[4146]: stack traceback:

Sun Mar 21 06:27:31 2021 daemon.err uhttpd[4146]:  /usr/lib/lua/luci/controller/gps.lua:80: in function </usr/lib/lua/luci/controller/gps.lua:74>

---

What is the output of "gpsctl -seix" on your device ?

---

Will check tomorrow when I have again access to it and let you know.

---

OK, I tried it out. When https is disabled it provides the current position. If I enable it it can‘t get any location and comes back with the error shown below. So there is clearly a connection between switching on https and the ability of the gps service to create a location.

---

That's an ubus/http issue not a GPS one per se. Are you sure the http(s) server at the other end is working properly ?

---

I‘m using a paid service (gps-server.net). I‘ve validated the address and port number with them to confirm they are correct. It also has worked in the past.

However, I will try out other services to validate that this is not causing the problem.

---

OK, I found a workaround that gives me what I need. Prior to all these problems I used the https service to upload the GPS coordinates to the server. For whatever reason this does not work anymore and causes the gps service to malfunction. Tried out other gps server solutions same result.

Today I now tried to use the AVL service. Same URLs and port configuration and now it works. Never used the AVL setup before but now it works. Something seems to have changed. In any case, it now works again as it should.

Many thanks for the support provided that helped me stepping through this.

Michael

---

Good to know it works this way. Maybe the issue with https is due to something unexpected/missing in certificate of the server ?

Regards,

---

Maybe, I don't know. All I know it used to work and now it does not anymore. Luckily the other one works. ;-)

---

I've had the same experience and this IS a known issue. And it's still not fixed! In the end I stopped using the Teltonika services via the UI and wrote my own data aggregation script. It's much more stable and uses much less resources than the builtin services.

---

Good to know that I‘m not the only one with those issues. After I made a lot changes including the ones outlined above it works. Let‘s keep fingers crossed … ;-)