Fixing S7-1500 "Diagnostic Data Not Available" Error After TIA Portal Upload

Applies to: SIMATIC S7-1500 CPU 6ES7 510-1DJ00-0AB0 (CPU 1510SP-1 PN), firmware V1.6 and V2.8, with ET 200SP distributed I/O on PROFINET. TIA Portal V14 → V16 cross-version upload scenario. Replaces a previous S5-based machine control upgrade path.

1. Problem Description

After uploading a legacy TIA Portal V14 project into a newly commissioned S7-1500 station (CPU 6ES7 510-1DJ00-0AB0, firmware V2.8) using TIA Portal V16, the controller exhibits a deterministic fault signature:

• CPU state: STOP, RUN/STOP LED steady yellow, MAINT LED off (no maintenance demanded), ERROR LED off.
• ET 200SP behaviour: Every channel-status LED on every I/O module blinks green at the slow diagnostic cadence (2 Hz) instead of showing a steady green "channel OK" or a steady red "channel fault".
• IM 155-6 behaviour: The PROFINET interface module accepts the AR (Application Relationship) but reports no module-level diagnostics.
• Online > Online & diagnostics > Diagnostic buffer: Entries present for the CPU itself, but the lower-level node expansion shows "Diagnostic data not available" against the IM and every slot.
• Project tree: Hardware catalog and device view render without error, but the compare view shows unresolved differences between configured and actual station.

The symptom is consistent with a hardware configuration that has been compiled and downloaded without a matching device description for the actual module firmware on the rack. TIA Portal generates a valid PLC program, but the I/O assignment table cannot be reconciled with the station, so the CPU remains in STOP with diagnostics suppressed.

2. Affected Hardware, Firmware, and Software

The 6ES7 510-1DJ00-0AB0 is a CPU 1510SP-1 PN for the ET 200SP form factor. Because Siemens ships firmware updates as free-of-charge downloads via the Siemens Industry Online Support portal, a station purchased "new" from distribution may carry any released firmware line. Two stations with the identical MLFB can therefore differ at the firmware level — which is exactly the situation in this case (V1.6 on the existing line, V2.8 on the new line).

The relevant Siemens documentation is the SIMATIC S7-1500 Automation System Manual and the ET 200SP Distributed I/O System Manual. The CPU's functional scope and supported module revisions are bound to its firmware version; therefore the TIA Portal project must be compiled against a device description (GSDML / HSP) that matches the firmware actually installed on the rack.

3. LED Status Interpretation

Correct interpretation of the LEDs is the first diagnostic step and confirms the fault path before touching the project.

4. Root Cause Analysis

Three contributing causes converge to produce the reported symptom. All three must be resolved before the CPU will transition to RUN.

4.1 Firmware mismatch between project and rack

TIA Portal V14 was used to commission the original station against CPU firmware V1.6. The project archive therefore carries device descriptors and compiled configuration blocks for V1.6. The new station carries V2.8 firmware. TIA Portal V16 alone does not retroactively upgrade the device descriptors inside an archived project; it only recognises the modules it has been told about through installed HSPs and the hardware catalog. The result is that the project compiles, but the download produces a configuration that the V2.8 station cannot reconcile.

4.2 Missing or stale Hardware Support Package (HSP)

An HSP is a ZIP bundle published by Siemens containing updated device descriptions (GSD/GSDML, module type definitions, firmware-level capabilities). When a new station is added to a project, the engineering station must have an HSP installed that covers the firmware revision present on the physical device. If the engineering station has only the original V1.6 descriptors, the V2.8 CPU either does not appear in the catalog or appears without its full V2.8 capability set. The download will then omit required configuration blocks.

4.3 ET 200SP Base Unit type mismatch

ET 200SP modules require a base unit whose colour/type code matches the slot definition. "Light" base units (BU type A0, e.g. 6ES7 193-6BP00-0DA0) feed a new potential group. "Dark" base units (BU type A1, e.g. 6ES7 193-6BP00-0BA0) continue the potential group from the left neighbour. If the base unit types selected in the TIA Portal device view do not match the physically inserted base units, the slot is marked invalid by the IM and module-level diagnostics cannot be retrieved — which surfaces as "Diagnostic data not available" for those components.

5. Prerequisites for Recovery

Before opening the project in TIA Portal V16, confirm the following on the engineering station (ES) and on the physical rack.

