How should I best implement a dimmer? - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · October 7th, 2009

Slot description isn't going to be much help. It will let the responder describe itself to the controller, but the Slot Description PIDs don't allow you to configure the device.

I would implement what you're describing with personalities and sub-devices. Present a sub-device for each channel. Each of those sub-devices would have 4 personalities to define its behavior (On, Off, Dim, and Switch). The advantage of doing it this way is that almost all controllers allow you to set the personality of a responder, and you can give each personality a human-readable name string that makes it clear what each one does.

berntd · October 7th, 2009

Hello

Thanks for that. It realy helps me a lot asI would not have thought of this.

If I understand this correct then:

Discovery Mute/Unmute needs to report a sub device flag(Bit1) = 1

DEVICE_INFO reports how many sub-devices are present.

SUPPORTED_PARAMTERS reports the paramters for the root (subdevice = 0) device AND if addressed to subdevice x, different paramters as per the subdevice.

For each subdevice, DMX_PERSONALITY / PERSONALITY_DESCRIPTION are then used to set the different modes.

I suppose I then do not need SLOT_DESCRIPTION / SLOT_INFO at all?

Anything else required to make this work for the controllers out there?

Kind regards
Bernt

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
What is the basic requirement to implement RDM?	wcai_cypress	RDM Physical Layer/Hardware Discussion	24	July 8th, 2009 08:26 PM
Simple dimmer error reporting	Milton Davis	RDM General Implementation Discussion	3	November 7th, 2008 11:15 AM

October 7th, 2009	#1
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	Slot description isn't going to be much help. It will let the responder describe itself to the controller, but the Slot Description PIDs don't allow you to configure the device. I would implement what you're describing with personalities and sub-devices. Present a sub-device for each channel. Each of those sub-devices would have 4 personalities to define its behavior (On, Off, Dim, and Switch). The advantage of doing it this way is that almost all controllers allow you to set the personality of a responder, and you can give each personality a human-readable name string that makes it clear what each one does.

October 7th, 2009	#2
berntd Senior Member Join Date: Jan 2008 Posts: 102	Hello Thanks for that. It realy helps me a lot asI would not have thought of this. If I understand this correct then: Discovery Mute/Unmute needs to report a sub device flag(Bit1) = 1 DEVICE_INFO reports how many sub-devices are present. SUPPORTED_PARAMTERS reports the paramters for the root (subdevice = 0) device AND if addressed to subdevice x, different paramters as per the subdevice. For each subdevice, DMX_PERSONALITY / PERSONALITY_DESCRIPTION are then used to set the different modes. I suppose I then do not need SLOT_DESCRIPTION / SLOT_INFO at all? Anything else required to make this work for the controllers out there? Kind regards Bernt