- Welcome to the RDM General Implementation Discussion Forum
- Who besides me is working on RDM equipment?
- Reference Platform
- Forum Tips -- Email Subscribe
- RDM Diagram
- RDM V1.0 and Art-Net
- Confusion about versions
- Minor coffee oops
- Slot Label Code
- RDM Appendix A #define header file attached
- ASN.1 description of RDM
- Checksum curiosa
- Anybody actually doing any opensource RDM design
- Discovery Checksum Problem Analysis
- Sensor string tables
- RDM Generator needed
- Discovery Response Preamble
- RDM Test Equipment?
- RDM PLUGFEST LONDON
- Packet Captures?
- RDM Data Exchange Capture for Book?
- LDI 2007
- Broadcasting to a device model
- RDM E1.20 Draft Errata
- Open Source RDM Project
- Anyone with Coemar?
- Master Fader accross Rdm implementation Question
- Personality & Subdevices
- Auto DMX Addressing via RDM ?!
- When is a different start code allowed?
- Incremental Discovery
- RDM and lighting designers
- ACK_TIMER Handling
- Partial RDM implementation?
- Simple dimmer error reporting
- ESTA Announces RDM Interoperability Plugfest
- RDM and Dimmers
- Uniquely defining the RDM response of devices
- Product Marking for RDM Compliance
- Captured RDM packets
- RDM/DMX Performance
- AVR Responder Lib tested with ENTTEC
- RDM Discovery - Effect of Manufacturer IDs
- RDM Plugfest Back by Popular Demand
- Firmware download
- PDL size and manufacturer specific parameter ID's
- Master list of RDM Product IDs
- capture & playback preset
- Additional Sensor Unit Defines - Table A13
- Figure 7-2: Device Discovery Process
- Sensor type and Sensor unit for DMX rate question
- Sensor type and Sensor unit for No of Phases question
- How should I best implement a dimmer?
- Controlling PWM freq. using RDM
- STATUS_MESSAGES
- Additional Status Message ID request?
- QUEUED_MESSAGE - ?
- Manufacturer Specific Pids
- ESTA Control Protocols Plug Fest Returns in January!
- When to use Queued Msg VS Status Msg
- DMX Addressing when Footprint is Zero
- Timing out IDENTIFY_DEVICE
- Refreshing of paramters need Queued Messages?
- Status Message Markers
- European RDM plug fest
- E1.37-1 RDM Message Extensions document in Public Review
- ESTA Control Protocols Plugfest Returns in July!
- Relative frequency of UID set changes to RDM messages events
- Missing RDM pararameters
- Call for RDM Gear for display at LDI Connectivity Booth and Sessions
- RDM Compatibility Corner at PLASA 2010
- Correctly handling ACK_OVERFLOW
- SENSOR_DEFINITION - User Defined
- Tuneable White: Mapping?
- RDM & DMX frames multiplexing
- Usage of PARAMETER_DESCRIPTION for manufacturer-specific PIDs
- RDM discover driving against dmx input (wrong cabling)
- eCue RDM with a Martin Mac 350
- Device Discovery
- SELF_TEST_DESCRIPTION index range
- RDM Responder Tests are Ready
- RDM Discovery packets
- RDM E1.20-2010 Version Now Available.
- PLASA Plugfest July 2011
- errors when testing discovery
- Handling incorrect messages
- Detailed questions on STATUS_MESSAGES
- IDENTIFY_ORIENTATION
- RDM Icon
- SENS_GPS
- DEVICE_TAGS
- Pixelstring on RDM
- Sub-Device Personalities
- Where to start.....
- European RDM/sACN Developers Conference and Plugfest 2012
- RDM and simple status reporting
- FRAMING ERROR Detection method
- Refreshing "parameter_description" ?
- Refreshing "parameter_description" ?
- Wireshark Arnet/RDM/DMX dissector
- RDM Master UID assignment question
- personalities and footprints
- Trying to run the automated tests
- Units in Status Messages
- RDM Firmware Uploads
- status error queued?/status id definnition
- European RDM/sACN Developers Conference and Plugfest 2013
- Discovery procedure clarification
- RDM and DMX512 will soon be retired!
- Differences in current OLA RDM Responder tests?
- Errors and Sub Device All Call
- Subdevice labelling question
- Disc_Unique_Branch response
- RDM Responder tests updated
- QUEUED_MESSAGE - must controllers support this?
- Enttec RDM USB Pro not decoding get response
- European RDM/sACN Developers Conference and Plugfest 2014
- Request Call for New PIDs!
- new PID suggestion: disable
- new PID suggestion: pan/tilt lock
- Sensor Defintion/Support Parameters
- new PID: comms_status_sc0
- new PID: last active port on splitter
- SubDevice Required PIDs
- PRESET_PLAYBACK and Non volatile memory
- Table C-2
- New PID "Slot Labels"
- New PID "CURVE DEFINITION"
- European RDM/sACN Developers Conference and Plugfest 2015
- Second configurable DMX address
- New PID: IDENTIFY_DEVICE_WITH_TIMEOUT
- New RDM Expansion PIDs doc in Public Review
- RDM Implementation Requirements
- Answer for unsuspected queries
- Time precision for *_HOURS
- RDM Responder Tests and background DMX
- What is the genral opinion about using ACK_TIMER for...
- UID / EUID convertor
- Non-ASCII Characters
- DMXter4 says "not responding"
- What is range of typical Controller traffic?
- Integrity software (Goddard, Jese Controllers)
- Responder help
- GET_STATUS_MESSAGES for fault reporting
- Responder is fully operational!
- Help needed for a responder
- Frequence min responder
- Does controller need it's UID and support any PIDs?
- How suitable is DMX/RDM for architectural lighting/home automation applications
- RDM on Arduino
- European RDM and sACN Developers Conference and Plugfest 2016
- RDM Hub Implementation
- How should master handle receiving DMX after sending request?
- Adressing the RDM
- change parameter setting
- European RDM and sACN Developers Conference and Plugfest - 2017
- How to handle DMX Footprint overrun
- Enable/Disable RDM?
- DMX_PERSONALITY
- RDM logo usage
- 2 sets of personality
- RDM logo
- same Software Version ID for different Model IDs ?
- Possible to use RDM to START a channel at the END of a fixture?
- PARAMETER_DESCRIPTION
- DMX
- OLA server error
- RDM repeater
- New C++-oriented `rdmconst.h` header
- InvalidDiscoveryPID: FAILED
- RDM Emulation (with ArtRDM)
- Tunable White RDM fixture
- Sensor commands
- Discovery response format
- Addressing Universes on RDM: Manufacturer PID V ENDPOINT_TO_UNIVERSE
- Status Messages
- E1.37-5 URL parameters
- Slot_Info / Slot ID Type-Slot Category/ID implementation issue
- Discovery response not recognized
- Help understanding an rdm response
- New SI prefixes
- Changing DMX512 footprint
- For developing a "not fast" RDM proxy hardware, use ACK_timer or other method?
- 8811E High-Speed RDM Decoder IC — Compact RDM Luminaire Design Solution
- E1.37-4 File Transfer Control