1. Confirm TIA Portal V16 Update 7 or later is installed. Earlier V16 builds have known issues with V2.8 module support that were fixed in subsequent updates. Reference: TIA Portal V16 release notes and updates.
2. Install the latest HSP that covers firmware V2.8 of the CPU and the V2.8 IM 155-6 (HSP_0186 or later). Path in TIA Portal: Options > Support Packages > Install HSP.
3. Confirm the engineering station can reach the new S7-1500 station over PROFINET. Verify the CPU's IP address, subnet mask, and that the ES network adapter is in the same subnet. Ping the CPU IP before launching TIA Portal.
4. Take an offline backup of the current (faulted) project archive. File > Archive > Project. Never modify the only copy.
5. Verify physical inventory against the bill of materials: CPU MLFB and firmware (readable via the CPU's display or the SIMATIC Automation Tool), every IM 155-6 MLFB and firmware, every I/O module MLFB and firmware, every base unit type code printed on the side of the BU.

6. Step-by-Step Recovery Procedure

The procedure below restores the configuration in a single, verifiable pass. Do not skip the verification steps between phases — each one isolates a specific cause from the three listed in Section 4.

Phase A — Read the actual station (do not assume)

1. In TIA Portal V16, open the project archive.
2. Switch to Project view > Devices & networks.
3. Right-click the PROFINET subnet containing the new station and select Go online > Online & diagnostics.
4. In the diagnostics view, expand the accessible node list and confirm the CPU is reachable. If not reachable, fix the IP / routing first.
5. Open the CPU's Online & diagnostics > Diagnostic buffer. Capture the most recent entries — they will reference the slot assignment failures and confirm the firmware version.

Phase B — Reconcile device catalog

1. In Devices & networks, select the new CPU device and double-click Device view.
2. Note the device version displayed in the title bar (e.g. "V2.8"). If V2.8 does not appear in the dropdown, the HSP is missing — return to Prerequisites step 2.
3. If the project is locked to V1.6 because it was compiled under V14, change the device version to V2.8 using the dropdown. TIA Portal will prompt for a recompile. Accept.
4. Open the ET 200SP IM 155-6 station. Right-click each slot and confirm the I/O module part number matches the module physically inserted. If a module is missing from the catalog, install the corresponding HSP.

Phase C — Force a clean hardware compile and download

1. In the project tree, right-click the CPU and select Compile > Hardware (rebuild all). This step regenerates the system data blocks (SDBs) from the current device configuration and discards the V14-era SDBs.
2. Resolve every entry that appears in the Compile results window. Do not ignore warnings; many warnings in the S7-1500 environment are fatal at runtime.
3. Select the CPU and click Download to device > Hardware and software (only changes).
4. In the download dialog, tick Overwrite all for the system data, untick "Keep current program" — the goal is to push a consistent, freshly-compiled configuration.
5. Click Go online after the download completes.

Phase D — Verify slot diagnostics

1. Online & diagnostics > expand the ET 200SP station.
2. Each module must show its firmware revision and "Status: OK". The "Diagnostic data not available" message must be gone.
3. Channel LEDs on the I/O modules must transition from flashing green to steady green within 5 seconds of the configuration being accepted.
4. If diagnostics are still missing for a single module while the rest are OK, the most likely cause is a base-unit-type mismatch on that slot — go to Section 7.

Phase E — Transition the CPU to RUN

1. In the online view, click Start CPU.
2. Confirm RUN/STOP LED transitions from yellow to flashing yellow (STOP requested) to steady green (RUN).
3. Monitor the diagnostic buffer for at least 60 seconds of clean operation before handing the line over.

7. ET 200SP Base Unit Verification

Base unit verification is the most frequently missed step. ET 200SP modules are inserted into base units (BUs); the base unit determines the potential group topology and therefore the slot's electrical environment. TIA Portal must know which base unit is at every slot before it can assign module parameters such as the supply voltage group, channel diagnostics enable, and value status.

Each base unit is marked on the side with a colour code that maps to a type designation:

To verify base unit alignment against the project:

1. Physically inspect the side of each base unit. Note the type code printed on the label (e.g. "BU A0", "BU A1").
2. In TIA Portal, open the ET 200SP device view and click each slot. In the inspector window under Properties > General, confirm the BU type matches the physical unit.
3. If the project was inherited from V14 and uses the older base unit selection logic, the BU assignment may default to the wrong type. Manually set the BU type for every slot.
4. Recompile hardware and redownload.

8. Firmware Migration Considerations (V1.6 → V2.8)

Firmware V2.8 of the CPU 1510SP-1 PN introduces functional changes relative to V1.6 that affect project portability:

• Motion / technology objects: V2.8 expands the count of supported TO instances and adds new cams/synchronous operation features. Projects originally compiled against V1.6 will compile against V2.8 without manual rework in most cases, but technology objects must be re-assigned at the device level (Technology objects > Assignment).
• Security / access protection: V2.8 enforces stricter password policy defaults. If the project contains protected blocks, the local CPU password must be re-entered.
• OPC UA server: V2.8 enables OPC UA server functionality by default if the project has the license. If the original station did not use OPC UA, disable the server explicitly to prevent unintended exposure.
• Diagnostic block behaviour: V2.8 reorganises some system diagnostic block (SDB) indices. Pre-V2.0 projects may reference SDB indices that are no longer emitted by V2.8 firmware. This is the mechanism that produces "Diagnostic data not available" — the diagnostic block dispatcher cannot find the expected SDB, so it returns an empty diagnostic record.

If firmware V1.6 must be preserved (for example because the existing line must remain bit-for-bit identical to the new line during the ramp-up phase), downgrade the new CPU using the SIMATIC Automation Tool or the CPU's web server before commissioning. Reference: Firmware update / downgrade S7-1500. A downgrade is destructive of the station configuration; back up first.

9. Verification and Commissioning Checklist

Use this checklist to confirm a clean recovery before handing the line back to operations.

10. Troubleshooting Matrix

11. Prevention and Best Practices

1. Maintain a per-station firmware register. Track every station's CPU and IM firmware version in a plant-level document. New stations must be commissioned against the registered firmware, or the firmware must be downgraded before commissioning.
2. Version your archives with explicit firmware context. Include the firmware version in the archive file name (for example Line2_S7_V14_CPU_V16.zip) and inside the project properties (Project tree > CPU > Properties > General > Comment).
3. Keep the engineering station current. Install every released HSP promptly. New HSPs add support for new firmware without requiring a TIA Portal upgrade.
4. Use a standardised base-unit pattern. Adopt a project template in which every light base unit is followed by a known number of dark base units before the next light base unit. Encode this pattern in the project template so that newly inserted stations inherit it.
5. Avoid "upload and forward" workflows. Uploading a project from a working station, editing it offline, and downloading to a different station is fragile across firmware revisions. Prefer to archive from the original engineering source and re-target explicitly.
6. Run the SIMATIC Automation Tool before commissioning. The tool performs an automated IP/name assignment and firmware comparison across the entire plant network and surfaces mismatches before they reach the diagnostic buffer.

12. Key Engineering Parameters

Record these values in the project's documentation block as a quick reference for any future engineer who picks up the station.