|
|
|||||||
| RDM Interpretation Questions Discussion and questions relating to interpreting and understanding the E1.20 RDM Standard. |
|
|
Thread Tools | Search this Thread | Display Modes |
June 8th, 2026
|
#5 |
|
Task Group Member
Join Date: Aug 2008
Posts: 390
|
Section 7.5 in -2010 probably should have said BROADCAST_ALL_DEVICES_ID rather than ALL_DEVICES_ID. That was the intent anyway.
I don't think there is a consensus best practice for how to handle vendorcast discovery beyond the “don't crash” advice I gave above. |
|
|
| Bookmarks |
|
|
Similar Threads
|
||||
| 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 |
Threaded Mode