1. Problem Statement
On a LOGO! 8 base module (for example, 6ED1052-1MD08-0BA1 LOGO! 12/24 RCE or 6ED1052-1CC08-0BA1 LOGO! 24 RCE), the on-board analog inputs I7 and I8 show a noisy, fluctuating process value when wired to a PT100-to-0-10 V transmitter. The fluctuation survives a stable supply voltage and disappears when the same input is driven from a digital potentiometer (a clean, low-impedance bench source). The observed jitter is typically 3-12 counts on a 0-1000 normalized scale (3 mV-12 mV on a 10 V span), which is well outside the LOGO! 8 data-sheet repeatability when the analog front end is properly terminated.
This pattern is the classic signature of common-mode and capacitive noise injection on a high-impedance analog node, not a failed module. The first thing to confirm is that the symptom is not a hardware defect by swapping the wiring between I7 and I8: if the noise stays with the cable, the cable is the source; if the noise stays with the input, the input is suspect. In the field, the cable wins almost every time.
2. Root Cause Analysis
The LOGO! 8 base module exposes I7 and I8 as 0-10 V single-ended analog inputs. The Siemens data sheet specifies an input impedance of approximately 80 kΩ on these channels. That high impedance is necessary to avoid loading the field device, but it also makes the node a good antenna: every volt of coupled common-mode noise appears directly as a process-value excursion.
The PT100 transmitter in the user's rig, by contrast, typically presents a low-impedance output (10-500 Ω) with a clean, driven 0-10 V rail. The digital potentiometer is even cleaner. So the transmitter itself is not the culprit; the path between the transmitter and the LOGO! terminal is.
The four real root causes seen in this scenario, in order of frequency, are:
- Unshielded analog pair routed in parallel with switching conductors. Capacitive coupling from adjacent AC or DC switching wires (relay coil returns, contactor legs, VFD output cables, even 24 V DC power) injects an AC component directly into the high-Z analog node. A 50 Hz/60 Hz mains field typically shows up as 3-6 count drift; a nearby PWM drive shows up as a 4 kHz-16 kHz ripple superimposed on the DC value.
- No or poor shield bonding. Even when shielded cable is used, a shield that is not bonded at one end (and only one end) acts as a pickup loop rather than a barrier. Shielding the analog pair is meaningless if the drain wire is floating.
- Shared or "dirty" ground reference. The 0-10 V return (M of the analog input, terminal M on the base module) tied to a ground bus that also carries load currents will have a few hundred millivolts of IR drop riding on it. The transmitter "sees" that ground bounce and the LOGO! "sees" it again, so it double-counts.
- Source impedance too high relative to input impedance. A passive or weakly-buffered PT100 transmitter with output impedance above 1 kΩ, paired with a long unshielded run, forms an RC low-pass that integrates line noise. Verify the source impedance spec; if the transmitter cannot drive 80 kΩ without measurable attenuation, the front end is technically out of spec.
3. Confirming the Diagnosis
Use this matrix to localize the noise source before changing anything. Each test is non-destructive and takes less than five minutes on a running machine.
| Test | Action | Pass / Fail Indication |
|---|---|---|
| Channel swap | Move the AI wire from I7 to I8 (or vice versa) at the LOGO! terminal only. | If noise follows the cable, the cable path is bad. If noise stays on the terminal, the input or connector is suspect. |
| Source swap | Replace the PT100 transmitter with a calibrated 0-10 V bench source (or a fresh 9 V battery + potentiometer) at the same terminal. | If noise disappears, the transmitter or its loop is the source. If noise remains, the LOGO! side is the source. |
| Scope the terminal | Connect an oscilloscope (AC coupled, 20 MHz BW) to AI+ and M at the LOGO! terminal. | A clean DC line within ±5 mV rules out the module. Visible ripple or 50/60 Hz hum confirms injection. |
| Ground lift test | Disconnect the transmitter's GND/0 V from the panel ground bus and read the AI value with a battery-powered meter referenced to LOGO! M. | If the noise drops, the panel ground is the return path for the noise; bond the transmitter ground directly to LOGO! M. |
| Cable reroute | Disconnect the analog pair and lay a temporary 1 m twisted shielded jumper from the transmitter to the LOGO! terminal, away from power cables. | If the noise goes away, the original routing is the source. |
If the channel swap and source swap both indicate the cable/transmitter side, proceed to Section 4. If both indicate the LOGO! side, check the terminal seating, then the firmware version, then consider RMA.
4. Step-by-Step Resolution
Apply these in order. Each step is independent, and you can stop as soon as the noise clears.
4.1 Re-seat the analog terminal block
Power down the LOGO!, remove the detachable terminal block for I7/I8, inspect for discoloration or loose screws, and re-install with the recommended torque. The Siemens manual specifies 0.6 Nm for the LOGO! 8 plug-in terminals. A loose M (analog common) is the single most common cause of intermittent analog noise on LOGO! installations.
4.2 Enable the on-board analog filter FB
LOGO! Soft Comfort (LSC) provides a dedicated Analog Filter function block (FB) under Special Functions > Analog > Analog Filter. This block performs a moving average over a configurable number of samples, which suppresses both high-frequency noise and 50/60 Hz pickup.
- Open the LSC program and place the Analog Filter FB on the AI input tag (for example,
AI1). - Set
Sn(number of samples) to a value appropriate for the response time you need. Each sample on a LOGO! 8 base module is one scan cycle, typically 50 ms when only digital I/O is configured, and longer when the AM2 PT100 expansion module is on the bus. - Select
Averageas the filter type. The block will then output the arithmetic mean of the lastSnsamples. - Compensate for the added lag in the downstream control loop. As a rule of thumb,
Sn = 20(1 second of averaging) is a sensible starting point for temperature loops driven by a PT100.
Sn cleans the display but adds lag. If I7/I8 is feeding a fast closed-loop controller, treat the filter as part of the loop time constant when tuning. For a temperature loop with a 30-60 second natural response, 1-2 seconds of filtering is invisible.4.3 Replace the cable with a shielded twisted pair
For 0-10 V analog runs longer than 0.5 m, use a shielded twisted pair (e.g., LiYCY 2 x 0.34 mm²) with the shield bonded to the LOGO! M terminal at the LOGO! end only. The transmitter end of the shield must remain open, or be capacitively bypassed (10 nF + 1 MΩ) to chassis ground, to avoid a ground loop. Per the LOGO! 8 system manual, the analog inputs are referenced to M, and the cable shield should be treated as an extension of that reference at the LOGO! end.
4.4 Reroute away from noise sources
Maintain at least 200 mm of physical separation between the analog pair and any of the following:
- AC power conductors (especially 230 V coil return lines from contactors and solenoid valves).
- LOGO! relay output conductors carrying inductive loads (the dry-contact outputs on the relay variants of the base module).
- Variable frequency drive output cables (PWM common-mode is broadband and aggressive).
- 24 V DC power trunks shared with solenoid valves.
If crossing is unavoidable, cross at 90 degrees rather than running parallel.
4.5 Provide a clean dedicated ground for the transmitter
Run a dedicated 0 V / M conductor from the LOGO! M terminal to the transmitter's GND terminal, and bond the cable shield at the LOGO! end to that same M terminal. The transmitter's chassis ground (if present) should be bonded to the panel chassis at the transmitter end, not at the LOGO! end. This is the standard "single-point shield ground" pattern that prevents shield currents from modulating the signal return.
4.6 Verify the transmitter output impedance is in spec
The transmitter's 0-10 V output must be able to drive the LOGO! 80 kΩ input without measurable attenuation. For a 4-wire (loop-powered or separately-powered) industrial PT100 transmitter, output impedance is typically ≤ 50 Ω and the loading error is below 0.07 %. If the transmitter in use is a low-cost 2-wire device with an output impedance above 1 kΩ, replace it with a 4-wire type or add an op-amp buffer (e.g., a single LM358 powered from the LOGO! 24 V rail) between the transmitter and the LOGO! terminal.
4.7 Add a hardware RC filter at the terminal as a last resort
If the noise is broadband and the filter FB is not enough, install a 10 kΩ resistor in series with the AI+ line and a 100 nF X7R ceramic capacitor from AI+ to M, both at the LOGO! terminal. This forms a ~1.6 kHz first-order low-pass that does not load a 50 Ω source but blocks RF and PWM noise. Combined with the filter FB, this is usually overkill in the good sense of the word.
5. Verification
After each fix, watch the LOGO! display or LSC online monitor for at least 10 minutes with the system in its normal operating state (drives running, contactors cycling). The AI value should be steady to within ±2 counts (2 mV) on a stable temperature.
Quantitative acceptance criteria:
- Steady-state noise: Peak-to-peak variation ≤ 0.5 % of span (5 counts on a 0-1000 scale).
- Step response: Time to reach 90 % of a 10 % input step within the expected loop time constant, plus filter delay. If the step is excessively slow, the filter FB or RC filter is over-tuned.
- Cross-channel isolation: Toggle a relay output on the same base module and confirm the AI value does not move more than 1-2 counts.
6. Firmware-Specific Notes
LOGO! 8 firmware has been updated several times since launch. The current long-term branch as of 2024 is FS: 03 (8BA8) for the LOGO! 8.2 line, with the newer LOGO! 8.3 (8.FW4) line shipping firmware FS: 04 on the 6ED1052-xMD08-0BA2 part numbers. The on-board AI behavior and the Analog Filter FB have not changed in a way that affects this troubleshooting path, but if the LOGO! is on a very early 8BA6 firmware, Siemens released an I/O timing fix that may slightly reduce noise coupling on the AI channels.
Sn value between firmware versions.7. Comparison with Other Small-PLC Analog Behavior
The same root cause pattern — fluctuating analog readings on a high-impedance input when driven by a real-world sensor — is well documented across the small-PLC landscape. The underlying physics is identical, and the remediation principles are identical.
| Platform | Symptom | Stated Cause | Resolution Pattern |
|---|---|---|---|
| Siemens LOGO! 8 (I7/I8) | 3-12 count jitter on 0-1000 scale from PT100 transmitter | Unshielded cable, no filter FB, ground reference shared with loads | Shielded twisted pair + Analog Filter FB + dedicated M return |
| Arduino Uno/Mega ADC | Several counts of jitter on a stable 5 V source | Source noise or too-high potentiometer resistance (analog-input pin impedance is far higher than PLC AI) | Lower source impedance, add 100 nF at the pin, average in software |
| Rockwell Micro820 (2080-IF2 or 2080-IF4) | Fluctuation within rated accuracy/error | External noise coupling, normal behavior within spec | Use manufacturer-rated filtering; ensure proper shield and ground; consult Rockwell Knowledgebase |
| AutomationDirect CLICK / ProductivityOpen | Intermittent raw-value jumps | Resets, shared ground, or noise on the analog common | Power-cycle test, isolate analog return, add RC filter at terminal |
The shared lesson is that all single-ended high-impedance analog inputs on compact controllers require shielded, separately-routed, single-point-grounded wiring for reliable sub-percent measurement. Treating the analog pair as a digital wire is the root cause of nearly every fluctuation ticket in the field.
8. Specification Reference
| Parameter | Value (LOGO! 8 base module, I7/I8) |
|---|---|
| Function | Analog input, single-ended, 0-10 V |
| Input impedance | ≥ 80 kΩ (per Siemens data sheet) |
| Resolution | 10 bits, normalized to 0-1000 in LSC |
| Maximum input voltage | 28.8 V continuous (damage threshold higher) |
| Sampling | Per base-module scan; typically 50 ms digital, longer with AM2 expansion on the bus |
| Repeatability / error | ±1.5 % of full scale at 25 °C (typical published value for 0-10 V on I7/I8) |
| Recommended cable | Shielded twisted pair, shield bonded at LOGO! M only |
| Terminal torque | 0.6 Nm |
9. Preventive Checklist for Future Installations
- Always run a shielded twisted pair for any AI on I7/I8, even for short runs inside the panel.
- Bond the shield at the LOGO! M terminal only, never at both ends.
- Provide a dedicated analog M conductor back to the LOGO!; do not share the analog return with a load's 0 V.
- Default to enabling the Analog Filter FB at
Sn = 10for any temperature loop and increase only if needed. - Maintain ≥ 200 mm of physical separation from AC, relay-output, and VFD cables; cross at 90° when necessary.
- Torque the LOGO! detachable terminals to 0.6 Nm and inspect annually for thermal cycling loosening.
- Verify that the PT100 transmitter is a 4-wire type or has an output impedance low enough to drive 80 kΩ without attenuation.
10. Quick Troubleshooting Matrix
| Symptom | Likely Cause | First Action |
|---|---|---|
| 3-12 count jitter, 50/60 Hz signature | Mains pickup on unshielded cable | Shielded cable, bond at LOGO! M |
| High-frequency ripple on AI value | VFD or PWM drive coupling | Increase physical separation, add RC filter, lower PWM carrier |
| Jitter proportional to load current elsewhere | Shared ground return | Run dedicated M to transmitter |
| Jitter disappears when transmitter is replaced by bench source | Source impedance or transmitter noise | Verify transmitter spec, replace with 4-wire type |
| Jitter follows the terminal, not the cable | Loose terminal or damaged input | Re-seat, retorque, swap channel, then RMA |
| Slow but clean response to temperature change | Filter FB over-tuned | Reduce Sn until loop time constant is acceptable |
Why are my LOGO! 8 analog inputs I7 and I8 fluctuating when connected to a PT100-to-0-10V transmitter but stable with a potentiometer?
The most common cause is noise injection on the analog pair. I7/I8 present a high input impedance of roughly 80 kΩ, so any capacitive coupling from adjacent switching wires, a poor shield bond, or a shared ground return shows up as visible process-value jitter. A bench potentiometer is a clean, low-impedance source and masks the issue. Replace the unshielded run with a shielded twisted pair bonded at the LOGO! M terminal, enable the Analog Filter FB in LOGO! Soft Comfort, and verify the transmitter's output impedance is low enough to drive 80 kΩ.
What input impedance do the LOGO! 8 on-board analog inputs I7 and I8 present?
Per the Siemens LOGO! 8 system manual, the 0-10 V analog inputs on the base module have an input impedance of approximately 80 kΩ. Any source with output impedance above 1 kΩ should be considered marginal, and a 4-wire PT100 transmitter with output impedance of 50 Ω or less is recommended.
How do I enable the analog input filter on a LOGO! 8 in LOGO! Soft Comfort?
Insert the "Analog Filter" FB from Special Functions > Analog onto the AI input tag (for example AI1), set the sample count Sn to 10-20 for a typical temperature loop, and select the "Average" filter type. Each sample corresponds to one LOGO! scan cycle, approximately 50 ms on a base module with no expansion. Higher Sn values reduce noise but add loop lag.
How tight should the detachable analog terminal block screws be on a LOGO! 8?
The Siemens LOGO! 8 manual specifies 0.6 Nm for the plug-in terminal blocks. A loose M (analog common) terminal is one of the most common causes of intermittent analog noise on LOGO! installations and should be re-torqued whenever an analog issue is investigated.
Is some fluctuation on the LOGO! 8 analog inputs normal?
A peak-to-peak variation of 1-2 counts (1-2 mV on a 10 V span) on a stable input is within the published ±1.5 % full-scale error of the I7/I8 channel. Jitter above 3 counts, or jitter that correlates with switching loads elsewhere on the machine, is not normal and indicates either wiring, grounding, or filter configuration issues that can be resolved with the steps in this guide.