Refreshing "parameter_description" ? - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · March 2nd, 2012

Although the standard doesn't explicitly require it, many RDM implementations will assume that the response to GET PARAMETER_DESCRIPTION for a given PID will be constant throughout the life of a given responder.

The exact behavior will depend on the specific controllers and responders that you are working with. Some controllers will request PARAMETER_DESCRIPTION for all manufacturer specific PIDs upon initialization, while others will only get the information when needed.

Your best option is to find a way to implement the functionality you need in a way that doesn't require changing the PARAMETER_DESCRIPTION response. You could use multiple PIDs, or some other method.

To give any more detailed advice, we'll need more information about what you're trying to accomplish.

As a side note: Make sure you've read section 6.2.10.2 of the E1.20-2010 document. Manufacturer specific PIDs have to have the same "meaning" across all products from a given manufacturer.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Usage of PARAMETER_DESCRIPTION for manufacturer-specific PIDs	R.Schladör	RDM General Implementation Discussion	9	September 26th, 2018 12:04 PM
Refreshing "parameter_description" ?	theguenni	RDM General Implementation Discussion	0	February 29th, 2012 02:36 PM
Refreshing of paramters need Queued Messages?	berntd	RDM General Implementation Discussion	33	May 25th, 2010 02:09 PM
PARAMETER_DESCRIPTION data type semantics	tim_ecue	RDM Interpretation Questions	4	October 14th, 2009 10:47 AM

March 2nd, 2012	#3
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	Although the standard doesn't explicitly require it, many RDM implementations will assume that the response to GET PARAMETER_DESCRIPTION for a given PID will be constant throughout the life of a given responder. The exact behavior will depend on the specific controllers and responders that you are working with. Some controllers will request PARAMETER_DESCRIPTION for all manufacturer specific PIDs upon initialization, while others will only get the information when needed. Your best option is to find a way to implement the functionality you need in a way that doesn't require changing the PARAMETER_DESCRIPTION response. You could use multiple PIDs, or some other method. To give any more detailed advice, we'll need more information about what you're trying to accomplish. As a side note: Make sure you've read section 6.2.10.2 of the E1.20-2010 document. Manufacturer specific PIDs have to have the same "meaning" across all products from a given manufacturer.