[802.3_RTPGE] Channel definitions ad hoc

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

Thread Links

Date Links

Thread Prev

[802.3_RTPGE] Channel definitions ad hoc - Follow up

Dear all,

attached a first short drawing of a typical application I would expect to be a worst case topology for the Return Loss:

The cam in the mirror: Here you may find 2 inline connectors quiet close (but not 4!)

In the following slides I have tried to sketch a possible “real” worst case and some “over-estimations”,

including a “worst-worst-case-channel” which could be used for tests with high return loss on both sides

and high insertion loss (shifting a real setup as close to the defined limits as possible)

If there are other proposals for the worst case Return loss, I would be happy to discuss them!

Regards,

Stefan

Von: Christopher DiMinico [mailto:CDimi80749@xxxxxxx]
Gesendet: Donnerstag, 17. Oktober 2013 17:04
An: STDS-802-3-RTPGE@xxxxxxxxxxxxxxxxx
Betreff: Re: [802.3_RTPGE] follow-up: [802.3_RTPGE] Channel definitions ad hoc - October 3

Colleagues,

Please find attached contribution on return loss from Michael Rucks Delpi.

Regards, Chris

In a message dated 10/14/2013 1:41:17 P.M. Eastern Daylight Time, CDimi80749@xxxxxxx writes:

Colleagues,

The focus of the ad hoc call is to resolve the baseline Link Segment specifications. For mode conversion we will take inputs from EMC ad hoc.

Please send in contributions to close return loss specifications i.e., topology (cable lengths between connectors and number of connectors), measurements and modeling to support limits.

Link segment transmission and coupling parameters (UTP)
•Insertion loss (complete)
•Return loss (open)
•Alien Crosstalk (complete)
‒PSANEXT, PSAACRF
•Common to differential conversion loss (SDC12/SDC21) (open)

If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.