Building S7-1200 Motor, Valve, and Analog Blocks in TIA Portal

Building S7-1200 Motor, Valve, and Analog Blocks in TIA Portal V14

This technical reference walks through the design of three reusable standard blocks for the SIMATIC S7-1200 CPU programmed in TIA Portal V14: a motor block, a solenoid/pneumatic valve block, and an analog I/O processing block. All logic is implemented in Ladder Diagram (LAD). The reference addresses a common field question: STL (Statement List) is not supported on the S7-1200 family, so engineers migrating from S7-300/400 must restructure their block libraries to use LAD or Function Block Diagram (FBD) on Siemens Industry Online Support.

1. Block Architecture on S7-1200

Before writing any logic, define the block hierarchy. The S7-1200 supports the standard SIMATIC block set: Organization Blocks (OB), Function Blocks (FB), Functions (FC), and Data Blocks (DB). Background OB and time-of-day OB interrupt classes are inherited from the S7-300/400 model and behave identically from the engineer's perspective. The official programming reference defines how called blocks are invoked and how their local data is exchanged through an Instance DB for each FB call. See Calling blocks from within your program in the S7-1200 manual collection.

Use FBs with Instance DBs for any block that must remember state across scans: latched motor starters, valve open requests, last-good analog values, fault latches. Use FCs for pure functions: scaling, debounce, moving data. Mixing the two keeps each block's retentivity behavior predictable and minimizes the global tag namespace.

2. Prerequisites

1. STEP 7 Basic/Professional V14 (TIA Portal V14) with the S7-1200 CPU support package installed.
2. S7-1200 CPU with firmware V4.0 or later recommended for full TIA V14 feature set (LAD/FBD instruction set is identical from V1.0, but the LGF requires V4.x for some blocks).
3. Signal modules: SM 1223 DI16/DQ16 for digital motor/valve I/O, SM 1231 AI4/AI8 or SM 1232 AQ2/AQ4 for analog channels.
4. Library of General Functions (LGF) for SIMATIC STEP 7 (TIA Portal) and S7-1200/S7-1500 imported as a global library. The LGF is a Siemens-shipped set of reusable FBs/FCs covering motor, valve, analog, and PID primitives.

3. State Machine for Motor and Valve Blocks

Field equipment rarely operates as a simple on/off. Real-world control requires an equipment module to switch between four operator intent states plus two running states. The standard model used in IEC 61131-3 packaging and ISA-88 batch terminology is:

The state machine is implemented in FB_Motor and FB_Valve as a flat 4-way selector. The selected mode routes Start/Stop/Close/Open requests to the actuator. Local mode always wins, even if the HMI is in Auto. This protects the technician at the cabinet from being overridden by software.

4. FB_Motor Block Design

The motor block is the workhorse of the standard library. It is reused for conveyors, pumps, fans, and mixers with only the I/O mapping changing. The block exposes a clean Input/Output/InOut/Static/Const interface so the HMI can be wired once and reused across the plant.

4.1 Block Interface

4.2 Network-by-Network LAD Logic

Each network is a short segment of ladder. The actual editor view is graphical; the text below describes each rung for engineers who need to read the logic in plain language or reproduce it in another LAD editor.

1. Network 1: Mode arbitration. A priority encoder selects the active mode. Local wins over Manual, which wins over Auto. Wire iLocal_Mode in series with the start request through a normally-closed iStop_Cmd. Manual is selected only when iManual_Mode is true and iLocal_Mode is false. Auto fills the remaining case. The result is latched in a static sMode_Word and mirrored to oMode_Active for the HMI faceplate.
2. Network 2: Start seal-in. When the active mode is Local, Manual, or Auto and iStart_Cmd is true and iStop_Cmd is false and iAux_OK is true, set sStart_Latch. The latch holds itself through an OR contact parallel to the start path. sStart_Latch drops when iStop_Cmd, the trip from iAux_OK, or the fault clear is asserted.
3. Network 3: Coil output. oMotor_Cmd := sStart_Latch AND NOT oFault. The fault gate is critical: a latched fault must drop the coil instantly, even if the operator is still pressing start.
4. Network 4: Feedback watchdog. When oMotor_Cmd goes high, start a TON with PT = kStart_Delay. If iRun_Fdbk fails to arrive within the preset, set oFault and latch sFault_Latch. The same timer resets when the command drops.
5. Network 5: Stop seal-out. When oMotor_Cmd is high and iRun_Fdbk stays high after a TOF of 1 s, generate a "stuck contactor" fault. This catches welded contactor contacts on the field side.
6. Network 6: Fault reset. A rising edge on ioHMI_Ctrl.Reset clears sFault_Latch only when iAux_OK and the stop request are both present. Never allow a reset while the start command is held.
7. Network 7: Running flag and runtime accumulator. oRunning := iRun_Fdbk AND NOT oFault. Add the OB1 cycle time (typically 10 ms to 100 ms) to sRun_Timer while oRunning is true. This gives a maintenance-visible runtime in seconds without a separate counter DB.

