ICC Rpi3B usb port(s) stopped working?

Sidewinder · July 8, 2019

Hi Rpi fans!

Over the last few weeks I have been struggling with a weird problem(s) on my pi 3B.

Can't remember the exact detail, but i suspect this started when I upgraded the OS. I did this in response to the default web browser not wanting to start, so i can view my other IP devices on my internal network. I installed Firefox and it is working 100%.

So symptoms are as follows: My BMV 702 with genuine VE.Direct to USB cable stopped reporting values etc to ICC. BMV itself is showing values.

ICC and the values from Inverters are still showing and recording as per normal.

So I swopped the position of the BMV usb cable to another port. Nothing.

Tested the BMV cable by plugging into PC with BMV Reader, and yes, the cable is sending data!

Unplugged the Inverter USB cable and plugged the BMV cable in it place. Nothing, Nada, Niks

Plugged the Inverter cable into the location where the BMV cable previously was...Sending data. All OK.

So with my limited linux knowledge, I suspect the FTDI drivers are not being loaded when the BMV cable is inserted.

I checked the message file and see the following:

pi@ICC-Solar:/var/lib $ dmesg | grep usb
[ 0.143131] usbcore: registered new interface driver usbfs
[ 0.143220] usbcore: registered new interface driver hub
[ 0.143319] usbcore: registered new device driver usb
[ 0.347217] usbcore: registered new interface driver smsc95xx
[ 0.748569] dwc_otg 3f980000.usb: DWC OTG Controller
[ 0.748607] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 0.748644] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[ 0.748912] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.748927] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.748940] usb usb1: Product: DWC OTG Controller
[ 0.748953] usb usb1: Manufacturer: Linux 4.4.38-v7+ dwc_otg_hcd
[ 0.748965] usb usb1: SerialNumber: 3f980000.usb
[ 0.750758] usbcore: registered new interface driver usb-storage
[ 0.867837] usbcore: registered new interface driver usbhid
[ 0.867845] usbhid: USB HID core driver
[ 1.127051] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 1.327314] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[ 1.327332] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.607042] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 1.707312] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[ 1.707333] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.770443] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:02:e2:9e
[ 1.847039] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[ 1.962438] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6015
[ 1.962461] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.962474] usb 1-1.2: Product: FT232EX
[ 1.962486] usb 1-1.2: Manufacturer: FTDI
[ 2.047077] usb 1-1.3: new low-speed USB device number 5 using dwc_otg
[ 2.185717] usb 1-1.3: New USB device found, idVendor=0665, idProduct=5161
[ 2.185741] usb 1-1.3: New USB device strings: Mfr=3, Product=1, SerialNumber=0
[ 2.199378] hid-generic 0003:0665:5161.0001: hiddev0,hidraw0: USB HID v1.11 Device [HID 0665:5161] on usb-3f980000.usb-1.3/input0
[212914.138590] usb 1-1.2: USB disconnect, device number 4
[213409.382225] usb 1-1.3: USB disconnect, device number 5
[213412.611403] usb 1-1.5: new low-speed USB device number 6 using dwc_otg
[213412.750097] usb 1-1.5: New USB device found, idVendor=0665, idProduct=5161
[213412.750145] usb 1-1.5: New USB device strings: Mfr=3, Product=1, SerialNumber=0
[213412.764865] hid-generic 0003:0665:5161.0002: hiddev0,hidraw0: USB HID v1.11 Device [HID 0665:5161] on usb-3f980000.usb-1.5/input0
[213423.741735] hid-generic 0003:0665:5161.0002: usb_submit_urb(ctrl) failed: -1
[213424.652350] usb 1-1.5: USB disconnect, device number 6
[213426.181484] usb 1-1.4: new low-speed USB device number 7 using dwc_otg
[213426.320282] usb 1-1.4: New USB device found, idVendor=0665, idProduct=5161
[213426.320308] usb 1-1.4: New USB device strings: Mfr=3, Product=1, SerialNumber=0
[213426.332649] hid-generic 0003:0665:5161.0003: hiddev0,hidraw0: USB HID v1.11 Device [HID 0665:5161] on usb-3f980000.usb-1.4/input0
[213441.031538] usb 1-1.3: new full-speed USB device number 8 using dwc_otg
[213441.146980] usb 1-1.3: New USB device found, idVendor=0403, idProduct=6015
[213441.147010] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[213441.147028] usb 1-1.3: Product: FT232EX
[213441.147044] usb 1-1.3: Manufacturer: FTDI

