In telecommunication and data storage, Manchester code (also known as phase encoding, or PE) is a line code in which the encoding of each data bit is either low then high, or high then low, for equal time. It is a self-clocking signal with no DC component. As a result, electrical connections using a Manchester code are easily galvanically isolated.
Manchester code was widely used for magnetic recording on 1600 bpi computer tapes before the introduction of 6250 bpi tapes which used the more efficient group-coded recording. Manchester code was used in early Ethernet physical layer standards and is still used in consumer IR protocols, RFID and near-field communication.
Manchester coding is a special case of binary phase-shift keying (BPSK), where the data controls the phase of a square wave carrier whose frequency is the data rate. Manchester code ensures frequent line voltage transitions, directly proportional to the clock rate; this helps clock recovery.
The DC component of the encoded signal is not dependent on the data and therefore carries no information. Therefore connections may be inductively or capacitively coupled, allowing the signal to be conveyed conveniently by galvanically isolated media (e.g., Ethernet) using a network isolator—a simple one-to-one isolation transformer which cannot convey a DC component.
There are more complex codes, such as 8B/10B encoding, that use less bandwidth to achieve the same data rate but may be less tolerant of frequency errors and jitter in the transmitter and receiver reference clocks.
Encoding and decoding
Extracting the original data from the received encoded bit (from Manchester as per 802.3):
|Original data||Clock||Manchester value|
- Each bit is transmitted in a fixed time (the "period").
0is expressed by a low-to-high transition, a
1by high-to-low transition (according to G. E. Thomas' convention—in the IEEE 802.3 convention, the reverse is true).
- The transitions which signify
1occur at the midpoint of a period.
- Transitions at the start of a period are overhead and don't signify data.
Manchester code always has a transition at the middle of each bit period and may (depending on the information to be transmitted) have a transition at the start of the period also. The direction of the mid-bit transition indicates the data. Transitions at the period boundaries do not carry information. They exist only to place the signal in the correct state to allow the mid-bit transition. The existence of guaranteed transitions allows the signal to be self-clocking, and also allows the receiver to align correctly; the receiver can identify if it is misaligned by half a bit period, as there will no longer always be a transition during each bit period. The price of these benefits is a doubling of the bandwidth requirement compared to simpler NRZ coding schemes (or see also NRZI).
Conventions for representation of data
There are two opposing conventions for the representations of data.
The first of these was first published by G. E. Thomas in 1949 and is followed by numerous authors (e.g., Andy Tanenbaum). It specifies that for a 0 bit the signal levels will be low-high (assuming an amplitude physical encoding of the data) - with a low level in the first half of the bit period, and a high level in the second half. For a 1 bit the signal levels will be high-low.
The second convention is also followed by numerous authors (e.g., William Stallings) as well as by IEEE 802.4 (token bus) and lower speed versions of IEEE 802.3 (Ethernet) standards. It states that a logic 0 is represented by a high-low signal sequence and a logic 1 is represented by a low-high signal sequence.
If a Manchester encoded signal is inverted in communication, it is transformed from one convention to the other. This ambiguity can be overcome by using differential Manchester encoding.
- Coded mark inversion
- Differential Manchester encoding
- Self-clocking signal
- Binary offset carrier modulation
- Ethernet Technologies, Cisco Systems, retrieved 2017-09-12,
Manchester encoding introduces some difficult frequency-related problems that make it unsuitable for use at higher data rates.
- Forster, R. (2000). "Manchester encoding: Opposing definitions resolved". Engineering Science & Education Journal. 9 (6): 278. doi:10.1049/esej:20000609.
- Tanenbaum, Andrew S. (2002). Computer Networks (4th ed.). Prentice Hall. pp. 274–275. ISBN 0-13-066102-3.
- Stallings, William (2004). Data and Computer Communications (7th ed.). Prentice Hall. pp. 137–138. ISBN 0-13-100681-9.