Well my focus is on Victron ecosystem with Cerbo and have little experience with Arduino.
Actually the first version of RemoteGPIO was based on Node-red with a modbus control layer.
It was quite cpu intensive.
There was some extensive work to make it Dbus native, still based on modbus control layer.
CPU wise it’s better but not perfect. Especially with complex installations including many mppts, inverter, BMS enabled batteries, many sensors, GX tanks and multiple RemoteGPIO devices.
My next goal is to switch the control layer to MQTT as I believe it to be the most efficient way to control the Dingtian relays and Digital inputs. I want to keep it Dbus native as at some point I hope to be able to also control the relays and DI with GUI v2.
1 Like
I am trying to better understand the mechanics and potentials of Remote GPIO.
From your previous post ( RemoteGPIO: Adding Relays and Digital Inputs) I see that you obtained a visual representation of the relays on your Venus/Cerbo display.
Is there a post where perhaps this part is better explained? As I mentioned earlier, I have only used the Digitian relays remotely via Ethernet which does not communicate back to Cerbo but can only be visualised from Node-Red.
On the other hand you opted for Modbus rather Lan, is this what makes the difference and enables the GPIO to be added to the Venus menu?
Thanks
The beginning of this post goes through the setup steps. It also shows the integration with the user interface.
RemoteGPIO supports both Ethernet and USB access, configurable directly from the GUI.
For more details on how it works, you could also have a look at my Github page with source code, the discussions and the issues (including the closed ones that can be very interesting) : GitHub - Lucifer06/RemoteGPIO: Remote General Purpose I/O for Venus OS devices (Cerbo GX, ...)
1 Like
Hi Helamast, vielen Dank für die Info - werde es testen.