Page 1 of 1

DevCfg: Toggle with slave vs without slave

Posted: Mon Jan 30, 2023 21:30
by joaquinbaeza
Hi, I have studing devcfg manual, and I have a question.
Regarding to Toggle function (4.3.9 section):
Lets say I want to configure the toggle switch that is in the left side of the base of Gladiator, and I want to use the toggle function. Lets say I want to send signal 3 when switch is up, signal 4 when switch is down, and signal 5 when switch comes back to middle position. I have found that it is possible to do this with slave property, as described in manual, and without slave property. So, is there a advantage to do it one way or another?

toggle.png
Example

Re: DevCfg: Toggle with slave vs without slave

Posted: Wed Feb 01, 2023 0:56
by Ron61
Switch SW1 has two buttons -3rd and 4th at the physical level. Which, in turn, press logical buttons 25 and 26, and the system sees them. To make a toggle switch with three positions, you need a master button and a dependent one. Since the 5th button is already occupied, you need to select any free one - let it be 89. And now, if you configure it according to the pictures, the toggle switch will work like this - up 25th - in the middle of 89th - down 26th.

toggle SW1.jpg
SW1 4 but.jpg