Some customer applications have been discovered in which an excessive jitter is observed when 82P2288 T1 short-haul pulse shape is measured by ANT-20 (by Spirent Communications). The following introduces some details of the measurement and a suggested workaround to fix this seemingly false measurement. No problem of this nature has ever been reported in E1 mode; only on T1 mode. In the rising edge of the defined pulse shape mask, there is a turn point (an “elbow” shape), as pointed by an arrow. 82P2288 transmitter constructs its pulse shape accordingly. Its built-in ROM-based pulse shape looks like the following:
The transmitted pulse shape from 82P2288 meets G.703 specification when the line condition are met (i.e., impedance matching is achieved). When an OmniBER-718 (by Agilent) is used to measure jitter generation from the transmitted port, it meets 0.05UI specification. However, when using ANT-20 to measure the jitter generation on customer systems using 82P2288, a few violations have been reported from customers. In one instance (see figure below), the measurement was greater than 0.84UI.
The possible reason for this excessive jitter measurement is construed to be the coincidence of ANT-20's sampling point and the “turn point” in the rising edge of the transmitted pulse shape, as described above. There are two facts that provide the support for the aforementioned statement.
1. With the same transmitted pulse shape, other instruments, such as OmniBER-718, measures the jitter generation within range;
2. When AWG (Arbitrary Waveform Generator) is used in 82P2288 to remove the “elbow” shape in the rising edge of T1 pulse, the same ANT-20 measures the same parameter; that is, the jitter generation of the transmit port is also within range.
As a result, AWG is recommended as a workaround for customers when experiencing the same jitter measurement problem by ANT-20. Other than ROM-based pulse shape, 82P2288 also provides RAM-based pulse generator. Customers can arbitrarily re-construct the transmitted pulse shape by downloading 64-byte of data into a per-port based RAM space.