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 12th, 2018   #12
majid
Member
 
Join Date: Oct 2017
Location: Turkiye
Posts: 38
Default

I am struggling similar situation, I need to define suitable requirement for behaviour for my responder (LED fixture).
Implementing timeout using PERSONLITY seems possible, so that "WITH TIMEOUT" and "WITHOUT TIMEOUT" will be selectable via PERSONALITY.

In fact my question is something else, but I think related to this dıscussion so I decide write here.
I defined requirements as below:

1) with only RDM signal and IDENTIFY_DEVICE = 1, then LEDs will show R-G-B etc.

2) with only DMX signal and IDENTFY_DEVICE = 0, then LEDs will be turned on according to DMX data

3) with both DMX and RDM alternately mixed signal (such as 40 fps = 39 DMX + 1 RDM ) and IDENTIFY_DEVICE = 0 then LEDs will be turned on according to DMX, no change at RDM signal

4) with both DMX and RDM alternately mixed signal and IDENTIFY_DEVICE = 1 then ... my question rise up here!

Maybe IDENTIFY show would be canceled after receiving DMX signal ...
Maybe DMX signal would be ignored while IDENTIFY_DEVICE is set ...

I am not sure since I have no real field experience about RDM.

I appreciate sharing experiences.

Last edited by majid; December 12th, 2018 at 06:53 AM.
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 09:38 PM.


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