Adapter module, RJ45 to 8 SMA Female

SKU:

$ 325.00

The PRL-RJ45-SMA adapter connects 8 SMA circuits to standard Cat 5e (or better) cabling.

The center pin of each SMA is connected to a signal pin on the shielded RJ45 connector, and the SMA shields and the RJ45 shield are all tied to chassis ground. Each top/bottom pair of SMAs is connected to a twisted pair in the Cat 5 cabling, based on the common TIA/EIA-568B or TIA/EIA-568A wiring, e.g:

  • 1,2
  • 3,6
  • 4,5
  • 7,8

The PRL-RJ45-SMA is designed primarily for converting differential signaling between SMAs and shielded twisted pair, but it can also be used for single-ended signaling by tying one of the SMAs in a pair to GND via an SMA termination.

If the drivers and receivers are DC-coupled circuits, shielded Cat 5e or better cabling is recommended whenever the driver and receiver are separated by long distances and/or when they are supplied by different power circuits (e.g. any time the grounds on opposite ends of the Cat 5e cable are subject to ground potential differences).

A discussion of impedance matching through this adapter (and other, similar adapters) is presented here.

The PRL-RJ45-SMA can be used with a variety of applications, such as:


Generic Differential Signaling

A discussion of impedance matching through this adapter (and other, similar adapters) is presented here:

 


Carrying Single-ended Signaling

The PRL-RJ45-SMA is a surprisingly good match for single-ended, 50 Ohm signaling, as shown here:

TDR→Coax→PRL→RJ45→SMA→Cat7 cable, 10’


Adapting Coaxial Ethernet

Several customers have reported good success using the PRL-RJ45-SMA adapters to adapt non-RJ45 Ethernet interfaces, such as SGMII or RGMII from an FPGA evaluation board, to RJ45 for connection to standard networks.

Although PRL has not done any detailed characterization of signaling with respect to Ethernet standards, we have performed end-to-end testing that demonstrates successful carriage of 1000BaseT signaling:

First, we connected a pair of PRL-RJ45-SMA modules with a set of eight 50 Ohm coax cables, and the connected the RJ45 sides to a PC's Gigabit network interface card and to an off-the-shelf, unmanaged Gigabit switch via Cat 5e cables:

Cat5e→PRL-RJ45-SMA→8x0.5mCoax→PRL-RJ45-SMA→Cat5e

The link negotiated 1000BaseT every time, and iperf reported typical throughput of 940 Mbps, which is the same that it reported for a link via a single Cat5e cable:


Measuring, Monitoring, and Debugging Ethernet

Next, we inserted a pair of PRL-860Q-SMA differential pickoff tees into the middle of the coax section:

Cat5e→PRL-RJ45-SMA→8x0.5mCoax→2xPRL-860Q→8x0.5mCoax→PRL-RJ45-SMA→Cat5e

with the Pickoff ports connected to a Tektronix CSA8200 Sampling scope:

The extraction of 5% of the signal power did not affect the link at all, and iperf continued to report throughput of 940 Mbps:

Now we can capture the Ethernet waveforms on the oscilloscope. First, we swapped out the Gigabit switch for an eval board for the Microchip KSZ9031RNX transceiver chip, and this board has a test point where I can extract the 125 MHz TX Clock signal. I connected the Ethernet jack of the Microchip board to a PC, via my cabling-and-adapter setup. Then I used the PC to set the speed and duplex, and brought up a link.

We needed a clean copy of the 125 MHz Tx Clock signal for the scope trigger, so we tapped into the Tx Clock pin on the Microchip eval board and buffered it with a PRL-350TTL comparator module.

We connected a Tx signal and an Rx signal to the oscilloscope and captured some traces. 100BaseT is easier to handle than 1000BaseT because:

  1. 100Base-TX is transmit or receive per pair, and uses 2 pairs to achieve full duplex.
  2. Therefore, if we trigger the scope on the TX Clk of the Microchip board, we should be able to see clearly the TX signal from the Microchip board.
  3. But we would _not_ be able to see clearly the RX pair, because that's clocked by the TX clock of the PHY on the other end of the 100Base-TX link, and that 125 MHz is asynchronous with this 125 MHz.
  4. Which pair becomes Rx or Tx depends on the Auto MDI-X negotiation, so we have a coin flip's chance of getting the TX pair on Scope Ch. 1 (green) every time the link negotiates.
  5. The signal has 3 discrete levels because 100BaseT uses 4B/5B and MLT-3 encoding to transmit 4 bits every 5 symbols

While we would like to show PAM-5 eye diagrams from 1000BaseT, this is significantly more difficult, because 1000BaseT is full-duplex per pair, relying on echo cancellation in the PHY to separate the Rx signal from the Tx signal, and the post-processed analog signal is not physically accessible outside the PHY in most implementations. Therefore triggering the scope and capturing a representative waveform of Rx or Tx is challenging.

The MLT-3 waveforms from 100BaseT are still a good proxy for signal fidelity measurements, because 1000BaseT uses the same 125 MBaud signaling rate at 100BaseT, relying on twice the number of pairs, 2.5x the number of bits encoded per symbol, and full-duplex per pair to increase the throughput to a Gigabit per second.

 

specifications coming soon

pdf coming soon