![]() |
|
|||||||
| 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 2008
Posts: 390
|
We run into this question with all of the PIDs that are "conditionally required" (DMX_START_ADDRESS, PARAMETER_DESCRIPTION, etc.). You can make a legitimate argument both ways.
In the real world, declaring extra PIDs in the list of supported parameters is unlikely to break any RDM Controllers. Controllers have to assume that new PIDs will be added in the future, so the extra information should just be ignored. Thus I would suggest including the _DESCRIPTION PIDs in the list of supported parameters. |
|
|
|
|
|
#2 |
|
Junior Member
Join Date: Apr 2014
Posts: 2
|
Thank you ericthegeek, that makes sense
![]() I would say it's the same for DMX_PERSONALITY_DESCRIPTION, which is not "conditionally required" in Table A-3 but should be, and I often see it in supported parameters. |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Sensor Defintion/Support Parameters | gthaliath | RDM General Implementation Discussion | 28 | July 18th, 2026 09:33 AM |