gpsd-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gpsd-dev] ubxtool and remote gpsd


From: Ken McGuire
Subject: [gpsd-dev] ubxtool and remote gpsd
Date: Sun, 30 Jun 2019 11:52:26 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1

Hi Gary, et. al.

Just subscribed to this list, but I've been reading the archives for several months.

I have several test setups using u-blox F9P/T devices as well as some older M8Ns.

One is a datalogger running on an Orange Pi Zero with the F9P connected via USB. I'm using the latest gpsd 3.19~dev. I can run gpsd and connect to it locally with cgps as well as my own monitor code (based on cgps). Works fine. I can connect locally with ubxtool and it too works. I can also connect to it remotely with cgps and my monitor tool and both work as expected. However when I try connect remotely with ubxtool (ubxtool 192.168.0.134) I get the following error:

ubxtool: failed to connect to gpsd [Errno 111] Connection refused.

Both <nc -zv 192.168.0.134 2940-2950> and <nmap 192.168.0.134 -p 2947>  indicate that the port is open.

After a bit of poking and a few print statements in ubxtool and client.py I found that ubxtool is trying to connect to 127.0.0.1:2947 and not 192168.0.134:2947 even with <ubxtool 192.168.0.134> as the command line.

At about line 6626 in ubxtool I change:

                self.ser = gps.gpscommon(host=None)

to:

                self.ser = gps.gpscommon(host=opts['target']['server'])

Which seems to solve the problem.

I am not a programmer but a hardware guy, so my solution may be all wet.

Hopefully you can get this fix or a more correct/complete/better one.... in before the 3.19 release.

   ...ken...




reply via email to

[Prev in Thread] Current Thread [Next in Thread]