Migrating Moeller to Siemens S7: Hardware and Software Reference

Migration Context: From Moeller to Siemens S7

Eaton's 2008 acquisition of Moeller Group brought the legacy Moeller programmable logic controller (PLC) families under the Eaton Electrical umbrella, as documented in European Commission Case No. COMP/M.5050 — EATON / MOELLER. Following the acquisition, active development on the Moeller PS4, XC, and easy families was consolidated into the Eaton Logic Controller (ELC) product line, with continued reliance on CoDeSys-based programming under IEC 61131-3.

Many installed Moeller systems have now reached end-of-firmware-update windows and diminishing spare-part availability. For end users standardizing on a long-lifecycle automation platform, migration to the Siemens SIMATIC S7 family — specifically the S7-1200 and S7-1500 lines with TIA Portal engineering — has become the dominant replacement path. This reference consolidates the engineering tasks required to convert a Moeller PS4, XC100/XC200, or easy800 application to a current-generation Siemens S7 controller, covering hardware selection, I/O module mapping, software environment migration, communication protocol conversion, and commissioning verification.

Source System Survey: Moeller PLC Families

Before any migration, catalog the existing system. The Moeller product range most commonly replaced by Siemens today includes:

Document for each system: CPU part number and firmware version, I/O module catalog numbers, expansion racks, communication modules (Profibus, CANopen, Ethernet), HMI panel part number, cable types, and the project archive (.bin, .zip, or .cpx for CoDeSys). This inventory is the basis for the Siemens hardware mapping.

Target Platform Selection: S7-1200, S7-1500, or ET 200

The current Siemens controller generation centers on S7-1200 and S7-1500 CPUs, both fully programmed in TIA Portal. The S7-300 and S7-400 lines are in legacy/withdrawal status; they are not recommended for new installations except when matching a long-running existing plant for which no further re-engineering is planned.

Hardware Mapping: CPUs and Power Supplies

Map the Moeller CPU's I/O count, program memory, and scan-time requirements to the Siemens CPU. A useful rule of thumb for new S7-1500 selection is to start at CPU 1515-2 PN for typical mid-range machine replacements, then size up or down based on program size, number of PROFINET devices, and motion axis count.

For power supplies, the Siemens 1-phase SITOP PSU100M (6EP1331-…) or 3-phase SITOP PSU8200 (6EP3436-…) are standard replacements. When the Moeller system uses 24 VDC field power, retain that convention; a separate PS-307-style 24 V supply is unnecessary if the S7-1200/1500 system load modules share a common 24 VDC bus already present in the cabinet.

I/O Module Mapping

For each Moeller digital and analog module, identify the channel count, signal type (sink/source, voltage range, current range), and isolation group. The Moeller PS4 series used a 24 VDC sink convention in most DI/DO modules; confirm polarity and grouping before module selection, as the Siemens signal modules default to PNP (sourcing) wiring for 24 VDC DI.

Software Environment: CoDeSys to TIA Portal

Moeller XC and PS4 projects were typically authored in CoDeSys 2.3 or CoDeSys 3.5 with IEC 61131-3 languages. Siemens TIA Portal STEP 7 (V17, V18, V19 at the time of writing) also implements IEC 61131-3 plus Siemens-proprietary extensions, so a direct source-to-source port is rarely possible, but the structural port is straightforward.

When the source application is structured with consistent POUs and a single GVL, a 1:1 manual port is the most reliable approach. A semi-automated path exists for very simple ladder-only easy800 programs by re-entering the ladder in TIA Portal, but in practice the engineering effort is dominated by tag I/O renumbering, not by language translation.

Communication Protocol Migration

Most Moeller systems include one or more of the following fieldbuses: Modbus RTU (over RS-485), CANopen, Profibus DP, or Moeller's own easyNet / Suconet. Map each to the Siemens equivalent on the new CPU.

Where a third-party device on the Moeller system supported only Modbus RTU, a Siemens CM 1241 RS-422/485 plus the Modbus RTU library provides a drop-in replacement. For more complex cases, the Software Toolbox Moeller PS4 to Siemens S7 communication reference documents how Data Block access patterns and addressing map when reusing existing S7 driver infrastructure on the new controller.

Tag and Address Mapping

The single largest conversion cost in any Moeller-to-Siemens migration is I/O address and tag renumbering. The Moeller PS4 used fixed physical addresses (e.g., %IW2.0, %QW4.0). Siemens TIA Portal uses symbolic addressing on top of optimized or absolute I/O addresses. Best practice:

1. Build a complete address cross-reference from the Moeller project: every input, output, flag, and timer/counter usage with its current symbol name.
2. In TIA Portal, create a default tag table mirroring the Moeller symbol names. Preserve operator-facing names exactly so HMI migration is trivial.
3. Assign addresses either as symbolic only (optimized block access) or as fixed addresses matching the Moeller layout for the first pass, then optimize later.
4. For retain data, mark tags as "Set in IDB" / "Retain" in the tag table. Do not rely on default behavior — the Moeller retain area was often 16-bit word, the S7-1500 retain area is byte-bounded and sized differently.

