Resolving CPU 410-5H Object Properties Greyed Out and Read-Only in SIMATIC PCS 7 HW Config

When CPU 410-5H object properties become greyed out and read-only in HW Config, the root cause is a project database lock imposed by an open NetPro session with unsaved changes, an active cross-project hardware compilation, another engineering instance accessing the station across a network share, or Windows read-only file attributes on the project directory (*.s7p, *.db). To restore edit access, close all open NetPro and HW Config windows across the multiproject, check Windows file permissions, and execute 'Save and Reorganize (Slow)' in SIMATIC Manager to clear orphaned lock files.

Mechanics of Database Locking in SIMATIC Manager and HW Config

SIMATIC PCS 7 manages complex Multiprojects using an underlying relational database architecture. When an engineer opens HW Config or NetPro to modify controller parameters (such as CPU 410-5H cycle times, memory reserve, Profinet device names, or clock synchronization), the STEP 7 database places an exclusive record lock on the hardware station database (hmsx.db and associated Sybase/SQL Anywhere tables).

This locking mechanism prevents concurrent write operations that could corrupt the hardware memory configuration. If another tool or process holds this lock, HW Config opens in Read-Only Mode, greying out all configuration tabs and preventing parameter changes.

Root Causes of Read-Only Hardware Properties on CPU 410-5H

Field troubleshooting on PCS 7 V8.1, V8.2, and V9.0 identifies four common triggers for read-only CPU properties:

NetPro Open with Unsaved Changes: If NetPro is currently open in the background (or was left open in another station of the Multiproject) with uncompiled connection edits, HW Config locks CPU properties to prevent network address conflicts.
Multi-User Engineering Collision: In multi-user engineering environments where the project is shared over a network drive, another engineer on a secondary Engineering Station may have the hardware station open.
Orphaned Database Lock Files: If SIMATIC Manager crashed or terminated abnormally during a previous compile or download, temporary lock flags in the project folder remain set.
Windows File System Read-Only Attribute: If the project was copied from a DVD-ROM, retrieved from an unzipped archive with read-only flags preserved, or restricted by Windows ACL permissions, Windows prevents database writes.

Identifying Active Locks: NetPro, Multi-User Collisions, and S7P Files

To isolate the source of the lock:

Check the HW Config title bar. If it displays [Read Only], the station is explicitly locked by the database engine.
Open Windows Task Manager on all engineering stations accessing the project. Check for lingering background processes: s7tgtopx.exe (SIMATIC Manager), s7wnsmsx.exe (Station Configurator), and s7hcfgx.exe (HW Config).
Inspect the project directory in Windows File Explorer. Check whether project database files (*.s7p, hmsx.db) have the 'Read-only' attribute set under file properties.

Step-by-Step Procedure to Clear Locks and Restore Edit Privileges

Follow this sequence to unlock the CPU 410-5H properties:

Close All Open Editors: Close all HW Config, NetPro, CFC, and SFC windows across all stations in the Multiproject.
Save NetPro Network Configuration: If NetPro prompts to save changes upon closing, select Save and Compile, ensuring all cross-station routing tables are cleanly written to disk.
Clear Windows Read-Only Flags: In Windows File Explorer, right-click the root project folder, select Properties, uncheck the Read-only checkbox, click Apply, and select 'Apply changes to this folder, subfolders, and files'.
Execute Save and Reorganize (Slow): In SIMATIC Manager, select File > 'Save As...'. Check the box With Reorganization (slow). Save the project under a temporary name or overwrite the existing project. This rebuilds internal database indices, purges deleted pointers, and clears orphaned locks.
Re-open HW Config: Open the station HW Config. Double-click the CPU 410-5H. Confirm that all tabs are editable.

HW Config State and Lock Indicator Matrix

The following table compares HW Config states, locking causes, and recovery methods:

HW Config Display StateUnderlying CauseImpact on EngineeringCorrective Action PathTitle bar: [Read Only]NetPro open in backgroundAll CPU and CP properties greyed outSave and close NetPro windowTitle bar: [Read Only]Multi-user file lock on networkProperties greyed out; compile disabledClose station on remote ES workstationTitle bar: [Read Only]Windows file system read-only flagCannot save hardware modificationsClear read-only attribute in File ExplorerCrash on property openCorrupted hardware database indexFatal application error (0xC0000005)Execute 'Save As with Reorganization (slow)'Normal (No [Read Only])Station unlocked and readyFull parameter editing enabledProceed with hardware configuration

Verification

Verify hardware property access through the following steps:

In SIMATIC Manager, open HW Config for the target AS station. Confirm that [Read Only] does NOT appear in the window title.
Double-click the CPU 410-5H object. Navigate through the General, Cycle/Clock Memory, and PROFINET tabs. Verify that text boxes, drop-down menus, and checkboxes are active and editable.
Make a minor parameter change (e.g., adjust scan cycle load from communication by 1%), click Save and Compile, and confirm that compilation completes with 0 errors.
Open NetPro and confirm that the station reflects the updated hardware timestamp without locking warnings.

Commercial Accuracy Disclaimer: Software order numbers (MLFBs), package structures, and hardware capacity prerequisites vary across PCS 7 versions and hardware platforms. System integrators must confirm exact software entitlements and licensing requirements against the official Siemens Catalog CA 01 and obtain an authorized Siemens distributor quotation prior to purchasing.

Limitations and Operational Precautions

Consider these operational rules when managing hardware stations:

Never Edit HW Config Across Unstable WAN/VPN Connections: Database locking over high-latency networks frequently causes transaction timeouts and leaves permanent locks; always engineer on a local LAN or use Remote Desktop.
Save Before Switching Editors: Always save changes in NetPro before opening HW Config, and vice versa, to prevent cross-editor lock collisions.
Backup Before Reorganization: Always create a standard project archive (File > Archive) before executing 'Save As with Reorganization (slow)'.

Engineer FAQ

Can unsaved changes in NetPro cause HW Config to become read-only?

Yes. NetPro and HW Config share the same hardware database. An uncommitted edit in NetPro automatically locks HW Config into read-only mode to prevent conflicting data.