Commissioning Your First Analog PLC Program: A Field Guide

1. Overview: Why Analog Is Harder Than Digital

Digital I/O has two states and is forgiving. Analog I/O is continuous, noisy, scaled, and can fail in a thousand quiet ways that digital cannot. When you load and run your first analog program, you are not just reading a voltage or current; you are translating a real-world physical quantity (temperature, pressure, flow, level) into a stable, calibrated engineering value that operators and downstream logic can trust.

There is a well-known piece of field wisdom that captures the rest of the journey: the easy part is making the I/O light up; the difficult part is trying to keep it from doing all the infinite number of things that can lead to a catastrophe. In PLC terms, the senior integrator paraphrase of Captain Edward A. Murphy, Jr.'s 1949 statement reads: "If there are 10 or more ways of writing the logic, and 01 of those ways can lead to a catastrophe, then someone will do it." Every analog channel you commission is a long-term responsibility. This guide walks through every step of taking that first program from "the input word changes when I inject 12 mA" to a production-ready, defensively-coded channel.

2. Analog Signal Standards You Will Encounter

Before writing a single line of code, lock down the signal standard. The four you will meet most often are voltage, current, RTD, and thermocouple. Each has a different module, different wiring rules, and different failure modes.

3. Prerequisites

Confirm you have every item below before you wire the first terminal. Skipping any one of these is the single most common cause of "first program" failures.

• PLC CPU with firmware current per manufacturer release notes (verify against Siemens Industry Online Support or your vendor equivalent).
• Analog input (AI) module matched to the signal type and channel count. Examples: Siemens SM 1231 AI4 / AI8, Allen-Bradley 5069-IF8, Schneider BMX AMI 0410.
• Field device with datasheet specifying output type, range, accuracy, and loop-power requirements.
• Programming software current to the CPU firmware: TIA Portal V17 or later for S7-1200/1500, Studio 5000 v34+ for CompactLogix/ControlLogix, EcoStruxure Control Expert for Modicon M340/M580.
• Calibration source: mA loop calibrator (e.g., Fluke 705, Beamex MC6), decade resistance box for RTD, or Type K reference for thermocouple.
• Shielded twisted-pair cable (Belden 8760, 9501, or 3084A are common).
• Panel-side 24 VDC power supply sized for the worst-case loop current × number of loops, with at least 25% margin.
• Multimeter with 0.1 mV / 0.01 mA resolution for verification.

4. Wiring and Shielding Best Practices

Analog signals live in the millivolt world. Treat them accordingly. A perfectly good program can be undermined by poor wiring practice in the first 30 minutes.

1. Run analog signal cables in dedicated conduit or continuous metallic tray, separated from VFD output cables, motor feeders, and welding leads by at least 200 mm (8 in). Cross perpendicular if you must cross.
2. Use shielded twisted pair. Ground the shield at the panel end only; floating the field end of the shield turns the cable into an antenna.
3. For 4–20 mA loops, ensure the transmitter is loop-powered from the analog module's sensor supply or an external 24 VDC source. Verify polarity with the datasheet: reverse polarity on some transmitters is silently tolerated, on others it destroys the output stage.
4. Torque terminal screws to the manufacturer's specified value. Phoenix-style spring terminals typically accept 0.5–0.6 N·m on solid conductors; under-torquing gives an intermittent connection that masquerades as a process problem.
5. Keep the run short. Anything over 100 m (328 ft) on a 4–20 mA loop should be reviewed for total loop resistance including the transmitter's compliance and the module's input impedance.

Signal flow diagram

5. Configuring the Analog Module

Configuration is where the most common first-program errors occur. The hardware setup must match the field device exactly. Mismatches are silent until they are not.

5.1 Siemens S7-1200 / SM 1231 AI4 (TIA Portal)

1. Open the device configuration in the project tree.
2. Select the channel (0–3) and set Measurement type to Voltage, Current, or Resistance (RTD) as required.
3. Set the Output range: e.g., 0–10 V, 4–20 mA, or Pt100 standard.
4. Enable Diagnostics: wire break (for current), overflow/underflow, and 24 V sensor supply loss. Reference the SM 1231 manual (Siemens 6ES7231-4HD32 entry ID 91696622) for the bit-level diagnostic mapping.
5. Set the hardware smoothing filter (None / Weak / Medium / Strong) to suppress mains-frequency noise. Weak = 4 samples, Medium = 16, Strong = 32.
6. Assign the input word address, e.g., %IW64 for channel 0 of an SM 1231 in slot 1.

