38 Proxy Sensing and Inductive Loops
38.1 Start With the Measurement Story
38.1.1 Ask What the Existing Signal Really Sees
A road already has a buried loop that changes when a metal object passes above it. A planning team wants to use those changes as a vehicle count. The loop does not see a vehicle in the way a person does. It sees a physical change that often stands in for one. That gap can alter a traffic decision.
Write the indirect claim in plain terms. Name the physical effect, the event inferred from it, the place covered, and the cases it may miss. Keep a direct count beside the inferred count during the trial. Record weather, nearby lanes, road work, small vehicles, stopped traffic, and any change to the original equipment.
Now challenge the link between signal and claim. Pass a bicycle, motorbike, van, and closely spaced pair. Place a metal object near the lane. Change the background slowly. Compare morning and evening. Check false calls, missed calls, delay, and the confidence label shown to the user. Recheck after any repair or road change.
This method can reuse equipment cheaply, but it does not turn an indirect clue into ground truth. The deeper sections explain the loop’s physical response, thresholds, drift, cross-talk, other reused signals, and the evidence needed to keep the useful operating range honest.
Proxy sensing turns indirect evidence into a measurement claim. Before using an inductive loop, Wi-Fi pattern, or infrastructure signal, ask what it really observes, what it misses, and how ground truth will check it.
The mathematical gist. For the chapter’s 40 kHz loop and catalog-typical 100 µH inductance, implies and s, or 1.59 cycles. The tuned capacitance is 158 nF and 10 mA RMS dissipates 251 µW. Ring-down is an amplitude-domain clue separate from the chapter’s frequency-shift proxy.
38.2 Learning Objectives
After this page, you should be able to:
- Explain how existing infrastructure signals become proxy sensing evidence rather than direct measurements.
- Describe how an inductive-loop detector turns conductive vehicle presence into an LC oscillator frequency shift.
- Set detection thresholds against drift, small-target sensitivity, adjacent-lane cross-talk, and false calls.
- Identify proxy drift and record the evidence needed before infrastructure sensing can support decisions.
38.3 After Infrastructure Sensing
Sensing with Existing Infrastructure introduces Wi-Fi, NILM, cellular, and campus-occupancy examples that reuse operational signals. This page focuses on the deeper boundary question: what does the proxy physically measure, what does it miss, and how fresh is the baseline that makes the inference credible?
Use it when an infrastructure-derived signal looks attractive because it is cheap and already deployed, but the decision still needs a defensible confidence label and a known operating envelope.
38.4 Overview: The Signal Is Already There
Infrastructure sensing starts from a practical question: what useful signal is the site already producing? A Wi-Fi access point already broadcasts and records signal strength, a smart meter already samples voltage and current, a cellular network already tracks handoff and load, and a traffic lane may already contain a buried loop. The sensing task is to turn those operational signals into a proxy for occupancy, location, traffic, appliance use, or equipment condition.
One of the most widely deployed infrastructure sensors is a loop of wire cut into the pavement at traffic lights. The inductive loop detector does not photograph or weigh a vehicle, and it needs no line of sight. It senses how a large mass of metal changes the magnetic behaviour of the buried coil. The same design pattern appears in Wi-Fi fingerprinting: the access point was installed for networking, but the radio signal map can also become a location or presence sensor.
The mechanism differs by infrastructure, but the evidence pattern is the same. First, identify the physical quantity that perturbs an existing signal. Second, record a baseline or fingerprint while the system is in a known state. Third, look for deviations large enough to support the decision you want to make. The result is usually a useful proxy, not a certified ground truth.
For the traffic loop, the mechanism is inductive transduction. The loop is a coil, and a coil has inductance. When a car — a large conductive body — sits over the loop, it changes the loop's effective inductance. Turn that inductance change into a measurable signal and you have a vehicle detector that can live under the road surface for years.
Intuition: the loop hums with an alternating magnetic field. A metal vehicle overhead soaks up and reshapes that field, and the loop "feels" the difference as a change in its own inductance — presence without ever seeing the car.
38.4.1 Overview Knowledge Check
38.5 Inductance to Frequency
The loop is wired as the inductor of an LC oscillator, so its inductance sets the oscillation frequency:
Oscillation frequency: f = 1 / (2π × sqrt(L × C)) Because f depends on 1/sqrt(L): Δf/f ≈ -(1/2) × ΔL/L
38.5.0.1 Worked example: a vehicle nudges the frequency
A vehicle's eddy currents lower the loop's effective inductance by about 0.1%: ΔL/L = -0.001 Since f rises when L falls: Δf/f ≈ -(1/2)(ΔL/L) = -(1/2)(-0.001) = +0.0005 = +0.05% So a car present RAISES the oscillator frequency by about 0.05%. Loop detectors are built to resolve these small, sub-0.1% inductance shifts reliably.
Reading a frequency shift is far easier and more robust than reading a tiny inductance directly, which is why the oscillator approach is standard: the vehicle becomes a small, clean change in a frequency the electronics can count precisely.
The important engineering move is the same for other infrastructure signals: convert a weak physical disturbance into a robust digital feature. In a loop detector that feature is frequency shift. In Wi-Fi sensing it might be RSSI from several access points, CSI subcarrier amplitude and phase, or associated-device count per access point. In a smart meter it might be a step in real power, a change in reactive power, or a harmonic signature.
A deployment should define the feature, the baseline, and the decision threshold before it is trusted. Suppose an empty lane oscillator sits at 40.000 kHz and normal temperature drift moves it by +/-4 Hz over an hour. A vehicle that shifts the frequency by +20 Hz is easy to separate from drift; a small motorcycle that shifts it by +3 Hz is not. Raising sensitivity catches the motorcycle but increases splash-over from adjacent lanes. The practitioner tradeoff is not "detect or not"; it is missed detections versus false calls.
The same threshold logic applies to Wi-Fi occupancy. If a conference-room access point reports 2-4 associated devices overnight and 18-24 during a scheduled meeting, the occupancy proxy is strong. If the count changes from 8 to 10, the evidence is weak unless it is combined with room booking data, CSI motion features, or a small number of dedicated PIR sensors. Infrastructure sensing works best when the decision only needs zone-level confidence.
38.5.1 Practitioner Knowledge Check
38.6 Eddy Currents and Baseline Drift
The physics that makes the loop work also defines exactly what it cannot see and why it must keep re-learning the empty road.
38.6.0.1 Eddy currents lower inductance
The loop's alternating field induces circulating eddy currents in the vehicle's conductive body; those currents create an opposing field that reduces the loop's effective inductance — the same effect an industrial inductive proximity sensor uses to detect metal.
38.6.0.2 It only sees conductive mass
Because detection needs eddy currents, the loop responds strongly to cars and trucks but weakly to non-conductive objects. A carbon-frame bicycle or a pedestrian may not trigger it at all — a well-known real-world blind spot.
38.6.0.3 Geometry and cross-talk
Detection depends on how much conductive area couples to the loop and how high it sits, so motorcycles are hard. Turn sensitivity up too far and adjacent loops interfere (splash-over); too low and small vehicles are missed.
38.6.0.4 Baseline drift and auto-tuning
Temperature, moisture, and cable changes slowly shift the empty-loop inductance. Detectors continuously re-baseline to the empty road and look for fast deviations, separating a real vehicle from slow environmental drift.
This is the general shape of infrastructure-based sensing: it is cheap, passive, and robust because it reuses something already there, but it inherits blind spots from its physics and needs constant baseline tracking to stay honest. Knowing that an inductive loop is deaf to carbon and plastic explains a great deal of real traffic-signal behaviour — including why some cyclists wait forever at a red light.
The hidden risk is proxy drift. A Wi-Fi fingerprint can degrade when access points move, furniture changes, or a new wall attenuates one path. A smart-meter NILM model can confuse appliances when two loads switch at the same time or when a variable-speed motor changes its signature. A cellular density estimate can change when carrier policy or handset behaviour changes. None of those failures look like a broken sensor; they look like a plausible but stale inference.
Good infrastructure-sensing systems therefore carry evidence metadata with every decision: which infrastructure signal was used, when the baseline was last refreshed, what confidence or residual check passed, and which cases fall outside the operating envelope. For safety-critical decisions, the proxy should trigger a follow-up sensor or human check rather than stand alone.
38.6.1 Under-the-Hood Knowledge Check
38.7 Decide Whether a Loop Saw a Vehicle
For the buried inductive loop, a wire loop buried under asphalt never measures a car directly. In this proxy-sensing lane, its oscillator shifts because a metal body changes the loop inductance, while rain, temperature, and nearby wiring can shift the same signal. Proxy sensing succeeds only when the indirect fingerprint stays distinct from those background changes.
In Figure, read the observation path from the existing radio or loop signal through feature extraction to the inferred state. At the inductive-loop boundary, the last label is an inference, not a new physical measurement. For the buried inductive loop, that boundary matters when two people, two vehicles, or two room layouts can produce similar fingerprints.
In this proxy-sensing lane, an empty lane sits at 40.000 kHz and moves by ±4 Hz during normal weather. A car produces +20 Hz, reaching 40.020 kHz, so even its lower edge remains 16 Hz above the empty centre. A motorcycle produces only +3 Hz, reaching 40.003 kHz, which lies inside the observed drift band. Lowering the threshold to catch that motorcycle would also turn ordinary drift into vehicle events.
38.7.1 Predict the Inductive-Loop Verdict
- Predict: The loop rises by 18 Hz and stays there for 1.2 s. Is that stronger evidence than a 3 Hz, 40 ms spike? Check: Yes. Both shift size and dwell time separate a vehicle-shaped event from short electrical noise.
- Predict: A resurfacing job changes the empty-lane baseline by 12 Hz. Can the old threshold remain trusted? Check: No. The physical loop environment changed, so the proxy baseline must be measured again.
38.8 Release Checklist
Before relying on an infrastructure-sensing proxy, confirm these points:
Start by the physical feature is named explicitly: frequency shift, RSSI/CSI pattern, device count, power step, harmonic signature, or another measurable proxy. Then the baseline was collected under known empty, normal, and edge-case conditions and has a refresh schedule. Next thresholds are tested against drift, adjacent-zone cross-talk, small targets, and ordinary environmental changes. After that blind spots are documented, such as non-conductive vehicles for loops or access-point layout changes for Wi-Fi fingerprints. Continue by each decision records source signal, baseline timestamp, confidence/residual check, and cases outside the operating envelope. Finally safety-critical actions trigger a dedicated sensor, human check, or other independent confirmation.
38.9 See Also
Start by Sensing with Existing Infrastructure for the main Wi-Fi, NILM, cellular, and campus occupancy workflow. Then Sensor Calibration Techniques for baselines, reference records, and drift control. Next Sensor Data Processing for filtering and confidence checks after acquisition. Finally Sensor Selection Guide for deciding when infrastructure reuse is enough and when dedicated hardware is required.
38.10 Next
Return to Sensing with Existing Infrastructure once the proxy boundary is clear, then continue to Sensor Selection Guide to compare reuse against dedicated sensor deployments.