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.

Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old April 30th, 2012   #1
Task Group Member
Join Date: Aug 2006
Posts: 28
Default Sub Device required PIDs

At the plug-fest Bob presented an interesting point: Do Sub Devices need to implement the minimum required PIDs list?
My common sense answer was yes, but review of the document suggests this is not a given.
The root device must support the 'required pids'. Sub Devices must all support the same set of pids which can differ from the root.
However 9.2.3 is open to interpretation. The problem is caused by the phrase 'which additional messages...'. The word additional implies 'in addition to the minimum required pid list' but could also be read to mean 'in addition to the SUPPORTED_PARAMETERS pid.
So there are two possibilities:
a) Sub devices shall at minimum implement the required pid list along with SUPPORTED_PARAMETERS.
b) Sub devices shall at minimum implement the SUPPORTED_PARAMETERS pid.
wayne@artisticlicence.com is offline   Reply With Quote


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
Required handling of sequences of RDM broadcast cmds eldoMS RDM Timing Discussion 9 August 23rd, 2011 10:40 AM
Is there a minimum required PID list for sub-devices? p_richart RDM Interpretation Questions 4 November 7th, 2008 02:04 PM

All times are GMT -6. The time now is 06:09 AM.

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