5.2 Allen-Bradley CompactLogix 5069-IF8 (Studio 5000)

1. Add the 5069-IF8 to the backplane configuration.
2. Open Module Properties → Channels → Ch0.
3. Set Input Range to 4–20 mA.
4. Enable Open Wire Detection and Over/Under Range Detection.
5. Set Digital Filter to a value appropriate to the response time you need (10 ms is a good default for pressure).
6. Confirm the input tag, e.g., Local:5:I.Ch0Data, is being updated on the controller tags view.

6. Scaling: From Raw Counts to Engineering Units

A raw analog input is an integer in the module's native range, not a physical unit. You must scale it before it is useful to operators or downstream logic.

6.1 Linear scaling formula

For a linear sensor (which most 4–20 mA pressure, level, flow, and temperature transmitters are, after linearization in the transmitter itself):

EU = ((Raw - Raw_min) / (Raw_max - Raw_min)) * (EU_max - EU_min) + EU_min

For a 4–20 mA pressure transmitter with 0–10 bar range on a Siemens SM 1231 (16-bit signed, raw 0 to 27648):

EU_bar = ((Raw - 0) / (27648 - 0)) * (10.0 - 0.0) + 0.0
         = Raw * 0.0003617

For a transmitter with a non-zero EU_min (e.g., -10 to +10 bar compound range, still 4–20 mA):

EU_bar = ((Raw - 0) / (27648 - 0)) * (10.0 - (-10.0)) + (-10.0)
         = Raw * 0.0007234 - 10.0

The general linear-scaling identity, useful when the raw range does not start at zero:

EU = ((Raw - Raw_at_EU_min) / (Raw_at_EU_max - Raw_at_EU_min)) * (EU_max - EU_min) + EU_min

6.2 Sample Structured Text scaling function block (Siemens SCL)

FUNCTION_BLOCK FB_AnalogScale
VAR_INPUT
    iRaw      : INT;            // raw input word from AI module
    iRawMin   : INT := 0;       // raw at EU_min (e.g., 0 for 0 mA; 0 for 4 mA only if bipolar)
    iRawMax   : INT := 27648;   // raw at EU_max (nominal full scale)
    rEuMin    : REAL := 0.0;    // engineering unit at iRawMin
    rEuMax    : REAL := 100.0;  // engineering unit at iRawMax
    iRawUnder : INT := -32768;  // module underflow sentinel
    iRawOver  : INT := 32767;   // module overflow sentinel
END_VAR
VAR_OUTPUT
    rScaled   : REAL;
    bFault    : BOOL;
END_VAR
VAR
    fRangeRaw : REAL;
    fRangeEu  : REAL;
END_VAR

IF (iRaw = iRawUnder) OR (iRaw = iRawOver) THEN
    // Hard fault: out-of-range raw. Do not scale; propagate fault.
    rScaled := 0.0;
    bFault  := TRUE;
    RETURN;
END_IF;

fRangeRaw := INT_TO_REAL(iRawMax - iRawMin);
fRangeEu  := rEuMax - rEuMin;

IF fRangeRaw < 1.0 THEN
    rScaled := 0.0;
    bFault  := TRUE;            // divide-by-zero guard
ELSE
    rScaled := (INT_TO_REAL(iRaw - iRawMin) / fRangeRaw) * fRangeEu + rEuMin;
    bFault  := (iRaw < iRawMin) OR (iRaw > iRawMax);
END_IF;
END_FUNCTION_BLOCK

6.3 Sample ladder rung (Allen-Bradley Studio 5000, equivalent)

[XIC Local:5:I.Ch0Status.OK] [MOV Local:5:I.Ch0Data LocalTag:ScaledRaw_INT]
[MUL LocalTag:ScaledRaw_INT 361.7 LocalTag:ScaledEU_REAL_x1000]   // 0–10 bar * 1000
[DIV LocalTag:ScaledEU_REAL_x1000 1000.0 LocalTag:ScaledEU_REAL]

7. The "What If" List: Defensive Programming for Analog

This is the single most important section. The veteran wisdom in the field is that the difficulty is not making the I/O work; the difficulty is keeping it from not working in all the catastrophic ways it can. The following table is the working checklist for a defensively-coded analog channel.

