gpsd-users
[Top][All Lists]
Advanced

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

Re: [gpsd-users] How to use ubxtool with gpsd


From: John Klug
Subject: Re: [gpsd-users] How to use ubxtool with gpsd
Date: Thu, 1 Nov 2018 15:10:04 +0000

The pps is specified because we have two pps devices (and sometime six or more 
tty).

As far as -F is concerned on the gpsd command line, I see that it is meant to 
allow a change of the gps device.  So is it non-functional when the devices are 
specified on the command line?  I verified that the device is actually created. 
 I suppose it could be used in the remote case that somebody connects a GPS to 
another serial line.

Sorry I was mixed up on the gps device parameter for ubxtool.  I found that if 
I use the correct serial port, ubxtool does work:

ubxtool -p PMS 127.0.0.1:2947:/dev/ttyXRUSB2
  ...

UBX-CFG-PMS:
 version: 0 powerSetupValue: 2 period: 128 onTime: 0x10 reserved1[0 0]
   powerSetupValue: Full power
...

Thanks


From: gpsd-users <address@hidden> on behalf of Gary E. Miller <address@hidden>
Sent: Wednesday, October 31, 2018 5:59 PM
To: gpsd
Subject: Re: [gpsd-users] How to use ubxtool with gpsd
    
Yo John!

On Wed, 31 Oct 2018 22:40:39 +0000
John Klug <address@hidden> wrote:

> Here is my gpsd command line:
> 
>   /usr/sbin/gpsd -n -D 1 -F /var/run/gpsd.sock -P /var/run/gpsd.pid  
>       /dev/ttyXRUSB2 /dev/pps0

Why do you need to specify the /dev/pps0?  Why do you use gpsd.sock AND
the tty?

> gps0:/home/mtadm# ubxtool -p PMS                              
> ubxtool: poll PMS
> sent:
> UBX-CFG-PMS:
>  Poll request
> 
> {"class":"ERROR","message":"No path specified in DEVICE, but multiple
> devices are attached."}

Hmm, I guess is should default the first device, you have at least two.

New tool, still kinks to work out.

> gps0:/home/mtadm# ubxtool -p PMS 127.0.0.1:2947:/dev/ttyXRUSB0
> ubxtool: poll PMS
> sent:
> UBX-CFG-PMS:
>  Poll request
> 
> {"class":"ERROR","message":"No such device as /dev/ttyXRUSB0"}
> {"class":"ERROR","message":"Can't open /dev/ttyXRUSB0."}

Use gpspipe to see what devices you have.  Clearly not that one.
You have a ttyXRUSB0 and a ttyXRUSB2?  You use both above.

# gpspipe -w -n 20 | fgrep DEVICE
{"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttyACM0","driver":"u-blox","subtype":"SW
 ROM CORE 3.01 (107888),HW 00080000,FWVER=SPG 
3.01,PROTVER=18.00,GPS;GLO;GAL;BDS,SBAS;IMES;QZ","activated":"2018-10-31T22:59:32.047Z","flags":1,"native":1,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00,"mincycle":0.25}]}


RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin
    


reply via email to

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