4.3 Calling FB_Motor from OB1

Each physical motor is one instance. Drag FB_Motor from the program blocks tree into Network 1 of OB1, then assign a unique Instance DB (e.g., iDB_Motor_101). Wire the inputs from the I/O symbols and HMI tags. Reuse the same block for every motor in the project. The HMI faceplate is bound to ioHMI_Ctrl, so the same WinCC Comfort/Advanced faceplate works for all instances.

5. FB_Valve Block Design

The valve block is structurally similar to the motor block but with two stable states (Open, Closed) and two feedback inputs (Open limit switch, Closed limit switch). The same Auto/Manual/Local arbitration applies. The differences are in the fault logic: a valve that fails to reach its commanded position within a configurable travel time is a "position fault," distinct from the motor's "failed to start" fault.

5.1 Block Interface (delta from FB_Motor)

5.2 Travel Time Watchdog

Each direction uses an independent TON. When oOpen_Cmd rises, start TON_Open with PT = kOpen_Time. If iOpen_Fdbk does not rise before PT expires, latch a position fault. The same logic applies on close. The two timers are mutually exclusive: only one command can be active at a time, enforced by an interlock in the output network.

5.3 Inferred Position

When feedback is healthy, oPosition equals the commanded position after a 200 ms debounce. If both limit switches are off (mid-travel), oPosition = 3 (Transit). If both are on (fault condition, indicates bad wiring or a stuck limit), latch oFault immediately. The valve faceplate on the HMI reflects the inferred position rather than the raw command, which is what the operator expects.

6. FB_Analog Block Design

The analog block converts the raw integer from the SM 1231 AI module into engineering units (EU) and back into the integer for the SM 1232 AQ module. TIA Portal V14 already includes the NORM_X and SCALE_X instructions, but they expect normalized real values; the FB handles the full 0..27648 range used by S7-1200 analog modules and the optional bipolar -27648..27648 range for ±10 V or ±20 mA signals.

6.1 Scaling Formula

The standard linear mapping is:

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

For unipolar 0..27648 with EU_min = 0 and EU_max = 100, this reduces to EU = Raw / 276.48. For a 4..20 mA input mapped to 0..100 °C, Raw_min = 5530 (4 mA) and Raw_max = 27648 (20 mA), so the formula becomes EU = ((Raw - 5530) / 22118) * 100.

6.2 Wire-Break and Overflow Detection

The SM 1231 sets specific raw values for diagnostic events. The block checks for these explicitly:

These constants are documented in the SM 1231 / SM 1232 chapters of the S7-1200 system manual. The block must debounce the diagnostic value for at least two OB1 cycles to avoid nuisance trips during module startup.

6.3 Block Interface

6.4 Network Sequence in LAD

1. Network 1: Range check. Compare iRaw against 32512, 32767, and -32768. Output the appropriate diagnostic bit. The diagnostic value (>= 32512) must be debounced with a TON of 0.5 s to reject module startup pulses.
2. Network 2: Bipolar guard. If iBipolar is true, swap iRaw_Min to -27648 and iRaw_Max to +27648 internally. Otherwise default to 0..27648.
3. Network 3: Conversion guard. Block any division by zero: if (iRaw_Max - iRaw_Min) = 0, set oEU to sLast_Good and a config fault. This catches engineering errors in the instance DB at runtime rather than letting the CPU go to STOP.
4. Network 4: Subtract and divide. Use SUB (Real) and DIV (Real) instructions to compute ((iRaw - iRaw_Min) / (iRaw_Max - iRaw_Min)). The intermediate result is a Real between 0.0 and 1.0.
5. Network 5: Scale to EU. Use MUL and ADD to apply EU range. Clamp the final value to [iEU_Min, iEU_Max] using MIN and MAX instructions to defend against out-of-range raw values that pass the diagnostic filter.
6. Network 6: Update last-good. When no diagnostic is active, copy oEU to sLast_Good. The retentive tag survives CPU restart so the HMI can display a sane value immediately after power-up.

7. Library of General Functions (LGF) Reference

