PDL size for GET Manufacturer-specific PID - E1.20 RDM (Remote Device Management) Protocol Forums

sergeychk · April 16th, 2020

I'd like to extend my understanding of the 10.4.2 section. For example, Manufacturer-specific parameter data has the fixed length = 1 byte.
Then, testing a software for a controller, I received the Manufacturer-specific PID associated PDL field value = 1 on my lighting fixture.
But provided that PDL in GET_COMAND request must have "0" value, should the lighting device respond "NR_FORMAT_ERROR"?
What PDL field value should set the lighting device, sending SET_COMMAND_RESPONSE to the controller's SET_COMMAND request?
a)SET_COMMAND_RESPONCE with ACK and PDL = 0 (without parameter data)?
b)SET_COMMAND_RESPONCE with ACK and PDL = 1 with parameter data?
To my opinion option "b" corresponds 10.4.2 section better, but I prefer option "a" due to it's compactness.
Plus option "b" may be more suitable for the controller's software realization.
I'm confusing between the above mentioned options because the controller's and the responder's software and firmware realization is very much depending on which option to choose.

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
Swisson support of manufacturer specific PIDs?	jdupre	RDM Marketplace Discussion	2	March 18th, 2017 01:41 PM
PID vs. PDL	erwin	RDM Interpretation Questions	5	May 1st, 2012 12:10 PM
Manufacturer Specific Pids	berntd	RDM General Implementation Discussion	4	November 29th, 2009 02:50 PM
PDL size and manufacturer specific parameter ID's	jamie	RDM General Implementation Discussion	5	July 13th, 2009 12:31 AM

April 16th, 2020	#1
sergeychk Junior Member Join Date: Apr 2014 Posts: 9	I'd like to extend my understanding of the 10.4.2 section. For example, Manufacturer-specific parameter data has the fixed length = 1 byte. Then, testing a software for a controller, I received the Manufacturer-specific PID associated PDL field value = 1 on my lighting fixture. But provided that PDL in GET_COMAND request must have "0" value, should the lighting device respond "NR_FORMAT_ERROR"? What PDL field value should set the lighting device, sending SET_COMMAND_RESPONSE to the controller's SET_COMMAND request? a)SET_COMMAND_RESPONCE with ACK and PDL = 0 (without parameter data)? b)SET_COMMAND_RESPONCE with ACK and PDL = 1 with parameter data? To my opinion option "b" corresponds 10.4.2 section better, but I prefer option "a" due to it's compactness. Plus option "b" may be more suitable for the controller's software realization. I'm confusing between the above mentioned options because the controller's and the responder's software and firmware realization is very much depending on which option to choose.