Resolving TIA Portal V20 Online/Offline Differences at Local Modules

Engineers commissioning SIMATIC S7-1500 stations in TIA Portal V20 (STEP 7 V20) frequently encounter an online/offline comparison that highlights a difference at a local module — most often the CPU 1515-2 PN, an ET 200MP submodule, or an ET 200SP station on PROFINET — even when the project has not been edited. The PLC is in RUN, the diagnostic buffer reports "Maintenance required: Application/technological function faulty" with reference to a .ModuleAccessPoint, and the Go Online icon turns yellow or red. This article walks through the field-proven Siemens-documented procedure to triage, isolate, and clear the discrepancy without rewriting the application.

1. Problem Description

When you perform Online > Compare Offline/Online (or simply Go Online) on a CPU 1515-2 PN in TIA Portal V20, the project tree or the device view marks one or more slots as different. Typical symptoms observed in the field:

• Yellow exclamation icon on the CPU or a downstream I/O module in the online view.
• Diagnostic buffer entry: Event ID 0x4542 — Maintenance required: Application/technological function faulty.
• Module reference: AHU2_7_xxx_SV / AHU2_7_xxx_SV.ModuleAccessPoint with status Outgoing event.
• No SF/BF LED on the CPU; the user program continues to execute.
• No compile errors, and the project was not edited between two consecutive downloads.

The display is non-destructive, but it obstructs reliable online monitoring and blocks Download to device prompts that would otherwise help diagnose the cause.

2. Root Cause Categories

Siemens documentation groups online/offline differences at local modules into five categories. Identifying the correct category is the first step toward a clean comparison.

2.1 Timestamp / Integrity Counter Mismatch

Each compilation of a STEP 7 project writes a project integrity ID and per-module timestamps. The online CPU stores the timestamp of the last successful download. If another station in the same multiproject is recompiled — for example, an HMI or a second CPU — TIA Portal V20 may regenerate the integrity counter for the entire multiproject without modifying the local station. The online view continues to show the older timestamp, so Compare Offline/Online reports a major difference even though hardware and software are functionally identical. This is a known false-positive behavior and is the most common cause in brownfield retrofits where multiple engineers share one TIA Portal installation.

2.2 PROFINET Topology Difference

If the CPU 1515-2 PN acts as a PROFINET IO controller and the topology editor has been used to assign port interconnections, a port swap on the field (for example, cables re-patched during maintenance) causes the topology comparison to flag a difference. The diagnostic buffer will not raise a fault; only the online topology view will highlight the swapped port in red.

2.3 Module Configuration Difference

Modifying parameters on the device (for instance, changing a digital input filter time via the web server) is reflected online but not in the offline project. TIA Portal V20 considers the parameters different and shows the module as divergent. A second download from the offline project resets the parameters, which is acceptable as long as the change was unintended.

2.4 Network Reload Side Effect

Reloading a device elsewhere in the same PROFINET subnet re-issues DCP hello frames and may force the controller to update its neighbor table. This is benign but triggers the online/offline comparison flag on the local CPU. The PLC continues to run without errors.

3. Affected Modules and Firmware

4. Diagnostic Procedure (Official Siemens Method)

Follow the steps in this order. Do not skip to the download — the goal is to confirm there is no real configuration drift before issuing a hardware-configuration download that will stop the CPU.

Step 1 — Open the Diagnostic Buffer

1. Right-click the CPU in the project tree and choose Online > Diagnostics > Diagnostic Buffer.
2. Locate the most recent 0x4542 entry and read the associated module reference.
3. Confirm the entry is marked Outgoing. If only an Incoming event is present, the maintenance condition is still active and must be cleared before any download.

Step 2 — Compare Offline/Online in the Project Tree

1. Right-click the CPU → Compare Offline/Online.
2. The comparison editor opens with two columns: Offline and Online.
3. Expand each slot. A yellow bar indicates a difference; a green bar means identical.
4. Click the difference to view the parameter-level delta. Record the slot, parameter name, and value.

Step 3 — Check the Device View

1. Open the device view of the local station (double-click the device in the project tree).
2. Switch the view to Online using the toolbar toggle Offline/Online.
3. Modules with a difference are highlighted. Hover over the module to see the tooltip — it lists the parameter that differs and the online value.

Step 4 — Online/Offline Topology Comparison

Use the topology view to confirm or rule out port-level differences. The official procedure is documented in the S7-1200/1500 manual collection; the workflow is identical for S7-1500 CPUs acting as PROFINET controllers.

