Serial device not added correctly

[kste]

Pi 4
Boot with USB SSD storage device
64 bit OS
Openplotter 3 all latest updates added (openplotter-serial 3.3.0)

if i start openplotter-serial in debug mode i get:

Code:

No module named 'openplotterSdrVhf.serialPorts'
No module named 'openplotterAvnav.serialPorts'
No module named 'openplotterNotifications.serialPorts'
No module named 'openplotterMaiana'
No module named 'openplotterIob'
No module named 'openplotterGpio.serialPorts'
No module named 'openplotterI2c.serialPorts'
inactive
No module named 'openplotterNetwork.serialPorts'
No module named 'openplotterDashboards.serialPorts'

lsusb command:

Code:

Bus 002 Device 002: ID 0781:558c SanDisk Corp. Extreme Portable SSD
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 005: ID 1546:01a7 U-Blox AG [u-blox 7]
Bus 001 Device 010: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 009: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 007: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 003: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

   

[baltika_no_9]

Edit - Ignore what follows, I had misunderstood the issue and my response is inappropriate.

What bug are you reporting exactly? Everything looks correct.

You just haven't set any up any serial ports. What are you expecting to see? Are you using a HAT (looks to me like you may be using a pican-m)?

[kste]

What bug are you reporting exactly? Everything looks correct.
You just haven't set any up any serial ports. What are you expecting to see? Are you using a HAT (looks to me like you may be using a pican-m)?

what should I do to set the serial ports (USB)? As the documentation says they are automatically detected:

[baltika_no_9]

What bug are you reporting exactly? Everything looks correct.
You just haven't set any up any serial ports. What are you expecting to see? Are you using a HAT (looks to me like you may be using a pican-m)?

what should I do to set the serial ports (USB)? As the documentation says they are automatically detected:

Edit:
Forgive me kste, I think I am misunderstanding your problem.

Let me try again. What are you expecting to see or happen in Openplotter?

[kste]

What bug are you reporting exactly? Everything looks correct.
You just haven't set any up any serial ports. What are you expecting to see? Are you using a HAT (looks to me like you may be using a pican-m)?

what should I do to set the serial ports (USB)? As the documentation says they are automatically detected:

Edit:
Forgive me kste, I think I am misunderstanding your problem.

Let me try again. What are you expecting to see or happen in Openplotter?

I expect the same thing to happen as with openplotter 2, i.e. if I insert the usb gps it appears in the list, otherwise how can I configure it?
Below if I start with op2 and enter the same gps that I have in op3
   

[baltika_no_9]

Ah I see!

You plug in your GPS into the OPv3 system and it does not appear in the Serial app is that correct? You plug it directly into a USB port on the pi I assume.

What do you see if you use the commands :

Code:

dmesg | grep ttyACM0   and   dmesg | grep blox

after you plug the GPS in? Assuming it is your u-blox GPS you're using

[kste]

Ah I see!

You plug in your GPS into the OPv3 system and it does not appear in the Serial app is that correct? You plug it directly into a USB port on the pi I assume.

What do you see if you use the commands :

Code:

dmesg | grep ttyACM0   and   dmesg | grep blox

after you plug the GPS in? Assuming it is your u-blox GPS you're using

it's two rpi4, the one with op3 is remote in the boat. if I type lsusb the gps sees it

Code:

~ $ sudo lsusb
Bus 002 Device 002: ID 0781:558c SanDisk Corp. Extreme Portable SSD
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 005: ID 1546:01a7 U-Blox AG [u-blox 7]
Bus 001 Device 010: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 009: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 007: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 003: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

but if I type dmsg it doesn't see it

Code:

~ $ dmesg | grep ttyACM0   and   dmesg | grep blox
grep: and: File o directory non esistente
grep: dmesg: File o directory non esistente

[baltika_no_9]

Ah I see!

You plug in your GPS into the OPv3 system and it does not appear in the Serial app is that correct? You plug it directly into a USB port on the pi I assume.

What do you see if you use the commands :

Code:

dmesg | grep ttyACM0   and   dmesg | grep blox

after you plug the GPS in? Assuming it is your u-blox GPS you're using

it's two rpi4, the one with op3 is remote in the boat. if I type lsusb the gps sees it

Code:

~ $ sudo lsusb
Bus 002 Device 002: ID 0781:558c SanDisk Corp. Extreme Portable SSD
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 005: ID 1546:01a7 U-Blox AG [u-blox 7]
Bus 001 Device 010: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 009: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 007: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 003: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

but if I type dmsg it doesn't see it

Code:

~ $ dmesg | grep ttyACM0   and   dmesg | grep blox
grep: and: File o directory non esistente
grep: dmesg: File o directory non esistente

I'm sorry, they are separate commands:

Code:

dmesg | grep ttyACM0

and

Code:

dmesg | grep blox

[kste]

Ah I see!

You plug in your GPS into the OPv3 system and it does not appear in the Serial app is that correct? You plug it directly into a USB port on the pi I assume.

What do you see if you use the commands :

Code:

dmesg | grep ttyACM0   and   dmesg | grep blox

after you plug the GPS in? Assuming it is your u-blox GPS you're using

it's two rpi4, the one with op3 is remote in the boat. if I type lsusb the gps sees it

Code:

~ $ sudo lsusb
Bus 002 Device 002: ID 0781:558c SanDisk Corp. Extreme Portable SSD
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 005: ID 1546:01a7 U-Blox AG [u-blox 7]
Bus 001 Device 010: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 009: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 007: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 003: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

but if I type dmsg it doesn't see it

Code:

~ $ dmesg | grep ttyACM0   and   dmesg | grep blox
grep: and: File o directory non esistente
grep: dmesg: File o directory non esistente

I'm sorry, they are separate commands:

Code:

dmesg | grep ttyACM0

and

Code:

dmesg | grep blox

Nothing
   

[baltika_no_9]

OK so the GPS is not plugged in then?

This is what I see when I plug mine in:

Code:

pi@cyclops:~ $ dmesg | grep blox
[ 5840.355630] usb 1-1.1: Product: u-blox 7 - GPS/GNSS Receiver
[ 5840.355636] usb 1-1.1: Manufacturer: u-blox AG - www.u-blox.com
pi@cyclops:~ $ dmesg | grep ACM0
[ 5840.407903] cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device
pi@cyclops:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 045e:0779 Microsoft Corp. LifeCam HD-3000
Bus 001 Device 003: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 005: ID 1546:01a7 U-Blox AG [u-blox 7]
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub