Fade with a GPIO-Input

[Martin]

Hello everybody,
I want to thread a PAR56 with a GPIO input.
If I create a switch on the VC and control it with a GPIO input, the switch is only activated when switching from low to high and the function is executed.

Is there a possibility (or trick ) to create this so that the headlight is controlled from 0 to 100 when opening the contact at the GPIO input and from 100 to 0 when the contact is closed?

Thanks for your help.

[mcallegari]

I'd say you just need a Scene with fade in and fade out timings set properly.

[Martin]

Hello Massimo,

in a scene, the fade in and fade out has no effect. See attachement

[GGGss]

If you change the button in toggle it works perfectly

Can't you change the gpio behaviour that you get a pulse evertime to input changes it's value??
Or through using a feedback mechanism so you use a toggle button? See annex

IMHO it's a bug
(tested w10 + latest 4.11.2)

[Martin]

Can't you change the gpio behaviour that you get a pulse evertime to input changes it's value??

I dont know how?

Or through using a feedback mechanism so you use a toggle button? See annex

Also with the feedback mechanism I have to open / close the contact for fade in and a second open / close for fade out.

Possibly. is there a completely different solution ....

I would like to switch on (fade in) a background lighting in a glasscabinet with a door contact connected to a GPIO input and switch it off (fade out) when the door is closed.

Does anyone have an idea for this?

[GGGss]

Never worked with GPIO YET
So you only get 'triggers' when closing the GPIO pins?

Then you have to remember this trigger (self triggering chaser with duration of oo) and set / reset this chaser - sounds complicated but do-able
you have to create a latch mechanism - everytime you get a trigger from GPIO the state of the latch has to change.

QLC+ has no logical operators so you (we) have to be creative

[Martin]

So you only get 'triggers' when closing the GPIO pins?

The GPIO inputs can evaluate both states. Open and close.
With a python script I can evaluate both states.
I do not know how QLC+ (or Massimo) evaluates the inputs.

[Martin]

I found the solution. Massimo wrote in "GPIO for cue list next stops after first trigger":

Have you tried to create a custom input profile and enable the "Generate an extra Press / Release when toggled" option?

That is the solution.

Thanks Massimo, my first problem is solved.