Discovery procedure clarification - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · March 21st, 2013

How are you determining what PIDs the DMXter is sending? The DMXter should only send a RESET_DEVICE when explicitly told to do so from the "Setup Device" menu, and never from the Discovery menu.

You will see IDENTIFY_DEVICE and DEVICE_MODEL_DESCRIPTION packets when browsing the list of devices to mute.

After doing a "Mute Device", go into the "Advance RDM":"Browse Packet History" menu and you can see the last few hundred packets that the DMXter has sent, and the associated response. This may help you determine what's happening.

Make sure you're handling broadcast packets properly. The DMXter does a number of broadcast SET IDENFITY_DEVICE packets, and I've frequently seen responders that have a problem with this.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Switch to Hybrid Mode Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
RDM Controller timing clarification	Dan Scheurell	RDM Timing Discussion	4	May 15th, 2014 10:34 PM

March 21st, 2013	#4
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	How are you determining what PIDs the DMXter is sending? The DMXter should only send a RESET_DEVICE when explicitly told to do so from the "Setup Device" menu, and never from the Discovery menu. You will see IDENTIFY_DEVICE and DEVICE_MODEL_DESCRIPTION packets when browsing the list of devices to mute. After doing a "Mute Device", go into the "Advance RDM":"Browse Packet History" menu and you can see the last few hundred packets that the DMXter has sent, and the associated response. This may help you determine what's happening. Make sure you're handling broadcast packets properly. The DMXter does a number of broadcast SET IDENFITY_DEVICE packets, and I've frequently seen responders that have a problem with this.