FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
1,147 views 4 comments
by anonymous

Hi,

My RUT955 is not reporting GPS position since a while ago (I think last 5 or 6 FW updates). Today I updated it again but GPS stills not working. Looks like the gpsd daemon crashes and don't run. Using gpsctl returns no info with any parameter. Here we can see the system log when I try to restart the gpsd daemon:

Wed Nov 27 12:28:50 2019 daemon.err gpsd: Failed to lookup "enabled" uci option
Wed Nov 27 12:28:50 2019 daemon.err gpsd: Invalid priority for AVL I/O rule
Wed Nov 27 12:28:50 2019 daemon.err gpsd: Failed to lookup "min" uci option
Wed Nov 27 12:28:50 2019 daemon.err gpsd: Failed to initialize I/O AVL rule
Wed Nov 27 12:28:50 2019 daemon.err gpsd: Failed to initialize AVL I/O rules
Wed Nov 27 12:28:50 2019 daemon.crit gpsd: Failed to initialize the AVL
Wed Nov 27 12:28:55 2019 daemon.err gpsd: Failed to lookup "enabled" uci option
Wed Nov 27 12:28:55 2019 daemon.err gpsd: Invalid priority for AVL I/O rule
Wed Nov 27 12:28:55 2019 daemon.err gpsd: Failed to lookup "min" uci option
Wed Nov 27 12:28:55 2019 daemon.err gpsd: Failed to initialize I/O AVL rule
Wed Nov 27 12:28:55 2019 daemon.err gpsd: Failed to initialize AVL I/O rules
Wed Nov 27 12:28:55 2019 daemon.crit gpsd: Failed to initialize the AVL
Wed Nov 27 12:29:00 2019 daemon.err gpsd: Failed to lookup "enabled" uci option
Wed Nov 27 12:29:00 2019 daemon.err gpsd: Invalid priority for AVL I/O rule
Wed Nov 27 12:29:00 2019 daemon.err gpsd: Failed to lookup "min" uci option
Wed Nov 27 12:29:00 2019 daemon.err gpsd: Failed to initialize I/O AVL rule
Wed Nov 27 12:29:00 2019 daemon.err gpsd: Failed to initialize AVL I/O rules
Wed Nov 27 12:29:00 2019 daemon.crit gpsd: Failed to initialize the AVL
Wed Nov 27 12:29:05 2019 daemon.err gpsd: Failed to lookup "enabled" uci option
Wed Nov 27 12:29:05 2019 daemon.err gpsd: Invalid priority for AVL I/O rule
Wed Nov 27 12:29:05 2019 daemon.err gpsd: Failed to lookup "min" uci option
Wed Nov 27 12:29:05 2019 daemon.err gpsd: Failed to initialize I/O AVL rule
Wed Nov 27 12:29:05 2019 daemon.err gpsd: Failed to initialize AVL I/O rules
Wed Nov 27 12:29:05 2019 daemon.crit gpsd: Failed to initialize the AVL
Wed Nov 27 12:29:10 2019 daemon.err gpsd: Failed to lookup "enabled" uci option
Wed Nov 27 12:29:10 2019 daemon.err gpsd: Invalid priority for AVL I/O rule
Wed Nov 27 12:29:10 2019 daemon.err gpsd: Failed to lookup "min" uci option
Wed Nov 27 12:29:10 2019 daemon.err gpsd: Failed to initialize I/O AVL rule
Wed Nov 27 12:29:10 2019 daemon.err gpsd: Failed to initialize AVL I/O rules
Wed Nov 27 12:29:10 2019 daemon.crit gpsd: Failed to initialize the AVL
Wed Nov 27 12:29:15 2019 daemon.err gpsd: Failed to lookup "enabled" uci option
Wed Nov 27 12:29:15 2019 daemon.err gpsd: Invalid priority for AVL I/O rule
Wed Nov 27 12:29:15 2019 daemon.err gpsd: Failed to lookup "min" uci option
Wed Nov 27 12:29:15 2019 daemon.err gpsd: Failed to initialize I/O AVL rule
Wed Nov 27 12:29:15 2019 daemon.err gpsd: Failed to initialize AVL I/O rules
Wed Nov 27 12:29:15 2019 daemon.crit gpsd: Failed to initialize the AVL
Wed Nov 27 12:29:15 2019 daemon.info procd: Instance gpsd::gpsd s in a crash loop 6 crashes, 0 seconds since last crash

Any clue about how to fix it or, at least, troubleshot it?

Thank you in advance.

Best regards

Aurelio

by anonymous
After another year I think I will give up and buy another GPS tracker. I tried almost everything: Installing new firmwares, reseting to factory...

After reseting to factory, it works a few days and then stop working again. I can't restart to factory every month. It's too unreliable for a production application.

If anyone have any idea to troubleshot this... Or someone from Teltonika wants to investigate... I am available to collect logs or anything.

Best regards

Aurelio

1 Answer

+1 vote
by anonymous

Hi,

This looks like a known issue which is in progress of being solved. There's a test firmware available with a fix. You can try testing it if you wish.

It's not an official release, it's just a firmware with the GPS fix implemented. So, I recommend only using it for tests and upgrade to the newest release when it becomes available. In any case, I will await your feedback.

by anonymous
Good news then. After almost a year seems to be fixed now. I'll try it in a couple of weeks as I will be in a trip with that vehicle for about 10 days and I don't want to risk Internet connection.

As soon as I install it I'll tell you if it's working.

Do you know when will be out an official firmware with the fix?

Thank you for your help.
by anonymous

I tested this version but it doesn't seem to fix the problem(DEVICE REPORTS READINESS TO READ BUT RETURNED NO DATA) when i run a python script to listen on /dev/ttyUSB1. I still restart the GPS to make it works, even after this when i make cat /dev/ttyUSB1 it turns a couple of secondes and stops.

https://community.teltonika-networks.com/11879/gps-device-reports-readiness-to-read-but-returned-no-data

by anonymous

Hello,

I have a similar issue with a RUTX11 gpsd process, the firmware version is RUTX_R_00.02.01.1:

[Error    ] Failed to lookup "enabled" uci option

[Crit     ] Failed to initialize NMEA collecting

The device itself is fine, cat /dev/ttyUSB1 returns NMEA data.

This is hard to debug as gpsd doesn't say witch option/section is missing. And without symbols gdb is blind.

Oops: found it, the SDK contains a working gps.conf and a non-stripped gpsd, enough to get it running.