Responder is fully operational!
I can't express enough how helpful it is to have a place to go for help when things aren't working. It would have been very difficult for a non-RDM guy like me to get the nuances of some of this without the help I got here.
Thanks again to Eric for his patient responses. Here's my final list of PIDs: DISC_UNIQUE_BRANCH DISC_MUTE DISC_UN_MUTE STATUS_MESSAGES STATUS_ID_DESCRIPTION SUPPORTED_PARAMETERS PARAMETER_DESCRIPTION DEVICE_INFO DEVICE_MODEL_DESCRIPTION MANUFACTURER_LABEL SOFTWARE_VERSION_LABEL DMX_START_ADDRESS SENSOR_DEFINITION SENSOR_VALUE IDENTIFY_DEVICE RESET_DEVICE TUNGSTEN_FADE_SETTING (mfgr custom) 8_16_BIT_DMX_SETTING (mfgr custom) The Goddard DMXter4A plus the Benjamin Electrics Integrity software ran a total of 3198 tests on my Responder that all passed, no failures, warnings, advisories, or timing errors! I'm planing on going to a Plugfest the next time there's one in North America. I suspect there's still some issues in this implementation that I''l bet the guys in the trenches can find. Thank you rdmprotocol.org! DougJ / BlackTank |
Thanks for the followup post. It's always nice to hear how things turned out.
I want to make sure you're aware of the E1.37-x documents as well. Each E1.37 document defines additional PIDs that can be used with RDM. I'm not sure what "TUNGSTEN_FADE_SETTING" does, but you might find that the dimmer-curve setup PIDs in E1.37-1 will accomplish something similar without having to use a manufacturer-specific PID. |
All times are GMT -6. The time now is 10:02 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.