pi@ICC-Solar:/var/lib $ lsusb
Bus 001 Device 007: ID 0665:5161 Cypress Semiconductor USB to Serial
Bus 001 Device 008: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
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.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@ICC-Solar:/var/lib $ lsusb -t
/: 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 3: Dev 8, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 4: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M

At startup, it seems it picks up two usb devices, which is correct (Inverter & BMV).

The latter entries must have been when I was testing the cables on other usb ports/swopping them around as described above.

Anybody with a little more linux/usb knowledge that can assist sorting out this problem?

PS. I have flashed a ICC image on a new SD card, but have not gotten around testing it, but that's going to be another story, as I would hate loosing 2.5 years information, as my emoncms version, even though it is 9.7.9, does not show the backup command in the dropdown menu, as I've seen on Youtube, where it appears on 9.4. Seems one can add the command manually, but some of the steps assumes one is a linux fundi! In the mean time, I have acquired a new Rpi3B+ with heatsinks! (don't forget those, else you will melt the Pi).

PPS. I said problem(s) in the beginning, as the second problem is actually more problematic, but I had a workaround. As my Inverter room is in a separate building, I used Wifi to connect. Worked fine for 2.4 years. Suddenly my Pi disappeared (not accessible via VNC). Testing the Pi in the house only showed "No Wireless devices found" Both Wifi and BT was dead on the Pi. On the next weekend I pulled in the 50m Ethernet cable (quite a job! - luckily I had a spare conduit under the paving between house and garage!). I must say, when I did the 2.8.8 ICC update the other day, it did that in no time at all.

So, any help in pinpointing the issue will be appreciated. Thanks again for reading.

Riaanh · July 8, 2019

Just a quick one, can you run lsusb from command and see what it picks up, either with the cables in or removed?

Sidewinder · July 8, 2019

USB Cables in:

pi@ICC-Solar:/var/lib $ lsusb

Bus 001 Device 007: ID 0665:5161 Cypress Semiconductor USB to Serial

Bus 001 Device 008: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)

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.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Not at home at this moment, but will pull usb stuff later today.

Riaanh · July 8, 2019

33 minutes ago, Sidewinder said:

Bus 001 Device 007: ID 0665:5161 Cypress Semiconductor USB to Serial

Inverter

33 minutes ago, Sidewinder said:

Bus 001 Device 008: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)

USB/Serial cable to device.

