NotMario Posted September 7, 2022 Share Posted September 7, 2022 (edited) I wrote a module to create a GenetrySolar Inverter device on Victron's GX units. As it is, the product has infrastructure to do modbus, so i've used that for now. As the GS doesn't have modbus support yet, this means that a proxy is needed to map the status.js to the modbus space. The genetrysolar.py file goes in /opt/victronenergy/dbus-modbus-client You have to add an import clause for it [after the one for smappee] in the dbus-modbus-client.py file in that same directory. (Unfortunately, they didn't make it pick it up automatically) The gsproxy.py can run anywhere. But you have to point your GX unit to it as a Modbus TCP device. It is invoked as: ./gsproxy.py <port> <fakeserial> Important to note that the proxy is only a simulator right now. I am not able to use my unit to test out the actual mapping from a real inverter. The code is trivial, so someone here could probably modify it before i get my equipment in order. Naturally, the ideal case would be for the GS to support Modbus natively - or for Victron to make infrastructure for JSON devices. I wasn't going to try and write that infrastructure for Victron. I wouldn't want the additional UI work so you could add a "json device". gsproxy.py genetrysolar.py Edited September 7, 2022 by NotMario Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.