Resolving SimoCode PROFINET Loss After TIA V15.1 to V17 Upgrade

Overview

When a SIMATIC S7-1500 project containing SIMOCODE pro motor management devices is migrated from TIA Portal V15.1 to TIA Portal V17, field reports consistently show that PROFINET-connected SIMOCODE pro V PN stations drop off the network. The symptom pattern is unambiguous: the SCALANCE X208 port LEDs on the affected SIMOCODE ports are dark, PRONETA network scans return no SIMOCODE stations, the TIA Portal online diagnostics for the IO controller report station failure, and the SIMOCODE ES 17 commissioning tool cannot establish a connection to the basic units. This reference documents the root cause analysis, the firmware and licensing checks, the SCALANCE and PRONETA diagnostics, and the SIMOCODE service interface (Sirius PtP) configuration required to restore the link.

The recovery workflow applies to all SIMOCODE pro V PN variants (basic, PROFIsafe, and current/voltage measurement) configured behind a CPU 1515F-2 PN or any other S7-1500 PROFINET controller running TIA Portal V17. The procedures below have been validated against the SCALANCE X-200 managed switch family, the PRONETA V3.x and V4.x network analysis tools, and the SIMOCODE ES V17 commissioning suite.

System Components in the Reported Failure

The combination of a 1515F-2 PN at firmware V2.1, a V17 engineering environment, and a V15 Premium license is the most likely trigger for the missing-link state. Each of the three is addressed in the diagnostic workflow below.

Symptom Matrix

Root Cause Analysis

Five root cause categories are common in this scenario. Confirm or eliminate each before opening a Siemens support request at Siemens Support Request.

1. CPU Firmware Incompatibility with TIA Portal V17

TIA Portal V17 expands the supported PROFINET conformance class and the supported GSDML versions. CPU 1515F-2 PN units at firmware V2.1 (released with TIA V15.1) are technically still configurable in V17, but certain V17 PROFINET stack changes, security defaults, and topology editor features only become active on firmware V2.6 or later. When the project is recompiled under V17 and downloaded to a V2.1 CPU, the controller can come up in a degraded state where the IO controller starts but does not complete AR (Application Relationship) establishment with the SIMOCODE pro V PN devices. The downstream effect is the reported pattern: the SCALANCE sees no link activity on those ports because the SIMOCODE devices are not yet part of an active AR, the devices have not completed their PROFINET startup handshake, and the basic unit PROFINET interface may remain in a power-on reset loop.

2. GSDML Version Mismatch in the V17 Device Catalog

TIA Portal V17 ships with an updated SIMOCODE pro GSDML file (GSDML-V2.3x-Siemens-SIMOCODE_PN-...). A project created in V15.1 references the older GSDML-V2.25 (or V2.3x) file. When the project is upgraded, TIA Portal normally re-binds the device description, but if the device was inserted with a manual GSD import, the upgrade can leave the V15.1 GSDML in place while the rest of the project is at V17. The mismatch can break the slot configuration, the record data layout, and the cyclic IO exchange, which presents at the network layer as missing-link or no-AR.

3. SIMOCODE ES V15 Premium License on a V17 Project

The SIMOCODE ES V15 Premium license is not forward-compatible with SIMOCODE ES V17. The V17 commissioning tool detects the V15 license at start-up and either downgrades the connection mode or refuses to write back parameters to the V17-configured station. The typical symptom is that SIMOCODE ES can read parameters from the device through the PROFINET path but cannot perform a full download. Where the V15 license trips the V17 tool into a license-missing fallback, the tool may block online connection entirely until the V17 license is installed.

4. PROFINET Device Name Reset After CPU Download

TIA Portal V17 changes the default behaviour for the PROFINET device name and the IP assignment during a download to the IO controller. If the SIMOCODE pro V PN devices were assigned a PROFINET name from a PC station that was not part of the V17 project, the V17 download to the CPU can rewrite the topology table in a way that orphans the existing device names. The orphaned devices then fail DCP identify (no PROFINET name, controller cannot find them, station failure).

5. SCALANCE X208 Port Configuration Drift

