Moving From 28 Gbps NRZ to 56 Gbps PAM-4: Is it a Free Lunch?


Reading time ( words)

The usual way of signaling through PCB interconnects is a two-level pulse, an encoding of 1s and 0s or bits, named NRZ (non-return-to-zero) or PAM-2 line code type. Increasing the data rate with the NRZ code type presents some obstacles. For a 28 Gbps NRZ signal, the bit time is about 35.7 ps with the main spectral lobe below 28 GHz. For a 56 Gbps NRZ signal, the bit time is about 17. 86 ps, with the main spectral lobe below 56 GHz.

One can feel the problem already: Getting PCB interconnect analysis and measurements up to 56 GHz and beyond is very challenging, to say the least. In addition, the expected attenuation (dielectric, conductor and roughness losses) would also be an obstacle for 56 GHz NRZ. To reduce the bandwidth of the signal, pulse amplitude modulation with four levels (PAM-4) is being used more frequently on production boards.

Instead of single bits, symbols 00, 01, 10, and 11 are coded by four levels of the pulse and the symbol time is twice as large as the bit time for NRZ signal with the same data rate; that is about 35.7 ps for 56 Gbps PAM-4—the same as for 28 Gbps NRZ! If we know how to design interconnects that correlate with the measurements for 28 Gbps NRZ, is it going to be a free lunch to move to 56 Gbps NRZ?

To read this entire article, which appeared in the August 2018 issue of Design007 Magazine, click here.

Share

Print


Suggested Items

Words of Advice: What Feature Would You Like to See in Your CAD Tool?

05/30/2019 | Andy Shaughnessy, Design007 Magazine
In a recent survey, we asked the following question: What feature would you like to see in your CAD tool? Here are a few of the answers, edited slightly for clarity.

Altium’s Craig Arcuri on Design Rules: Past, Present, and Future

05/28/2019 | Andy Shaughnessy, Design007 Magazine
We recently spoke with Altium’s Craig Arcuri about his views on design and manufacturing rules. Craig has experience running both design and manufacturing companies, so he has a fairly circumspect view of constraints from both sides of the product realization process. Craig details some of the challenges with setting and managing hundreds of often divergent design and manufacturing rules, and how both design and manufacturing constraints need to evolve.

XNC Format: Gerber Takes Data Into the Future

05/20/2019 | Denis Morin, Karel Tavernier, Jean-Pierre Charras, and Marius Matioc
The problem is that so many NC files are of deplorable quality because the NC format was never designed as a data transfer format. It has always been a machine driver and contains all sorts of information that a drilling machine needs, but that is irrelevant and confusing for data exchange.



Copyright © 2019 I-Connect007. All rights reserved.