Buttons and Coupler:
First consider, how you as a user want to use the buttons:
- Do you have a real switch and use a Push Button Coupler?
- Do you really need "Long Press" or "Double Press"?
- Do you need the "Long Press Repeat" mode?
Using a real switch
Here you only use the "Switch On" and "Switch Off" event ports or the "Is Pressed" state of the DALI Button block. In the button properties in the Setup Tab switch off all events except "Pressed Event" and "Released Event".
Using "Press only"
These are the same settings as for switches. You can react to the "Is Pressed" state or the "Pressed Event" and "Released Event".
The advantage: the system will react immediately without a delay.
Using "Long Press"
If you want to use "Long Press" and "Short Press" with the same button in order to have two possible actions with the same button, then you need to know:
- the button or pbc needs to distinguish between a "Short Press" or a "Long Press", this will take time.
- The "Short Timer" is used. It should be set in a range between 260ms to 500ms. This depends on the group of people that operates the button.
- With a setting of 260ms it takes ~1/4s to detect a "Long Press". But that is also the time, that you may not exceed with pressing and releasing the button to create a "Short Press" event.
- In opposite to the "Press only" mode above, the "Short Press" event is fired only when the button is released (i.e. not immediately).
- Do not use the "Long Press Repeat" event, except you know, what you are doing. When wrong configured, it can flood the DALI bus. And repeated events can be also generated by a Periodic Trigger block directly in the workflow without additional traffic on the DALI bus.
Here you only use the "Short Press", "Long Press Start" and "Long Press Stop" event ports of the DALI Button block. In the button properties in the Setup Tab switch off all events except "Short Press Event", "Long Press Start Event" and "Long Press Stop Event".
Please note that the "Is Pressed" state of the DALI Button block will react delayed.
Using "Double Press"
If you want to use "Double Press", "Long Press" and "Short Press" with the same button in order to have three possible actions with the same button, then you need to know:
- the button or pbc needs to distinguish on the one hand between a "Short Press" and a "Long Press" and on the other hand between a single and a "Double Press". This will take more time than in the scenario above.
- The "Short Timer" is used. It should be set in a range between 260ms to 500ms. This depends on the group of people that operates the button.
- With a setting of 260ms it takes ~1/4s to detect a "Long Press". But that is also the time, before a "Double Press" can be detected.
- The "Double Timer" is used. It should be set in a range between 160ms to 300ms. This depends on the group of people that operates the button.
- With a setting of 130ms it takes an additional ~1/8s to detect a "Double Press".
But that is also the time, where you have to press the button a second time to create a "Double Press" event.
- In opposite to the "Press only" mode above, the "Short Press" event is fired, when the button is not pressed a second time after being released and the "Double Timer" is expired.
- Do not use the "Long Press Repeat" event, except you know, what you are doing. If configured incorrectly, it can flood the DALI bus. And repeated events can also be generated by a Periodic Trigger block directly in the workflow, without additional traffic on the DALI bus.
Here you only use the "Short Press", "Long Press Start", "Long Press Stop" and "Double Press" event ports of the DALI Button block. In the button properties in the Setup Tab switch off all events except "Short Press Event", "Long Press Start Event", "Long Press Stop Event" and "Double Press Event".
Please note that the "Is Pressed" state of the DALI Button block will react delayed.
Using other combinations of the events and remarks
Using other combinations than those above, might reduce events, but will not reduce the specific delays caused by the timers.
Also the "Is Pressed" state will no longer work in the correct way. Then at least activate "Pressed Event" and "Released Event".
The "Switch On" and "Switch Off" ports of the "DALI Button" workflow block are coupled with the "Is Pressed" state. These will not only react on the "Pressed Event" and the "Released Event", but consider all incoming button events.