Measurement and design 5 MIN READ

Your sensor log can hide an oscillation

A smooth trace can be a sampling artifact. Before retuning a controller, check how the trace was measured.

A smooth trace can be a sampling artifact. Before retuning a controller, check how the trace was measured.

01 / FIELD NOTE

Start with how the trace was acquired

A low-frequency ripple appears in a motor log. Lowering controller gain is tempting, but the ripple might be a high-frequency component folded down by sampling. Write down the sensor sampling rate, any decimation, the analog filter and timestamps before changing the control law. The plotted frame rate is not necessarily the sensor sampling rate.

02 / FIELD NOTE

Two curves, identical measurements

Use the 7 Hz at 10 Hz preset. Predict a 3 Hz apparent frequency and inspect the circles on the original and dashed candidate. They coincide despite different curves between them. Now raise only the sampling rate to 20 Hz: the candidate becomes the original 7 Hz signal. Finally try the Nyquist boundary preset, then move phase from 0° to 90°. An all-zero log can turn into alternating extremes without changing amplitude or frequency.

03 / FIELD NOTE

Repair the measurement path first

A smoother plot or a digital filter cannot establish what the pre-sampled waveform was. Reacquire with a suitable rate and analog filtering, then compare the same physical operating condition. This isolated sine example contains no sensor noise or jitter; real measurements also need timestamp and calibration checks. Do not treat a clean-looking trace as evidence that the plant stopped vibrating.

TAKEAWAY

An anti-alias filter acts before sampling to reduce unwanted high frequencies. Filtering already aliased samples generally cannot tell overlapping frequencies apart. Sampling rate, quantization, and measurement delay are different effects; this bench isolates sampling.

PUT IT TO THE TEST

From reading to a repeatable run.