Manchester code

related topics
{system, computer, user}
{math, number, function}
{rate, high, increase}
{work, book, publish}

In telecommunication, Manchester code (also known as Phase Encoding, or PE) is a line code in which the encoding of each data bit has at least one transition and occupies the same time. It therefore has no DC component, and is self-clocking, which means that it may be inductively or capacitively coupled, and that a clock signal can be recovered from the encoded data.

Manchester code is widely used (e.g. in Ethernet; see also RFID). 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.

Contents

Features

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, allowing the signal to be conveyed conveniently by media (e.g. Ethernet) which usually do not convey a DC component.

Description

Extracting the original data from the received encoded bit (from Manchester as per 802.3):

original data XOR clock   =   Manchester value
     0              0                 0
     0              1                 1
     1              0                 1
     1              1                 0

Summary:

  • Each bit is transmitted in a fixed time (the "period").
  • A 0 is expressed by a low-to-high transition, a 1 by high-to-low transition (according to G.E. Thomas' convention -- in the IEEE 802.3 convention, the reverse is true).
  • The transitions which signify 0 or 1 occur 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).

In the Thomas convention, the result is that the first half of a bit period matches the information bit and the second half is its complement.

[edit] Manchester encoding as phase-shift keying

Manchester encoding 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. Such a signal is easy to generate.

[edit] Conventions for representation of data

Encoding of 11011000100 in Manchester code (as per G. E. Thomas)

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., 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., 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.

[edit] References

[edit] See also

 This article incorporates public domain material from the General Services Administration document "Federal Standard 1037C" (in support of MIL-STD-188).

Full article ▸

related documents
Floating point unit
Network Layer
High Performance File System
Windows Metafile
Electronic mixer
Windowing system
Csound
Real mode
POSIX
Mobile ad-hoc network
System-on-a-chip
Schematic
Jaggies
DASS2
Acoustic coupler
Peripheral
Multimeter
Input/output
Bugzilla
Megabyte
Star network
Red Hat Linux
JOHNNIAC
Notepad
Computer hardware
GeForce
SoftICE
Parallel processing
Trivial File Transfer Protocol
Audio editing