This is an old revision of this page, as edited by 71.41.210.146 (talk) at 00:18, 31 January 2009 (→Data link layer: Slight phrasing improvement. Deleted dangling <references/> left from editing.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 00:18, 31 January 2009 by 71.41.210.146 (talk) (→Data link layer: Slight phrasing improvement. Deleted dangling <references/> left from editing.)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)Twinaxial cabling, or "Twinax", is a type of cable similar to coax, but with two inner conductors instead of one. Due to cost efficiency it is becoming common in modern very short range high speed differential signaling applications.
Legacy Applications
IBM
Historically, twinax was the cable specified for the IBM 5250 terminals and printers, used with IBM's midrange hosts, which are currently AS/400 (Application System 400) minicomputers (which are now called iSeries or i5), and also with its predecessors, such as the S/36. The data transmission is half-duplex, balanced transmission, at 1 Mbit/s, on a single shielded, 110 Ω twisted pair.
With Twinax seven devices can be addressed, from workstation address 0 to 6. The devices do not have to be sequential.
Straight Twinax cables can go up to 5,000 feet (1,500 m) or 1 mile (1.6 km). Twinax is a bus topology that requires termination to function properly. Most Twinax T-connectors have an automatic termination feature. For use in buildings wired with Category 3 or higher twisted pair there are Baluns that convert twinax to twisted pair and hubs that convert from a bus topology to a star topology.
Twinax was designed by IBM as a replacement for RS-232 dumb terminals. Its main advantages were high speed (1 Mbit/s versus 9600 bit/s) and multiple addressable devices per connection. The main disadvantage was the requirement for proprietary Twinax cabling with bulky screw-shell connectors.
Physical layer
Signals are sent differentially over the wires at 1 Mbit/s (1 μs/bit, ±2%), Manchester coded, with preemphasis. The signal coding is only approximately differential, and not completely differentially balanced. In general, one of the two signal lines is driven to −0.32V (±20%), while the other carries 0V. This, itself, could be considered as two differential signals of ±0.16V superimposed on a −0.16V common mode level. However, to provide preemphasis, for the first 250 ns (1/4 bit time) after a signal is driven low, the negative signal line is driven to −1.6V. During this time, the common-mode voltage is −0.8V.
This signal is designed to provide a minimum of ±100 mV at the end of 500 feet of cable.
The two wires are denoted A and B. To encode a 0 bit, A>B for the first half of the bit time, and A<B for the second half. A 1 bit is the opposite. Thus, each signal line is driven low for either 500 or 1000 ns at a time, of which the first 250 ns is emphasized.
Data link layer
A message begins with five normal 1 bits (A driven low for 500 ns, then B driven low for 500 ns) for bit synchronization, followed by a special frame sync pattern, three bit times long, that violates the usual Manchester encoding rules. A is driven low for 1500 ns, then B is driven low for 1500 ns. This is like a 1 bit sent at 1/3 normal speed (although the premphasis pulses remain 250 ns long).
This pattern is followed by up to 256 16-bit data frames. Each data frame consists of a start bit of 1, an 8-bit data field, a 3-bit station address, and an even parity bit (which includes the start bit, so it equivalent to odd parity over the data and address fields only). This is then followed by three or more fill bits of 0. Unusually for an IBM protocol, the bits within each frame are sent lsbit-first.
All messages are sent between the controller (master) and one slave device. The first frame in a message from the controller contains the device's address, from 0 to 6. The address field of following frames can be any value from 0 to 6, although is usually set to the device's address as well. The final frame in a message includes an address of 7 (all ones) as an end-of-message (EOM) indicator. A single-frame message does not have an EOM indicator.
When a command calls for a response, the device is expected to respond in 30 to 80 μs. A device's response also consists of up to 256 frames, and includes its address in all frames but the last. In this case, a single-frame response includes the EOM address, and the controller assumes it comes from the device it most recently addressed.
Generally, the first frame in a message is a command byte, and following frames are associated data.
NEC
NEC Astra system also uses this kind of cable for networking.
Current Applications
One of major applications includes Cisco Systems implementation coupled with SFP+ modules. This is referred to as "Direct Attach" or "SFP+ Copper". This type of connection is able to transmit at 10 Gigabit full duplex speed over 10 meter distances. Moreover this setup offers 15 to 25 times lower transceiver latency than current 10GBASE-T CAT6/CAT6a/CAT7 cabling systems: 0.1 μs for Twinax with SFP+ versus 1.5 to 2.5 μs for current 10GBASE-T specification. The power draw of Twinax with SFP+ is around 0.1 watts, which is also much better than 4–8 watts for 10GBASE-T.
As always with cabling one of the consideration points is Bit error ratio or BER for short. Twinax copper cabling has BER better than 10 according to Cisco, and therefore is acceptable for applications in critical environments.
Many manufacturers of DisplayPort cabling are also using twinaxial configurations to accommodate the strict insertion loss, return loss, and crosstalk requirements for the 2.7 Gbit/s signaling rate.
References
- "NLynx Technologies - what is Twinax?". NLynx. 2006.
- ^ Quigley, Thomas J. (March 1988), Interfacing the DP8344 to Twinax (PDF), National Semiconductor, AN-516
- ^ Twinax Cable Information, Anzac Computer Equipment Corporation, 2004-07-22, retrieved 2009-01-30
- Norcross, Thomas; Patchen, Paul J.; Quigley, Thomas J.; Short, Tim; Worsley, Debra; Johnson, Laura (April 1995), MPA-II—A Multi-Protocol Terminal Emulation Adapter Using the DP8344 (PDF), National Semiconductor, AN-641
See also
External links
This electronics-related article is a stub. You can help Misplaced Pages by expanding it. |