...
The flow can be divided into several main parts responsible for the whole functionality. The order of these parts is the same as the flow of the signal in this program, so Part II follows Part I, etc.
Part I (see the flow image) is responsible for detecting the input signals from the control devices e.g. buttons and assigning these signals to tags representing appropriate virtual “areas”. The tags are stored in msg.topic objects.
Example:
Area A, command 1 -> msg.topic = A1
Area C, command 3 -> msg.topic = C3Part II (a switch node)checks in which area has the event been detected. If the event comes from the original area of the command then Part C is skipped.
Part III checks the state of the reed switches (find reed switches K1 and K2 at the top of the flow). The message passes if all the switches are open between the sending and receiving areas.
Part IV checks the command to be triggered on a group of luminaires.
| Info |
|---|
During the routing, the msg.topic is reserved for this functionality. So if you need msg.topic for other action, place that action after the routing nodes. |
What can I modify?
Select the reed switches and buttons in appropriate dali2devs nodes.
Define actions to be triggered in vertex action nodes after Part IV.
Test the flow using inject nodes.
Add more reed switches and areas in the flow if you have more of these in your office.
Add extra functions and areas if you want to. All you need to do is to edit the tags and filtering of the messages. The tags can be thought of as a sort of matrix: x-axis = area code, y-axis = command number code, etc. Messages can be filtered based on any parameter of the tags.
Related articles
| Filter by label | ||||||
|---|---|---|---|---|---|---|
|