E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM General Implementation Discussion
Register FAQ Community Calendar Today's Posts Search

RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product.

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old December 18th, 2018   #15
majid
Member
 
Join Date: Oct 2017
Location: Turkiye
Posts: 38
Default

Quote:
Originally Posted by peternewman View Post
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.

Quote:
Originally Posted by sblair View Post
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.
majid is offline   Reply With Quote
 

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 10:59 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.