Summed Break and MAB time - E1.20 RDM (Remote Device Management) Protocol Forums

kster · July 5th, 2009

In the RDM specifications in table 3-3, line 1, the maximum break and MAB are specifed as 1 second for receiving (responder). So when I receive a break of 0.99second followed by a MAB of 0.99second, this is still a valid signal?

If this is the case it would be very difficult to comply to this when the UART framing error is used to detect the break. This can only detect the start of the break and not the end(start of the MAB).

I find it also very unclear what must happen when the timing of the incomming signal are not within spec. For example when the MAB is less then 8uS. Must then the packet be dropped? This would also be very difficult to implement using only a UART.

Regards,

Kurt

July 5th, 2009	#1
kster Junior Member Join Date: Jun 2009 Posts: 5	Summed Break and MAB time In the RDM specifications in table 3-3, line 1, the maximum break and MAB are specifed as 1 second for receiving (responder). So when I receive a break of 0.99second followed by a MAB of 0.99second, this is still a valid signal? If this is the case it would be very difficult to comply to this when the UART framing error is used to detect the break. This can only detect the start of the break and not the end(start of the MAB). I find it also very unclear what must happen when the timing of the incomming signal are not within spec. For example when the MAB is less then 8uS. Must then the packet be dropped? This would also be very difficult to implement using only a UART. Regards, Kurt

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
Time between controller packets	Dan Scheurell	RDM Timing Discussion	1	April 1st, 2007 11:38 PM
Exceeding MAB time	Dan Scheurell	RDM Timing Discussion	2	March 30th, 2007 08:23 AM