HMI Migration

Moeller HMIs in the source system are typically the XV100 / XV200 series (CoDeSys WebVis, later Eaton XV with Galileo) or the MFD-Titan displays. Map to current Siemens HMI as follows:

Tag import from a TIA Portal PLC tag table into a WinCC project is automated; it cuts the HMI port from days to hours when the source symbol names were preserved. Multi-language text, alarm classes, and historical data layouts must be rebuilt manually.

Migration Procedure (Step by Step)

1. Inventory — Export the Moeller project, list every CPU, I/O, comm, and HMI part number with firmware versions. Capture the wiring diagrams.
2. Map — Build a Moeller-to-Siemens mapping table (CPU, I/O, comm, HMI, power, network). Use the Siemens Interactive Catalog and the TIA Portal hardware catalog to lock the bill of materials.
3. Build the TIA Portal project skeleton — Create the project, add the CPU, configure PROFINET, and insert the ET 200 / SM modules per the mapping table. Download the GSD files for any third-party PROFINET devices.
4. Import tags — Use the cross-reference from step 1 to populate the default tag table. Mark retain tags explicitly.
5. Port POUs — Translate each Program, FB, and FC manually. Start with the main cycle (OB1), then cyclic interrupts (OB35), then event OBs (OB40, OB82, OB121).
6. Compile and check — Use TIA Portal's "Compile" / "Go online" diagnostics. Address compiler errors, implicit type conversions, and IEC timer/counter instance-DB differences first.
7. Simulate — Use PLCSIM (S7-1200/1500) to dry-run the program against the converted tag table before connecting to hardware.
8. Wire and bench-test — Land the new panel to a bench rig. Verify every input and output point against the wiring diagram. Pay special attention to PNP/NPN sensor convention and analog wiring polarity.
9. Cut over — Schedule a planned downtime. Power down, swap modules one-for-one (label everything), power up, download project, run a full functional test.
10. Validate — Run the controlled system through its full operating sequence with operators present, capturing any timing or behavior differences vs. the Moeller reference.

Verification Checklist

Before signing off the migration, the engineering team must verify:

Common Pitfalls and Field Notes

• PNP vs. NPN sensors. The Moeller PS4 DI modules were commonly NPN (sinking); S7-1200/1500 DI modules are PNP (sourcing). Verify sensor type and rewire, or use Siemens SM 1221 DI 8×24VDC SRC (sourcing-type) if NPN must be retained.
• Analog ground reference. Moeller PS4 analog modules used a common ground convention different from some Siemens AI modules. Tie the field 24 V return and the M-ana of the Siemens module to the same ground bar, never to chassis.
• Retain memory size. S7-1200 retain is sized in 10 KB blocks and is limited; S7-1500 retain is much larger but not unlimited. A migration that bloats retain tags (e.g., moving all bit memory to retain) can exhaust retain on an S7-1212C.
• IEC timer/counter instance DBs. CoDeSys and TIA Portal both create instance DBs for IEC timers (TP, TON, TOF, RTC) and counters, but the DB numbering is independent. Any external OPC client that read IEC timer instance DBs by absolute address must be reconfigured to read by symbolic name.
• Communication timeout differences. Moeller Profibus slaves and Siemens PROFINET devices can have different default watchdog times. A 1:1 slave replacement can produce "station failure" on the new network if the watchdog is shorter than the configured update time.
• Power budget. The new Siemens CPU and PROFINET I/O typically draw slightly more backplane current than the Moeller equivalent. Recalculate the 24 VDC power supply sizing and the breaker / fuse protection.

Spare Parts and Lifecycle Planning

The decision to migrate is usually driven by lifecycle. Cross-reference the Moeller installed base against the Eaton (post-acquisition) product status and the Siemens active-product status:

• Moeller PS4 — discontinued, spare parts limited to stock at distributors. Eaton's official support channel directs end users to migrate.
• Moeller XC100 / XC200 — succeeded by ELC series. Active support for firmware updates has been tapering.
• Siemens S7-1200 (current firmware V4.x) and S7-1500 (current firmware V3.x) — active mainstream products with a 10-year spare-parts guarantee from product phase-out.

Use the Siemens "Spares on Web" tool (via the Interactive Catalog) to verify availability of a specific S7 module before finalizing the BOM.

When Not to Migrate

Migration is not always the right answer. A Moeller system should remain in place when:

• The application is a one-off, low-complexity logic controller and a 1:1 swap to a current Eaton ELC (CoDeSys-based) is materially cheaper.
• The facility is already standardized on Eaton / Moeller, and migrating creates multi-platform maintenance overhead.
• Safety functions in the source use a Moeller-specific safety PLC without an existing Siemens F-CPU equivalent, and the safety revalidation cost outweighs the migration benefit.

For most mid-to-large industrial applications, however, the longevity, third-party support, and engineering-tool maturity of the Siemens S7-1500 platform justify the conversion.

FAQ