E1.20 RDM (Remote Device Management) Protocol Forums

E1.20 RDM (Remote Device Management) Protocol Forums (http://www.rdmprotocol.org/forums/index.php)
-   RDM General Implementation Discussion (http://www.rdmprotocol.org/forums/forumdisplay.php?f=4)
-   -   new PID suggestion: disable (http://www.rdmprotocol.org/forums/showthread.php?t=1190)

diane January 28th, 2014 11:10 AM

new PID suggestion: disable
I would like to propose a PID for disabling mechanisms. It would have SET and GET capabilities: set would allow you to disable a specific mechanism; get would return a list of mechanisms which are already disabled.

sblair January 28th, 2014 05:23 PM


Can you elaborate a bit more on how you would see this being used and applications where you would use it? I want to make sure we understand it better.

diane January 29th, 2014 07:12 AM

new PID suggestion: disable
We use it for teching automated lights, disabling specific motors (pan, tilt, etc) or determining which are in an error condition, but now that I think about it the command may not have a broad enough application to be useful to others.

ericthegeek January 29th, 2014 10:29 AM

Diane, can your propose a packet format?

Sometime like this?

-Feature number (8-bit)

-Feature number (8-bit)
-Total number of features
-0=Feature not Disabled, 1=Feature Disabled
-32 Character Feature Description string

-Feature number (8-bit)
-0=Feature not Disabled, 1=Feature Disabled

(No data)

diane January 30th, 2014 10:20 AM

new PID suggestion: disable
Hi Eric, that packet format looks great. It covers all of the functionality I had in mind.

ericthegeek January 30th, 2014 10:56 AM

Additional thoughts:
Feature number 0xFF means "All features"

SET for "All Features" can disable/enable all at once
GET for "All Features" is not defined and shall return "Unsupported Command Class"

Features must be numbered sequentially starting at 1.

Feature 0 shall return "Out of Range"

All times are GMT -6. The time now is 07:32 PM.

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