How should a device with footprint=0 respond to setting the DMX start address? - E1.20 RDM (Remote Device Management) Protocol Forums

peternewman · December 17th, 2018

Actually re-reading your post, I'd perhaps suggest there are three states, and maybe that's where our disagreement comes from:

Transient:
Failed this time, may work later, worth retrying
E.g. Proxy Reject, Buffer Full
I'd probably put hardware error in here too, but perhaps retry fewer times than some of the other errors

Final:
Won't work without changes to the packet or potentially external changes
E.g. write protected, data out of range

Terminal (other, better names are available I'm sure):
Will never work without changes to the packet
E.g. format error
Personally I would put unknown PID/unsupported command class in this section, I believe you feel it should go in the one above?

E.g. setting the DMX address to 510 will fail (or at least should) while the fixture is in 10 channel mode, but if we switch it into 1 channel mode, the exact same packet will then succeed. Likewise for a locked/unlocked device, or a slot label request to slot 10 between the two different personalities.

However a set DMX address with a PDL of zero will fail terminally with a format error; it can never work regardless of what we do to the fixture. I think unknown PID/unsupported command class should be in the same category, otherwise I have to keep retrying a set DMX address to see if the fixture has now decided to allow me to do so.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to handle DMX Footprint overrun	RobbG	RDM General Implementation Discussion	3	May 8th, 2017 08:42 AM
change parameter setting	ilek79	RDM General Implementation Discussion	4	January 12th, 2017 09:15 PM
Second configurable DMX address	stefkuhb	RDM General Implementation Discussion	5	October 22nd, 2014 08:17 AM
DMX Addressing when Footprint is Zero	Mark_C	RDM General Implementation Discussion	8	January 17th, 2010 10:47 AM
Sub-device response to SET/GET DMX512 start address	p_richart	RDM Interpretation Questions	2	September 29th, 2006 09:27 AM

December 17th, 2018	#16
peternewman Junior Member Join Date: Oct 2018 Location: London Posts: 11	Actually re-reading your post, I'd perhaps suggest there are three states, and maybe that's where our disagreement comes from: Transient: Failed this time, may work later, worth retrying E.g. Proxy Reject, Buffer Full I'd probably put hardware error in here too, but perhaps retry fewer times than some of the other errors Final: Won't work without changes to the packet or potentially external changes E.g. write protected, data out of range Terminal (other, better names are available I'm sure): Will never work without changes to the packet E.g. format error Personally I would put unknown PID/unsupported command class in this section, I believe you feel it should go in the one above? E.g. setting the DMX address to 510 will fail (or at least should) while the fixture is in 10 channel mode, but if we switch it into 1 channel mode, the exact same packet will then succeed. Likewise for a locked/unlocked device, or a slot label request to slot 10 between the two different personalities. However a set DMX address with a PDL of zero will fail terminally with a format error; it can never work regardless of what we do to the fixture. I think unknown PID/unsupported command class should be in the same category, otherwise I have to keep retrying a set DMX address to see if the fixture has now decided to allow me to do so.