Request a quote
Benešl Automation / AI for TIA Portal / Migrating S7-300/400 to S7-1500
S7-300 · S7-400 → S7-1500 · STL → SCL · TIA Portal

Migrating S7-300/400 to S7-1500 with AI

Moving from S7-300 or S7-400 to S7-1500? TIA Portal itself converts the project from STEP 7 V5.x into TIA Portal. AI with TIA MCP helps with the work that remains after that: converting STL to SCL, finding old system functions and absolute addresses, reviewing and comparing the program, tests and documentation.

What TIA Portal does and where AI helps

Let us be clear: TIA MCP does not replace the migration functions of TIA Portal. It works with a project you already have open in TIA Portal and saves manual work where migration usually takes longest.

StepTIA PortalAI with TIA MCP
Converting the project from STEP 7 V5.xyes, project migration in TIA Portalno – checks the result and the compile errors
New S7-1500 station and moving the programyes, with TIA Portal tools following the Siemens proceduremodule I/O addresses, IP and PROFINET names, swapping a module for a compatible type or another firmware version
Converting STL to SCLno, STL stays STLyes, with warnings where conversion is not possible
Old SFC and SFB system functionserrors and warnings when compilingfinds calls that are not S7-1500 instructions and looks up a replacement in the reference
Program reviewcompilingcode review, absolute addresses, unused blocks and tags, comparison with the original program
Documentation–block comments, block help and handover documentation as PDF

The migration procedure to S7-1500

This is how we usually migrate S7-300/400 to S7-1500. AI mainly speeds up steps 4 and 5.

  1. Preparation

    Backup, an error-free STEP 7 project, a list of hardware, libraries and communication.

  2. Into TIA Portal

    Project migration from STEP 7 V5.x. Done by TIA Portal.

  3. S7-1500 and hardware

    New station, I/O addresses, IP and PROFINET. AI helps with addresses and checks.

  4. Program

    STL to SCL where it makes sense, replacing SFCs and SFBs, preparing for optimized DBs.

  5. Checks and tests

    Compiling, code review, comparison with the original program, tests in PLCSIM Advanced.

  6. Documentation and commissioning

    Description of changes, handover documentation and commissioning on the machine.

Where AI helps in the migration to S7-1500

You give instructions in plain language, for example: “Convert the STL blocks to SCL, check the calls for S7-1500 and compare the program with the original PLC.” The AI uses the TIA MCP tools and shows the result in the project.

STL to SCL

Bit logic, accumulator, arithmetic, comparisons, jumps and block calls, including German mnemonics. What the conversion cannot handle (S5 timers and counters, indirect addressing, status word) remains as a comment and in the warnings.

Old system functions

An SCL check against the S7-1500 instruction reference flags calls that do not exist on S7-1500. The AI looks up the newer instruction with its parameters in the reference.

Absolute addresses

Full-text search and cross-references across the whole program, and the code review reports absolute addresses. A basis for moving to optimized DBs.

Program comparison

Offline comparison of two PLCs (blocks only left, only right and different) and the diff of individual blocks. You quickly see that nothing was lost in the migration.

Code review and clean-up

Multiple writes, unused variables, CASE without ELSE, unused blocks and tags. A summary by severity for the whole PLC.

Tests in simulation

Unit tests of converted FBs and FCs in PLCSIM Advanced: you give inputs and expected outputs, the AI creates a test block and evaluates it.

Moving blocks and libraries

Blocks from XML exports or SCL sources into the target PLC with a preview of renames, collisions and review. Upgrading global libraries from older TIA Portal versions.

Hardware

Module I/O addresses, IP plan and PROFINET names. Swapping a CPU or module for a compatible type or another firmware version while keeping the configuration.

Documentation

Block and network comments, block help and software handover documentation as PDF, including changes since the previous release.

What to watch out for when migrating to S7-1500

These are the points we deal with most often in older programs. AI helps to find them and suggests a solution, but the programmer makes the decision.

  • Optimized data blocks. S7-1500 works best with optimized access, where DBs have no fixed addresses. Migrated blocks keep standard access. Before switching you need to find all absolute accesses (DBX, DBW, AT, pointers) in the program, in the HMI and in the communication.
  • Indirect addressing. ANY and POINTER, the address registers AR1 and AR2 and opening DBs by a variable number. In SCL they are usually replaced by arrays, structures, the VARIANT type or block instructions. The STL to SCL conversion does not convert these places and flags them.
  • SFC and SFB system functions. Some old calls have newer instructions on S7-1500, for example reading the clock (READ_CLK → RD_SYS_T or RD_LOC_T) or copying areas (BLKMOV → MOVE_BLK). Communication, diagnostics and alarms differ more and are worth going through by hand.
  • S5 timers and counters. We recommend replacing them with IEC timers and counters (TON, TOF, TP, CTU) with their own instance.
  • Error handling. S7-1500 can handle program errors locally in the block (GET_ERROR, GET_ERR_ID). Check what the program did in the error OBs.
  • Timing and cycle. S7-1500 is considerably faster. Logic that depends on the cycle time, wait loops and cycle counting may behave differently.
  • Communication and HMI. PUT/GET access has to be enabled in the CPU settings on S7-1500. Convert panels and SCADA using absolute addresses to symbolic access, or keep the relevant DBs with standard access.
  • Safety program. The F-program has its own migration procedure and must be validated again after the change. AI can help with the overview and documentation here, not with the decision.

Migrating from another brand, for example Beckhoff TwinCAT, B&R, CODESYS or Schneider? For that we have a separate conversion into TIA Portal: PLC migration to Siemens TIA Portal

Replacing Comfort panels with WinCC Unified as well? Read the article HMI migration to WinCC Unified

FAQ about migrating S7-300/400 to S7-1500

Does TIA MCP convert a STEP 7 V5.x project into TIA Portal?

No. A STEP 7 V5.x project is converted into TIA Portal by the project migration built into TIA Portal. TIA MCP works with a project that is already open in TIA Portal and helps with the next steps: STL to SCL, call checks, review, comparison, tests and documentation.

Do I have to convert STL to SCL when migrating to S7-1500?

No. S7-1500 supports STL. Converting to SCL is a choice for better readability, maintenance and the move to optimized DBs. Often only the blocks that will keep changing are converted.

How reliable is the STL to SCL conversion?

The conversion is deterministic: the same input always gives the same result and it follows the S7 evaluation order (AND before OR). Whatever it cannot do it leaves as a comment and lists in the warnings. The result always needs to be checked and compiled, and you verify the behaviour with unit tests in PLCSIM Advanced.

Does this also apply to S7-400?

Yes, the procedure is the same – the program has to be in a TIA Portal project. Special cases such as S7-400H redundant systems are handled individually.

Will you do the migration to S7-1500 for us?

Yes. We migrate S7-300/400 to S7-1500 turnkey or together with your team, including commissioning on the machine. Send us the project for assessment.

How much does TIA MCP cost?

A PRO licence costs €295 per year per computer, excluding VAT. You can try TIA MCP free for the first 7 days.