PCIe Cable Selection Guide

A PCIe link inside a server is a board, a card, and a run of differential wire between them. The board and the card are chosen long before the wire. Then the wire gets ordered late, by whoever is left, from a spec sheet that lists rates and not much else. This guide is for that person. It walks through the six decisions on a PCIe wire order, in the order they should be made, and ends with a checklist you can paste into a quote request.

The product behind it is Lianbang's PCIe twinax cable, bare differential wire in 5.0, 6.0, and 7.0 builds. The rules below apply to any in-chassis PCIe wire.

Decision 1: Generation. Start from the link rate, not the GPU.

A PCIe link trains to the highest rate that both ends support. A PCIe 5.0 slot with a 6.0 card runs at 5.0. A 6.0 slot with a 5.0 card also runs at 5.0. The wire has to hold whatever rate the link will actually train to, so read the slower end of the pair, not the faster.

Each doubling of the lane rate cuts the time per symbol in half. The same run of wire, with the same loss and the same skew between its two conductors, eats a larger share of the eye at 64 GT/s than at 32 GT/s. That is why a wire that passed at 5.0 is not automatically a 6.0 wire. The impedance tolerance and the intra-pair skew have to be tighter, and the build changes to hold them.

Two practical rules:

• If the platform is fixed at one generation for its life, buy that generation. Ordering a 7.0 build for a 5.0 link buys tolerance you will not use.
• If the board is a 5.0 design today and the same chassis will take a 6.0 board at the next refresh, ask for both builds in the quote and decide on the price difference. Do not assume the 5.0 wire will carry over.

Note on encoding. PCIe 6.0 and 7.0 move to PAM4 with Flit Mode. PAM4 puts four levels in the same voltage swing that NRZ used for two, so the signal has less margin per level and is less forgiving of loss and reflections. If your team has only shipped 4.0 and 5.0 links, the step to 6.0 is a bigger change in the wire than the step from 4.0 to 5.0 was.

Decision 2: Length. Measure the route, not the gap.

The length on the order is the path the wire will actually take inside the chassis: down from the board connector, around the drive cage or the GPU tray, through the tie points, into the card. It is not the straight-line distance between the two connectors. Measure it on a mock-up or a 3D model, then add a service loop so the assembler is not pulling the pair tight over a sheet-metal edge.

Length is the single biggest lever on loss. Every extra centimeter adds insertion loss, and at 64 and 128 GT/s the loss budget the board designer left you is small. Longer runs push you toward a heavier gauge (Decision 3), which pushes back on the bend radius and the space in the tray. This is the trade that gets negotiated on most orders, so bring the real route length to the quote.

If the run is long enough that the passive wire alone cannot close the budget, the answer is a retimer on the board or in the path, not a thicker wire. That is a board decision. Raise it before the wire is cut, not after.

Decision 3: Gauge. Thin bends, thick carries.

Wire gauge is a loss-versus-fit trade.

• A finer conductor (higher AWG number) is smaller, lighter, and bends through a tighter radius. It also has more loss per unit length.
• A heavier conductor (lower AWG number) has less loss, so it supports a longer run at the same rate. It is stiffer, takes more space in a dense GPU tray, and pushes harder on the card when it turns.

Lianbang's 7.0 build is listed at 28–34 AWG. Inside that range, the choice follows Decisions 1 and 2: a short run at 128 GT/s inside a dense accelerator tray leans toward the finer end; a longer run leans toward the heavier end. Gauge for the 5.0 and 6.0 builds is confirmed on the order together with the length, because the two are set as a pair.

Do not pick a gauge from a general AWG table. Pick it from the route length and the rate, and let the wire supplier tell you which gauge closes the budget.

Decision 4: Shielding. Add it when the route is crowded.

An unshielded differential pair rejects common-mode noise well on its own; that is why the link uses a differential pair in the first place. Shielding earns its cost when the pair runs close to other high-speed pairs, along a power distribution board, or next to fan and PSU cabling for a long stretch. Crosstalk between adjacent lanes is the usual reason a passing link starts throwing correctable errors once the chassis is fully populated.

Shielding is optional on the Lianbang build and set per order. The cost is outer diameter and stiffness, which feed straight back into Decision 3 and the bend radius. If the route is short and the pairs are spaced, leave it off. If you are routing 32 pairs of x16 through a single cutout next to a busbar, quote it with shielding.

Decision 5: Lane count. Count pairs, not lanes.

A PCIe lane is one differential pair in each direction. An x4 link is 8 pairs, x8 is 16, x16 is 32. The 7.0 build is listed in x4, x8, and x16. When you state the lane count on an order, state whether you are counting lanes or pairs, and whether you want the wire supplied as individual pairs or grouped by link. Half the length disputes on PCIe wire orders come from this line.

Decision 6: Impedance and skew. These are set on the order.

Two numbers make a PCIe pair work at rate.

Differential impedance has to match the board and the connector. A mismatch reflects part of the signal back toward the transmitter and shows up as ringing and a closed eye. The wire is built to the PCIe differential requirement for its generation, and the exact value and tolerance are confirmed on the order, because your board's target is the reference.

Intra-pair skew is the difference in arrival time between the two conductors of one pair. Skew converts differential signal into common-mode noise and eats eye height. It is controlled by cutting and pairing the two conductors as one length. Skew is set per order for the same reason: the budget is yours, not the wire's.

If your board team has a target impedance and a skew budget, put both on the quote request. If they do not, say so, and ask for the values the build normally holds at that generation.

Five mistakes that cost a respin

1. Ordering by the card's advertised bandwidth instead of the slot's negotiated rate.
2. Measuring the connector-to-connector gap instead of the routed path, then finding the wire is short by the depth of the drive cage.
3. Choosing the gauge first and the length second. Do it the other way.
4. Passing signal integrity at bench temperature and skipping the rated range. This build is rated −40 to +85°C; test where the chassis will actually run.
5. Confusing bare wire with a finished assembly. The Lianbang PCIe twinax cable is the wire itself, for server and module builders to terminate. If you need connectors on both ends, that is a cable assembly and a different quote.

What to send for a quote

Paste this into the request. The more of it you fill, the fewer rounds.

• Board generation the link will train to: 5.0 / 6.0 / 7.0
• Lane count, and whether you are counting lanes or pairs
• Routed length, with the service loop, and a drawing or photo of the route if you have one
• Tightest bend in the route
• Shielded or unshielded, and why (what the pair runs next to)
• Target differential impedance and skew budget, if the board team has them
• Insulation color, if the assembler needs to tell links apart
• Quantity range, so the quote is on the right build

Length, wire diameter, shielding, and insulation color are made to order on the PCIe twinax cable. Impedance and skew are confirmed on the order. Send the list above and the quote comes back against your route, not a catalog line.