Resolving TIA Portal S7-1200 Resources Tab I/O Count Errors

Problem Summary

The TIA Portal "Resources" tab on S7-1200 projects (CPU 1212C with SM 1234 AI4/AO2) routinely reports inconsistent I/O usage statistics. Field reports show percentage values above 100% (e.g., 133.33% or 166% of configured analog inputs) and mismatched digital output counts even when the user program compiles cleanly, downloads successfully, and executes the correct logic on the target hardware.

This is a display-side accounting issue in the TIA Portal engineering view, not a runtime I/O fault. The PLC continues to scan and control physical I/O correctly; the discrepancy appears only in the static resource view that the engineering software uses to summarize configured versus referenced addresses.

Affected Hardware and Software

Reference documentation:

• S7-1200 Programmable Controller System Manual (Siemens Online Support)
• S7-1200 CPU 1212C / 1214C / 1215C / 1217C Device Manual
• STEP 7 Basic in TIA Portal Programming and Operating Manual
• S7-1200 Signal Modules SM 1231 / SM 1232 / SM 1234 Manual

Root Cause Analysis

The Resources view performs a static scan of the offline project database and counts references to process image addresses. It does not execute the program; it does not inspect the runtime process image; it only inspects the symbolic and absolute address usage as written by the editor. The display logic has three known classes of miscount:

1. HSC address expansion inflates DI counts

When a high-speed counter (HSC) is configured on the CPU, TIA Portal allocates the dedicated HSC input process image region at I1000 through I1003 (4 bytes per HSC instance, depending on configuration). Configuring even one HSC causes the resource display to roll up the full HSC byte range as "configured DIs." In the reported case, configuring HSC brought the configured DI count to 40, even though the actual discrete input byte used by the program remained at IB0.

2. NORM_X / SCALE_X instruction symbol expansion

The NORM_X and SCALE_X instructions operate on REAL (floating-point) values. When a NORM_X block is placed in the program and its VALUE input is wired to an analog input word (IW), the resource counter records the address referenced by the input pin. However, depending on how the input pin is wired (direct address, PLC tag, or unconnected default), the counter can over-report. In the reported project, the user wired IW5, IW7, IW9, and IW11 to four NORM_X blocks. The view showed 10 AIs in use (166% of 6 configured), reflecting cumulative references from intermediate tag declarations rather than actual scan-time reads.

3. Indirect or symbolic aliasing

When PLC tags are declared with the same data type as the analog input word (INT), and the tag is later renamed or repointed, residual address cross-references can remain in the project. The Resources view walks the cross-reference (XREF) tree in addition to direct address usage, which can double-count tag-to-tag aliasing.

HSC Address Map and the IB1000 Region

The S7-1200 reserves a fixed process image range for high-speed counter inputs. The exact mapping depends on the HSC instance ID and the configured edge evaluation mode. The first HSC is mapped to a 4-byte input region beginning at IB1000 when edge evaluation or enhanced functionality is selected.

This reserved process image region is invisible to user ladder logic, but TIA Portal reports it under "configured digital inputs," inflating the DI baseline. The HSC region cannot be written by the user program and does not consume physical inputs; the count is a display artifact.

OB204 Data Type Conflict

During diagnosis, a data type conflict was identified in OB204 (a hardware interrupt OB generated by the SM 1234 module on limit-exceedance events). The instruction at temporary local variable MD10 (DWORD / DUINT) is being interpreted by the Resources view as if it were an INT (16-bit signed) reference. The conflict surfaces only as a cross-reference anomaly; it does not prevent the OB from executing.

Diagnostic Procedure

1. Open the project offline in TIA Portal; do not connect to a live CPU.
2. Navigate to Project tree > PLC_1 > Program blocks.
3. Select Tools > Cross references (or press Ctrl+Alt+F7) to generate the XREF table for the entire program.
4. Filter the XREF table for byte ranges IB1000 through IB1023. These are HSC-reserved bytes; they will appear as "Used" even though the program never reads them.
5. Filter the XREF for every analog input word declared on the SM 1234 (default: IW64–IW71 for a 4-AI module in slot 1; the user's case used a non-default mapping with IW1, IW3, IW5, IW7, IW9, IW11). Count every distinct address; the resource percentage is (referenced unique addresses) / (configured addresses) × 100.
6. Open the PLC tags table and remove any tag whose data type is INT and whose name suggests an analog channel but whose value is not wired to an IW in any code block.
7. Check the Watch and force tables and any Recipe or Data block instances for residual IW references inherited from earlier revisions of the project.
8. Compile the project (Project tree > PLC_1 > right-click > Compile > Software (rebuild all blocks)).
9. Re-open the Resources view and click the Update icon (the circular refresh button at the top right of the resource panel). If the count still does not match, close the project and reopen it; the XREF cache is rebuilt on project open.

Verification on the Live CPU

To confirm the Resources display is a static-analysis artifact rather than a hardware fault, perform a runtime verification:

1. Go online with the CPU (Project tree > PLC_1 > Go online).
2. Open Watch table and force the analog input word that the display claims is "unused" (for example, IW1 for channel 0 of the SM 1234).
3. Read back the value. If the value tracks the physical input (use a calibrator or short the terminals to 0/4–20 mA), the I/O is functional and the Resources tab miscounts because the address is referenced from a tag only and not from code.
4. Repeat for each IW the Resources view flags as over-counted. The PLC tag is the source of the XREF entry; either wire the tag to a code block or remove the tag.

Workarounds

Escalation to Siemens Support

If the discrepancy persists after the steps above, open a support request via the Siemens Industry Online Support portal. Include:

1. The TIA Portal version (e.g., V15.1 + Upd 4), installed packages, and build number (Help > About).
2. The CPU order number and firmware version (online > diagnostics > module information).
3. The packed project archive (.zap14 or .zap15) — these are the TIA Portal pack formats; legacy .ap14 and .ap15 are unpacked project directories that exceed the upload limit and must be packed first.
4. A screenshot of the Resources tab and the XREF export (CSV).
5. A short description of the discrepancy, with the actual scanned I/O list and the displayed I/O list side by side.

Use the Siemens support entry "TIA Portal: Resources view shows incorrect percentage" type descriptions to locate related OSS notes and FAQ entries. Direct link to the support entry point:

• Siemens Industry Online Support – Entry Point
• S7-1200 CPU 1212C Product Page

Long-Term Best Practice

Treat the Resources view as a design-time sanity check, not a runtime diagnostic. Build the project around three ground-truth sources:

1. The Device configuration (online > Device view), which is the source of truth for what is physically wired and configured.
2. The Cross-reference table, which is the source of truth for what addresses the program actually touches.
3. A Watch table downloaded to the live CPU, which is the source of truth for what the program is doing right now.

Keep PLC tag names stable across revisions, and avoid creating an INT tag that mirrors an IW address unless the tag is wired to a code block. The combination of stable symbol names and a clean XREF will minimize the divergence between the offline resource count and the actual I/O usage on the CPU.