Before writing any block from scratch, install the Siemens-shipped Library of General Functions (LGF) for SIMATIC STEP 7 (TIA Portal) and S7-1200 / S7-1500. The LGF provides vetted versions of motor, valve, analog, and PID primitives, all written in LAD/FBD/SCL. The library is distributed via Siemens Industry Online Support and can be opened as a global library in TIA Portal. The LGF is the recommended starting point because:

• The blocks have been bench-tested and field-validated across hundreds of installations.
• They expose a consistent tag interface across the motor, valve, and analog categories, so HMI faceplates can be generic.
• Siemens maintains the library across TIA Portal versions, so a project upgrade from V14 to V15/V16/V17 requires only re-compilation, not rewriting.
• The license terms permit modification for in-house use, so the standard blocks can be extended with project-specific interlocks while keeping the proven core intact.

Use the LGF blocks as a template: copy the LGF block into your project master copy library, rename it (e.g., LGF_Motor -> S7_1200_Motor), and modify the additional features you need. This avoids reinventing the watchdog, debounce, and fault-latch logic and keeps your custom code reviewable against the Siemens reference.

8. HMI Faceplate Integration

All three blocks share the same HMI control cluster concept. Define a UDT_HMI_Ctrl in the PLC with a fixed layout: Start PB, Stop PB, Reset PB, Mode selector, Mode_Local bit, Mode_Manual bit, Mode_Auto bit, Fault, Warning, Running, Mode_Active (Int). Create a WinCC Comfort/Advanced faceplate bound to the UDT. Then the faceplate can be instanced against any motor, valve, or analog channel simply by changing the tag prefix. This is the same pattern used in the LGF faceplates.

9. Calling Blocks from Your Program

The S7-1200 programming manual describes how the CPU enters OB1 on every cycle, evaluates Network 1 to Network N in order, and when it encounters a call to an FB or FC, it pushes the current program counter onto the call stack, opens the called block, executes its networks, and returns to the next network of the caller. Each call to an FB requires an Instance DB; each call to an FC uses the caller's local stack. The official reference is the chapter Calling blocks from within your program in the S7-1200 manual collection, which contains the canonical call-stack diagram and the difference between single-instance and multi-instance FBs.

Two practical rules follow from that reference:

1. Order your OB1 networks so that safety-related FBs (E-Stop, guard interlock) are called before motor FBs that depend on them. Ladder evaluates networks sequentially; a downstream motor block cannot see a permissive computed in a later network within the same cycle.
2. Never call an FB conditionally with a jump or skip. The Instance DB is only updated when the call executes, so a motor that is "skipped" will retain stale state and may behave unpredictably when the call returns. Use the mode arbitration inside the FB instead.

10. Verification and Commissioning

After the blocks are compiled, follow this sequence in the TIA Portal V14 online view:

1. Compile all blocks. Resolve any "tag not declared" or "type mismatch" warnings before downloading. Warnings on the LGF blocks usually indicate a missing Instance DB or a TIA Portal version mismatch.
2. Download to the CPU. Use a consistent STOP/RUN download if the program structure changed. Hot reload of new FB types is not supported on S7-1200.
3. Go ONLINE in OB1. Confirm the motor, valve, and analog FBs are called in the expected order and that each Instance DB exists with the expected static tags.
4. Force-test each mode. From the watch table, set iLocal_Mode, iManual_Mode, and iAuto_Mode one at a time. Verify that the start command in the corresponding mode reaches oMotor_Cmd and that mode arbitration prevents two modes from being active simultaneously.
5. Fault injection. Force iRun_Fdbk low while the motor is commanded; verify that the start watchdog trips within kStart_Delay. For valves, force iOpen_Fdbk low during a commanded open; verify the position fault latches. For analog, force iRaw to 32512; verify the wire-break flag and that sLast_Good retains the previous good value.
6. HMI faceplate check. Open the HMI project in WinCC Comfort/Advanced runtime. Verify the faceplate starts in Off mode, responds to local selector, and that the fault banner appears and clears only on reset with permissive.

11. Troubleshooting Matrix

12. Performance and Cycle Time Considerations

On an S7-1200 CPU 1214C DC/DC/DC with 50 motor instances, 30 valve instances, and 20 analog instances, the typical OB1 execution time is in the 8 ms to 15 ms range. The dominant cost is the Instance DB access for the static tags of the FB calls. Two optimizations help when the count grows:

• Group equipment that is always operated together into a single area FB with multi-instances. The compiler can hoist the call overhead.
• Use cyclic interrupt OB (OB30 to OB38) at a slower phase, say 100 ms, for non-critical interlocks. The default OB1 stays at 10 ms for fast protection logic.