Subdevice labelling question

[sblair]

Bernt,

We're still alive and kicking here! First off, you can implement a GET_COMMAND only without allowing a SET_COMMAND for a given PID. You'll notice Table A-3 states "Get Allowed / Set Allowed", not required.

Given you're trying to overcome the limitations of someone else's implementation I would probably go that route rather than changing the Device Model Description, as what you suggested there would go against the requirements in the standard that for a given Device Model ID that the Device Model Description is always identical. The intent with that is that we explicitly didn't want to have controllers pulling redundant messages from every device on the network when they are all the same.

I would also suggest getting in contact with the folks at ETC on what would help make their implementation more usable. I'm not certain how they are dealing with the same issue themselves as it would seem they would have the same challenges with representing their own products.

[berntd]

Hi

Thanks for the reply!
Good to see that things are still active!
It has been quite a while since I worked on RDM so everything has gone rusty


It has been so long that I can't even remember your name - sorry

Now, how does the controller get told that I will only supporting GET for a command?

I know I have to respond with UNSUPPORTED_COMMAND_CLASS for SET but I can't remember if I have to tell the controller somewhere that I only support GET?

Best regards
Bernt

[sblair]

There's nothing you need to do to alert the controller in advance. As you mentioned you just NACK any SET_COMMANDs with the UNSUPPORTED COMMAND CLASS reason.

Scott

[berntd]

Thanks Scott.

We will also be contacting ETC to see what they think.

Best regards
Bernt