Siemens S7-1200 Ladder Coils Without Contacts: LAD/FBD Rules

Overview

Programming engineers trained on legacy Step 7 V5.x or third-party controllers often assume that every ( ) coil in a Ladder Diagram (LAD) network must be preceded by at least one normally-open or normally-closed contact, with the contact fed by a Boolean rung condition. The question frequently recurs for the S7-1200, S7-300, and S7-400 families programmed in TIA Portal (Step 7 Basic / Professional): is it legal to drop two or more set/reset coils straight onto the power rail, or to chain three set coils in series with no contact in front of them?

The short answer is yes, with caveats. The PLC execution engine does not interpret the LAD network in the same way a human reader does. The controller compiles the network down to its internal MC7 / AWL/STL-equivalent form and evaluates Boolean state on the basis of Enable EN, ENO, and the actual instruction semantics, not on the visual layout of the rung. As long as the TIA Portal compiler accepts the network, downloads it, and the CPU does not report a consistency error, the program is functionally valid.

There are, however, real situations in which the compiler will reject a coil-less network, mainly when the instruction being placed on the rung expects a Boolean input from the left rail. The remainder of this reference walks through the exact rule, the edge cases, the behavior differences between CPU families, and a step-by-step verification procedure you can run on the bench.

LAD/FBD Display Rules vs. PLC Execution Semantics

Step 7 V5.x and TIA Portal enforce display rules on LAD and FBD networks so that the on-screen view matches IEC 61131-3 graphical conventions. These rules cover:

• Power-flow direction (left to right, top to bottom)
• Placement of contacts and coils on the power rail
• Required Boolean input conditions for boxes, function blocks, and some instructions

These are editor / compiler rules. They are not PLC execution rules. The CPU executes the compiled code; it never reads your graphic. For confirmation, see the Siemens Automation Support entry ID 21952992 - Differences between LAD/FBD and STL/AWL with respect to the rules for graphic display, which clarifies that the CPU cares only about the compiled result, not the visual arrangement of the network.

Concretely, this means that the following networks are functionally equivalent at runtime:

Step-by-Step: Verifying Coils Without Contacts in TIA Portal V11 and Newer

1. Open or create a project. Launch TIA Portal and create a new project for an S7-1200 (e.g., CPU 1214C DC/DC/DC, 6ES7214-1AG40-0XB0) or S7-1500 target. The behavior is identical for S7-300/S7-400 in Step 7 Professional V11+.
2. Add a new LAD network in OB1 (Main). Right-click the network number, choose Insert Network, and confirm the language is LAD.
3. Drag two (S) coils from the bit-logic palette directly onto the right side of the power rail. The first coil should sit on the rail, the second in parallel below it. Do not insert any contact.
4. Compile the project with Project > Compile > Software (rebuild all blocks). If the status bar reports No errors, the network is valid. If you see a red marker on the network, hover over it for the error code (typical message: "Missing or incorrect input at box" or "No valid input").
5. Download to the PLC using Online > Download to device. Watch the diagnostics buffer; a clean download will populate OB1 with the two unconditional SET instructions and the CPU will go to RUN.
6. Go online and monitor the affected tags. Both target bits will be latched to 1 the moment OB1 executes, confirming the coil chain works without a contact.
7. Repeat for S/R/-(N) and -(P)/-(N) edge coils to confirm that all standard bit-logic output elements compile and execute without a contact prefix.

Instructions That DO Require a Boolean Contact

The compiler is strict whenever the instruction expects a Boolean rung condition, has a fixed left-side input pin, or carries an EN that the LAD/FBD editor treats as a mandatory rung state. The following classes reject a bare power-rail placement:

If you place one of these instructions on a bare rail, the compiler will either reject the network or auto-insert a --[=1]-- "always true" rung state. In TIA Portal V16-V18, this is rendered as an explicit NO contact on a TRUE constant. In older V11-V13 builds, the editor may show an error code F-0005 ("Invalid input") and refuse to compile until you add a contact or constant.

Behavior Across S7-1200, S7-300, and S7-400

The behavior is consistent across the families because the LAD compiler, the FBD compiler, and the underlying MC7 / SCL code generator are the same code base in TIA Portal. Differences show up only when the target firmware is older and a specific instruction has been reclassified between versions. For S7-300/S7-400, you may still see the option of generating STL/AWL from the network; the resulting STL is valid even if it would not round-trip back into a clean LAD display.

Why Old School Training Says "Always Use a Contact"

Pre-2000 PLC curricula and IEC 61131-3 stylists argue that every coil should be gated by an explicit condition for three reasons:

1. Readability. A future maintainer scanning the rung needs to know under what conditions the output fires. An unconditional coil is a maintenance trap.
2. Traceability. Audited code (e.g., IEC 61508 SIL 2/3 applications) requires that every output be derivable from a defined input condition. A bare coil makes the safety case harder to write.
3. Defensive design. If somebody later edits the network and moves the coil after a contact, the new contact's state will gate the output. With a bare coil there is no safety net.

For non-safety, debug, or initialization code, the "always-on contact" idiom is a common compromise. The recommended constant contact is a marker that is unconditionally TRUE, often named "TRUE_1" or "AlwaysOn", set once in startup OB100 and never reset. This gives you a rung condition that the LAD editor accepts universally and that the human reviewer recognizes as intentional.

Verification Checklist

Common Use Cases for Coils Without Contacts

• First-scan initialization. A bare (S) coil in OB100 (or inside an IF "FirstScan" THEN block in SCL) latches a startup marker.
• Resetting latches on cold restart. A bare (R) on a known address clears the bit on every OB1 cycle, useful for debug override patterns.
• Forcing a marker high for HMI visibility. Tying a coil to the rail guarantees the bit is always 1, removing a layer of logic from the HMI tag evaluation.
• Generating a non-retriggerable trigger. Use the bare (S) in front of a --(P)-- edge detector to get a single positive edge per OB1 cycle (acts as a clock generator at the OB1 rate).

Best Practices and Safety Caveats

• Reserve bare-rail coils for OB100, OB101, debug blocks, or well-commented initialization networks. Production control logic in OB1 should always carry a defined Boolean condition.
• When the IEC 61131-3 source must round-trip through LAD and FBD editors without information loss, always provide a contact. Some version-control diff tools and the "go to FBD" view are less lossy with explicit rung conditions.
• For safety-related projects (F-CPU S7-1200F / S7-1500F), the F-Compiler is far stricter. It will reject unconditional coils in the safety program unless they are inside an approved F-block template.
• Document every bare-rail coil in the program comments. The default TIA Portal comment field is the most efficient place; include the reason ("Init: enable safety reset") and the change-date / author.
• When migrating from Step 7 V5.5 to TIA Portal V15+, re-validate any STL networks that round-tripped through LAD. The TIA Portal STL parser is stricter about EN/ENO propagation and may flag legacy unconditional coils.

Compiler Error Codes You May Encounter

Related Documentation

For the underlying standard, refer to IEC 61131-3:2013, section 5.4 ("Ladder diagram language elements") and section 6.2 ("Declaration and initialization of program organization units"). The standard defines the graphical layout rules but explicitly defers to the vendor on the semantic interpretation of unconditional coils; Siemens's interpretation is "accept if compiler accepts".

For the S7-1200 system manual, see the S7-1200 Programmable Controller System Manual entry 6ES7298-8FA00-8BP0. For S7-300/400 in TIA Portal, see the S7-300/400 in TIA Portal Programming and Operating Manual. For LAD/FBD vs. STL display rules, see the FAQ ID 21952992 in the Siemens Automation Support knowledge base.