I bought a Venus GX and updated it to v3.72. Added 1 mppt via a direct cable and tried to add the other 2 via a duppa board.
The Venus GX just goes through a boot cycle constantly. I removed the Duppa board and the GX is running normally.
I do have a multiples plugged into the ve bus as well. I used to run a Pi but it was driving me nuts
Do I need a powered usb hub with the Venus GX to use a usb device. I know it is a low powered device
No, it should work fine directly off the Cerbo.
It could be an issue with the hardware or VenusOS. I doubt Victron would deliberately remove support for those devices. But i dont have one around to test it myself. Id guess the issue is the Duppa unit itself. I know its a bit of a risk, but does it work if you plug it into a regular PC?
I am thinking of re-installing the update via the micro-sd just in case I had a bad install. I had thought it odd that it kept rebooting without any beeps
I have two duppa 4port adaptors plugged into a very cheap(£2.36) ebay 4port usb hub to mp2 gx, all working fine with 2xjkbms + shunt + 2xmppt + arduino nano. Also have another two mppt’s plugged in direct to mp2gx via ve direct.
I dropped the firmware to 3.67, and plugged the Duppa unit in, not sure if it locks up or what after an hour or so. updated to 3.72 and plugged in the Duppa into the bottom port to see, the one beside the ethernet port.
Last night I plugged in a VE.Bus to USB-C MK3-USB which I had as spare. And that seemed ok
Continuous rebooting is a sign of an overloaded cpu.
Just noticed the Venus GX this is an older device with a single core processor. As the firmware has been developed over time, some of the older GX devices are struggling and the more components added to the system the higher the cpu load. The Colour Control GX, another single core unit has been limited to Venus OS 3.55. I do not know if you ate running into similar issues here with V3.6X and V3.7X firmware.
The duppa is also an unsupported device.
That would make sense. Ok, will drop out to 3.55 and see what happens, will do the full reinstall of the OS
Very true
Leaning towards this. It sounds like a power problem. Or a grounding one.
If the pi was driving you nuts the venus definitely will. Sometimes a re install helps and no venus large. It is definitely not powerful enough for much except the basics.
It is connected directly to the one of the 2 batteries (12v 280ah) . I went back to 3.55 but that still barfed. So stuck the Duppa back on the Pi and left just the one can bus mppt , 1 ve direct mppt and the Phoenix Compact 1600 that is connected via ve bus. The Venus GX has been running like that since 01:30 (am) so about 16 hours and no issues. On the Pi is the battery monitor and a 75/15 mppt. These are on the duppa device. I am thinking of changing it off the battery and onto the fuse board, just in case it is better that way
I am not a power user, I use the battery bank mainly to power my Cpap machine and laptops and a few Pi. It is a bit of an overkill for what I use 
I did a couple of tests over the weekend. Thursday/Friday, I ran the VGX with no usb devices, just one device in the VE Direct port, one in the VE Bus and one in the Ve Can, no issues at all. Saturday, plugged in a spare Duppa device with no attached devices, the VGX went into a reboot cycle after about 30. minutes. Unplugged the power and tried restarting with the Duppa device connected, would not fully start, just power cycled. I have a spare USB Ve Bus mk3 so started the VGX with that plugged in and no Duppa devices, it is still running, I did a reboot 12 hours about to test and it is still going.
My thought is that it is a USB cable issue. I don’t have many usb c to A cables oddly. I have also ordered another ve direct cable to see. I could do with taking one of my mppt devices off as they don’t generate much, the big Ve Can 150/100 generates most of my power. I just had a couple of small panels that I added
