Thread: DMX_PERSONALITY
View Single Post
Old June 29th, 2017   #2
ericthegeek
Task Group Member
 
Join Date: Aug 2008
Posts: 362
Default

I can certainly understand why you'd like to keep the consistency between different generations of the hardware. But from an RDM standpoint, a different generation with different features would be considered a different model and thus could have different personality behavior.

Unfortunately there's no perfect solution here. Personalities have to be consecutively numbered, so controllers will not expect there to be gaps in the numbering. It's quite common for controllers to ask for the PERSONALITY_DESCRIPTION for every personality when the user starts to setup the fixture.

I suppose you could declare all seven personalities, but then NACK when the controller tries to set one that's not supported. If you also set the Description string to "Not Available", then at least the user will have some idea why it's not accepted.
ericthegeek is offline   Reply With Quote