C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

How to Resolve PCS 7 Invalid Object Type Errors During Block and CMT Copying

How to Resolve PCS 7 Invalid Object Type Errors During Block and CMT Copying

The error 'Invalid object type' during block, chart, or Control Module Type (CMT) copy operations in SIMATIC PCS 7 V9.0 SP3 occurs when the destination project lacks required optional software packages (such as CEMAT), when library version descriptors conflict, or when internal database dictionaries become corrupted. In multi-user engineering environments, copying technological objects between libraries and project folders relies on proprietary object-type definitions registered in the STEP 7 Sybase/SQL database. If an engineering station lacks the specific library package used to create the object, or if project files were modified without running database reorganization, the copy wizard fails. To resolve this error, install missing library options, verify project consistency, and execute 'Save As with Reorganization (Slow)'.

Table of Contents

Root Cause Analysis: Why 'Invalid Object Type' Occurs

In SIMATIC PCS 7, blocks and charts are not independent flat files; they are complex relational entities managed by the STEP 7 engineering database:
* The Object Type Registry: When a block or Control Module Type (CMT) is created, the engineering system assigns an internal type identifier linking the object to specific system schema libraries.
* The Failure Mechanism: When an engineer attempts to drag and drop or copy/paste a block into a chart or library folder, SIMATIC Manager queries the target project's internal schema registry.
* The Exception: If the target project database returns an unknown schema ID, or if the local PC lacks the software component registered as the object's parent handler, SIMATIC Manager halts the operation with:
Error: Invalid object type.

Library Dependencies and Optional Software Packages

The most frequent catalyst for this fault in PCS 7 V9.0 SP3 is copying objects created with industry-specific libraries:
* CEMAT Library Dependencies: Blocks from the CEMAT mineral processing library (e.g., C_DRV_1D, C_GROUP, C_VALVE) embed custom metadata classes. If a project was created on an Engineering Station equipped with CEMAT V9.0 SP3, copying those blocks on an engineering workstation where CEMAT is not installed immediately triggers 'Invalid object type'.
* Control Module Type Schema Mismatch: CMTs created in newer PCS 7 update releases embed XML schema structures that older base installations cannot interpret.
* Cross-Version Drag-and-Drop: Dragging blocks directly between projects of differing major releases without using official library migration tools corrupts object type dictionaries.

Database Index Corruption in Multi-User Engineering

In projects where multiple automation engineers work simultaneously on a central server across the network:
* Abrupt Disconnections: Network latency drops or abrupt PC shutdowns corrupt the temporary project cache files (*.tmp, *.s7x).
* Orphaned Pointers: Internal relational pointers between the symbol table, the block directory (baustein.dbf), and the technological hierarchy lose synchronization.
* Read-Only File Flags: If project archives were unpacked from optical media or compressed archives that preserved Windows Read-Only attributes, database write transactions fail, manifesting as invalid object faults.

Method: Step-by-Step Resolution and Database Recovery

Follow this engineering recovery procedure to resolve the error:

Step 1: Verify Installed Optional Software Packages

  1. In SIMATIC Manager, select Help > About.
  2. Click Installed Software.
  3. Inspect the installed packages list:
    - Verify that CEMAT, APL, and all required library components are installed and match the exact version of the source project.
    - If an optional package is missing, install it from official installation media and reboot.

Step 2: Clear File Attributes and Local Cache

  1. Close SIMATIC Manager.
  2. In Windows Explorer, navigate to the multiproject root directory.
  3. Right-click the project folder and select Properties.
  4. Ensure the Read-Only attribute checkbox is completely cleared. Click Apply to all subfolders and files.

Step 3: Execute 'Save As with Reorganization (Slow)'

This crucial STEP 7 database maintenance utility purges fragmented records and reconstructs the internal object type dictionary:
1. Open SIMATIC Manager. Open the target project or multiproject.
2. Select File > Save As... from the menu.
3. In the dialog, check the box With Reorganization (Slow).
4. Specify a new project name or path and click OK.
5. Wait for the reorganization process to complete (this may require 15 to 45 minutes on large projects as the database engine rebuilds all cross-reference tables).
6. Open the newly reorganized project.

Step 4: Synchronize Master Data Library

  1. Open the Master Data Library within the multiproject.
  2. Right-click the block folder and select Options > Check Block Consistency.
  3. Re-attempt the copy operation. The block or CMT will paste without generating error dialogs.

Verification

To verify that object copying and library management are restored:

  1. In SIMATIC Manager, select the previously failing block or CMT.
  2. Copy and paste the object into the target CFC chart or library folder.
  3. Verify that the object pastes cleanly without error prompts.
  4. Open the pasted block properties in CFC. Verify that all I/O parameters, comments, and attributes (s7_m_c) display properly.
  5. Compile the target chart: verify that the compiler reports 0 Errors, 0 Warnings.

Limitations and Operational Precautions

  • Backup Before Reorganization: Always create a compressed ZIP archive of the project (File > Archive) before executing 'Save As with Reorganization'. If a database corruption is severe, the reorganization process can fail midway, leaving the project inaccessible.
  • Exclusive Access Required: Reorganization requires exclusive database locks. All other engineering workstations and runtime instances must be disconnected from the project during the procedure.
  • Do Not Edit Database Files Directly: Never attempt to repair project corruption by manually editing .dbf or .s7p files using external database editors.

Engineer FAQ

Why does 'Save As with Reorganization (Slow)' succeed when standard saving fails?
Standard saving only appends changes to the existing project database; it does not clear deleted records. The 'Slow' option rebuilds the relational database from scratch, removing fragmented pointers and repairing corrupted object indices.

Can missing Windows operating system language settings cause this error?
Yes. If a project was created on an operating system with specific regional language code pages (such as German or Chinese) and opened on a system with incompatible non-Unicode settings, character mapping fails and triggers object errors.

Does 'Invalid object type' indicate a damaged controller memory card?
No. This error is strictly an Engineering Station software and project database issue; it does not reflect PLC hardware or memory card defects.

Technical References

  • Siemens Industry Online Support Entry ID 109742323: SIMATIC Process Control System PCS 7 Engineering System Manual
  • SIMATIC PCS 7 Project Architecture and Database Administration (Document No. A5E00278782)
  • Siemens Industry Online Support Entry ID 109809264: Troubleshooting Project Corruption and Reorganization in STEP 7

Related Articles

Related Tags

  • https://industrialautomation.net/search?query=simatic-pcs7
  • https://industrialautomation.net/search?query=simatic-manager
  • https://industrialautomation.net/search?query=cemat
  • https://industrialautomation.net/search?query=database-recovery
20 respuestas