3.2.1 Responder Packet Timings - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · May 12th, 2009

Technically it's a valid solution. The key word is "may". A responder can wait as long as it wishes for the inter-slot timeout. Realistically though, no controller would generate packets like that because it would fail with many responders.

RDM has pretty tight timing restrictions. A device (controller or responder) which has scheduling delays in the 10ms range is unlikely to work reliably with RDM. You really need sub-millisecond level control to build an RDM device.

Typically, that means the USB UARTs from companies like FTDI and SiLabs won't work for RDM on their own. You need a microcontroller or PLD to generate more accurate timing.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Packet Captures?	jhuntington	RDM General Implementation Discussion	0	March 4th, 2007 07:19 PM
Any RDM Responder Devices out there yet?	sblair	RDM Marketplace Discussion	8	September 20th, 2006 06:03 AM

May 12th, 2009	#1
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	Technically it's a valid solution. The key word is "may". A responder can wait as long as it wishes for the inter-slot timeout. Realistically though, no controller would generate packets like that because it would fail with many responders. RDM has pretty tight timing restrictions. A device (controller or responder) which has scheduling delays in the 10ms range is unlikely to work reliably with RDM. You really need sub-millisecond level control to build an RDM device. Typically, that means the USB UARTs from companies like FTDI and SiLabs won't work for RDM on their own. You need a microcontroller or PLD to generate more accurate timing.