![]() |
|
|||||||
| RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product. |
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
|
|
#1 |
|
Administrator
|
Jamie,
The intent of the PARAMETER_DESCRIPTION message was for it to only be used to describe very basic GET/SET parameters for a single function as these are very common and easy to understand. Every manufacturer tends to have those menu settings that are specific to their product, so this was an attempt at addressing that. As a consequence of that this message was intended to be used where there are no other modifiers in the GET request or the SET response message that would need to be specified. For the situation you describe where you want to get/set curves for individual dimmer channels then it would make the most sense for the dimmers to be implemented as sub-devices. The sub-device number would then be used to specify which "channel" rather than putting it in the PD area as well. Hope this helps clarify.
__________________
Scott M. Blair ![]() RDM Protocol Forums Admin |
|
|
|
|
|
#2 |
|
Junior Member
Join Date: Jul 2009
Location: Brisbane, Australia
Posts: 3
|
Thanks for your answer scott.
Unfortunately not all manufacturers think the same way you do, otherwise things would be easier! To get around the problem, I'll just require the user to select how many bytes they want to send with a manufacturer specific GET command. It's not the best solution, but at least it's generic and should work with most devices. Regards, Jamie. |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Command Class / Parameter ID mismatch handling | dangeross | RDM Interpretation Questions | 2 | April 16th, 2009 01:39 PM |
| RDM Discovery - Effect of Manufacturer IDs | zshenker | RDM General Implementation Discussion | 4 | April 10th, 2009 02:30 PM |