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 February 24th, 2016   #1
prwatE120
Task Group Member
 
Join Date: Jun 2006
Posts: 180
Default NACK Code to use for Subdevice that has no data for requested PID?

A further complication in the use of NACK reason codes applies to the case whereby not all subdevices can meaningfully reply to all of the PIDS listed as "supported" by subdevices.

For example, I have multiple subdevices, only some of which can support CURVE. But as stated in the standard, there is only one list of supported PIDs for subdevices. (essentially the superset of all PIDS supported by all subdevices).

So it follows that a message such as GET:CURVE sent to Subdevice 001 could respond with NACK: Unknown PID and the same message sent to SubDevice 002 could respond with the CURVE detail.

I cannot use the NACK : ACTION NOT SUPPORTED from E1.37-2 since it specifically refers to use with SET commands.

Is there another or better NACK reason code to use ?

So for a controller to build a complete picture of which messages can be sent to which subdevices requires trial and error of each PID with each Subdevice.

Which is likely to be slower than fetching a list of suported PIDS for each subdevice and allowing them to be different.
prwatE120 is offline   Reply With Quote
Old February 24th, 2016   #2
ericthegeek
Task Group Member
 
Join Date: Aug 2008
Posts: 355
Default

Asymmetrical Sub-devices have long been a grey area. The problem you're raising is similar to when you have a dimmer rack with both dimmer and relay modules installed. There are PIDs that make sense for some modules, but not for other modules.

I think the best you can do is declare the superset of all PIDs in the Supported Parameters list, and when an inapplicable PID is sent, NACK it with Unknown PID.

Sub optimal to be sure, but the best you can do with the current doc. In a future rev, perhaps allow each sub-device to declare a different list of PIDs?
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
What NACK to use for messages sent to Subdevices ? prwatE120 RDM Interpretation Questions 0 February 24th, 2016 05:08 PM
SubDevice Required PIDs LarryDew RDM General Implementation Discussion 1 March 25th, 2014 08:27 PM
Subdevice labelling question berntd RDM General Implementation Discussion 13 August 15th, 2013 11:13 PM
PARAMETER_DESCRIPTION data type semantics tim_ecue RDM Interpretation Questions 4 October 14th, 2009 10:47 AM
Reset sensor data of all sensors sjackman RDM Interpretation Questions 1 January 20th, 2008 06:47 PM


All times are GMT -6. The time now is 10:13 AM.


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