Analog Electronics and 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.

When debugging ADC measurements, it is natural to focus on the input pin: sensor output, divider ratio, front-end filtering.

But the ADC result is not determined by input voltage alone. Reference voltage participates in every conversion.

A more accurate first model is:

ADC code ≈ Vin / Vref * full scale

The ADC reads the ratio between input voltage Vin and reference voltage Vref. If Vin changes, the result changes. If Vref changes, the result also changes.

Many sensor field problems look like unstable algorithms, ADC jitter, or poor modules. They often end up being ground and power problems.

The reading is stable when the device is idle, but jumps when a motor starts. Temperature moves during radio transmission. Pressure shifts after a relay turns on. USB power and battery power give different values. Short lab wiring works, while the field installation is noisy.

The physical quantity may not have changed. The measurement reference changed.

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.

When a device reading jitters, a common first reaction is to add a capacitor at the input.

It often helps. ADC values become steadier. Button voltage is less jumpy. Long-wire spikes are reduced. Sensor curves look smoother.

But another problem often appears after that: the device responds more slowly. A water leak alarm becomes late. Overcurrent protection reacts too slowly. A button voltage trails after release. A control loop feels dull or even starts to oscillate.

A voltage divider looks like one of the simplest analog circuits.

Vout = Vin * R2 / (R1 + R2)

Two resistors in series, a midpoint into the ADC, and a high voltage becomes a lower voltage. Battery voltage, button ladders, external inputs, and NTC dividers often use this pattern.

But many field problems start here too. The ratio is correct, but the ADC value is not. Large resistors save power, but readings jitter. Connecting the next stage pulls the voltage down. Moisture makes the divider drift. Input overvoltage creates more protection current than expected.