In preparation for for an electrician to install the AC cabling on AC-In & AC-Out's of 2 Multiplus II in parallel, I cludged up an AC cable to provide power to both the AC-In's in order to use Ve.Bus Quick Conbfigure & VEConfig to set them up.
That all worked well with a MK3-USB adapter from PC. Then plugged MK3-USB adapter into RPi Venus OS running v3.00. Again, works & Multi's visible in Remote Console as per:
However after a short period of time the Multi's seem to lose connection to Venus although there is no indication on the Multi's LED that anything wrong.
The main console display indicates Multi's are Off.
But the Multi's entry shows:
Tried using Remote Console to Power Off-Power On the Multi's to no effect - Multi's did not actually power off then on.
So then tried Restarting VE.Bus system but the Remote Console shows it in Restarting state until I reboot Venus. Same behavior occurs when attempting Redetect VE.Bus system.
After reboot of Venus, the cycle starts again.
As VRM shows here, the length of VE.Bus active times is variable.
Started examining the dmesg outputs for clues:
root@raspberrypi4:~# dmesg | grep 1-1.2 [ 3.577136] usb 1-1.2: new full-speed USB device number 3 using xhci_hcd [ 3.738811] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6015, bcdDevice=10.00 [ 3.751639] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.759135] usb 1-1.2: Product: MK3-USB Interface [ 3.763945] usb 1-1.2: Manufacturer: VictronEnergy [ 3.768836] usb 1-1.2: SerialNumber: HQ1806W4YYM [ 4.959433] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected [ 4.972670] usb 1-1.2: Detected FT-X [ 4.984101] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
So far looks good, but these messages follow:
root@raspberrypi4:~# dmesg | grep ftdi [ 4.911384] usbcore: registered new interface driver ftdi_sio [ 4.959433] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected [ 25.254072] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 [ 25.262633] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 [ 26.223114] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32 [ 27.225763] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32 [ 28.218033] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32 [ 29.220288] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32 [ 48.419136] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32 [ 49.421597] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32 [ 50.424003] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32 [ 816.671563] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32 [ 1026.931590] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32 [ 1093.681723] ftdi_sio ttyUSB0: failed to set flow control: -32 [ 1093.687940] ftdi_sio ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32
Is there an incompatibility issue here or should I update a FTDI file?
Firmware is as follows:
It may be important to note that there are no loads on the Multi's - neither battery nor AC.
