OpenMarine
Serial device not added correctly - Printable Version

+- OpenMarine (https://forum.openmarine.net)
+-- Forum: OpenPlotter (https://forum.openmarine.net/forumdisplay.php?fid=1)
+--- Forum: Bug Reports (https://forum.openmarine.net/forumdisplay.php?fid=4)
+--- Thread: Serial device not added correctly (/showthread.php?tid=4675)

Pages: 1 2 3 4 5 6 7 8

RE: Serial device not added correctly - kste - 2023-07-14

is plugged. otherwise how could it see the lsusb command?
It's connected through a hub though, I think that's the problem. but the same hub with openplotter 2 worked fine

RE: Serial device not added correctly - baltika_no_9 - 2023-07-14

(2023-07-14, 04:49 AM)kste Wrote: is plugged. otherwise how could it see the lsusb command?
It's connected through a hub though, I think that's the problem. but the same hub with openplotter 2 worked fine

You are correct, lsusb can see it. I missed that. It could be the hub but I don't see why, the OS can see the device so OP should do the same, strange!

If I start my system without the Ublox and I plug it in and then, immediately after, issue the command

Code:
tail -30 /var/log/syslog

I see the following:

Code:
Jul 14 11:28:49 bobby kernel: [  111.492366] usb 1-1.3: new full-speed USB device number 4 using xhci_hcd
Jul 14 11:28:49 bobby kernel: [  111.596800] usb 1-1.3: New USB device found, idVendor=1546, idProduct=01a7, bcdDevice= 1.00
Jul 14 11:28:49 bobby kernel: [  111.596838] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 14 11:28:49 bobby kernel: [  111.596855] usb 1-1.3: Product: u-blox 7 - GPS/GNSS Receiver
Jul 14 11:28:49 bobby kernel: [  111.596870] usb 1-1.3: Manufacturer: u-blox AG - www.u-blox.com
Jul 14 11:28:49 bobby mtp-probe: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3"
Jul 14 11:28:49 bobby mtp-probe: bus: 1, device: 4 was not an MTP device
Jul 14 11:28:49 bobby kernel: [  111.676731] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
Jul 14 11:28:49 bobby kernel: [  111.676961] usbcore: registered new interface driver cdc_acm
Jul 14 11:28:49 bobby kernel: [  111.676977] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Jul 14 11:28:49 bobby mtp-probe: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3"
Jul 14 11:28:49 bobby mtp-probe: bus: 1, device: 4 was not an MTP device
Jul 14 11:28:49 bobby systemd[1]: Created slice system-gpsdctl.slice.
Jul 14 11:28:49 bobby systemd[1]: Starting Manage ttyACM0 for GPS daemon...
Jul 14 11:28:49 bobby gpsdctl: gpsd_control(action=add, arg=/dev/ttyACM0)
Jul 14 11:28:49 bobby gpsdctl: reached a running gpsd
Jul 14 11:28:49 bobby systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 14 11:28:49 bobby systemd[1]: Started GPS (Global Positioning System) Daemon.
Jul 14 11:28:49 bobby systemd[1]: Finished Manage ttyACM0 for GPS daemon.

Do you get anything like that?

RE: Serial device not added correctly - kste - 2023-07-14

(2023-07-14, 11:31 AM)baltika_no_9 Wrote:
(2023-07-14, 04:49 AM)kste Wrote: is plugged. otherwise how could it see the lsusb command?
It's connected through a hub though, I think that's the problem. but the same hub with openplotter 2 worked fine

You are correct, lsusb can see it. I missed that. It could be the hub but I don't see why, the OS can see the device so OP should do the same, strange!

If I start my system without the Ublox and I plug it in and then, immediately after, issue the command

Code:
tail -30 /var/log/syslog

I see the following:

Code:
Jul 14 11:28:49 bobby kernel: [  111.492366] usb 1-1.3: new full-speed USB device number 4 using xhci_hcd
Jul 14 11:28:49 bobby kernel: [  111.596800] usb 1-1.3: New USB device found, idVendor=1546, idProduct=01a7, bcdDevice= 1.00
Jul 14 11:28:49 bobby kernel: [  111.596838] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 14 11:28:49 bobby kernel: [  111.596855] usb 1-1.3: Product: u-blox 7 - GPS/GNSS Receiver
Jul 14 11:28:49 bobby kernel: [  111.596870] usb 1-1.3: Manufacturer: u-blox AG - www.u-blox.com
Jul 14 11:28:49 bobby mtp-probe: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3"
Jul 14 11:28:49 bobby mtp-probe: bus: 1, device: 4 was not an MTP device
Jul 14 11:28:49 bobby kernel: [  111.676731] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
Jul 14 11:28:49 bobby kernel: [  111.676961] usbcore: registered new interface driver cdc_acm
Jul 14 11:28:49 bobby kernel: [  111.676977] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Jul 14 11:28:49 bobby mtp-probe: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3"
Jul 14 11:28:49 bobby mtp-probe: bus: 1, device: 4 was not an MTP device
Jul 14 11:28:49 bobby systemd[1]: Created slice system-gpsdctl.slice.
Jul 14 11:28:49 bobby systemd[1]: Starting Manage ttyACM0 for GPS daemon...
Jul 14 11:28:49 bobby gpsdctl: gpsd_control(action=add, arg=/dev/ttyACM0)
Jul 14 11:28:49 bobby gpsdctl: reached a running gpsd
Jul 14 11:28:49 bobby systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 14 11:28:49 bobby systemd[1]: Started GPS (Global Positioning System) Daemon.
Jul 14 11:28:49 bobby systemd[1]: Finished Manage ttyACM0 for GPS daemon.

Do you get anything like that?

Code:
~ $ tail -30 /var/log/syslog
Jul 14 22:42:14 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/self #033[33m404#033[0m 1.828 ms - 166#033[0m
Jul 14 22:42:14 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/ #033[32m200#033[0m 1.565 ms - 2#033[0m
Jul 14 22:42:14 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/atons/ #033[33m404#033[0m 1.525 ms - 160#033[0m
Jul 14 22:42:24 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/ #033[32m200#033[0m 2.563 ms - 2#033[0m
Jul 14 22:42:24 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/atons/ #033[33m404#033[0m 2.740 ms - 160#033[0m
Jul 14 22:42:26 etta2 kernel: [177079.438284] w1_master_driver w1_bus_master1: Attaching one wire slave 00.2e7000000000 crc 8a
Jul 14 22:42:26 etta2 kernel: [177079.443434] w1_master_driver w1_bus_master1: Family 0 for 00.2e7000000000.8a is not registered.
Jul 14 22:42:34 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/ #033[32m200#033[0m 2.502 ms - 2#033[0m
Jul 14 22:42:34 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/atons/ #033[33m404#033[0m 2.668 ms - 160#033[0m
Jul 14 22:42:44 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/self #033[33m404#033[0m 2.779 ms - 166#033[0m
Jul 14 22:42:44 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/ #033[32m200#033[0m 2.466 ms - 2#033[0m
Jul 14 22:42:44 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/atons/ #033[33m404#033[0m 2.982 ms - 160#033[0m
Jul 14 22:42:54 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/ #033[32m200#033[0m 2.557 ms - 2#033[0m
Jul 14 22:42:54 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/atons/ #033[33m404#033[0m 2.640 ms - 160#033[0m
Jul 14 22:43:04 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/ #033[32m200#033[0m 1.504 ms - 2#033[0m
Jul 14 22:43:04 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/atons/ #033[33m404#033[0m 1.532 ms - 160#033[0m
Jul 14 22:43:06 etta2 vncserver-x11[738,root]: Connections: connected: 241.88.165.28::54738 (TCP)
Jul 14 22:43:14 etta2 kernel: [177126.990841] w1_master_driver w1_bus_master1: Attaching one wire slave 00.ae7000000000 crc 06
Jul 14 22:43:14 etta2 kernel: [177126.996001] w1_master_driver w1_bus_master1: Family 0 for 00.ae7000000000.06 is not registered.
Jul 14 22:43:14 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/self #033[33m404#033[0m 2.085 ms - 166#033[0m
Jul 14 22:43:14 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/ #033[32m200#033[0m 1.997 ms - 2#033[0m
Jul 14 22:43:14 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/atons/ #033[33m404#033[0m 1.956 ms - 160#033[0m
Jul 14 22:43:14 etta2 vncserver-x11[738,root]: Connections: authenticated: 79.8.65.28::54738 (TCP), as pi (d permissions)
Jul 14 22:43:24 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/ #033[32m200#033[0m 2.113 ms - 2#033[0m
Jul 14 22:43:24 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/atons/ #033[33m404#033[0m 2.605 ms - 160#033[0m
Jul 14 22:43:34 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/ #033[32m200#033[0m 2.911 ms - 2#033[0m
Jul 14 22:43:34 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/atons/ #033[33m404#033[0m 5.645 ms - 160#033[0m
Jul 14 22:43:44 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/self #033[33m404#033[0m 2.731 ms - 166#033[0m
Jul 14 22:43:44 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/vessels/ #033[32m200#033[0m 2.550 ms - 2#033[0m
Jul 14 22:43:44 etta2 signalk-server[615]: #033[0mGET /signalk/v1/api/atons/ #033[33m404#033[0m 3.361 ms - 160#033[0m


RE: Serial device not added correctly - baltika_no_9 - 2023-07-15

OK your log is drowning in signalk messages, why not try again but with signal k stopped.

Start with the GPS unplugged

Code:
sudo systemctl stop signalk.service
sudo systemctl stop signalk.socket

Then plug the GPS and try these two concatenated commands:

Code:
tail -40 /var/log/syslog > log.txt && dmesg | tail -30 > dmesg.txt

You will have two files, log.txt and dmesg.txt, what do they say?

You can start signal k  by changing "stop" to "start" in the above commands.

RE: Serial device not added correctly - kste - 2023-07-15

I tried unplugging the usb hub and plugging the gps directly into the usb port, so it works!
So it seems that my hub is not compatible with openplotter 3

RE: Serial device not added correctly - baltika_no_9 - 2023-07-15

(2023-07-15, 12:43 PM)kste Wrote: I tried unplugging the usb hub and plugging the gps directly into the usb port, so it works!
So it seems that my hub is not compatible with openplotter 3

That's good news!

RE: Serial device not added correctly - kste - 2023-07-15

(2023-07-15, 12:45 PM)baltika_no_9 Wrote:
(2023-07-15, 12:43 PM)kste Wrote: I tried unplugging the usb hub and plugging the gps directly into the usb port, so it works!
So it seems that my hub is not compatible with openplotter 3

That's good news!

I did other tests, it's not the usb hub that creates problems but a device connected to the hub, it's the cable for the Victron battery monitor (Victron Energy VE.Direct).
If I connect the cable to the usb the openplootter serial module stops working.
Maybe I need to make a separate post as a bug? Or do I have to set something?
P.S. its not the bad cable, i have 2 of them and they both create the same problem.

RE: Serial device not added correctly - baltika_no_9 - 2023-07-16

That's an interesting problem and is probably worth raising as a separate issue.

RE: Serial device not added correctly - alicebell - 2024-06-01

Hey @baltika_no_9, I agree with you. It's the problem due to the latest version.

Visit this: https://answers.microsoft.com/en-us/windows/forum/all/issues-with-usb-to-serial-on-windows-10/72b7d5e8-865b-4fc4-bc48-e6a13eea2f7en-alteryx

RE: Serial device not added correctly - baltika_no_9 - 2024-06-01

(2024-06-01, 06:17 PM)alicebell Wrote: Hey @baltika_no_9, I agree with you. It's the problem due to the latest version.

Visit this: https://answers.microsoft.com/en-us/windows/forum/all/issues-with-usb-to-serial-on-windows-10/72b7d5e8-865b-4fc4-bc48-e6a13eea2f7en-alteryx

What utter nonsense. Latest release of what exactly? Nothing to do with Microsoft Windows.

Not a very bright BOT are you?