Responder Packet Timing issue - E1.20 RDM (Remote Device Management) Protocol Forums

sblair · May 27th, 2015

Looks like I'm a little late to the party tonight but I was going to suggest the same thing it looks like you've already arrived at.

I've used DMA in some of my implementations and I do as suggested, I get the first few bytes so I can get the packet length info and then set my DMA routine to trigger me again once I've gotten them all and that has worked well. It is really the ONLY way you can use any kind of DMA routine.

As Eric mentioned, the critical factor in the timings was in maintaining DMX Null Start Code performance so using timeouts just really wouldn't have worked without a more serious impact.

May 27th, 2015	#10
sblair Administrator Join Date: Feb 2006 Posts: 441	Looks like I'm a little late to the party tonight but I was going to suggest the same thing it looks like you've already arrived at. I've used DMA in some of my implementations and I do as suggested, I get the first few bytes so I can get the packet length info and then set my DMA routine to trigger me again once I've gotten them all and that has worked well. It is really the ONLY way you can use any kind of DMA routine. As Eric mentioned, the critical factor in the timings was in maintaining DMX Null Start Code performance so using timeouts just really wouldn't have worked without a more serious impact. __________________ Scott M. Blair RDM Protocol Forums Admin

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Timing contraints driver switch from controller to responder	mkoelman	RDM Timing Discussion	2	March 18th, 2015 01:44 AM
3.2.1 Responder Packet Timings	prwatE120	RDM Timing Discussion	6	May 23rd, 2009 08:32 AM
Packet Captures?	jhuntington	RDM General Implementation Discussion	0	March 4th, 2007 07:19 PM