19 Signal Processing Essentials

19.1 In 60 Seconds

Keep One Fast Event Visible

Picture a vibration sensor reporting a smooth line while a brief machine strike disappears. 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. Choose both from the fastest useful event and the required range.

Feed in one known slow signal and one known fast pulse. Change the rate, input range, and filter; retain raw and processed traces, settings, times, and missed-event results.

This runway does not prove that every signal is preserved. The deeper sections explain aliasing, resolution, quantization, filtering, calibration, noise, and the limits of each validation trace.

Signal processing is the evidence path between a physical event and a digital decision. Preserve the phenomenon first, then choose sample rate, ADC resolution, filtering, and validation from the event shape, range, noise, and timing constraints. More samples, more bits, or more filtering only help when they protect evidence the application actually needs.

19.2 Start With the Story

You will separate sampling, ADC resolution, and filtering decisions and identify the evidence each one needs. Start with the physical signal, its useful bandwidth, and the changes your application must detect.

Trace one measurement across four beats to see how every processing choice changes the evidence that finally leaves the device.

The mathematical gist. Resolving $10.0$ g across $5000$ g needs $\lceil\log_2(5000/10)\rceil=9$ bits: $8$ bits give $19.5$ g codes and fail, while $9$ bits give $9.77$ g codes and pass. 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.

Math Bridge · guided foundationsHow many bits resolve 10 g on a 5 kg scale?Phoebe works backward from the requirement, checks both sides, and names the analog-noise limit.Learn the maths

19.3 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.

The important idea is that the best design is not the fastest or most precise possible. It is the one that preserves the required phenomenon with enough evidence to explain the decision.

Think of a witness statement. You want an accurate, explainable account of what happened, not the longest possible transcript. 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. 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.

Connect Turn a Signal into Trustworthy Evidence to the visual Figure 19.1 by locating Sensor and range + noise. The pair turns The signal chain: sensor output, analog conditioning, ADC sampling, digital filtering, and validated data into something the team can verify.

Signal chain review order begins the visual in Figure 19.1 and names a responsibility. Next, Sensor marks information entry; finally, range + noise sets spatial acceptance. 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. Carry Sensor into the next Turn a Signal into Trustworthy Evidence decision.

The Three Core Decisions

Beginner Examples

• A slow humidity monitor can use a modest sample rate and simple validation because the physical event changes gradually.
• A motor-current sensor must preserve short load changes, so the review checks bandwidth and sampling before any smoothing.
• An acoustic monitor combines analog filtering, sampling, compression, and packet budgeting, so the record covers both signal quality and network cost.

Signal Basics Knowledge Check

If you can name the core decisions, you can stop here. Continue to Practitioner to make and record a signal-processing decision.

19.4 Apply It: Make a Signal-Processing Decision

Every decision should connect back to the phenomenon the product must preserve. Separating the three choices makes the review far easier, because rate, resolution, and filtering each solve a different problem.

Walkthrough: From Phenomenon to Record

1. State the phenomenon. Name the physical variable, expected range, timing, and event shape.
2. Choose the boundary. Decide what belongs in analog conditioning, ADC conversion, digital filtering, or later handling.
3. Match the setting to evidence. Select sample rate, bit depth, and filter type from bandwidth, noise, range, and validation needs.
4. Record what changed. Keep enough raw and processed evidence to explain why the chosen settings are safe.

Make Walkthrough: From Phenomenon to Record traceable: inspect Figure 19.2 for Keep the three decisions separate. Focus next on Sample Rate, the companion label anchoring The three decisions, separated by the evidence each one needs and the risk each one carries.

Compare the three columns of Figure 19.2 from left to right. Sample rate depends on timing evidence, resolution on amplitude evidence, and filter choice on the failure pattern. Each setting addresses a different problem, so one cannot justify the others.

Try It: Filter Frequency Response Explorer

Filtering is the decision learners most often rush. Choose a filter only after you can name the failure pattern. Use the explorer to move a cutoff and see which frequencies pass and which are attenuated, so the filter matches the problem rather than guessing.

Worked Review: A Slow Sensor with Sharp Jumps

An environmental sensor occasionally reports sharp jumps. Do not immediately raise resolution or average more samples. Review the chain in order:

