Math Bridge: NFC Field-Clock Division

← Back to NFC Modes and Protocols
Math BridgeNFCClock division

Where do 106, 212, and 424 kbps come from?

Divide the shared 13.56 MHz field clock, time one bit, and compare the result with a bounded capacity screen.

Eddie, the electronics guideEddie guides
The one targetDerive the chapter's NFC rates from one carrier clock.
The chapter case13.56 MHz divided by 128, 64, and 32.
What it buys youA physical explanation for protocol-rate names without treating NFC like Wi-Fi.

A field team faces an unresolved physical question: Where do 106, 212, and 424 kbps come from? They must answer it before changing cycles per bit on the real device. Predict the direction first.

See the relationship before changing it

The figure reads from left to right. The blue card is cycles per bit. The middle card applies this page's relationship. The green card is carrier wavelength. Walk the arrows once: set the input, apply the rule, then read the result with its unit.

The retained audit below checks several chapter fixtures. This added model holds every other chapter fixture fixed, so the numeric fixture does not switch without explanation.

Cycles per bit changes carrier wavelength An input card leads through the page relationship to the carrier wavelength result. SET INPUT ONE CONTROL APPLY RULE predict calculate check units READ RESULT
Walk the arrows. Halving cycles per bit doubles the data rate because the shared carrier completes the bit twice as quickly.

Derive the baseline in four named moves

  1. 1

    Name the input. The chapter baseline for cycles per bit is 128.

  2. 2

    Name the relationship. λ = 3x10⁸ / 13.56x10⁶ = 22.12 m; rnf = 3.52 m 13,560,000/128 = 105,937.5 bps; /64 = 211,875 bps; /32 = 423,750 bps C(1 MHz, 30 dB) = 9.967 Mbps

  3. 3

    Substitute the chapter fixture. Set cycles per bit to 128. The page ledger gives carrier wavelength as 22.12 m.

  4. 4

    Read the result. Keep m beside the value. Use it only inside the technical boundary on this page.

Predict, then change cycles per bit

Try Predict the direction of carrier wavelength. Move one control, calculate, then check your prediction.

128
Chapter baseline
Carrier wavelength

Observe Halving cycles per bit doubles the data rate because the shared carrier completes the bit twice as quickly. Reset the control to 128 and compare carrier wavelength.

Explain Only cycles per bit moves here. The other chapter fixtures remain fixed.

Check yourself

What should you do before trusting a moved-control result?
Answer: Predict its direction, apply the shown relationship, keep the units, and reset to the worked baseline.
What does this small model leave out?
Answer: Only cycles per bit moves. Field effects named in the page's technical boundary stay fixed.

Honesty note. This teaching model changes only cycles per bit. It replays the chapter fixture; it is not a field prediction.

1. Start with the physical story

An NFC target load-modulates a field supplied by the reader. Both ends share that field clock, so simple integer division can define the bit timing.

Eddie: The rate table is a clock-division table wearing kbps units.

2. Name every algebra move

1

Find wavelengthDivide wave speed by 13.56 MHz.

2

Mark near fieldDivide wavelength by 2π.

3

Divide the clockDivide 13,560,000 cycles/s by cycles/bit.

4

Bound capacityUse B log2(1+SNR) only as a comparison ceiling.

3. Reproduce the chapter case

λ = 3×10⁸ / 13.56×10⁶ = 22.12 m; rnf = 3.52 m
13,560,000/128 = 105,937.5 bps; /64 = 211,875 bps; /32 = 423,750 bps
C(1 MHz, 30 dB) = 9.967 Mbps

The standard names round those three clock divisions to 106, 212, and 424 kbps.

4. Try one real input

TryMove cycles per bit among clock divisions while carrier, bandwidth, and SNR stay fixed.

Cycles per bit
Carrier wavelength
Near-field boundary
Bit rate
Rounded rate
One-bit interval
Capacity screen
Capacity/rate
Capacity used

ObserveAt 128 cycles/bit the result is 105.94 kbps and a 9.44 µs bit; the comparison ceiling is about 94.09 times larger.

ExplainHalving cycles per bit doubles the data rate because the shared carrier completes the bit twice as quickly.

Technical boundaries.

Clock division explains the named rates; it is not a complete NFC physical-layer model.

Near field
Wavelength and λ/2π mark the regime; real coupling depends on coil size, alignment, Q, tuning, load, and separation.
Protocol
Modulation, coding, framing, turnaround, collision handling, and mode-specific rules reduce useful throughput.
Capacity
The 1 MHz and 30 dB values are an illustrative comparison, not a measured NFC channel claim.

Correct, not complete: this bridge does not certify a protocol rate or coupling margin.

5. Use the result in the lab

Capture the reader field and load-modulated reply, measure cycles per symbol, and compare protocol timing with the requested mode.

6. Record the evidence state

Keep carrier accuracy, mode, divisor, coding, frame timing, coil and match state, separation, alignment, errors, retries, and effective payload rate.

7. Check yourself

Why does division by 128 give about 106 kbps?
Answer: 13,560,000 carrier cycles each second divided by 128 cycles per bit is 105,937.5 bit/s.
Does 9.967 Mbps mean NFC should transmit that fast?
Answer: No. It is an illustrative Shannon ceiling, not the selected modulation and protocol rate.
Does the 3.52 m boundary mean NFC works at 3.52 m?
Answer: No. It marks a field regime; usable coupling is normally only centimetres.
Honesty boundary.

The bridge derives the chapter's named rates from one shared field clock.

Computed
Wavelength, boundary, divided rates, bit time, capacity screen, and ratios are reproducible.
Specified
Mode, divisor, coding, bandwidth, SNR, coil design, and timing rules come from the selected implementation.
Observed
Waveforms, timing, errors, retries, coupling, and useful throughput determine conformance.

Correct, not complete: inspect the real mode and physical link before making a rate claim.

Return to NFC Modes and Protocols with the rates derived →