This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Serial 2.3.3 crashes
#1
Hello,

HW: RPi4 2G, external powered usb-hub, usb-gps BU353s4, usb-serial converter XS885/USConverters
SW: OP2, Serial 2.3.3

Problem: connecting XS885 in the hub, Serial 2.3.3 shows previously green marked device 353s4 red, XS885 not to be found.

The setup with the same cables has been working ok with RPi3/OP1, and still is, just tested it.

When XS885 is connected, and Serial shows red upon 353s4:

The BU353 keeps on running ok, SignalK and openCPN are receiving fixes and time.
Via terminal ttyUSB0 =BU353s4 and ttyUSB1 =XS885 are identified correctly.
Echoing via terminal makes the XS885 Tx-led blink momentarily (echo "Hello world" > /dev/ttyUSB1).
Catting via terminal prints fixes from BU353s4 (cat /dev/ttyUSB0).

Seems to me the system runs ok but the Serial-app crashes ?
No help from restart, only restart without the XS885 brings back 353s4 as green in the Serial 2.3.3

Any ideas ?

Debug file is attached (really do not know if I generated it properly)

.txt   debug.txt (Size: 1.31 KB / Downloads: 20)

wbr,
tjm
Reply
#2
how are the devices remembered? by device data or by port position?

maybe both devices have the same device data, try switching one of them to "remember port"
Reply
#3
(2022-04-24, 06:49 PM)Sailoog Wrote: how are the devices remembered? by device data or by port position?

maybe both devices have the same device data, try switching one of them to "remember port"

Devices are remembered by "vendor/product/serial".
Changing that to "port", does not help.

Anyway the "vendor/product/serial"-data is different between bu354 and xs885, I have seen the data in my older setup RPi3/OP1, have a photo of that data somewhere...

New observation: command "lsusb" lists about 8 rows of data, after plugging xs885 it lists only one row "Linux Foundation 2.0 root hub"
Reply
#4
could you post the lsusb output before and after connecting the device?
Reply
#5
(2022-04-26, 07:23 PM)Sailoog Wrote: could you post the lsusb output before and after connecting the device?


The Serial-app is version 2.2.3, sorry about the typo.

Two attachments:
First is "lsusb"-listing before and after connecting xs885
The second is extraction from Settings2.9.1 /System log / See all after connecting xs885.

   

.txt   rs422.txt (Size: 1.65 KB / Downloads: 18)
Reply
#6
that matches the openplotter-serial app behavior marking in red the rest of devices as missing.

It seems that this killer device is not working right. Maybe it is requiring more power than your powered hub can serve. Maybe it is defective... try connecting only this device directly to the raspberry.
Reply
#7
(2022-04-27, 07:49 PM)Sailoog Wrote: that matches the openplotter-serial app behavior marking in red the rest of devices as missing.

It seems that this killer device is not working right. Maybe it is requiring  more power than your powered hub can serve. Maybe it is defective... try connecting only this device directly to the raspberry.



Ok, thanks for your effort Sailoog.

tjm
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)