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

Troubleshoot an Empty Hardware Catalog in PAA 3.1.1

Troubleshoot an Empty Hardware Catalog in PAA 3.1.1

An empty ET hardware selection in PAA 3.1.1 should be investigated as a software-and-database-content problem before changing the customized database. A COMOS 10.2.2 database opening in COMOS 10.4.0 does not prove that it contains the content required by the PAA hardware configurator. Siemens documents explicit software and database requirements for PAA 3.1, but those requirements do not establish the exact supported combination or repair for PAA 3.1.1. Use an isolated baseline comparison before selecting an update path.

Table of Contents

Separate Software Versions from Database Content

The affected configuration uses PAA 3.1.1, COMOS 10.4.0 and a customized database originating from 10.2.2. The hardware configurator opens, but its ET station selections are empty. Other working functions and an apparently correct base-object hierarchy do not establish that the required catalog content and its dependencies are present.

The verified PAA 3.1 readme specifies COMOS 10.3.3.1 plus patch 10.3.3.1.15, and either iDB V10.3.3 plus PAA Content Layer V3.1 or PAA DB V3.1. This demonstrates that database content is an explicit requirement; it does not establish the supported combination for PAA 3.1.1 and COMOS 10.4.0. Siemens readme, chapter 4

Isolate a Content Problem Without Changing Production

The following is a project-specific diagnostic comparison, not a confirmed repair.

  1. Preserve the customized database and associated external files in a recoverable backup.
  2. Record the installed PAA and COMOS builds, the database release and the PAA content-layer release separately. A COMOS executable version is not the database-content version.
  3. In a separate test environment, establish a manufacturer-supported software/database combination for PAA 3.1.1. Confirm that combination before importing or converting customer data.
  4. Open the hardware configurator in the supported baseline and inspect the same ET family selections.
  5. Compare that result with a copy of the customized database. Record which selections are absent, which base objects or dependencies differ, and whether customization overrides standard content.

A populated baseline and an empty customized database would narrow the problem to a database/content difference. That observation alone would not identify the exact missing object or prove that copying an individual object is safe.

Documented PAA 3.1 Update-Package Import

For PAA 3.1, chapter 5.1 documents the following package-import stage. Apply it only to an isolated copy after confirming that the update package and version path are appropriate; it is not a verified 10.2.2-to-3.1.1 migration procedure.

  1. Open the database as an administrator with the matching PAA iDB ZIP available.
  2. Select Administrator > System > Database update....
  3. Browse in New database service pack and select the package. The archive must contain DatabaseReleaseInformation.xml, and its version must be higher than the displayed database service-pack version.
  4. Select Import, then acknowledge completion.

The readme distinguishes importing update data from applying it to customer projects. Import stages data in selection layers; it is not the complete content-selection and project-update workflow. Do not stop at an import success message and assume the ET catalog has been repaired. Siemens readme, chapter 5.1

Verification

For the test copy, record the exact ET station family and module choices visible after the comparison or approved content update. Confirm that a representative station can be configured with the intended component identities and that existing custom engineering objects retain their intended behavior.

Keep the before/after database and content versions with the test results. A database that opens successfully, an imported package, or a correct-looking hierarchy is insufficient evidence of full configurator operation. The exact missing-content cause in the stated PAA 3.1.1 configuration remains unresolved.

Limitations and Operational Precautions

The opened readme covers PAA 3.1, not PAA 3.1.1. Its requirements must not be used to declare COMOS 10.4.0 incompatible without applicable evidence. No manufacturer-supported repair avoiding all database-content changes was established.

Siemens warns that customized base objects can be lost during database updates and recommends keeping such changes in a separate working layer. Preserve customizations and validate any proposed update on a copy before production use. The PAA 3.1 readme also says that its GSDML importer is not a remedy for missing standard hardware such as ET 200SP; importing arbitrary device files is therefore not an established fix for this symptom.

Engineer FAQ

Does successful database opening prove that the PAA hardware content is compatible?
No. Opening the database and supplying the configurator's required content are separate acceptance checks.

Is a complete migration the only proven solution?
No exact repair is proven for the stated configuration. A controlled baseline comparison should first identify what is actually missing.

Technical References

Related Articles

Related Tags

20 respuestas