Resolving PROFINET Subnet and Hardware Export Errors in PCS 7 AdvES

In SIMATIC PCS 7 Advanced Engineering System (AdvES), encountering errors such as "Global subnet 'Profinet' not known" when attempting to derive a hardware configuration from an instrumentation list occurs because AdvES hardware mapping requires exact case-sensitive synchronization with NetPro subnet identifiers. While AdvES natively supports PROFIBUS DP architectures, configuring PROFINET IO stations requires that the PROFINET subnet is pre-configured in the STEP 7 base project with a name matching the AdvES subnet descriptor exactly. If the subnet name is missing, mismatched, or if PROFINET GSDML device definitions have not been imported into the AdvES Device Management library, the export wizard aborts.

AdvES Hardware Generation Mechanics for Fieldbuses

In digital plant engineering, tools like SIMATIC PCS 7 Advanced Engineering System (AdvES) automate hardware configuration by reading instrumentation tags, ordering numbers (MLFBs), and I/O channels from database tables and generating the complete STEP 7 Hardware Configuration (HW Config).

When AdvES generates a fieldbus topology, it must map each distributed I/O station (e.g., ET 200M, ET 200SP, or ET 200SP HA) to a specific communications master and physical subnet. While PROFIBUS DP subnets are established using standardized master system IDs (e.g., DP master system (1)), PROFINET networks require binding each IO Device to a named PROFINET IO System and an associated Industrial Ethernet subnet.

Root Cause of 'Global Subnet Not Known' During Export

When an engineer enters MLFBs in the AdvES PLS table view, assigns the subnet name as Profinet, and triggers the export wizard, the operation halts with contradictory errors:
* Entering Profinet: Error reports Global subnet 'Profinet' is not known.
* Leaving subnet blank: Export assistant complains that a subnet is required.

Configuration LayerRequired SettingDefect TriggerResolutionSTEP 7 NetPro Subnet NameMust match AdvES string exactly (e.g., PROFINET(1))Name mismatch or case difference (Profinet vs PROFINET)Align string names identicallyAdvES Device CatalogDevice MLFB registered in AdvES libraryMLFB typed manually without catalog importImport GSDML / device into AdvES Device ManagerSubnet Type AssignmentSet to Industrial Ethernet / PROFINETSubnet created as PROFIBUS DPRe-create subnet as Industrial EthernetIO Controller AssignmentCPU PN port or CP 443-1 assigned as IO ControllerPort configured only for general EthernetEnable PROFINET IO System in HW Config

The AdvES export parser does not create new PROFINET networks dynamically; it looks for an existing global subnet in the template project database matching the exact string provided.

Aligning Subnet Identifiers in STEP 7 NetPro and AdvES

To resolve the subnet binding conflict:

Inspect STEP 7 NetPro Subnet Name:
- Open the base project in SIMATIC Manager.
- Open NetPro.
- Locate the Industrial Ethernet subnet connected to the CPU's PROFINET interface (or CP 443-1).
- Double-click the subnet line to view properties. Note the exact case-sensitive name: e.g., PROFINET(1) or PN_Plant_Bus.
Assign Matching Subnet in AdvES:
- In AdvES, open the Hardware Assignment tab.
- In the Subnet field for the target devices, enter the exact string noted from NetPro (e.g., PROFINET(1)).
- Verify that the assigned CPU interface is configured as a PROFINET IO Controller.

Importing PROFINET GSDML Device Types into AdvES

If the export wizard complains that the device cannot be generated despite correct subnet naming:
1. In AdvES, navigate to Administration -> Device Management.
2. Click Import Device....
3. Select the PROFINET XML file (GSDML) or import the STEP 7 Hardware Catalog directly.
4. Verify that the target distributed I/O station (e.g., IM 155-6 PN) appears in the AdvES device tree with its supported terminal modules and I/O cards.

Verification

To verify that hardware configuration generation succeeds:
1. In AdvES, execute the Export Assistant to export the hardware configuration to STEP 7.
2. Confirm that the export finishes with status 0 Errors, 0 Warnings.
3. Open SIMATIC Manager and open HW Config for the target AS.
4. Verify that the PROFINET IO system contains the distributed I/O racks, that all I/O addresses are assigned according to the AdvES signal list, and that HW Config compiles without errors.

Limitations and Operational Precautions

AdvES V1.x/V2.x was originally developed for PROFIBUS DP; modern high-density PROFINET features (such as ET 200SP HA terminal blocks, redundant S2 PROFINET controllers, and Compact Field Units) are not fully supported in legacy AdvES. For advanced PROFINET architectures in PCS 7 V9.0 and higher, use SIMATIC PCS 7 Plant Automation Accelerator (PAA), which provides full native support for PROFINET topologies.

Engineer FAQ

Can AdvES automatically create a PROFINET subnet in NetPro?

No. The Industrial Ethernet / PROFINET subnet must be pre-created in the base STEP 7 project before running the AdvES hardware export.

Is subnet naming in AdvES case-sensitive?

Yes. Mismatches in letter case (e.g., writing Profinet instead of PROFINET) cause AdvES to report that the subnet is unknown.

Does AdvES support PROFINET system redundancy (S2)?

Full PROFINET S2 redundancy support requires SIMATIC PCS 7 Plant Automation Accelerator (PAA) rather than legacy AdvES.

Technical References

Related Tags

AdvES
PROFINET
Subnet Configuration
NetPro
Hardware Export

6 respuestas

Resolving PROFINET Subnet and Hardware Export Errors in PCS 7 AdvES