Table of Contents
Advertisement
Programming
Programming Hints
The programmer should make the following assumptions and write the interface software based on
these assumptions:
1. Assume all lights are offline on startup. The device will notify the main program of the state of
every light that is configured when the ALD-D48 connects to the master. It will not notify for
lights that are offline (since this is assumed). This cuts down on the event traffic within
NetLinx for systems that are not fully populated with 48 lights. After initialization, if a light
was online and goes offline this will be reported immediately.
2. Assume all channels are off on startup. This implies that the programmer should consider all
lights to be off unless told otherwise.
3. Assume all levels have a value of zero. This implies that the programmer should consider all
lights to be off unless told otherwise.
4. The programmer should assume that the intensity level range for a light is 0-100%. From a
programming perspective this is a good assumption and the code should reflect it. However, in
reality the ALD-D48 only has 32 unique intensity levels. So don't be surprised when you
change the intensity level of a light to 50% and 48% is what gets reported.
5. When ramping the feedback will be reported faster than the actual values on the light. So the
device may report 75% when the light is actually at 60%. The light will catch up in a very short
period of time. This is due to the timing at the hardware level of the ALD-D48.
6. When setting the intensity level of a light using a fade time the status of the light will be
reported immediately without consideration of fade time. For example, if you command a light
to go to 80% over 10 seconds it will report 80% immediately and nothing else will be reported
after the 10 seconds expires.
24
ALD-D48 Network Lighting Solutions
Advertisement
Table of Contents
