Migrating from Allen-Bradley RSLogix to Siemens TIA Portal

Overview

Engineers fluent in Allen-Bradley (Rockwell Automation) Logix Designer / RSLogix 5000 routinely underestimate the cognitive cost of a parallel move to Siemens SIMATIC. The two platforms solve the same automation problem but with materially different paradigms: tag-based, structured-text-friendly architecture (AB) versus data-block-bound, language-routed architecture (Siemens). The transition is not a brand-skin swap; it is a re-mapping of how memory, addressing, and execution models are conceptualized.

The most cited friction points, based on cross-vendor support telemetry from system integrators and OEM motion vendors, are:

1. Indirect addressing inside ladder logic (a feature that exists implicitly in AB but requires STL or SCL in Siemens).
2. The role and lifecycle of Function Blocks (FB) and their associated Instance Data Blocks (DB).
3. Online editing workflows and download-without-stop semantics.
4. Project navigation in TIA Portal versus the flat ACD database of Logix Designer.
5. Tag database scoping (controller-scoped vs program-scoped vs global DB in Siemens).

This guide consolidates the mechanics that must be relearned, not the marketing comparison sheets. It assumes the reader has shipped at least one ControlLogix or CompactLogix machine and is preparing to commission a SIMATIC S7-1200, S7-1500, ET 200SP, or legacy S7-300/400 system.

Development Environment Comparison

The single most visible workflow change is that TIA Portal splits the project into a strict hierarchy: PLC station → Program blocks → System blocks → Tags. Rockwell uses a flat tag table at the controller root. Any tool or routine that depends on a single flat tag list (CSV exports, Excel add-ins, HMIs polling tag names) requires re-engineering when ported to Siemens.

Ladder Logic Paradigm Differences

Ladder in AB (Logix Designer) and LAD in Siemens (TIA Portal) look superficially identical but diverge in execution semantics.

Engineers frequently trip on the destination handling: AB's ADD(SourceA, SourceB, Dest) takes a third operand; Siemens ADD in LAD has no destination field — the result is written to an implicit operand shown on the box (typically a pre-declared tag in the interface). Forgetting to declare the tag results in a compile error rather than a runtime fault.

Indirect Addressing: The Critical Skill Gap

Indirect addressing is the single most reported blocker for AB-trained engineers stepping onto S7 platforms. AB performs indirect addressing transparently via array index syntax; Siemens LAD does not expose index notation at all, forcing the engineer into STL or SCL.

Allen-Bradley Approach (Logix Designer)

In AB, arrays are first-class tags and indexed in any language:

// User-defined tag (controller scope)
Recipe[0..99] : DINT;      // array of 100 DINTs
Index : DINT;              // runtime index

// Ladder rung
COP(Recipe[0], DestArray[0], 50);   // bulk copy 50 DINTs
MOV(Recipe[Index], TempValue);      // indexed read
Recipe[Index] := 1234;              // indexed write (ST routine)

The [Index] token resolves at runtime. No special language or compiler directive is required.

Siemens STL Approach (Step 7 Classic / TIA Portal STL)

