E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM Interpretation Questions

RDM Interpretation Questions Discussion and questions relating to interpreting and understanding the E1.20 RDM Standard.

Reply
 
Thread Tools Search this Thread Display Modes
Old June 11th, 2018   #1
Vinayakadj
Junior Member
 
Join Date: Jun 2018
Posts: 3
Default

Thanks Scott for your reply. I have few more question which really helps me.
1. What would be the source Id for the response generated by Proxied device?. As the message is generated by Proxy should the source ID be Proxy's source ID or it should be the source ID of Proxied device.
2. This question is regarding Binding UID field and Port ID. As per my understanding
If one physical device has multiple logical devices we can bind UID to it. Can you explain me the difference between using a binding UID vs Proxy device? In my implementation of hardware, we have a physical device with multiple logical devices associated with it. Should I choose Binding UID and represent them as the single physical device or should I use Proxy to represent them?

Regards,
Vinayaka D J
Vinayakadj is offline   Reply With Quote
Old June 11th, 2018   #2
ericthegeek
Task Group Member
 
Join Date: Aug 2008
Posts: 390
Default

Quote:
Originally Posted by Vinayakadj View Post
1. What would be the source Id for the response generated by Proxied device?. As the message is generated by Proxy should the source ID be Proxy's source ID or it should be the source ID of Proxied device.

The source address should be the UID of the proxied device.



Quote:
Originally Posted by Vinayakadj View Post
2. This question is regarding Binding UID field and Port ID. As per my understanding
If one physical device has multiple logical devices we can bind UID to it. Can you explain me the difference between using a binding UID vs Proxy device? In my implementation of hardware, we have a physical device with multiple logical devices associated with it. Should I choose Binding UID and represent them as the single physical device or should I use Proxy to represent them?

The binding UID is used when you have a responder with multiple DMX input connectors.



Proxy is used when you have multiple *logical* devices behind a single DMX input connector.



For example, a dimmer rack that has two DMX inputs would use the Binding UID to tell the controller that those two different UIDs are both connected to the same rack. Without this, the controller would believe it's seeing two different dimmer racks.


A color scroller system with a power supply and 8 scrollers would use proxy because you want to controller to recognize it as 9 separate things.


Quote:
Originally Posted by Vinayakadj View Post
In RDM message structure there is a field for Port ID is this port ID same as the binding UID port ID?

No. The Port ID field gives the *controller* port number and only exists in an RDM request. If the controller has multiple outputs it lets you determine which output generated the request.



The Binding UID is used by*responders* to give information to the controller.
ericthegeek is offline   Reply With Quote
Reply

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

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

Similar Threads
Thread Thread Starter Forum Replies Last Post
Proxy dezelectric RDM Interpretation Questions 3 July 20th, 2011 12:29 PM
Uniquely defining the RDM response of devices Andy Macdonald RDM General Implementation Discussion 6 February 9th, 2009 02:24 PM
Multi-devices or sub-devices Fokko RDM Interpretation Questions 4 December 1st, 2006 11:10 AM
Any RDM Responder Devices out there yet? sblair RDM Marketplace Discussion 8 September 20th, 2006 06:03 AM


All times are GMT -6. The time now is 09:22 PM.


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