Page 2 of 2

Re: RevPi failed to get modem status

Posted: 23 Jun 2020, 09:27
by RMeissnerCC
Dear Lukas,
thank you for that link. I will apply it as soon as I am back on the device (hopefully tomorrow).

Here are the outputs you asked for:

pi@RevPi:/var/log $ lsusb
Bus 001 Device 008: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 004: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@RevPi:/var/log $ lsusb -tv
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
|__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 6, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M
|__ Port 3: Dev 7, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M
|__ Port 4: Dev 8, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M

Re: RevPi failed to get modem status

Posted: 23 Jun 2020, 10:20
by RMeissnerCC
Dear all,
I scanned a bit further through the logs and found this message:
"Jun 23 07:40:57 RevPi kernel: [57501.668550] piControl: dev 33: recv ioprotocol crc error 13000/13855955"
That one appears rather often. I do not comprehend yet from the source code what that means but it appears about every 50-70 minutes once. It happened once on June 21st, and then since yesterday when I changed the coherent_pool to 4M.
Best, Robert

Re: RevPi failed to get modem status

Posted: 23 Jun 2020, 10:42
by zhan
Hi RMeissnerCC,

from the kern.log and lsusb output you've provided, it can be seen that a 4-port usb hub has been used to connect all the usb-serial adapter.
And it seems that all the failures(which are indicated by error No.-110 as timeout error) are happened on that usb hub.
My sugesstion is, maybe you can do some check of reliability of the usb connections, e.g. connect the usb-serial adapter directly with device,
or change the usb hub or usb cable if necessary.

Re: RevPi failed to get modem status

Posted: 23 Jun 2020, 11:24
by RMeissnerCC
Hy Zhan,
I can tomorrow unplug the usb hub and connect one of the adapters to the RevPi directly.

We are using this usb hub right now: https://www.amazon.de/atolla-Netzteil-S ... 157&sr=8-9

Can you suggest a better alternative?

Regarding the cabling: I read in another forum post here, that some usb cables are better suited. I asked in that post which cables would be suitable. Could you suggest some?

Best, Robert

Re: RevPi failed to get modem status

Posted: 24 Jun 2020, 10:04
by zhan
Hi RMeissnerCC,

in the field environment, I always try to use a industrial level product, which normally might be with some enhancements in power supply, EMI, etc. e.g. https://revolution.kunbus.de/shop/de/in ... hub-4-port
However, concerning to this specific problem, it isn't yet quite sure that it's caused by the failure or Non-compliant of the usb hub.
So it is better to do something to check the failure point and then to consider the following issues.

Best regards
Simon

Re: RevPi failed to get modem status

Posted: 24 Jun 2020, 10:27
by RMeissnerCC
Hy zhan/Simon,
I agree. Thank you for pointing out your USB hub suggestion. I will forward that to our customer.

I would then connect just one of our USB devices directly to the RevPi Core and remove the external USB hub. Normally, it takes about 4 days until the problem shows up.

Best, Robert

Re: RevPi failed to get modem status

Posted: 08 Jul 2020, 08:36
by dirk
Hi Robert, how is it going? Is the issue now solved?

Re: RevPi failed to get modem status

Posted: 13 Jul 2020, 09:58
by RMeissnerCC
Dear all,
I apologize for the long wait, I was out of the office.
I am unsure whether the problem is resolved yet. I changed the cabling and the issue reappeared BUT the message of failed to get modem status appeared too, but is not correlated in time with the problem. It actually appears a few times in the log prior to the problem. I am unsure yet and have to look closer at the logs. I will post here again if I can say anything more.
Right now, I have the impression we did not change anything. It might be, that my connection between the two events was more imaginary and there is another issue below that :$
Best, Robert