Methods of Error Detection

Summary — What This Chapter Covers

• Why errors happen: interference (wired or wireless) causes data loss, data gain, or data change.
• Why we check: computers need data in an expected format — unexpected data is hard or impossible to interpret correctly.
• Parity check: adds one extra bit per byte so the total number of 1s matches an agreed rule (odd/even). Detects an error but not .
• Parity block & parity byte: parity calculated both horizontally (per byte) and vertically (per bit-column) — this combination can actually the faulty bit.
• Checksum: a calculated value sent alongside data; recalculated by the receiver and compared. Mismatch = error, but no location given.
• Echo check: receiver sends the data straight back to the sender to compare — simple, but not fully reliable (error could occur on the way back too).
• Check digits: one extra digit at the end of a numeric code (ISBN, barcodes) calculated by an algorithm to catch mistyped, missing, extra, or swapped digits.
• Automatic Repeat reQuest (ARQ): a protocol using acknowledgements and timeouts to automatically request re-transmission of corrupted or missing data.

1  Why Errors Occur

Interference is the root cause

Think of data transmission like sending a message by shouting across a windy field versus passing a note by hand. Along the way, things can interfere with the message and change it — that's exactly what happens electronically too.

Wireless technology (radio signals, Wi-Fi, Bluetooth) can be disrupted by:

• Physical barriers — buildings, walls, cars, even your own body standing in the way
• Bad weather — rain, clouds, storms
• Other wireless signals or electromagnetic radiation "talking over" your signal

Wired technology is actually prone to error overall, because physical cables can:

• Get damaged or degrade over time
• Pick up interference from nearby electrical sources
• Suffer from interrupted or intermittent connections, causing data loss

The three ways interference shows up

Why checking even matters

Computers only understand data that arrives in an expected format — an agreed way of arranging data so both sender and receiver interpret it the same way. Dates are a classic example: 13/04/14 could be DD/MM/YY, and 12/31/2020 is clearly MM/DD/YYYY (since there's no 31st month). But what about 04/03/17? Is that 4th March or 3rd April? Without an agreed format and error checking, ambiguous or corrupted data leads to misinterpretation — and in the real world, that can mean wrong dates, wrong amounts, wrong instructions.

2  Parity Check

The core idea

parity bit every byte must contain an odd number of 1s every byte must contain an even number of 1s

3  Parity Byte & Block Check

4  Checksum

algorithm

5

6

7

protocol