Timing out IDENTIFY_DEVICE

[peternewman]

Originally Posted by majid

Maybe DMX signal would be ignored while IDENTIFY_DEVICE is set ...

I'll just echo what others have said majid, and also point out IDENTIFY_MODE in E1.37-1 which would be a better way to control whether the DMX signal is ignored (in loud mode) or not.

A value of 0x00 represents a “Quiet Identify” mode. This would typically be used for flashing a front panel indicator or display to visually identify the device discretely in a show situation with an audience present.

A value of 0xFF represents a “Loud Identify” mode. This would typically be used for a highly visual indication such as strobing a lighting fixture or outputting fog in a non-show situation without an audience present.

[majid]

Originally Posted by peternewman

I'll just echo what others have said majid, and also point out IDENTIFY_MODE in E1.37-1 which would be a better way to control whether the DMX signal is ignored (in loud mode) or not.

Thanks for comments Peter.

Originally Posted by sblair

Majid, it really all depends on your market and customer requirements as well as type of product.

DMX signal loss behavior is different in almost every product...

I think even with IDENTIFY_DEVICE=0 , DMX signal timeout behaviour of LED fixtures maybe confusing.
I imagine during an RDM setup session, controller sets only one of responders IDENTIFY_DEVICE=1 and clears other responders.
after desired timeout , the one with IDENTIFY_DEVICE=1 remains in identify mode and all other fixtures with IDENTIFY_DEVICE=0 start glowing demo/default mode and bother user sight.

to avoid this situation, maybe the responder somehow ought to detect the RDM setup is runnig and never start demo/default mode even with IDENTIFY_DEVICE=0
for example after receiving DISC_MUTE command, the responder would cancel demo mode until next restart. etc.

[ericthegeek]

Originally Posted by majid

for example after receiving DISC_MUTE command, the responder would cancel demo mode until next restart. etc.

Many systems will have discovery disabled during showtime, so you can't use DISC_MUTE to determine whether there's a RDM controller present.

If you want to do something like this, you might want to consider monitoring for *any* RDM traffic.