Signal Conditioning

Many digital input problems come down to a simple cause: nobody is really driving the pin.

A button input toggles when it is not pressed. A relay glitches during power-up. An I2C edge rises too slowly. A long input wire false-triggers when a motor starts. Firmware sees only 0 and 1, but the physical node behaves like a random state.

The first job of a pull-up or pull-down resistor is to give a node a defined level when no active driver is controlling it.

Many device bring-up sessions run into the same symptom: the sensor is not moving, the environment looks stable, but the raw ADC value keeps jumping.

The first reaction is often to add averaging, add a low-pass filter, or adjust thresholds. Sometimes that makes the curve look better, but it does not necessarily solve the problem. ADC jitter is not a single issue. It is the visible result of the whole analog chain.

Many sensors work well on the bench, then fail once the cable becomes long.

A door sensor toggles randomly. A water leak probe alarms without water. An external button triggers by itself. An analog voltage input shows strange spikes. The issue gets worse near motors, relays, or inverters.

These problems are often called “interference,” but a long wire is not just extra copper. It turns an on-board input node into a field-exposed system.

Op-amps are common in sensor front ends. They amplify small voltages, buffer high-impedance signals, add bias, build filters, or convert current into voltage.

They are also easy to misuse. On a schematic, an op-amp looks like a simple triangle, and the formula often looks simple:

output = input * gain

In real circuits, an op-amp is not an ideal amplifier that works at any voltage, frequency, and load. It has input range, output range, speed, accuracy, noise, power, and stability limits. Once one of those limits is hit, the ADC value seen by firmware may saturate, slow down, drift, oscillate, or carry strange noise.