question

questvent avatar image

Venus (Rpi) no longer shows BMV-712

I've got an Rpi 3 B+ running the 2.30~45 version of the Venus OS installed from the development images. It has two devices connected to it via VE.Direct to USB adapters, device 1 is an MPPT 150/85 rev.2, and the other is a BMV-712. Everything worked great for several months, but then on June 28th around 7am PST, it stopped displaying the information from the BMV-712. I've tried to unplug the USB adapter and plug it back in, and I've rebooted it several times both with the devices plugged in and without. If I run 'lsusb -v', (attached) it shows the BMV connected, but it no longer shows in the console or in the VRM portal.

I also updated to 2.32~2 thinking that maybe it would reset whatever is wrong, but it did not fix the problem. Can you think of anything else that I can try? If doing a reformat and re-install would fix it, I'm open to that, too. Thank you for any help or ideas that you can provide.

Venus_USB_Dump_MPPT_BMV.txt

MPPT - Solar Charge ControllerBMV Battery MonitorVenus OSRaspberry Pi
10 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

4 Answers
Markus avatar image
Markus answered ·

Hi,

if you connect the BMV's Ve Direct USB Adapter to a Windows or MAC PC and try to connect to it with Victron Connect, does this work?

Regards,

Markus

Share
10 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

stefan.cs avatar image
stefan.cs answered ·

I may have a similar problem: my BMV-712 does not show up on RPi 2 or 3b+ running Venus OS 2.32 and 2.42. No problems connecting same BMV-712 / same VE.Direct-to-USB cable to Win 10 PC App. Removing and reattaching cables, swapping RPis, using different Venus OS versions did not change anything.

I get the following via ssh on an pi2 running v2.42 and connecting a single BMV-712 via Victron VE.Direct-to-USB-cable:

# tail -f /var/log/messages:

ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32

and sometimes:

ftdi_set_termios urb failed to set baudrate 
ftdi_sio ttyUSB0: urb failed to clear flow control 
ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32

# lsusb -v -s sometimes lists iProduct response, sometimes it doesn't:

 iManufacturer           1 (error)
  iProduct                2 VE Direct cable
  iSerial                 3 (error)
 iManufacturer           1 (error)
  iProduct                2 (error)
  iSerial                 3 (error)


Full output:

# lsusb
Bus 001 Device 004: 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. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

for the FTDI device I get:

# lsusb -v -s 00
Bus 001 Device 004: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6015 Bridge(I2C/SPI/UART/FIFO)
  bcdDevice           10.00
  iManufacturer           1 (error)
  iProduct                2 (error)
  iSerial                 3 (error)
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               90mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 (error)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x6c18
  (Bus Powered)

repeating this on a different physical USB slot I get these:

Bus 001 Device 014: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6015 Bridge(I2C/SPI/UART/FIFO)
  bcdDevice           10.00
  iManufacturer           1 (error)
  iProduct                2 (error)
  iSerial                 3 (error)
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               90mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 (error)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)
Bus 001 Device 010: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6015 Bridge(I2C/SPI/UART/FIFO)
  bcdDevice           10.00
  iManufacturer           1 (error)
  iProduct                2 VE Direct cable
  iSerial                 3 (error)
  bNumConfigurations      0
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0000
  (Bus Powere

when attaching / reattaching the USB cable to the pi I get this:

# tail -f /var/log/messages
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.127029] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.636469] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6015
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.636488] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.636499] usb 1-1.2: Product: VE Direct cable
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.636508] usb 1-1.2: SerialNumber: VE4A9CXM
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.663564] usbcore: registered new interface driver usbserial
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.663675] usbcore: registered new interface driver usbserial_generic
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.663787] usbserial: USB Serial support registered for generic
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.676285] usbcore: registered new interface driver ftdi_sio
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.676413] usbserial: USB Serial support registered for FTDI USB Serial Device
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.676802] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.677302] usb 1-1.2: Detected FT-X
Jan  1 00:23:16 raspberrypi2 user.info kernel: [  284.678572] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
Jan  1 00:23:23 raspberrypi2 user.err kernel: [  291.703133] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
Jan  1 00:23:23 raspberrypi2 user.err kernel: [  291.857811] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32

and sometimes:

Jan  1 00:33:06 raspberrypi2 user.info kernel: [  873.879494] usb 1-1.3: Detected FT-X
Jan  1 00:33:06 raspberrypi2 user.info kernel: [  873.880728] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB0
Jan  1 00:33:13 raspberrypi2 user.err kernel: [  881.259344] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
Jan  1 00:33:13 raspberrypi2 user.err kernel: [  881.267596] ftdi_sio ttyUSB0: urb failed to clear flow control
Jan  1 00:33:13 raspberrypi2 user.err kernel: [  881.311709] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32

