When to plan replacement of an S5 controller
A working machine with a Siemens SIMATIC S5 controller does not always need its controls replaced immediately. It is worth planning a move to S7-1500 when parts become harder to obtain, the current project is missing or the existing system limits expansion.
At ETOPA, we start machine and control system modernisation by establishing how the installation actually operates and which functions must be retained. We also agree new requirements: additional devices, clearer alarms, reporting or changes to operator interaction.
Reading the S5 and collecting documentation
We have equipment for SIMATIC S5 service. After identifying the CPU and memory arrangement, we confirm whether we can connect, read the available blocks and safeguard the program internally for the work.
Before dismantling the system, we collect the STEP 5 project, drawings, signal list and details of changes made at the plant. We compare the uploaded blocks with the available archive. STEP 5 comments are not transferred to the PLC: recovering the complete documented project requires files retained on the programmer's computer.
If descriptions are missing, time is needed to understand the program and confirm machine operation with its operators. We also discuss preparation of older systems in our article on SIMATIC S5 program updates.
Moving a STEP 5 program to S7-1500
During analysis, we decide which functions to retain through conversion and which to develop again. The route described by Siemens uses the S5/S7 converter in STEP 7 Classic, corrections to the resulting code and then project migration to TIA Portal. Moving the program to an S7-1500 CPU is a further stage. Each stage needs its own checks; we select tool versions for the project and target hardware.
TIA Portal V21 does not support direct migration of STEP 7 Classic projects. One route documented by Siemens uses Migration Tool V20 and TIA Portal V20, followed by upgrading the project to V21. This transition between engineering versions is separate from adapting the program to the new CPU. See the TIA Portal V21 migration documentation.
In the converted code, we check block calls, indirect addressing, system functions, start-up handling and data structures. Some constructs need manual changes, as described in the Siemens converter manual “From S5 to S7”, chapter 7. Compilation is one check; tests must also establish sequence behaviour and equipment responses. These findings define the scope of PLC programming.
Selecting the CPU, inputs and outputs
We prepare the new configuration using an inventory of devices and signals. We consider process requirements, communication, required functions and planned expansion. For I/O, we check electrical parameters, measurement ranges, wiring and the requirements of special modules.
The replacement scope also covers cabinet space, power supply, terminals and wire identification. We assess whether existing wiring or adapters can be used for the specific modules. Retaining part of the installation requires confirmation that it is compatible with the new configuration.
HMI, drives and connections to the rest of the line
Before replacement, we list every S5 connection: operator panel, drives, distributed stations, neighbouring PLCs and supervisory systems. For each connection, we determine how data will be exchanged after modernisation and which elements must be replaced or reprogrammed.
We plan HMI and SCADA changes together with the PLC program. We agree the alarm list, settings, recipes and operating approach so operators can manage the process effectively after commissioning.
Shutdown, testing and rollback
We plan the migration within an agreed shutdown window. Before work begins, we establish the changeover sequence, time for testing and conditions for restoring the previous controls. We prepare an internal program backup, connection documentation and acceptance criteria agreed with the plant. We assess rollback feasibility against the planned wiring changes and whether the old system will be retained.
- Check input and output signals and the direction of device operation.
- Test sequences, alarms, interlocks and data exchange with equipment.
- Verify measurement scaling, settings and required behaviour after stopping and restarting.
- Carry out agreed process trials with the operators involved.
- Discuss the changes made, machine operation and recommendations for maintenance.
Program tests prepared before the shutdown help reveal errors earlier. After the changeover, the actual devices and machine operation must also be checked at the plant. If the modernisation affects safety functions, we plan their assessment and verification separately.
What to send ETOPA before modernisation
- The full S5 CPU designation and photographs of modules in the cabinet.
- The available STEP 5 project, drawings and signal list.
- HMI panel, drive and communication device designations.
- A description of the current process, problems and required new functions.
- The plant location and possible shutdown windows.
This information lets us establish the required site survey and prepare the scope of an S5-to-S7-1500 modernisation. For installations using the newer family, we have a separate guide to migration from S7-300 to S7-1500.
Technical documentation
Planning and conversion principles are described in the 2015 Siemens guide to migration from S5 to S7-1500. Its hardware and software examples are not a current purchasing list. Configuration selection requires the documentation for the chosen devices, alongside migration information for the TIA Portal version being used.