STL is the only place where pure indirect addressing in the spirit of L D [AR1, P#0.0] exists. Two 32-bit address registers, AR1 and AR2, hold the base pointer; offset is added via P#<bytes>.<bits>.

// STL fragment - Siemens S7-1200/1500
// Assume AR1 was loaded with the DB number earlier
LAR1  P##RecipeArray         // load pointer to symbol RecipeArray
L     D [AR1, P#0.0]         // load DINT at offset 0
T     "DB_Temp".Value       // transfer to temp storage

// Loop with index in MD100 (DINT)
L     MD100                  // load index
SLD   2                      // shift left 2 (DINT = 4 bytes)
LAR1                         // load AR1 with index * 4
L     DB [DB_NO], D [AR1, P#0.0]  // indexed load using DB register
T     DB [DB_NO], D [AR2, P#4.0]  // write to next slot

Siemens SCL Approach (Modern Recommendation)

For S7-1200 and S7-1500, SCL makes indirect addressing trivial and is the recommended path for any code ported from AB:

// SCL in TIA Portal V18
FOR #i := 0 TO 99 BY 1 DO
    "Recipe"[#i] := "Source".value;
END_FOR;

IF ("Recipe"[#index] > 1000) THEN
    "Alarm" := TRUE;
END_IF;

The ARRAY[*] of ANY data type and the VARIANT pointer are also available for fully generic data access in SCL V17+ — useful when porting AB AOI parameter blocks.

Function Block Architecture and Data Blocks

AB and Siemens both implement reusable code blocks, but the term "FB" carries different lifecycle semantics.

Siemens FB must have an associated DB to retain state. Calling an FB without supplying or auto-generating an instance DB is a compile-time error. AB AOIs do not have this binding — internal tags are scoped to the AOI's local instance automatically. Engineers who forget to assign instance DBs when porting code will see "DB not generated" errors on the first download.

Online/Offline Editing Workflows

The two vendors approach live modification very differently. Logix Designer has the concept of "pending edits" with a final-accept/assemble step; TIA Portal on S7-1500 supports online editing with a "Download to device" dialog that exposes delta vs full download modes.

For S7-300/400 controllers, online edits have stricter constraints: most code changes require STOP. The S7-1500 platform (firmware V2.5+) is the first Siemens controller to deliver robust online code modification without stop.

Industrial Network Protocol Considerations

Profinet (Siemens) and EtherNet/IP (Rockwell) are functionally similar at the application layer but differ sharply in configuration burden.

The Profinet stack footprint is a real constraint on S7-1200 firmware V4.x: complex Profinet configurations with many IO devices can exhaust the work memory of the CPU. Engineering rule of thumb: S7-1214C has ~50 KB of user program space after Profinet loads; S7-1511 has substantially more headroom.

SCADA Migration: iFix to Wonderware InTouch / AVEVA

The HMI/SCADA side of the move is independent of the PLC brand change, but commonly happens in the same project. GE Proficy iFix (Emerson) and Wonderware InTouch (AVEVA, formerly Schneider Electric) are the two most-encountered SCADA platforms in US-based plants.

Engineers moving from iFix to InTouch report the steepest ramp in the ArchestrA object model: Area, Equipment, Template, Instance hierarchy. iFix is configuration-flat; ArchestrA is template-instanced. A single template change in ArchestrA propagates to all instances; in iFix, a screen change requires manual edits across all pictures.

Training Path and Recommended Sequence

For a productive Siemens TIA Portal engineer inside 6 to 10 weeks:

1. Week 1–2: Environment and OB model. Understand OB1 (cyclic), OB35 (cyclic interrupt), OB82/OB86 (diagnostic), OB100 (warm restart), OB101 (hot restart), OB102 (cold restart). Map them against Logix Designer's periodic task / continuous task / fault handlers.
2. Week 2–3: Tag and DB scoping. Practice creating global PLC tags, instance-DB-tagged FB calls, and multi-instance FB blocks. Migrate three AB AOIs to equivalent Siemens FBs in SCL.
3. Week 3–4: Indirect addressing mastery. Reimplement five AB routines that rely on indexed array reads in both SCL and STL. Compare line count and runtime cost (SCL compiles to STL anyway, but readability matters for maintenance).
4. Week 4–5: Hardware configuration. Build a PROFINET topology with a SIMATIC ET 200SP station, drive (Sinamics G120), and HMI (Comfort Panel TP1500). Cross-reference GSDML versions with firmware — mismatched GSDML is the top cause of station-not-found faults.
5. Week 5–6: Library and versioning. Build a global library with versioned FB master copies. Practice the "Update Instance DB" workflow on a backup project to see each conflict-resolution mode.
6. Week 6–8: Online commissioning. Use S7-PLCSIM V18 / PLCSIM Advanced. Practice online edits and demonstrate the limitations when adding new program blocks.
7. Week 8–10: HMI integration. Wire WinCC Professional or WinCC Comfort to a SIMATIC HMI, then progress to a TIA-integrated SCADA pattern. For multi-vendor SCADA, integrate via OPC UA rather than vendor-native drivers.

Common Pitfalls and Field-Tested Workarounds

Verification Checklist Before First Commissioning

1. Compile project in TIA Portal with full build; resolve all warnings (many warnings are real bugs, especially "Implicit tag conversion").
2. Run S7-PLCSIM simulation against the exact firmware version of the physical CPU. Firmware mismatch invalidates diagnostic bit behavior.
3. Download full project (not delta) on first commissioning. Verify CPU is in STOP during hardware config download.
4. After download, run "Compare online/offline" — values that diverge from the offline project indicate parameter-overlap or IP conflicts.
5. Force each FB instance DB and confirm values in the Inspector / Watch table. Spot-check at least three FBs that the engineering team frequently uses.
6. Verify PROFINET device names via TIA Portal "Assign PROFINET device name" step.
7. Verify retentive tag behavior by powering off the CPU (or simulating via PLCSIM) and confirming that retentive markers and retain DB areas retain values.
8. Run the HMI offline simulation against the PLC project; confirm alarm prioritization and screen-to-tag resolution.

Documentation References

Primary resources to keep within reach:

• SIMATIC S7-1500 Automation System Manual — covers OB/FB/DB model and PROFINET configuration (Siemens Support entry 109817183).
• TIA Portal Programming and Operating Manual — covers cross-reference, libraries, and online edit semantics (Siemens Support entry 81318674).
• Logix Designer Application Programming Manual — for cross-checking AB tag/array semantics (Rockwell Automation Literature Library).
• AVEVA InTouch / ArchestrA System Configuration Guide — for ArchestrA galaxy and template model (AVEVA Documentation).
• Emerson GE Proficy iFix Reference — for alarm, scripting, and PDB comparison (Emerson GE Digital iFix product page).

FAQ