Take the 2-minute tour ×
Electrical Engineering Stack Exchange is a question and answer site for electronics and electrical engineering professionals, students, and enthusiasts. It's 100% free, no registration required.

I'm building a patch-board for CAT-5e cables, whereby any pin can be re-wired to any other by a set of jumper cables. This is for testing black-box systems where weird things have been done to Ethernet sockets in order to make it difficult for someone to just walk up and plug in a laptop.

I'm in the PCB design phase, and have the following design in mind:

Here's the design I have in mind:

Ethernet PCB traces

The board is using 0.254mm traces, and the total length of each trace is no more than 25mm. I've alternated the traces on each side of the board to increase clearance between them, and hopefully the PCB itself should provide a little insulation against EM leakage.

I'd like to know if impedance matching is going to be an issue on a standard 10/100 Ethernet link, across this kind of design. Obviously the outer traces are currently about 50% longer than the middle one.

Any other recommendations on improving the design would also be welcome.

share|improve this question

3 Answers 3

up vote 4 down vote accepted

About trace length matching:

IEEE 802.3 specifies propagation delay and not distance (see 23.6.2.4 Delay from IEEE standard section 2). It says that you should have a maximum propagation delay of 570ns for your entire link and also propagation speed per meter should not exceed 5.7ns/m (thus the 100 meter common "limit").

But you are not concerned by these specs (just a reminder, in case you have a long link).

23.6.2.4.3 Difference in link delays
The difference in propagation delay, or skew, under all conditions, between the fastest and the slowest simplex link segment in a link segment shall not exceed 50 ns at all frequencies between 2.0 MHz and 12.5 MHz. It is a further functional requirement that, once installed, the skew between all pair combinations due to environmental conditions shall not vary more than ± 10 ns, within the above requirement.

You should retain that the maximum skew allowed on your whole link is around 10% of the maximum propagation delay (570 ns). As you are designing a custom adapter, we will take large margins to simplify computations and consider your adapter is equivalent to 1 meter of link.

So the maximum propagation delay allowed for your segment is 1/100 of 570ns = 5.7ns. The allowed skew between pairs is 1/100 of 50 ns = 500 ps.

Given your routing specs, the propagation delay of the signal is around 50 ps/cm. So with a 500 ps allowed skew delay, you can have a length difference of 10 cm.

No worries here.

Also, about EM leakage, 100 Mbits Ethernet signal frequency is 12.5 MHz, even if it is rise time equivalent frequency that matters, you don't have to worry to much if you are following advices given here by Dzarda and dextorb

share|improve this answer

Your trace impedance will be mainly controlled by your board stack-up parameters, not, interestingly enough, the trace length.

If you're interested, play around with a PCB calculator for a bit. Saturn PCB Design, Inc. provides a nice toolkit.

You will need to know some parameters of your stack-up in order to calculate your differential impedance. You will want to target a \$Z_{diff}\$ (differential impedance) of 100Ω for Ethernet.
Take notice there is a tolerance window; it doesn't have to be exact. How aggressive you want to be depends on the application. In some situations, perhaps you can get away with +/-20%, and maybe sometimes you can't.

Also, you'll want to route the RX+/- and TX+/- pairs together, on the same layer, as they are differential pairs.

Length-matching, while related to signal integrity, is a different matter. Just keep the traces short like you have and you will be fine.

share|improve this answer
    
"you'll want to route the RX+/- and TX+/- pairs together, on the same layer" - this cannot ever be guaranteed, as the jumper lines between each socket can arbitrarily re-wire the pairs. Is this likely to cause significant problems? –  Polynomial Mar 11 at 16:37
    
@Polynomial Once the signals go off board, I would keep the jumper wire pairs twisted together. I'd be hard pressed to say this would cause significant problems. –  dext0rb Mar 11 at 16:52

I wouldn't worry about it too much. Of course there are standards saying that you need to maintain \$100\Omega\$ differential impedance, also to keep your differential pairs length-matched to 50 mils, etc...

Just a tip:

I'd stick with 45° turns. Or if you need to get fancy, you can use round corners.

If you require as much reliability as you can get, match your lengths using meanders

share|improve this answer
    
Is there a reason for suggesting that I stick with 45 degree turns? –  Polynomial Mar 11 at 15:53
    
@Polynomial 90 degree bends are bad for high-frequency signals; they can cause EMI and signal integrity issues, due to reflections. It is a general rule of thumb to avoid them entirely. Many layout programs let you select between 45 or 90 degree bends. I know Altium also lets you use any arbitrary angle you wish. –  dext0rb Mar 11 at 16:11
    
@dext0rb I'm aware of the issue with 90-degree turns, but I was wondering why 45 degrees was preferable over other arbitrary acute angles. –  Polynomial Mar 11 at 16:35
    
@Polynomial Some people will tell you design software limitations, others will say manufacturability, acute angles trap the etching acid and over etch the trace or something like that. I'm not sure if this is a big deal nowadays or a holdover from ancient times. –  dext0rb Mar 11 at 16:41
    
@Polynomial I guess that the 45-degree rule is simply a matter of taste. I don't have a proof that arbitrarily similar angles cause signal disturbance. It's just that from time to time you will encounter a person like me who will criticise your routing style :) –  Dzarda Mar 11 at 17:12

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.