7.1 Median filter for spike rejection

A median-of-5 filter is more effective than a moving average at removing single-sample EMI spikes while preserving step response. Pseudocode:

// each scan, push the latest scaled value into a 5-element ring buffer
buf[idx MOD 5] := rScaled
idx := idx + 1
// after 5 samples, sort and take the median
rFiltered := MEDIAN(buf[0], buf[1], buf[2], buf[3], buf[4])
// rFiltered is what downstream logic should use

7.2 Rate-of-change limit

For a process variable that physically cannot change faster than X units per second, a rate limiter clamps false spikes:

// rMaxDeltaEUPerSec set from process knowledge (e.g., 0.5 bar/s for a 10 bar pump)
rFiltered := rPrev + LIMIT(rScaled - rPrev, -rMaxDeltaEUPerSec * tScan, +rMaxDeltaEUPerSec * tScan)
rPrev := rFiltered

8. Loading, Testing, and Dry-Run Validation

Before you let your program control anything live, validate it in this order. Skipping any step is gambling with the process.

1. Compile clean. Resolve every warning. TIA Portal and Studio 5000 both produce diagnostic warnings on uninitialized tags and implicit conversions; fix them, do not silence them.
2. Online force / monitor. Watch the raw input word in the engineering tool. With no field device connected, it should read the module's underflow or zero value consistently. Jitter here means a wiring or termination issue, not a code issue.
3. Three-point calibrator injection. Disconnect the field device at the transmitter terminals. Inject 4.000 mA, 12.000 mA, and 20.000 mA with a precision calibrator. Record the scaled EU at each point. Acceptable error: ±0.1% of span for instrumentation-grade transmitters, or whatever the site quality standard specifies.
4. Loop-back with field device. Reconnect the field device. Read the EU with the process at three known states (e.g., empty / half / full tank; ambient / hot / very hot for a temperature loop). Verify against a local gauge or a handheld reference instrument.
5. Failure-mode simulation. Open the loop (disconnect one wire) and verify the wire-break diagnostic trips. Short the input terminals and verify the overflow diagnostic trips. Restore normal wiring.
6. HMI / SCADA check. Confirm the engineering value displays on the operator screen with correct decimal places, units, range bars, and alarm setpoints.
7. Alarm acknowledgment. Trip each alarm, acknowledge it, reset it. Verify the alarm log captures the event with timestamp and tag.

9. Troubleshooting Matrix

When the first program "doesn't work," the symptoms almost always fall into one of the rows below. Diagnose top-down: module online → wiring → field device → scaling → downstream logic.

10. Field Commissioning Checklist

Print this. Sign it. File it. Every analog channel should leave the site with a completed copy.

1. Module firmware version verified against current release notes
2. Channel configuration matches transmitter datasheet (range, units, filter)
3. Shielding terminated at panel end only, with documented shield ground point
4. Loop-powered transmitter verified for correct polarity and supply voltage at the terminals
5. Three-point calibrator test (4, 12, 20 mA) recorded on the loop sheet with serial-numbered calibrator
6. Wire-break and overflow diagnostics tested and wired to alarm tag in the controller
7. Scaled engineering value cross-checked against local gauge at low, mid, and high process states
8. HMI display verified with correct units, decimal places, and engineering range (e.g., 0.0 to 10.0 bar)
9. Operator walkthrough completed with printout of tag list and alarm setpoints
10. As-built drawing, configuration file, and this checklist archived to the engineering server with project number and date

11. From First Program to Production-Ready

Getting the first analog program to light up an input word is a real milestone — the moment it lights up, the I/O is real, the process is real, and the responsibility is real. The discipline of getting it production-ready is the work that follows. Every analog channel you commission is a long-term responsibility: it will fail, it will drift, and eventually it will mislead an operator at 3 AM. The defensive code you write today — wire-break alarms, scale validation, rate limiters, median filters, watchdogs — is the difference between a nuisance trip and a process incident.

Treat the "what if" list as a non-negotiable deliverable, not a nice-to-have. If there is a way for the channel to report a bad value, assume it will, and decide in advance how the program and the operator should respond. The integration effort that goes into a defensively-coded analog channel is roughly three times that of a minimal channel. The maintenance effort over the next ten years is roughly one-tenth.

That is the real Murphy's Law of PLC programs: someone will eventually do the thing that can lead to a catastrophe. The job is to make sure the thing they do is the safe thing.