E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM Timing Discussion

RDM Timing Discussion Discussion and questions relating to the timing requirements of RDM.

Thread Tools Search this Thread Display Modes
Old August 7th, 2006   #1
Task Group Member
Join Date: Jun 2006
Posts: 181
Default In-line device Port Turnaround during Discovery

In I have forgotten why there is a special case for requiring that the in-line device NOT return to forward data flow before 5.6ms for messages of command class DISCOVERY_COMMAND.

Can anyone enlighten me ?

I can see that once any start of response from a responder is detected, the in-line device must return to forward data flow no later than 5.8ms, but if there is NO response commencing within 2ms (Table 3-4 Line2) plus an allowance for data delay (4.2.2), cannot an in-line device legimately return to forward data flow, as indeed it must for messages that are NOT of command class DISCOVERY_COMMAND.

Why the special case?

For "normal" operation I assume the return to forward data flow must be within 3ms, in order to allow operation with controllers in accordance with Table 3-2 line 5.
prwatE120 is offline   Reply With Quote
Old August 7th, 2006   #2
Join Date: Feb 2006
Posts: 433
Send a message via AIM to sblair Send a message via MSN to sblair


I don't recall the exact reasons as I've managed some sleep since then. Looking at it, I can see a couple possible reasons though.

Table 3-4 timings are from Controller EOP to Responder SOP. Since there are no BREAKS this can make things confusing sometimes to detect SOP for the Responder.

You could have multiple responders on a link that respond far enough apart to get multiple discovery responses with no collisions in that time frame.

Because of the possibility for error, I think the safe position for 'dumb' splitters was to remain in this reverse data flow direction for the entire response window to ensure things functioned.

Regardless of the reasons, it doesn't really matter as this is a SHALL requirement so all in-line devices are required to observe the timing requirement.
Scott M. Blair
RDM Protocol Forums Admin
sblair is offline   Reply With Quote


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Line biasing Flaws - need solutions berntd RDM Physical Layer/Hardware Discussion 7 April 9th, 2009 05:32 PM
Line biasing Andy Macdonald RDM Physical Layer/Hardware Discussion 1 October 26th, 2006 11:02 AM

All times are GMT -6. The time now is 07:50 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.