Resolving STEP 7 'Address Cannot Be Monitored' Error in Blocks

Problem Overview

When commissioning or debugging a SIMATIC S7-300/S7-400 program in STEP 7 V5.3, V5.4, or V5.5, an engineer may see the literal symbol Address Cannot be Monitored (German: Adresse kann nicht beobachtet werden) appear in the Monitor/Modify view or in the Declaration View of a Function Block (FB), Function (FC), Instance Data Block (DB), or Shared Data Block. The placeholder appears in the Actual Value, Setpoint, or Status column in place of the live process value, blocking visibility into the tag during online operation.

The same symbol can also appear when an attempt to modify an address online returns --- with a status field of Status: cannot be monitored. This article decomposes the four documented causes in the STEP 7 online help, maps them to real CPU families, and provides field-verified workarounds.

Root Cause Analysis: The Four Documented Reasons

STEP 7 online help enumerates four scenarios that produce Address Cannot be Monitored. Each must be eliminated before suspecting hardware or wiring faults.

Cause 1: Address Outside the Permitted CPU Range

Every S7 CPU has a hard-coded address space that defines which inputs (I/IB/IW/ID), outputs (Q/QB/QW/QD), peripheral (PI/PQ), and bit-memory (M) areas can be online-monitored. The maximum values differ by CPU model and firmware version.

Reference ranges for common S7-300 CPUs

Reference ranges for common S7-400 CPUs

Resolution procedure

1. Open the symbol table (Symbols) in STEP 7 and locate the operand flagged with Address Cannot be Monitored.
2. Confirm the absolute address (for example MW 12000) against the CPU datasheet on the Siemens Industry Online Support portal. Search by MLFB and verify the Address areas section of the technical data sheet.
3. If the address exceeds the CPU limit, the application logic must be re-mapped into a valid range. STEP 7 cannot lift this limitation at runtime.
4. If the address is valid but still shows Address Cannot be Monitored, proceed to Cause 2 (missing DB).

Cause 2: Data Block Not Present in the Target CPU

When monitoring a tag inside an instance DB or shared DB, the block must be physically loaded into the CPU. STEP 7 will refuse to display any value from a DB that does not exist in the target system.

Diagnostic sequence

1. Connect online: PLC → Connect to Target System.
2. Open the S7 Program → Blocks container. The online view (small icon next to the block) reveals which blocks are actually on the CPU.
3. Compare offline (PG) vs online (CPU) block list. Any block marked with a yellow triangle is either missing on the CPU or has a different timestamp/checksum.
4. For a missing DB: select the block and execute PLC → Download (or PLC → Download User Program to Memory Card if the DB is large).

Cause 3: Peripheral Outputs (PQ) Cannot Be Monitored

STEP 7 prohibits online monitoring of peripheral output addresses (PQ, PQB, PQW, PQD). The CPU does not return a current image for the output side of the I/O bus, so the symbol Address Cannot be Monitored is hard-coded.

Why peripheral outputs are not readable

• Peripheral outputs are write-only from the CPU's perspective; reading them requires a hardware echo that PROFIBUS/PROFINET slaves typically do not provide.
• The process-image output (Q) is readable, but only if the corresponding PQ is mapped into the process image partition (OB1-OB100 in HW Config → Update of the process image tab).

Field-verified workarounds

// In OB1, mirror the value just written
L PQW 256
T MW 200

Cause 4: Block Password / F-Safe Access Restrictions

The fourth and most common cause during commissioning of safety projects is that the block is protected by KNOW_HOW_PROTECT or by an F-attribute applied to a F-safe block running on an F-CPU (e.g., CPU 315F-2 DP, CPU 416F-3 PN/DP).

Recognising the four block-protection states in STEP 7 V5.3+

Procedure for F-Safe blocks (S7-300F/S7-400F)

1. Right-click the block in the SIMATIC Manager and select Object Properties → Protection.
2. If the Safety tab is present, the block carries an F-attribute. STEP 7 enforces read-only access.
3. From the LAD/FBD/STL editor, choose Options → Block Protection → Read-only access → For this access only. This opens the block for one online session without modifying the safety password.
4. Confirm by monitoring a known tag (e.g., DB100.DBD0). If a numeric value appears, the F-block is now observable for the current session.

Procedure for KNOW_HOW_PROTECT blocks

1. If you know the password: Options → Block Protection → Enter Password. The block becomes fully readable; monitoring proceeds normally.
2. If you do not know the password: monitor is blocked for that block. There is no STEP 7 menu path to bypass KNOW_HOW_PROTECT.
3. Contact the original programmer or the OEM that delivered the machine. The password must be supplied by the project owner; field engineers should not rely on third-party "password recovery" utilities, which target outdated project files and may violate the end-user license agreement.

STEP 7 Version-Specific Behaviour

Diagnostic Workflow Summary

Verification

After applying the appropriate fix, perform these checks to confirm that monitoring is restored:

1. In SIMATIC Manager, open PLC → Monitor/Modify → Monitor (New VAT).
2. Enter the previously failing operand (e.g., MW 200 for a mirrored PQ, or DB100.DBW0 for an F-block).
3. Set the trigger to Monitor (continuous) or Monitor once / now. The actual numeric value (decimal or hex) must replace the Address Cannot be Monitored placeholder.
4. Toggle the input in the running process; the value must update within one OB1 cycle.
5. If the symbol persists, re-check Cause 1 by verifying the address against the CPU datasheet on Siemens Industry Online Support.

Troubleshooting Matrix

Best-Practice Checklist

• Always cross-reference the absolute address with the CPU datasheet (MLFB) before assuming a wiring fault.
• Use a mirrored tag pattern (QW→MW) for any output value that must be observable during FAT/SAT.
• Document the safety password of every F-block in the project vault; never rely on a single engineer remembering it.
• When commissioning a third-party machine, request the unencrypted STEP 7 source alongside the compiled .s7f archive.
• Keep STEP 7 V5.5 SP4 (or the latest SP) installed; older versions ship with the F-block handling bugs that have been patched in V5.4 SP5 and later.

FAQ