![]() |
|
RDM Interpretation Questions Discussion and questions relating to interpreting and understanding the E1.20 RDM Standard. |
|
Thread Tools | Search this Thread | Display Modes |
![]() |
#1 |
Task Group Member
Join Date: Aug 2006
Posts: 15
|
![]()
I have come across an interesting discovery behavior that the standard does not appear to address.
The DISCOVER_UNIQUE_BRANCH command is always supposed to be sent to the broadcast address: 0xff ff ff ff ff ff. However, what is supposed to happen if the DISCOVER_UNIQUE_BRANCH is sent to a specific UID as the destination address? This is obviously wrong on the part of the controller, but it is something that the RDM Integrity software does. It sends a discovery command addressed to the specific UID of the responder and it sets the parameter data (upper and lower bounds) for the same UID after it has narrowed things down to the single device. There are three possible routes to take in my mind: 1. Respond with a standard discovery response. 2. Do not respond. 3. Respond with a NACK format error response. My products take route 2 as I have received an illegal command. I'm open to hearing thoughts from others on how this situation should be addressed. Last edited by Milton Davis; August 1st, 2024 at 01:59 PM. Reason: Incomplete paste |
![]() |
![]() |
Bookmarks |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Addressing Universes on RDM: Manufacturer PID V ENDPOINT_TO_UNIVERSE | Thierry Dupont | RDM General Implementation Discussion | 1 | November 20th, 2020 01:37 PM |
DMX Addressing when Footprint is Zero | Mark_C | RDM General Implementation Discussion | 8 | January 17th, 2010 10:47 AM |
Auto DMX Addressing via RDM ?! | chamber | RDM General Implementation Discussion | 12 | November 11th, 2009 12:47 PM |
Figure 7-2: Device Discovery Process | mike_k | RDM General Implementation Discussion | 2 | October 1st, 2009 02:28 PM |