Manchester code: Difference between revisions

Revision as of 22:28, 12 September 2017

Revision as of 20:13, 5 October 2017

Line 8:

Manchester coding is widely used (e.g., in [[10BASE-T]] Ethernet; [[consumer IR]] protocols; see also [[RFID]] or [[near-field communication]]). There are more complex codes, such as [[8B/10B encoding]], that use less [[bandwidth (signal processing)|bandwidth]] to achieve the same data rate but may be less tolerant of frequency errors and [[jitter]] in the transmitter and receiver reference clocks.{{cn|date=November 2015}}

According to [[Cisco]], "Manchester encoding introduces some difficult frequency-related problems that make it unsuitable for use at higher data rates".<ref>{{citation |url=http://docwiki.cisco.com/wiki/Ethernet_Technologies |title=Ethernet Technologies |publisher=[[Cisco Systems]] |access-date=2017-09-12 |quote=Manchester encoding introduces some difficult frequency-related problems that make it unsuitable for use at higher data rates.}}</ref><!--Difficulties are in meeting [[Title 47 CFR Part 15]] and other RF emissions requirements.-->[[Category:Kvng RTH]]

== Features ==

Manchester code ensures frequent line voltage transitions, directly proportional to the clock rate; this helps [[clock recovery]].

The [[directDC current|DCcomponent]] component of the encoded signal is not dependent on the data and therefore carries no information, allowing the signal to be conveyed conveniently by galvanically isolated media (e.g., Ethernet) which usually do notcannot convey a DC component.

== Encoding and decoding ==[[Category:Kvng RTH]]

== Description ==

[[Image:Manchester encoding both conventions.svg|thumb|center|650px|An example of Manchester encoding showing both [[Manchester code#Conventions for representation of data|conventions]]]]