Any ideas what to do or what else to check?

Regards,

Stefan

1 comment Share
10 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Update: my Victron VE.Direct-to-USB cable still does not work with any of my RPi 2 or 3b+ running Venus 2.52 or earlier (haven't tried later releases). That same cable does connect the BMV to the Victron App on Windows.

I now use a DIY VE Direct to USB cable between my BMV and my RPi which connects perfectly. Seems to be an issue with some FTDI devices.

Regards,

Stefan

Ralf Klüber avatar image
Ralf Klüber answered ·

Hello,

same problem here. It worked, not sure if recent SW update for BMV 712 broke it. I tried to reboot several times the rPi. I disconnected USB and Ve Direct USB on both ends ... . No success.

 # lsusb -v lists the USB connector
 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)

after reattaching usb on the rPi I get:

 # tail -f /var/log/messages
 Sep  9 09:51:47 raspberrypi2 user.info kernel: [   99.717186] usb 1-1.5: new full-speed USB device number 5 using dwc_otg
 Sep  9 09:51:47 raspberrypi2 user.info kernel: [   99.878831] usb 1-1.5: New USB device found, idVendor=0403, idProduct=6015
 Sep  9 09:51:47 raspberrypi2 user.info kernel: [   99.878845] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
 Sep  9 09:51:47 raspberrypi2 user.info kernel: [   99.878853] usb 1-1.5: Product: VE Direct cable
 Sep  9 09:51:47 raspberrypi2 user.info kernel: [   99.878860] usb 1-1.5: Manufacturer: VictronEnergy BV
 Sep  9 09:51:47 raspberrypi2 user.info kernel: [   99.878867] usb 1-1.5: SerialNumber: VE3VTOFW
 Sep  9 09:51:47 raspberrypi2 user.info kernel: [   99.887257] ftdi_sio 1-1.5:1.0: FTDI USB Serial Device converter detected
 Sep  9 09:51:47 raspberrypi2 user.info kernel: [   99.887492] usb 1-1.5: Detected FT-X
 Sep  9 09:51:47 raspberrypi2 user.info kernel: [   99.888445] usb 1-1.5: FTDI USB Serial Device converter now attached to ttyUSB0

I connected the USB to a Mac using Victron Connect and it worked on the mac. Anyone having another idea where to look for trouble shooting?

I have added a i2c device (HWClock and USV) on the rPi thus did

 # modprobe i2c-dev

I will recheck on a vanilla install when I have a 2nd SD card.

Anyone any idea?

Running Venus OS v2.33

Regards Ralf

3 comments Share
10 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Hello,

When I execute the following on the command line (via ssh)

 # /service/vedirect-interface.ttyUSB0/run

I see a lot fancy output and the BMV 712 is visible in the GUI. It seems that this service is not started. But I dont know enough to understand or to know where to look to find out why it is not started.

Any recommendation where to start reading how this works?

in that folder there is an empty file called "down". I deleted it and rebooted, but its get created again.

Please help.

Regards Ralf

Ralf,

On my setup I've got two devices connected using the VE.Direct to USB adapters, and I did the same basic troubleshooting that you're doing. The adapter was showing up but apparently being ignored by the software.

For me, I shut the MPPT, BMV, and RPi down, removed the two adapters and swapped them so that the one from the MPPT was now on the BMV, and vice-versa. When I say swapped, I mean I also swapped the USB ports, so swapped on both ends. Then after starting it back up again both devices showed up. The problem with this approach seems to be that the VRM portal sees the devices as new now, so I had to go in and change some things around so that the statistics lined up again.

Good luck.

I did that already without success. Could it be that you can use the "wrong" (physical) USB port? I am not sure which one it was when it worked. Can't try out now. I will set up a vanilla SD card, check and come back.

Anyone have a clue what mechanism is being used to start services? It's not systemd.

questvent avatar image
questvent answered ·

Thanks for the suggestion, I had forgotten about the PC version of the app...I installed it and was able to connect the MPPT via USB to verify that the USB drivers work, but when I connect the VE.Direct to USB cable connected to the BMV, it doesn't find it on the app.

I swapped the cables so that the charge controller was using the BMV cable and vice-versa, rebooted the Venus and it recognized both devices again. So maybe the BMV just needed to have the cable removed and re-attached? Who knows. But if anyone experiences this issue, you might want to try that.

Share
10 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.