We've launched our new site at www.openlighting.org. This wiki will remain and be updated with more technical information.
Difference between revisions of "Using the RDM Test UI"
From wiki.openlighting.org
(→RDM Responder Tests) |
(→Starting the Test Server) |
||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== RDM Responder Tests == | == RDM Responder Tests == | ||
Revision as of 19:51, 9 November 2012
Contents
RDM Responder Tests
Warning: The tests send SET messages to the broadcast UIDs. This means that they will change the start address, device label etc. of all devices connected to the controller. Think twice about running this on your production lighting rig.
Procedure
Saving the Logs
The logs can be saved for offline analysis.
RDM Responder Publisher
The RDM Responder Publisher can be used to collect information about a device (using RDM) and then publish that information to the http://rdm.openlighting.org site. This allows manufacturers to quickly list their responders on the site.
The following information is collected:
- Device Model ID
- Manufacturer ID
- Product Category
- Personalities (label, index & DMX slot count)
- Sensors
- Software Version Label
- Supported Parameters (IDs only)
Procedure
Under the 'RDM Responder Publisher' tab, select the universe to use.
Reporting Bugs
If an error occurs while running the tests or collecting RDM responder information a dialog box will be displayed. Clicking on the 'Report Bug' button will open a new window and allow you to submit a bug report. The bug tracking system is hosted on Google Code, so you'll need to sign in with a Google account.
All other bugs can be reported at http://code.google.com/p/open-lighting/issues/entry
