Manchester code: Difference between revisions

Content deleted Content added
m unpiped links using script. repos ref.
 
(5 intermediate revisions by 4 users not shown)
Line 21:
 
==Encoding and decoding==
[[Image:Manchester encoding both conventions.svg|class=skin-invert-image|thumb|650px|An example of Manchester encoding showing both [[Manchester code#Conventions for representation of data|conventions for representation of data]], where : {{math|1=''[[Leet|1337]]''<sub>10</sub> = ''10100111001''<sub>2</sub>}}]]
 
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.
Line 63:
Encoding conventions are as follows:
* Each bit is transmitted in a fixed time (the period).
* A <code>0</code> is expressed by a low-to-high transition, a <code>1</code> by high-to-low transition (according to G. E. Thomas's convention – in the IEEE 802.3 convention, the reverse is true).<ref name="Manchesterencoding">{{Cite journal |author-last1=Forster |author-first1=R. |title=Manchester encoding: Opposing definitions resolved |doi=10.1049/esej:20000609 |journal=Engineering Science & Education Journal |volume=9 |issue=6 |pages=278–280 |date=2000|doi-broken-date=12 July 2025 }}</ref>
* The transitions which signify <code>0</code> or <code>1</code> occur at the midpoint of a period.
* Transitions at the start of a period are overhead and don't signify data.
Line 82:
[[Category:Line codes]]
[[Category:Department of Computer Science, University of Manchester]]
[[Category:History of computing in the United Kingdom]]
[[Category:History of telecommunications in the United Kingdom]]