SCALANCE X-200 managed switches store their port configuration in non-volatile memory. A V17 migration that changes the topology editor view of the switch can leave the port admin state in disabled if the port was previously assigned to a now-removed VLAN member. The LED stays off, the port does not auto-negotiate, and the SIMOCODE device appears offline even though the cabling is intact.

Step-by-Step Diagnostic Procedure

Work through the following checks in order. Each step isolates one of the five root cause categories.

Step 1 - Confirm the Physical Layer

1. Verify 24 V DC on the SIMOCODE pro V basic unit (TM terminals 1 and 2). Measure under load; a marginal supply that holds the relay but not the PROFINET PHY will light the device status LED but not the PROFINET LEDs.
2. Inspect the RJ45 seating at both ends of every PROFINET patch cable. A partially seated connector on a SIMOCODE pro V PN device can pass DCP (link pulses) but fail cyclic data.
3. Swap a known-good patch cable on the first affected port to rule out a damaged cable.

Step 2 - Inspect the SCALANCE X208 Port State

The SCALANCE X208 Web Based Management (WBM) and the CLI both expose the per-port link state, speed, duplex, and admin state.

1. Open the SCALANCE X208 WBM (default URL: https://switch-IP) and authenticate.
2. Navigate to Information, then Ports, then Port Statistics. Locate the ports connected to the SIMOCODE pro devices.
3. For each affected port, record: link status (must be Up), speed (must be 100 Mbps full duplex; SIMOCODE pro V PN is 100 Mbit/s, no Gigabit auto-negotiation), admin state (must be Enabled), and received/transmitted packets (a port stuck at 0 frames after 30 s indicates a dead link).

If the admin state is Disabled, enable the port and save the configuration. If the link is Down with admin state Enabled, proceed to Step 3.

Step 3 - Run a PRONETA Network Analysis

PRONETA (PROFINET Network Analysis) is the official Siemens tool for PROFINET commissioning and diagnostics. Use the latest version compatible with TIA Portal V17.

1. Install PRONETA V3.x or V4.x on a service laptop and connect to the same SCALANCE X208 segment.
2. Launch PRONETA and click Network Analysis.
3. Allow the scan to complete (typically 5 to 10 s on a 4-device segment).
4. In the device list, look for the SIMOCODE pro V PN MAC addresses (vendor prefix 00:0E:8C, Siemens AG).
5. For each discovered SIMOCODE pro device, check: PROFINET device name (must match the V17 project assignment), IP address (must be in the configured subnet), device type (must read SIMOCODE pro V PN or SIMOCODE pro V PROFIsafe PN).

If PRONETA shows no SIMOCODE devices and the SCALANCE port LED is OFF, the basic unit is not transmitting on PROFINET. Go to Step 4. If PRONETA shows the SIMOCODE devices but they have no PROFINET name, go to Step 5.

Step 4 - Validate the CPU 1515F-2 PN Firmware

1. In TIA Portal V17, open the CPU 1515F-2 PN online, then Online & Diagnostics, then Diagnostics.
2. Read the order number (6ES7515-2FM02-0AB0 is the typical 1515F-2 PN) and the firmware version.
3. Cross-check the firmware against the TIA Portal V17 release notes. For CPU 1515F-2 PN at firmware V2.1, the recommended target is V2.9.x (or the latest V2.9 service pack) to ensure full V17 PROFINET stack compatibility.
4. If the firmware is below V2.6, plan a firmware update. Use the Siemens firmware update tool or the TIA Portal Update firmware function. Back up the project before the update.

Step 5 - Validate PROFINET Device Name Assignment

1. In TIA Portal V17, open the Devices & Networks view, select the SIMOCODE pro V PN device, and open Properties, then PROFINET interface, then Ethernet addresses.
2. Confirm the PROFINET device name (for example, simocode1 through simocode4) and the IP address assignment.
3. Use PRONETA to assign the device name to each SIMOCODE pro V PN: select the device, click Assign PROFINET device name, enter the name from the V17 project, and click Assign.
4. After the assignment, the SCALANCE X208 port LED should light within 5 s, and PRONETA should report a PROFINET IO device status.

Step 6 - Validate the SIMOCODE ES Licensing

1. Launch SIMOCODE ES 17.
2. Open Help, then License Management. The license overview should list the active licenses under SIMOCODE ES V17.
3. If the V15 Premium license is the only one detected, the V17 tool is running in read-only or V15-compatibility mode. Contact Siemens licensing to upgrade the V15 Premium license to a V17 Premium license, or purchase a new V17 license. The V15 license is not interchangeable.
4. As a temporary workaround, install SIMOCODE ES V15.1 on a separate engineering station and parameterize the SIMOCODE pro V PN devices through the PROFINET path while the V17 license issue is resolved.

Step 7 - Validate the GSDML and the SIMOCODE pro V PN Device Catalog Entry

1. In TIA Portal V17, open the TIA Portal Options, then Manage Device Description Files (GSD).
2. Confirm that the GSDML file listed for the SIMOCODE pro V PN matches the TIA V17 default. Re-import the GSDML from the TIA V17 installation media or from the Siemens support website if needed.
3. Open Devices & Networks, then Device catalog, then Other field devices, then PROFINET IO, then Siemens AG, then SIMOCODE pro V PN. Drag a fresh device into the project and compare its slot configuration with the migrated device. A mismatch in module slot count (for example, 2 slots in the migrated device versus 4 slots in the V17 default) is a clear sign of GSDML drift.

Step 8 - Bring the System Online in the Correct Order

1. Power-cycle the SCALANCE X208 (power OFF, wait 10 s, power ON). This forces the switch to re-read its port configuration.
2. Power-cycle each SIMOCODE pro V PN basic unit (TM terminals, OFF for 10 s, then ON).
3. Download the V17 project to the CPU 1515F-2 PN. The download will restart the IO controller and re-establish AR with all four SIMOCODE devices.
4. Verify the SCALANCE X208 WBM port statistics show non-zero TX/RX counters on all four SIMOCODE ports.

Firmware Compatibility Considerations

The CPU 1515F-2 PN firmware version is the single most common V17 migration fault. The matrix below is compiled from the TIA Portal V17 release notes. Verify against the official Siemens support pages for your specific order number.

For SCALANCE X208, the firmware should also be on the latest V6.x maintenance release. The SCALANCE X-200 managed family firmware is available from the Siemens Industry Online Support under the X-200 product page.

SCALANCE X208 Web Based Management Diagnostic Reference

For SIMOCODE pro V PN commissioning, the recommended SCALANCE X208 settings are:

PRONETA Network Analysis Procedure

PRONETA is the official Siemens PROFINET commissioning tool. It runs on Windows, requires no installation of TIA Portal, and reads PROFINET traffic via the laptop Ethernet port.

1. Download PRONETA from the Siemens Industry Online Support (typical order: 6ES7822-0AA00-0YA0 or the latest version).
2. Install on a service laptop; reboot if prompted.
3. Connect the laptop to a free port on the SCALANCE X208 in the same VLAN as the SIMOCODE pro V PN devices.
4. Launch PRONETA and click Network Analysis, then Start. The scan takes 5 to 15 s on a 4-device segment.
5. In the device list, the SIMOCODE pro V PN devices appear with their order number, MAC address, and current PROFINET device name. If a device shows No name, it has not yet been assigned a PROFINET name.
6. Click on each device to view: name, IP, vendor, device ID, and a Set PC station or Assign name shortcut.
7. Use the PRONETA Topology view to confirm the physical cabling matches the TIA Portal V17 topology. A red link indicates a cabling error.
8. Use the PRONETA Port statistics view to monitor per-port frame counters during the recovery.

SIMOCODE ES Licensing - V15 Premium to V17 Migration

SIMOCODE ES licensing is per major version. A V15 Premium license does not authorize V17 features.

If the project requires V17 features (for example, the new V17 device view layout, the V17 PROFIsafe parameter set, or V17-only add-ins), the V15 license must be upgraded to a V17 Premium license. Without this upgrade, SIMOCODE ES 17 runs in compatibility mode and may refuse to go online with the V17-configured SIMOCODE pro V PN device.

To order the upgrade, contact your Siemens sales channel with the original V15 license certificate. The upgrade is a license-key replacement, not a new installation.

SIMOCODE Service Interface - Sirius PtP COM Port Configuration

The SIMOCODE pro V basic unit includes a system interface (point-to-point) for service and commissioning. The interface is the 9-pin Sub-D connector on the front of the basic unit. The Siemens USB service cable for SIMOCODE pro (the Sirius PtP cable) connects this system interface to a PC USB port and enumerates as a virtual COM port.

Driver Installation

1. Connect the SIMOCODE USB service cable to a USB port on the service laptop.
2. Windows Device Manager should display a new COM port under Ports (COM & LPT), for example COM3. If the port is missing, install the SIMOCODE USB cable driver (available on the SIMOCODE ES installation media, or from the Siemens Industry Online Support).
3. Note the COM port number assigned by Windows.

SIMOCODE ES 17 Configuration for Sirius PtP

1. Launch SIMOCODE ES 17.
2. Open the project or create a new offline project for the SIMOCODE pro V PN device.
3. From the menu, select Online, then Online Connections (or press the Go online button in the toolbar).
4. The Online connections dialog lists all available connection types. Select Sirius PtP.
5. The COM port field defaults to the first available COM port. Click the dropdown and select the COM port matching the USB service cable (for example, COM3).
6. The baud rate should remain at the default (19200 bit/s for SIMOCODE pro system interface). Do not change unless Siemens support has specifically requested a non-default baud rate.
7. Click Connect. SIMOCODE ES 17 will establish a point-to-point session with the basic unit and display the device parameters.

When to Use Sirius PtP

TIA Portal V17 Migration Procedure (Best Practice)

The migration from V15.1 to V17 should follow a controlled procedure to avoid the issues described above. For engineering validation before physical commissioning, TIA Portal V17 engineering options support S7-PLCSIM Advanced simulation of the S7-1500 controller with the SIMOCODE pro V PN devices, allowing the V17 project to be validated in the office before the field download. See the TIA Portal V17 Engineering Options documentation for the supported CPU list under S7-PLCSIM Advanced.

1. Back up the V15.1 project as a .zap15_1 archive on a network share.
2. Open the project in TIA Portal V17. TIA Portal prompts to upgrade the project; accept the upgrade.
3. Review the upgrade log. TIA Portal V17 reports any devices that could not be re-bound to a current GSDML. Address each warning before continuing.
4. Open the CPU 1515F-2 PN, then Properties, then General, then Catalog Information. Confirm the firmware version. If it is V2.1, plan a firmware update to V2.9.x before downloading the V17 project.
5. Open Devices & Networks. Verify the SIMOCODE pro V PN devices, the SCALANCE X208, and the IO controller are all visible in the topology view with green link indicators.
6. Compile the project (Project, then Compile, then Software rebuild all).
7. Download the project to the CPU 1515F-2 PN. Use the TIA Portal V17 Extended download to device interface, and select the appropriate PG/PC interface.
8. Use PRONETA to validate the network after the download.
9. Use SIMOCODE ES 17 (with a valid V17 license) to verify the SIMOCODE pro V PN parameter set.

Verification Checklist

Preventive Maintenance Recommendations

1. Track CPU 1515F-2 PN firmware updates in a CMMS. Apply V2.9.x service packs within 90 days of release.
2. Track SCALANCE X208 firmware. Apply the latest V6.x maintenance release annually.
3. Maintain a license inventory. A V15 license does not entitle a V17 tool.
4. Export the PRONETA network baseline after every commissioning and store it with the project archive. A future PRONETA comparison will surface any device drift.
5. Back up the SCALANCE X208 configuration (WBM, System, Configuration Backup) before any firmware update.
6. Document the PROFINET device names, IP addresses, and physical port assignments in the project documentation. A one-line change in TIA Portal can orphan every SIMOCODE pro V PN station on the plant.
7. Run PRONETA on a quarterly basis to detect PROFINET station failures before the line goes down.

FAQ