Hi,
I successfully enabled 3 additional relays on RPI running latest stable Venus OS but only first two are visible on GUI.
The other 2 are fully functional using CLI dbus Set/Get.
Is it possible to make them all visible on GUI and how?
Thanks,
Mihai
Hi Mihai
What is the procedure to make the other 2 relays go i can see four in the gui the last two are blank won't switch on , i had added all the files as per txt below etc.
Is there a order they should be installed in or sim linking files? running Ver 2.40.45
Just adding those change to the files is not correct for ver 2.40.45.
What is the correct order of doing this?new-text-document.txt
Regards
Rob D
NZ
Hi Rob,
You should first try to test the relay functionality before enabling the toggle button on GUI.
Please wire a low current LED in series with 4k7 resistor between ground and your designated GPIO port for Relay 2 and issue the following commands to power ON and OFF the LED :
# dbus -y com.victronenergy.system /Relay/1/State SetValue 1
# dbus -y com.victronenergy.system /Relay/1/State SetValue 0
Warning: DO NOT wire a relay directly to any GPIO output port! Always add an open collector NPN transistor as buffer and a reverse biasing diode in parallel with your relay (as in the following link, Driving a relay)
Solved!
I just modified /opt/victronenergy/gui/qml/PageSettingsRelay.qml and now is working :-))
On top of the script you have to add:
property VBusItem relay2Item: VBusItem { bind: "com.victronenergy.system/Relay/2/State" }
property bool hasRelay2: relay1Item.valid
property VBusItem relay3Item: VBusItem { bind: "com.victronenergy.system/Relay/3/State" }
property bool hasRelay3: relay1Item.valid
and on the bottom the following lines:
MbSwitch {
id: manualSwitch2
name: qsTr("Relay 3 On")
bind: "com.victronenergy.system/Relay/2/State"
show: hasRelay2
}
MbSwitch {
id: manualSwitch3
name: qsTr("Relay 4 On")
bind: "com.victronenergy.system/Relay/3/State"
show: hasRelay3
}
strictly speaking you need to fix the number in these:
property VBusItem relay2Item: VBusItem { bind: "com.victronenergy.system/Relay/2/State" }
property bool hasRelay2: relay1Item.valid
property VBusItem relay3Item: VBusItem { bind: "com.victronenergy.system/Relay/3/State" }
property bool hasRelay3: relay1Item.valid
but it will work without that for you as well.
Hi
Just a question, does it have show a function (relay)1, 2, 3, 4 to operate and assign the correct port for each function like generator for 1 tank pump for 2 etc?
As it only shows function (relay1).
You can assign a function only to relay 1. For the rest of them only manual access via GUI or one could assign a function through CLI scripting
Hi
What is the procedure to make the other 2 relays go i can see four in the gui the last two are blank won't switch on , i had added all the files as per txt below etc.
Is there a order they should be installed in or sim linking files? running Ver 2.40.45
After some investigations I feel that any relays over 2 was on purpose disabled by Victron in the latest Venus OS version . I presume a simple reason, there are no commercially products with more than 2 relays capabilities.
Anyway, here is an workaround:
For any additional number of relays over two, the relay definition in /etc/venus/gpio_list must be different than standard syntax relay_n. There will be no dbus support for those relays
In this way, after reboot the system will not become unstable and you can control the additional relays as in any other RPI project:
switching on: # echo 1 > /dev/gpio/relay-3/value
switching off: # echo 0 > /dev/gpio/relay-3/value
My apologies to Victron team if this presumption proof to be wrong.
Hi
I have found that this folder is missing the extra relay files gpio for gpio22, gpio27
in Ver 33 all is there, but in later versions these are not added at all only the ADC and 2 relay files gpio 21, gpio 17, would this be the cause?
/sys/devices/platform/soc/3f200000.gpio/gpiochip0/gpio
So the work around makes it active again?
No. The python scripts responsible to relay control was dramatically changed.
In ver.2.33 there are routines capable to autodiscovery any number of user defined relays.
example: /opt/victronenergy/dbus-systemcalc-py/delegates/relaystate.py
In the latest version there are only two relays defined
One with adventurous spirit can try to copy the python files from previous version to latest and see what happen :-)
Hi
I will give it ago nothing to lose. Just had look yes the file size between the old version is very different in size, they have cut lots out in the latest version for both relaystate.py and pyc files.
Hi
Cracked it all good now, have full operation of all relays and is stable.
Thanks for the advise of were to look.
i will advise Mark as he was having trouble after the changes.
I can now do the HAT with full relay control etc, will be posting the design soon.
Regards
Rob D
NZ
The source of the script is here, https://github.com/victronenergy/dbus-systemcalc-py/blob/master/delegates/relaystate.py#L26.
It should actually be able to detect any number of relays, what seems to be broken is requesting the initial state, so it can be restored after reboot. That shouldn't be limited to two. I don't know the details though, but https://github.com/victronenergy/dbus-systemcalc-py/blob/master/delegates/relaystate.py#L37 should return all relays and that is intended behavior. I guess it should be rather straightforward to do something similar in get_settings instead of hard coding it.
Hi Jeroen
All i did was replace the new relaystate.py with the old version from 2.40.33 and it all runs fine now with any number of relays selected and stable.
Regards
Rob D
NZ
I'm working on adding some relays on a Cerbo GX, connected externally through Modbus serial interface.
The above procedure is assuming the relays are physical controlled with the rpi gpio. Would it be possible to get the same result, displaying the external relays on Venus GUI?
Thx in advance for any hints, I'm stuck.
