E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM General Implementation Discussion

RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product.

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old July 30th, 2013   #2
sblair
Administrator
 
Join Date: Feb 2006
Posts: 441
Send a message via AIM to sblair Send a message via MSN to sblair
Default

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.
__________________
Scott M. Blair
RDM Protocol Forums Admin
sblair is offline   Reply With Quote
 

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 12:20 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.