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

Nigel Worsley · May 26th, 2015

Looks like a very good reason not to use a timeout to detect end of packet! However if this is unavoidable then the specification can still be met:

Set the timeout to 1.05mS
When a timout is generated but the packet is incomplete then restart the timeout.
Two timeouts without anything being received in between is an inter slot timeout and can be processed accordingly.

My personal preferrence would be to handle all of the data in interrupts though.

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

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

May 26th, 2015	#1
Nigel Worsley Junior Member Join Date: Jun 2006 Location: London Posts: 13	Looks like a very good reason not to use a timeout to detect end of packet! However if this is unavoidable then the specification can still be met: Set the timeout to 1.05mS When a timout is generated but the packet is incomplete then restart the timeout. Two timeouts without anything being received in between is an inter slot timeout and can be processed accordingly. My personal preferrence would be to handle all of the data in interrupts though.