I have a small test system for building and testing equipment to be moved to remote sites. The devices are of course 1-2 solar panels 200-400w, 100 a/h 24v LiPo battery, MPPT 75/15, SmarShunt 300a, VenusOS on RPi 3B+. Running Beta 3.60~7. The issue I am encountering
is the link to the SmartShunt300 is being dropped. I can reboot the VenuOS RPi and it will come
up but at some point it gets dropped again. The MPPT 75/15 stays on line.
I have run the original code on the system and it does not drop the SS300A. I have tested the Beta code with a SS500a, it does not get dropped, but I can move the SmartShunt300 a to another system and it stays on line. I have moved the devices to different USB ports on the RPI, but still the same thing.
I see that all of the devices are linked on Bluetooth, sure would be nice to not need the USB cables to link them since they are already talking on BT.
When you use a Victron GX device it is recommended that you either have things wired by VE Direct OR a Bluetooth VE Smart Network but NOT both as that can give problems. If yours are communicating via both means that may be an issue.
Ahh, then I can get rid of the cables, and just use the BT connection, that is even better. Space in these boxes
is limited and if I can use BT to link these devices that is even better.
I have all of these sites running a RPi with VenusOS, it has BT but I do not see the option to connect to BT VE Smart Network. So should I turn it off and use VE Direct, or is there a work around. In this case the BT connection is very attractive because all of the devices in in a weather proof case just cm of separation. I would certainly like to eliminate the cabling if possible due to space limitations.
VE Smart Networking is intended for device to device comms, i.e. SmartShunt to Smart solar, connections to the Venus OS device need to be wired. So keep your wires and make sure VE Smart Networking is off.
The other suggestion is post this question in the modification space where the rpi users post more frequently in case it is an rpi issue.