HS/FS alternative logik Treppenlichtfunktion

[ChrisChros]

Hallo,

momentan verwende ich den Logikbaustein Treppenhauslicht-Funktion der beim Experten dabei ist um Lichter zu schalten die auf unterschiedlichen Aktoren geklemmt sind. Ansich funktioniert auch alles wie es soll, nur bin ich mit dem 1Hz Bliken nicht zufrieden, ich komme mir vor wie in einer Disko.
Gibt es einen alternativen Baustein bei dem man eventuell Einstellmöglichkeiten über die Frequenz hat oder der es so ähnlich löst wie bei den MDT AKS Aktoren (1mal blinken x sekunden vor Ende)?

MfG
ChrisChros

[bramlangen]

Christian, I would use a sequencer and set it to be retriggerable. You can then have the blinking any which way you want it. If you also want the lights to go off when an 'off' telegram is sent by the pushbutton, then include a 'stop sequence' command along with that off-signal.

Bram

[ChrisChros]

Hello bram, thanks for your suggestion. I will try my best to implement this opportunity during the weekend.
But where can I get such a sequencer, is it part from the Erxperte?

[bramlangen]

Yes, standard issue of the Experte software, see attachment which includes a simple example. Start the sequencer using a line of logic. For instance, create a new group address, and assign that to the stairway push buttons to trigger the sequencer. Connect that (using a binary trigger module) to an output box with has the command to start (or stop) the sequencer.
One drawback of this simple approach: pushing the buttons does not result in the lights to go on if the HomeServer is not running.
A better but more elaborate approach is to have the push buttons directly turn on the light. Let that 'Light On' telegram (not the feedback!) trigger the sequencer. The sequencer then will turn the light off after a preset time. 10 seconds or so before the end the sequencer can force ('zwangstellung') the light off for a second, then release that forced condition again which then leaves the lights on for that final 10 seconds, allowing a retrigger if needed.
Bram

[ChrisChros]

OK thanks a lot. I thought the sequencer would be a logic building block. Now its clear to me, but it means also I have to read a lot ;-)

[ChrisChros]

Hello Bram,

I tried your second suggested solution and I failed.
I have now 1 group adress (1/2/4) where I have connected the push buttons and the channel from the actor to switch on the light also without HomeServer is running.
And a second group adress (1/2/5) where I have connected only the push buttons, this group adress I use to start the sequence.
Unfortunately this constelation doesent work and the light will not switch off automaticaly.

Can you help me to solve the problem?

Attached some pictures from the logic to start the sequence and the group adresse in ETS.

ChrisChros

[bramlangen]

For a first pass of the logic, try:
- push button sends a '1' only on GA 1/2/4 (this 'ON' action of the button allows a re-trigger of the sequencer, instead of turning the
lights off when the button is pushed a second time if the action is set to 'toggle' ('UM'))
- 1/2/4 is tied to the 'switch on/off' communication object of the stairlight actor channel
- Keep the Experte logic like you show, but with GA 1/2/4 instead of 1/2/5 as input
- Sequencer entry at 180 seconds same as in your example, will turn off the light after 3 minutes
(unless the push button has been activated earlier, which will restart the sequencer)
- The two earlier sequencer entries need control the 'lock' communication object of the stairlight actor channel. First force the light off,
then turn it back on. This will require a separate GA. How this is done depends on your actor. Which brand and type do you have?

I am guessing that how your logic works now, that the sequencer will be retriggered every time the lights turn on, so also at the 166 second step of the sequencer. It would then never reach the end. If you want to see the sequencer action, insert an internal GA at for instance zero seconds, 165 seconds and 167 seconds. Assign it for instance a text or value at those points. You can read out the GA in EIBMON if you assign it some address, say 101/2/4.

If you first set up your logic without the 'lock' (so, without the warning blink just before the end of the cycle), you can at least check to see if the basic function works (turn the light on by pressing the switch, then off after a specific period by action of the sequencer). Then you can insert the blinking action as a next update.

Bram

[ChrisChros]

I have a MDT AKS actor and an ABB SA/S8.16.2.1.

[bramlangen]

For the AKS this should work, attached is how I have the switch on/off and the lock tied to this particular light which also has a 'blinking' function. So, should work in your case too.

[ChrisChros]

ok thanks a lot for you help, now it works.
but one question. Why is it necessary to use the "lock" communication object instead of the normal "on and off" object?

If the actor has no lock object is there another possibility to realize this approach?

[bramlangen]

Well, the idea is to have this function work without the need for the HS. If the HS were to be down, or rebooting, the staircase light still should go on if someone presses the switch. This means that the switch must send the 'ON' telegram for the light. This is the critical function (at least, for a staircase). Secondarily, the HS will see this telegram as well, and start the sequencer.

If the sequencer would use the same GA, then it would re-trigger itself when sending the ON telegram after a blink. The light then would never go off, it would be a perpetual loop.

Since your actor has this 'lock' function, you can force the light to go off, and back on when the lock is released, without sending the same GA as the switch did.

To allow for an extended outage of the HS, you can for instance configure a long press of the same button to send an 'OFF' telegram.

You also should include a line of logic to trigger the sequencer if the light is on when a reboot occurrs - that way, the normal time-out procedure for the staircase light will be followed.

Bram

[bramlangen]

Regarding your second question: you can add a block ('Sperre') to your logic, normally open. Have the sequencer block it at 165 seconds, along with the OFF signal, then release it again at 167 seconds. It may also work if you make the release the second entry at 166 seconds. Either way, you would have a short period that a press of the button would not be seen. If someone happens to press right then, the light will not blink again but will go out shortly after.

Come to think of it: if someone presses that button when the lock is on, the sequencer would restart but not release the lock of the actor channel until much later. So, the release also should also be included at time zero of the sequencer.

Bram