(This is the chipset used in some USB-Serial devices, so on the other end can be a BMV, Battery BMS or such, so difficult to say exactly.

The rest are the standard onboard stuff.

See the sample below, similar to yours, connected to Inverter and Pylontech batter BMS.

Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
Bus 001 Device 006: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Sidewinder · July 8, 2019

Thanks @Riaanh,

OK, so you have 6 entries in your table. I have 5, and taking into account that the Ethernet port is mapped to Device 003, I actually have two entries missing (I conclude that you are not connecting your Pi to Internet via Ethernet, but then you may have a mouse/keyboard etc connected). I run my Pi completely headless, (and armless).

Yet the two entries of importance is FTDI & Cypress, which both of our configs have!.

So making headway, but not much.

Sidewinder · July 8, 2019

SOLVED!!!!!

So was just playing around on ICC via VNC.

On ICC, i went to the battery settings page. Stop ICC, Disable BMV, save, Enable BMV, save and lastly Start again. No change,

so I did....

On ICC, i went to the battery settings page. Stop ICC, Disable BMV, save, Start ICC and check BMV thread not present. Then Stop ICC, Enable BMV, save and lastly Start again.

And there she goes....

Weird that a cold boot did not solve this.

Sidewinder · July 8, 2019

NOT SO SOLVED

So even though ICC report Battery info on Dashboard2, they are static., i.e. not moving, and Inverter/BMV Values, most of the values are 0, bar the ones displayed on Dashboard 2.

What I normally do when this happens is the pull the offending cable out at the USB port and re-seat. This happens only every 6 months or so, and just on the inverter cable.

Will try and re-set the BMV cable this later afternoon.

Sidewinder · July 8, 2019

So I does seem like ICC "sees" about 3 mins of activity on the graphs, even though Dashboard 2 shows static values.

Sidewinder · July 9, 2019

Status with Inverter & BMV cable disconnected:

pi@ICC-Solar:/var/lib $ lsusb

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.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Sidewinder · July 10, 2019

Can someone with a BMV device connect to a Rpi please post the output of the following command: lsusb and lsusb -t

From my own results, I see that my result is as follows:

pi@ICC-Solar:/var/lib $ lsusb
Bus 001 Device 007: ID 0665:5161 Cypress Semiconductor USB to Serial
Bus 001 Device 008: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
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.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@ICC-Solar:/var/lib $ lsusb -t
/: 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 3: Dev 8, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 4: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M

So i conclude that the VE.Direct cable is on Device 8, yet the driver it is using is blank, surely it should load a driver, just like all the other entries for Ethernet port and Inverter.

If so, please indicate how do I fix this?

Edited July 10, 2019 by Sidewinder

Riaanh · July 10, 2019

2 hours ago, Sidewinder said:

Can someone with a BMV device connect to a Rpi please post the output of the following command: lsusb and lsusb -t

I will connect one tonight and post the results for you.

Just for reference, what all have you got connected, so I can try and simulate?

Sidewinder · July 10, 2019

I have Infini Inverter connected via usb, and bmv via official ve.direct usb cable.

And Internet via Ethernet port, which is also part of USB. Rpi 3b.

Riaanh · July 10, 2019

12 minutes ago, Sidewinder said:

I have Infini Inverter connected via usb, and bmv via official ve.direct usb cable.

OK, this is as close as I can get: RPi 3b, Infini 4 Super and Official ve.direct USB Cable.

Running Headless, no monitor, keyboard or mouse. Connected via LAN cable to network, accessed via VNC.

pi@Infini4:~ $ lsusb
Bus 001 Device 021: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 019: ID 0665:5161 Cypress Semiconductor USB to Serial
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@Infini4:~ $ lsusb -t
/: 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 19, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 5: Dev 21, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M

Hope this helps?

Sidewinder · July 10, 2019

Thanks. Yes, is confirms my hunch that the driver is missing.

So next is WHY, and most importantly, how to fix it. I have been googling, but have not been able to find an answer yet. Will keep looking.

Sidewinder · July 12, 2019

Small update..

So i found the latest FTDI driver. Ver 1.4.8, from https://www.ftdichip.com/Drivers/D2XX/Linux/libftd2xx-arm-v6-hf-1.4.8.gz

On the download page is a link to a how to video.

.I followed the instructions carefully, and all when accordingly till the remove part, which failed, assuming because the offending old drivers ftdi_sio does not exist. (I assuming they where trashed when I did the "apt-get update".

In response to the last sudo ./read command, I get:

root@ICC-Solar:/home/pi/Downloads/release/examples/EEPROM/read# sudo ./read

Library version = 0x10408

Opening port 0

FT_Open succeeded. Handle is 0x1fd5308

FT_GetDeviceInfo succeeded. Device is type 9.

FT_EE_Read succeeded.

Signature1 = 0

Signature2 = -1

Version = 0

VendorId = 0x0403

ProductId = 0x6015

Manufacturer =

ManufacturerId =

Description =

SerialNumber =

MaxPower = 90

PnP = 1

SelfPowered = 0

RemoteWakeup = 0

Returning 0

I think this is still the old info, as I suspect I need to unplug and re-plug the cable, and then run the command again.

or even do a reboot. Will do over the weekend.

Sidewinder · July 17, 2019

OK, Finally sorted this out.

Seeing I upgraded the kernel, I simply downgraded (to 4.4.17) using the command:

rpi-update 50f4bc47fc16c05c657c6f6f15719e57917f9b81

then reboot command:

Quick fix, but lot's of reading......

Sidewinder · July 18, 2019

BTW, All of a Sardine the Wifi & BT is also working again. Why do them people that create upgrades don't test their S/W on real live systems.

vlan_one · July 30, 2019

On 2019/07/18 at 7:22 AM, Sidewinder said:

All of a Sardine

wow, I have not heard this line in years

ICC Rpi3B usb port(s) stopped working?

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation