Line code: Difference between revisions

Revision as of 08:33, 6 October 2019

Revision as of 02:44, 11 October 2019

Line 135:

|url=https://www.researchgate.net/publication/3179483_EFMPIus_The_coding_format_of_the_multimedia_compact_disc

|pages=491–497

|quote=A high-density alternative to EFM is described.}}</ref> Higher density RLL (2,7) and RLL (1,7) codes became the [[de facto standard]]s for hard disks by the early 1990s.{{citation needed|date=August 2019}}<!--[[User:Kvng/RTH]]-->

== Synchronization ==

{{main | clockClock recovery}}

Line coding should make it possible for the receiver to synchronize itself to the [[Phase (waves)|phase]] of the received signal. If the synchronizationclock recovery is not ideal, then the signal to be decoded will not havebe optimalsampled differences (in amplitude) betweenat the various digits or symbols used in the lineoptimal codetimes. This will increase the error probability of error in the received data.<br />

Biphase line codes require at least one transition per bit time. This makes it easier to synchronize the transceivers and detect errors, however, the baud rate is greater than that of NRZ codes.<!--[[User:Kvng/RTH]]-->

Line coding should make it possible for the receiver to synchronize itself to the [[Phase (waves)|phase]] of the received signal. If the synchronization is not ideal, then the signal to be decoded will not have optimal differences (in amplitude) between the various digits or symbols used in the line code. This will increase the error probability in the received data.<br />

Biphase line codes require at least one transition per bit time. This makes it easier to synchronize the transceivers and detect errors, however, the baud rate is greater than that of NRZ codes.

== Other considerations ==