Solar Array Telemetry: Analog Smoothing, Moving Averages & Data Logging

Solar array telemetry and moving average signal conditioning schematic
FIG 1.1 // REMOTE SOLAR PV MICROGRID TELEMETRYSYSTEM: PV-STRING // 24VDC - 32VDC BUS SIGNAL CONDITIONING

The 4,000 False Alarms & The Weekend Database Crash

Imagine driving down a bumpy, rocky dirt road. If your car speedometer displayed the raw instant speed of each bounce every millisecond, the needle would violently blur between 20 MPH and 50 MPH! You wouldn't be able to read your speed, and your cruise control would violently jerk the throttle.

Modern cars solve this with digital smoothing—averaging recent readings to display a smooth, steady number.

In solar energy automation, sensors face the exact same problem from nature: passing clouds:

The Desert Microgrid Incident:

At an off-grid solar microgrid site in Nevada, an engineering intern configured the telemetry station to send an SMS alert whenever the solar battery charging voltage dipped below 24VDC.

On a partly cloudy Saturday afternoon, puffy cumulus clouds drifted across the desert sky. Every few seconds, the sunlight would dim for a brief moment, causing the raw voltage to dip from 28V down to 22V, and then bounce right back up.

The raw threshold comparator tripped and untripped continuously! By Sunday evening, the system had spammed over 4,200 text messages to the plant manager's phone and filled the remote cellular gateway memory to 100%, causing a complete communications lockup.

The Golden Lesson: Never connect raw, noisy analog signals directly to alarm thresholds or high-frequency loggers. Always filter transients with a Moving Average (AVERAGE) and log clean, periodic snapshots with a DATA_LOG block.

Understanding Analog Noise vs. Real Trends

When monitoring physical sensors (like solar voltage, wind speed, or temperature), readings contain two components:

  • The True Engineering Trend: The actual, meaningful state of the process (e.g., the sun is shining brightly at midday).
  • High-Frequency Noise: Temporary fluctuations caused by electromagnetic interference, cable induction, or passing cloud shadows.

If an automation system reacts to every millisecond of noise: Mechanical relays and contactors chatter violently, burning out contacts; databases get overwhelmed with useless junk; and false alarms wake up on-call technicians.

Stage 1: The Raw Unfiltered Comparator (Contactor Chattering)

Below is Stage 1 of our interactive lab. The raw solar voltage is wired directly into an ANALOG_COMPARATOR with a 24V threshold.

Try adjusting the slider in the simulation below:

Stage 1 of 3Stage 1 - Raw Unfiltered Solar Noise
0.0 s
Mini Map

YOUR NEXT EXPERIMENT

Start with a signal.

Add an input from the component library, connect a block, and press Run.

SIMULATION PAUSED100 ms / scan
Paused · Click to inspect

Loading workspace…

0 blocks · 0 wires
The Beginner Flaw in Stage 1

In the lab above, drag Raw Solar Voltage (V) back and forth across 24V (e.g., 23V, 25V, 22V, 26V). Notice how the Battery Charge Contactor immediately clicks ON and OFF with zero delay! In a real battery room, this rapid contactor chatter creates electrical sparks, welds relay points, and triggers hundreds of nuisance alarms.

Stage 2: Analog Smoothing with a Moving Average Filter

To solve signal chatter, we pass the raw analog signal through an AVERAGE block.

How a Moving Average Works: The block maintains a small FIFO memory buffer of recent measurements (e.g., 5 samples):

Smoothed_Output = (V1 + V2 + V3 + V4 + V5) / 5

When a brief shadow or voltage spike occurs, its impact is diluted across the buffer. The resulting output is a clean, stable engineering value that reflects the true trend without jitter!

Stage 2 of 3Stage 2 - Analog Smoothing with Moving Average
0.0 s
Mini Map

YOUR NEXT EXPERIMENT

Start with a signal.

Add an input from the component library, connect a block, and press Run.

SIMULATION PAUSED100 ms / scan
Paused · Click to inspect

Loading workspace…

0 blocks · 0 wires
Interactive Exercise — Stage 2

Observe Smoothed Array Voltage (V). When you change the raw voltage, notice how the filtered value transitions smoothly rather than jumping instantly. This gives the battery charging system a rock-solid, jitter-free signal to make smart decisions.

Stage 3: Full Microgrid Telemetry & Battery Charge Manager

In a production solar microgrid, the control logic must perform two essential tasks:

  • Safe Window Charging: Batteries must only charge when voltage is within safe limits (e.g., between 24V and 32V). Below 24V, sunlight is insufficient; above 32V, over-voltage threatens to boil battery electrolyte!
  • Periodic Telemetry Logging (DATA_LOG): Instead of logging continuous streams of data, the DATA_LOG block samples the clean, smoothed voltage at a steady, configured interval (e.g., every 500ms). This produces compact, orderly datasets ready for cloud transmission via MQTT or cellular IoT.
Stage 3 of 3Stage 3 - Full Solar Telemetry & Battery Charge Manager
0.0 s
Mini Map

YOUR NEXT EXPERIMENT

Start with a signal.

Add an input from the component library, connect a block, and press Run.

SIMULATION PAUSED100 ms / scan
Paused · Click to inspect

Loading workspace…

0 blocks · 0 wires
Interactive Exercise — Stage 3

1. At normal 28V, notice Battery Charge Contactor (KM-101) is energized and Telemetry Data Logging Active is TRUE.
2. Increase voltage to 34V (simulate a faulty charge controller). The Over-Voltage Hazard Alarm trips and cuts the contactor instantly to protect the battery bank!
3. Set voltage to 20V (simulate dusk or heavy overcast). The contactor disconnects safely without chattering.

Commissioning & Field Calibration Checklist

When deploying analog telemetry or data loggers on a remote solar installation, follow this 5-point field checkout:

  1. Verify Instrument Cable Shielding: Ensure the shielded drain wire from the voltage transducer (VT-101) is grounded at one end only (at the RTU cabinet) to avoid creating ground loops.
  2. Tune the Averaging Window: Sizing the sample buffer is a balance: too few samples (e.g., 2) leaves jitter; too many samples (e.g., 50) introduces noticeable phase lag during genuine daylight transitions. 5 to 10 samples is ideal for solar PV strings.
  3. Verify Logging Frequency: Confirm that data logging intervals match your network budget. On satellite or cellular IoT skids, sampling every 500ms to 5 seconds provides high fidelity without exceeding monthly data caps.
  4. Calibrate Analog Span: Measure the physical string voltage with a calibrated Fluke multimeter. Ensure the scaled analog reading on the PLC display matches within ±0.1VDC.
  5. Test Over-Voltage Cutoff: Inject a simulated test voltage of 33VDC into the analog channel and verify the battery charge contactor drops out immediately.

Key Engineering Takeaways

01 Filter Before Deciding

Always smooth volatile analog signals before feeding them into comparators or safety trips.

02 Moving Averages (AVERAGE)

Rolling FIFO buffers flatten noise while preserving genuine physical trends without high phase lag.

03 Save Bandwidth with DATA_LOG

Record clean, periodic snapshots rather than flooding databases and cellular links with millisecond noise.

04 Dual Boundary Limits

Always protect battery assets with both low-voltage dropout and high-voltage overcharge protection.