1. In the project tree, select the CPU and open Topology View.
2. On the toolbar, click Go Online for the topology. TIA Portal V20 queries each PROFINET device for its port neighbors and overlays the result on the configured topology.
3. Red port numbers or red interconnections indicate a topology drift. The tooltip shows the configured neighbor and the detected neighbor.

5. Resolution Methods

Three field-proven methods are documented in the Siemens function manuals. Apply them in the order listed.

Method 1 — Download Software Only (No STOP Required)

1. Right-click the CPU → Download to device > Software (all blocks).
2. Confirm the prompt. The CPU remains in RUN; only the user program and configuration data are reloaded.
3. After download, perform Compare Offline/Online again. If only the timestamp triggered the warning, the comparison will turn green.

Method 2 — Download Hardware Configuration (Requires CPU STOP)

Use this method when the comparison editor or device view shows a real parameter drift that Method 1 cannot clear (for example, a module parameter or a port interconnection).

1. Bring the process to a safe state and confirm the operator is ready.
2. Right-click the CPU → Download to device > Hardware configuration.
3. TIA Portal V20 issues a prompt: "The CPU will be set to STOP for the download. Do you want to continue?" Confirm.
4. After the download completes, restart the CPU in RUN.

Method 3 — Update TIA Portal and Service Packs

Siemens releases service packs for TIA Portal V20 that refine the integrity counter handling and improve the topology comparison view. If Method 1 and Method 2 do not produce a clean comparison, install the current TIA Portal V20 service pack and re-run the procedure.

6. Verification

After applying any of the three methods, perform the following verification steps before returning the station to production.

1. Right-click CPU → Compare Offline/Online. The comparison editor must show all-green entries.
2. Open the diagnostic buffer. Confirm the last 0x4542 event is Outgoing and no new Incoming event has been logged.
3. Toggle the device view to Online. No module should display a yellow or red icon.
4. Open the topology view → Go Online. All port numbers and interconnections must be green.
5. Check the CPU diagnostic LEDs: RUN solid green, MAINT off (or briefly flashing during a planned maintenance event), SF off, BF off.

7. Edge Cases and Field-Proven Caveats

7.1 Process Cannot Be Stopped

If the process cannot tolerate a CPU STOP, restrict yourself to Method 1 (Software (all blocks)) and accept that topology-level or module-parameter drifts will persist. Document the open items in the maintenance log and schedule a planned downtime window. Do not skip the comparison — operators must know that the online view is intentionally not green.

7.2 SF LED on After Adding an Encoder

If the comparison tool reports "The online and offline module configuration data are different" and the SF LED is on after adding an encoder, the cause is most often a wrong device description (GSD import missing) or a parameter mismatch (resolution, code type, or counting mode). Resolve by importing the correct GSD, recomparing, and downloading the hardware configuration. For Siemens SIMATIC encoders, the device description is integrated in TIA Portal V20 and a GSD import is not required.

7.3 F-CPU (Safety) Signature Check

On a CPU 1515F-2 PN, the F-runtime signature is part of the comparison. After a software-only download, the F-signature changes. The safety program must be re-accepted and the F-signature re-issued using the F-acceptance tool before production can resume. This is a mandatory step in STEP 7 Safety Advanced V20.

7.4 HMI Variables Re-Fetched After Download

WinCC Professional V20 and Unified Comfort Panels re-read the HMI tags after a CPU download. If the HMI shows stale data or red connection icons for a few seconds, this is normal and does not indicate a fault. Wait for the HMI to complete the tag re-read.

7.5 Multiproject vs. Single Project

In a multiproject with shared PROFINET subnet, recompiling a sibling station updates the integrity counter of the entire multiproject. The local CPU comparison will turn red even though nothing changed locally. Method 1 resolves it. To prevent recurrence, lock the multiproject for editing while a colleague is performing a download.

8. Safety Considerations

• Method 2 forces the CPU to STOP. Place the process in a safe state, inform the operator, and confirm that a STOP is permissible under the project safety matrix.
• For F-CPUs, do not perform Method 2 without a current F-acceptance test report. The F-signature must be re-issued and acknowledged.
• If a hardware change is downloaded without a STOP, verify the change by reading the parameter online. The download may appear successful while the new value is not active.
• Always confirm the diagnostic buffer is free of unacknowledged faults before issuing another download.

9. Quick Reference Checklist

10. Related Diagnostic Information

The Siemens S7-1500 system diagnostic provides additional event IDs that often accompany an online/offline drift. Use the table below as a quick lookup.

FAQ