IoT Fundamentals · Study deck
Signal Processing Essentials
Picture a vibration sensor reporting a smooth line while a brief machine strike disappears.
Physics Phoebe is your guide for this deck.
After studying this chapter
Learning objectives
You will be able to:
- Explain: The ideal $9$-bit quantization floor is $9.77/\sqrt{12}=2.82$ g RMS, but real sensor and front-end noise can sit above it, so more bits cannot clean a noisy analog signal.
- Explain: This route carries: Under the Hood: Boundaries, Resolution Fit, and Filter Choice from Signal-processing concept map: sampling, ADC resolution, filtering, and SNR are coupled decisions, not independent tuning knobs into the project record.
- Explain: The observable change from: Signal chain review order to range + noise explains The signal chain: sensor output, analog conditioning, ADC sampling, digital filtering, and validated data.
Major section
In 60 Seconds
The number looks tidy, but the processing chain may have removed the event the team needed to see.
- Sampling rate means how many measurements are taken each second.
- Analog-to-digital converter means a circuit that turns a voltage into a number; it is often shortened to ADC.
- This runway does not prove that every signal is preserved.
Major section
Start With the Story
You will separate sampling, ADC resolution, and filtering decisions and identify the evidence each one needs.
- The ideal $9$-bit quantization floor is $9.77/\sqrt{12}=2.82$ g RMS, but real sensor and front-end noise can sit above it, so more bits cannot clean a noisy analog signal.
Major section
Turn a Signal into Trustworthy Evidence
Signal processing turns a sensor's changing electrical signal into digital evidence that software can trust.
- The essential choices are where the useful signal lives, how fast to sample it, how much ADC resolution is meaningful, what filtering belongs before or after conversion, and how the result will be validated.
Major section
Turn a Signal into Trustworthy Evidence (continued)
The important idea is that the best design is not the fastest or most precise possible.
- Oversized settings can record pages of noise; a good signal-processing design records the part that matters and can show why.
- For example, a motor-current monitor should preserve the short rise that marks a jam or stall, not merely the average current over a long window.
- If you can name the core decisions, you can stop here.
Major section
Turn a Signal into Trustworthy Evidence (continued)
Sampling too slowly can make the pulse disappear; filtering too aggressively can make it look like a gentle ramp; choosing more ADC bits cannot help if the pulse was never captured.
- The useful design records enough raw evidence to show the event, then filters only the noise pattern that would mislead the decision.
- That record should include one raw trace, one filtered trace, and the reason the filter preserves the event.
- The pair turns The signal chain: sensor output, analog conditioning, ADC sampling, digital filtering, and validated data into something the team can verify.
Major section
Turn a Signal into Trustworthy Evidence (continued)
The observable change from: Signal chain review order to range + noise explains The signal chain: sensor output, analog conditioning, ADC sampling, digital filtering, and validated data.
- More bits help only when the sensor and front end can support them.
- A motor-current sensor must preserve short load changes, so the review checks bandwidth and sampling before any smoothing.
- Beginner Examples A slow humidity monitor can use a modest sample rate and simple validation because the physical event changes gradually.
Major section
Apply It: Make a Signal-Processing Decision
Every decision should connect back to the phenomenon the product must preserve.
- Each setting addresses a different problem, so one cannot justify the others.
- Useful bandwidth, event duration, anti-alias boundary, timestamp need.
- Too slow makes false patterns; too fast grows energy, storage, and transmission load.
Major section
Apply It: Make a Signal-Processing Decision (continued)
Sensor range, useful span, required change size, noise, reference, calibration.
- Too coarse hides changes; too fine records noise and wastes budget.
- The wrong filter adds lag, smears faults, or removes the event you need.
- Intermediate For a motor-current channel, write why bandwidth and sampling are checked before any smoothing.
Major section
Under the Hood: Boundaries, Resolution Fit, and Filter Choice
The deeper layer explains why the order of the chain matters and how each setting is bounded by physics rather than by the largest available specification.
- A concept map keeps the dependencies visible.
- This gives: Under the Hood: Boundaries, Resolution Fit, and Filter Choice evidence to revisit.
Major section
Under the Hood: Boundaries, Resolution Fit, and Filter Choice (continued)
Resolution Fit Resolution is an amplitude decision.
- Sampling sets time resolution and anti-aliasing requirements; ADC range and bit depth set amplitude resolution; filtering changes lag and bandwidth; SNR limits whether the extra samples or extra bits are actually informative.
- The Boundary Rule Digital filtering cannot recover information that the analog front end or sampling plan already lost.
- If bench noise already jitters by several codes, adding more bits mostly records noise.
Major section
Under the Hood: Boundaries, Resolution Fit, and Filter Choice (continued)
This route carries: Under the Hood: Boundaries, Resolution Fit, and Filter Choice from Signal-processing concept map: sampling, ADC resolution, filtering, and SNR are coupled decisions, not independent tuning knobs into the project record.
- Aliasing, clipping, saturation, and an unsuitable reference range must be handled before or during conversion, not explained away afterward.
- Software can make a sampled sequence smoother, but it cannot prove that the lost information never mattered.
- If analog noise, sensor accuracy, or calibration uncertainty is larger than the code step, extra bits may add no information.
- Where Each Decision Is Developed This chapter is a map.
Major section
Under the Hood: Boundaries, Resolution Fit, and Filter Choice (continued)
Moving average Use when random jitter dominates and a slower response is acceptable.
- Worked example: a load-cell front end may need to detect a 10 g change on a 5 kg scale.
- If the conditioned signal maps that change to less than one ADC code, the design needs more gain, a narrower reference, or a better converter.
- Median Use when occasional isolated spikes appear and should not pull nearby readings.
Major section
Under the Hood: Boundaries, Resolution Fit, and Filter Choice (continued)
The review should compare required physical change, conditioned voltage span, code step, and measured noise before declaring the resolution good enough.
- The same record should state which physical change the chosen code step can still separate.
- The response sketches show which frequencies pass or are rejected; use them to match the filter to the observed problem.
- Low-pass Use when useful behavior is slower than the unwanted high-frequency noise.
Major section
Under the Hood: Boundaries, Resolution Fit, and Filter Choice (continued)
Notch Use when one known interference tone, such as mains hum, can be targeted.
- Common Pitfalls Treating more data as better data.: Higher rates and wider bit depths can grow files without preserving better evidence.
- Filtering before naming the failure pattern.: A filter chosen without evidence can hide the event the system should detect.
- Fixing analog problems in software.: Smoothing cannot undo clipping, reference mismatch, saturation, or aliased content.
Deck summary
Key takeaways
The number looks tidy, but the processing chain may have removed the event the team needed to see.
- You will separate sampling, ADC resolution, and filtering decisions and identify the evidence each one needs.
- Signal processing turns a sensor's changing electrical signal into digital evidence that software can trust.
- The important idea is that the best design is not the fastest or most precise possible.
- Sampling too slowly can make the pulse disappear; filtering too aggressively can make it look like a gentle ramp; choosing more ADC bits cannot help if the pulse was never captured.
Retrieval practice
Recall check 1 of 3
Physics Phoebe says: answer from memory, then check your reasoning.
Q1A sampled signal looks unstable and hard to interpret. Which set of basics should be checked first?
Show answer
Answer: B Signal quality depends on sampling, filtering, calibration, sensor range, and the noise sources around the measurement.
Retrieval practice
Recall check 2 of 3
Physics Phoebe says: answer from memory, then check your reasoning.
Q2A sampled sensor trace looks smooth, but a faster reference capture shows brief pulses that never appear in the logged data. What should be reviewed first?
Show answer
Answer: C If the event is missed before or during sampling, no later filtering can recover it.
Retrieval practice
Recall check 3 of 3
Physics Phoebe says: answer from memory, then check your reasoning.
Q3A channel shows occasional isolated spikes. An engineer adds a long moving-average filter to remove them. What is the likely problem?
Show answer
Answer: C Averaging spreads a spike's energy and delays the response.
Print reference
Answers
Answer key.
- B · Signal quality depends on sampling, filtering, calibration, sensor range, and the noise sources around the measurement.
- C · If the event is missed before or during sampling, no later filtering can recover it.
- C · Averaging spreads a spike's energy and delays the response.