PDA

View Full Version : PRESET_PLAYBACK of a non programmed Scene


docsale
April 4th, 2014, 04:29 AM
Hi,

what is supposed to do a responder device if the controller send a PRESET_PLAYBACK command with a Scene number supported but not programmed?

- Answare NACK_OUT_OF_RANGE and stays in the current status: probably this is the right behaviour if the Scene number is out of supported range
- Answare ACK and stays in the current status: in this case the controller doesn't see any error and thinks everything is ok
- Any other possibility?

If controller implements the E1.37 it should know if a scene is programmed throught PRESET_STATUS command, but only few controller are compliant with E1.37!

Any suggestion?

ericthegeek
April 4th, 2014, 12:54 PM
- Answare NACK_OUT_OF_RANGE and stays in the current status: probably this is the right behaviour if the Scene number is out of supported range


This is acceptable behavior.


- Answare ACK and stays in the current status: in this case the controller doesn't see any error and thinks everything is ok


This is not a good idea. It can confuse the user if they tell it to change presets, but nothing happens.

If it were my product, I would probably have a default look recorded into every scene. This way there's always something to play back. For a dimmer, it would simply be all channels off. For an LED fixture I'd have various colors and patterns. When the user records their own scene, it records over the default looks.


If controller implements the E1.37 it should know if a scene is programmed throught PRESET_STATUS command, but only few controller are compliant with E1.37!


I've only seen a few controllers with E1.37. I suspect we'll see more updated to support it over the next year or two.

prwatE120
April 8th, 2014, 03:32 PM
Best use NACK : DATA_OUT_OF_RANGE