By default out of the box, most products are running in Standalone Mode.
This is a mode in which event messages are interpreted as lighting commands and Broadcast to the bus.
Enable/Disable and Configuration
The described behaviour applies to the following products
- Smart devices version 2.XX
- ECD-only devices like zc-switch / zc-sensor
- Smart Driver Version 0.60 and above.
Standalone Mode is automatically disabled when any of the following conditions are met for the devices ECD:
- The device (ECD) is addressed
- or the Device (ECD) Operating Mode is set to 0
- or The ECD commands INITIALISE, TERMINATE, SET SHORT ADDRESS, WITHDRAW are heard
If The ECD commands INITIALISE, TERMINATE, SET SHORT ADDRESS, WITHDRAW were heard the standalone mode will be disabled temporarily and will reset on a power cycle.
or if the ECG is
- is addressed
- or Has the ECG Operating Mode set to 0
- or The ECG commands INITIALISE, TERMINATE, SET SHORT ADDRESS, WITHDRAW are heard
Then the Standalone mode is not completely disabled. It will stop broadcasting commands onto the DALI line but will continue to function as a standalone device controlling only itself. During this mode commands from another control system will be able to turn the lighting on/off however this does not override functionality such as sensors, which will detect the lighting has been turned on and will turn off the lighting after no movement ( time dependant on settings)
If The ECG commands INITIALISE, TERMINATE, SET SHORT ADDRESS, WITHDRAW were heard the standalone mode will temporarily perform the internal control methodology described above and will reset on a power cycle.
Standalone Mode can be re-enabled by following these steps.
- Reset the short address for the ECG or ECD depending on the mode you want to enable. In some cases you will need to reset both addresses
- Ensure the operating mode of the ECG and ECD is not set to 0
- Reenable the device's standalone mode by either
- Power cycling the device
- or sending ECD command ENABLE APPLICATION CONTROLLER
Note, devices such as the zc-switch and zc-sensor do not support ENABLE APPLICATION CONTROLLER
Configuration of a device depends on what hardware is supported and what version the product is;
Only command target is configurable as follows:
ADD TO DEVICE GROUP 0 - 15: If a group is configured, the device will target the lowest group configured
REMOVE FROM DEVICE GROUP 0 - 15: If the device is not targeting any groups, it will BROADCAST.
Configuration depends on what hardware is present on the device:
Device can be fully configured via the Express app.
Hold time, warn time, warn level, and many other things can be configured via the IR remote.
Using Edali commands, all aspects of Standalone Mode can be configured.
The commands which are sent in Standalone Mode depends on the instance which is generating them.
By default, these commands are targeting BROADCAST, but GROUP 0 - 15 can also be configured as the target. How this is configured depends on the products features.
A 301 instance sends different commands depending on the last commands sent and the event generated;
Short press event:
Toggles between RECALL MAX/RECALL LAST ACTIVE LEVEL and OFF.
Whether RECALL MAX or RECALL LAST ACTIVE LEVEL are sent depends on FW version.
Long Press and Long Press Repeat:
Sends either UP or DOWN depending on the last direction it was dimming.
If the last command sent was OFF, a Long Press will generate an ON AND STEP UP
A 303 instance sends different commands depending on the last commands sent and the current detection state/time.
When a 303 instance sends a DAPC command, it will also configure the FADE TIME to be fast for fading to a brighter level and slow for fading to a dimmer level.
From the off state, the 303 controller will send an Edali Motion Notification as well as a DAPC 254 (by default).
This starts a default 15min "hold" timer (default depends on FW version).
From a Lighting Command or an Edali Motion Notification:
Device counts down a 15min "hold" timer. When this timer expires, the device will send DAPC 1 by default (default depends on FW version), and start a 5min "warn" timer (default depends on FW version).
If motion is detected during the "hold" timer, the device will send out a new Edali Motion Notification to the bus.
From the Warn timer
Device counts down a 5min "warn" timer. When this timer expires, the device will send DAPC 0.
If motion is detected during the "warn" timer, the device will tread this motion as though it came from an OFF state.
Article is closed for comments.