1. Physical behavior: decide whether sharp jumps are even possible in this environment.
2. Analog boundary: check supply, reference, grounding, range, and whether the signal clips.
3. Sample plan: confirm the interval can see the fastest event that matters.
4. Resolution fit: compare the required change with the code step and noise.
5. Failure pattern: decide whether the jumps are isolated spikes, aliasing, saturation, or real events.
6. Filter decision: choose median, average, low-pass, notch, or no filter from that pattern.
7. Validation: capture before and after evidence and record what the filter might hide.

Incremental Practice

Sampling Boundary Knowledge Check

If you can make and record a defensible decision, you can stop here. Continue to Under the Hood for the boundary rule, resolution fit, and filter selection details.

19.5 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. 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. Review each decision against the evidence it depends on before treating a smoother or more precise-looking trace as more trustworthy.

Before Under the Hood: Boundaries, Resolution Fit, and Filter Choice, inspect the figure Figure 19.3. Compare Signal Processing with filtering improves SNR; their difference reveals Signal-processing concept map: sampling, ADC resolution, filtering, and SNR are coupled decisions, not independent tuning knobs. This gives Under the Hood: Boundaries, Resolution Fit, and Filter Choice evidence to revisit.

In the diagram Figure 19.3, begin at Signal Processing, which highlights Signal Processing. Shift next to filtering improves SNR because it highlights filtering improves SNR, and close on Anti-aliasing filter required, which highlights Anti-aliasing filter required. 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.

The Boundary Rule

Digital filtering cannot recover information that the analog front end or sampling plan already lost. 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.

Resolution Fit

Resolution is an amplitude decision. Compute the code step from the reference range and bit depth, then compare it with the smallest meaningful physical change:

If analog noise, sensor accuracy, or calibration uncertainty is larger than the code step, extra bits may add no information. Useful questions: what physical change must be detected, what voltage span maps to it after conditioning, is the reference matched to that span, and is the noise floor below the planned code step?

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. If bench noise already jitters by several codes, adding more bits mostly records noise. 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.

Filter Selection by Failure Pattern

Name the failure pattern first, then pick the filter that targets it.

Use the figure Figure 19.4 to test Filter Selection by Failure Pattern against the depicted system. Filter Selection Guide and Smooth sensor readings expose the two named boundaries behind Choose the filter from the noise pattern: low-pass, high-pass, band-pass, or notch, each matched to a specific problem.

Start with the noise question at the top of Figure 19.4, then follow the matching branch downward. The response sketches show which frequencies pass or are rejected; use them to match the filter to the observed problem.

Common Pitfalls

1. Treating more data as better data. Higher rates and wider bit depths can grow files without preserving better evidence.
2. Filtering before naming the failure pattern. A filter chosen without evidence can hide the event the system should detect.
3. Fixing analog problems in software. Smoothing cannot undo clipping, reference mismatch, saturation, or aliased content.

Filter Selection Knowledge Check

Where Each Decision Is Developed

This chapter is a map. The focused chapters carry the deeper method for each decision: timing and Nyquist, code-step and filtering detail, and sensor dynamics.

The next Where Each Decision Is Developed decision depends on the diagram Figure 19.5. Reading Overview against sample plan clarifies the practical meaning of The review route to the focused signal-processing chapters.

Start at the overview in Figure 19.5 and use the nearby labels to choose a focused chapter. The upper row covers sampling and filtering; the lower row directs you to lag, calibration, and compression questions.

At this depth, signal processing is the evidence path between the physical world and a digital decision. The strongest designs are easy to explain: they preserve the phenomenon that matters, discard what does not, and leave enough evidence for another engineer to repeat the decision.

19.6 Summary

• Signal processing turns a changing electrical signal into digital evidence software can trust.
• Separate the three core decisions: sample rate is timing, ADC resolution is amplitude, and filtering responds to a named failure pattern.
• The boundary rule holds: digital filtering cannot recover information lost to aliasing, clipping, saturation, or a bad reference.
• Fit resolution to the smallest meaningful change and the noise floor, not to the largest available bit depth.
• Choose a filter from the observed problem; a median rejects isolated spikes, a moving average smooths jitter, a low-pass removes high-frequency noise, and a notch targets one known tone.
• The strongest designs leave a record that another engineer can use to repeat the decision.

19.7 See Also