You must also do:- sudo apt remove gpsd-clients
- sudo apt purge gpsd-clients
You installed those, also, and they are included in the normal gpsd source/tarball.
You Linux OS vendor chose to break gpsd up into “gpsd” & “gpsd-clients”.
The gpsd project includes both, not broken out separately.
Thanks, Frank
On Jul 23, 2021, at 5:02 PM, Aranza Shaccid Leon < leon18@pnw.edu> wrote:
Hello and good afternoon!
Here is the lsusb -v information: pi@clover-1060:~ $ lsusb -v
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice 5.10 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x001f bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 bMaxBurst 0
Bus 001 Device 004: ID 26ac:0012 Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x26ac idProduct 0x0012 bcdDevice 1.01 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x003e bNumInterfaces 2 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 2 Communications bInterfaceSubClass 2 Abstract (modem) bInterfaceProtocol 1 AT-commands (v.25ter) iInterface 0 CDC Header: bcdCDC 1.10 CDC ACM: bmCapabilities 0x06 sends break line coding and serial state CDC Call Management: bmCapabilities 0x03 call management use DataInterface bDataInterface 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 10 CDC Data bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1
Bus 001 Device 003: ID 1546:01a8 U-Blox AG [u-blox 8] Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x1546 U-Blox AG idProduct 0x01a8 [u-blox 8] bcdDevice 3.01 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x003e bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 2 Communications bInterfaceSubClass 2 Abstract (modem) bInterfaceProtocol 1 AT-commands (v.25ter) iInterface 0 CDC Header: bcdCDC 1.10 CDC ACM: bmCapabilities 0x02 line coding and serial state CDC Call Management: bmCapabilities 0x03 call management use DataInterface bDataInterface 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 255 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 10 CDC Data bInterfaceSubClass 0 bInterfaceProtocol 255 Vendor specific iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 1 Single TT bMaxPacketSize0 64 idVendor 0x2109 VIA Labs, Inc. idProduct 0x3431 Hub bcdDevice 4.21 iManufacturer 0 iProduct 1 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 1 Single TT bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 5.10 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12
I initially ran the command sudo apt-get install gpsd gpsd-clients which installed the 3.17 gpsd version as a different link recommended.
To get gpspipe to work, would I have to update my gpsd version? If yes, what is the simplest method to do so (is it using tarbell or wget) and would I have to remove my previous gpsd version?
The commands were: - sudo apt remove gpsd
- sudo apt purge gpsd
- sudo rm /local/bin/*gps*
- sudo apt-get update
- sudo apt-get dist-upgrade
- sudo reboot
May I ask why I need these programs installed as well? - sudo apt-get install scons libncurses-dev python-dev pps-tools
- sudo apt-get install git-core
- sudo apt-get install build-essential manpages-dev pkg-config
If no, how should I update gpspipe?
Since I currently have my GPS still attached to the Raspberry Pi via USB, may I ask if all these details being gathered are to help identify the GPS once I've attached to the flight controller instead and set a connection path to it then?
Thank you for your time and consideration.
Sincerely, Leon
CAUTION: This email originated from outside of the PNW environment. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Systemd(oing too much) seems to grab port 2947 on Raspbian and I haven’t worked out the necessary incantation to stop it doing so.
> On 22 Jul 2021, at 21:20, Gary E. Miller <gem@rellim.com> wrote:
>
> Yo Aranza!
>
>> On Thu, 22 Jul 2021 15:00:24 -0700
>> Aranza Shaccid Leon <leon18@pnw.edu> wrote:
>>
>> I used udev rules in order to connect my GPS when I had it on a
>> separate USB connection (had to disconnect from the flight controller
>> for this to work though) and in the rules, I named it ttyGPS.
>
> That standard symlink name is "/dev/gps0". Yours works, just adds
> a bit of confusion.
>
>> The gpsdebuginfo above is with the gpsd socket/gpsd disabled and with
>> the GPS plugged into only the flight controller.
>
> Which, of course, is not the configuration you could not get to work
> and raised an issue about.
>
>> This is the gpsdebuginfo with the gpsd socket/gpsd enabled (is this
>> what you mean be get gpsd running?)
>
> No. I have always, firmly, railed aginst enabling gpsd under
> systemd(umb). Which is why you were instructed to turn it off, and did
> in fact urn it off.
>
>
>> and the GPS plugged into only the USB.
>
> I take that to mean NOT also plugged into the flight controller, so
> once again NOT the configuration you want and that we were trying to debug?
>
>> /usr/bin/lsof
>> + lsof -iTCP:2947 -s TCP:LISTEN
>> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
>> systemd 1 root 70u IPv6 16942 0t0 TCP localhost:gpsd (LISTEN)
>> systemd 1 root 75u IPv4 16944 0t0 TCP localhost:gpsd (LISTEN)
>> gpsd 735 gpsd 4u IPv6 16942 0t0 TCP localhost:gpsd (LISTEN)
>> gpsd 735 gpsd 5u IPv4 16944 0t0 TCP localhost:gpsd (LISTEN)
>
> That is very odd. Somehow systemd(roll) and gpsd both have port 2947 open?
> Which is why I don't do systemd(umber).
>
>> + lsof -c gpsd
>> + sed -nE 1p;/CHR|LISTEN/p
>> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
>> gpsd 735 gpsd 0u CHR 1,3 0t0 5 /dev/null
>> gpsd 735 gpsd 1u CHR 1,3 0t0 5 /dev/null
>> gpsd 735 gpsd 2u CHR 1,3 0t0 5 /dev/null
>> gpsd 735 gpsd 4u IPv6 16942 0t0 TCP localhost:gpsd (LISTEN)
>> gpsd 735 gpsd 5u IPv4 16944 0t0 TCP localhost:gpsd (LISTEN)
>> gpsdebugi 1005 root 0u CHR 136,0 0t0 3 /dev/pts/0
>
> Notice that gpsd is NOT conencted to your GPS. Your systemd(umber)
> config is broken. But I can't help you there since I do not do
> systemd(umbest).
>
>> + ps ax
>> + sed -nE 1p;/gpsd/p
>> PID TTY STAT TIME COMMAND
>> 735 ? S<s 0:00 /usr/sbin/gpsd /dev/ttyGPS
>
> You tried to get it to open /dev/ttyGPS, but it failed. See above.
>
> Since you used a non-standard name, the debug output is less helpful.
>
>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 001 Device 003: ID 26ac:0012
>
> You still did not answer my question on what 26ac:0012 is, it is
> not obeying the USB standard...
>
>> Bus 001 Device 004: ID 1546:01a8 U-Blox AG [u-blox 8]
>
> At least the u-blox is plugged in.
>
> But I can't help you when systemd(umpkopf) is controlling gpsd.
>
>
> RGDS
> GARY
> ---------------------------------------------------------------------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
> gem@rellim.com Tel:+1 541 382 8588
>
> Veritas liberabit vos. -- Quid est veritas?
> "If you can't measure it, you can't improve it." - Lord Kelvin
|