Resolving 'Go to I/O Module' Navigation Failures Between CFC and HW Config in SIMATIC PCS 7

In SIMATIC PCS 7 CFC, when selecting 'Go to I/O Module' on a channel driver block opens HW Config but fails to highlight the target module, the root cause is typically broken module driver cross-references or an unlinked hardware address. If CFC cannot resolve the address to a recognized card profile in the hardware tree, the navigation jump fails. To resolve this, ensure the channel driver address is selected from the Symbol Table, eliminate corrupted fieldbus/GSD device references in HW Config, and execute an Entire Program compilation with 'Generate module drivers' enabled.

Cross-Subsystem Navigation Mechanics - CFC to HW Config

In SIMATIC PCS 7, the engineering system provides seamless bi-directional cross-referencing between the graphical software logic (CFC) and the physical hardware rack layout (HW Config).

When an engineer right-clicks the input/output pin of a channel driver block (e.g. Pcs7AnIn, Pcs7DiIn, CH_AI) and selects Go to I/O Module:
1. CFC queries internal cross-reference databases (s7tgtopx.s7p).
2. It resolves the logical address (e.g. IW 512) to a physical rack slot and channel.
3. It launches STEP 7 HW Config, navigates to the specific station, highlights the subrack in blue, and outlines the physical module in dark grey.

Why the System Fails to Highlight the Target I/O Card

When HW Config opens but leaves the rack completely unselected with no highlighted module:
* Manual Address Entry: The address on the channel driver was manually typed into the block pin without selecting it from the Symbol Table (Symbols), resulting in missing internal database pointers.
* Skipped Module Driver Generation: If the charts were compiled with Generate module drivers unchecked, the compiler never bound the technological block to the hardware diagnostic blocks (MOD_D1, MOD_PND).
* Corrupted Fieldbus / PDM Asset Device: If an attached PROFIBUS PA or PROFINET device has an orphaned GSD configuration or broken PDM asset record, the hardware parser halts symbol resolution prematurely.

Resolving Corrupted GSD and PDM Field Device References

If a project database experiences corruption where field instruments cannot be deleted or resolved:

[STEP 7 HW Config -> Station Export/Import Recovery]
   │
   ├─► Open affected AS Station in HW Config
   ├─► Select: Station -> Export... (Save as ASCII text file: "Station_Clean.cfg")
   │
   ├─► In HW Config: Delete the corrupted fieldbus slave (or re-initialize rack)
   │
   ├─► Select: Station -> Import... -> Load "Station_Clean.cfg"
   │     • Rebuilds the internal STEP 7 hardware object dictionary
   │     • Strips orphaned COM/ActiveX pointers from deleted PDM devices
   │
   └─► Save and Compile HW Config (0 Errors)

Module Driver Recompilation and Address Validation

The table below outlines the necessary conditions for successful 'Go to I/O' navigation:

Engineering RequirementConfiguration StepVerification CheckSymbolic InterconnectionConnect driver block pin via Symbol BrowserPin displays symbolic name (e.g. PT_101) in quotation marks.Module Driver GenerationCFC Compile -> Check Generate module driversCompiler creates @System charts without warnings.Hardware Catalog SupportVerified module profile in HW ConfigStation opens cleanly without Error (1230:2016).Symbol Table IntegritySIMATIC Manager -> Options -> Reference DataNo duplicate addresses or unassigned I/O ranges.

Verification

To confirm that 'Go to I/O Module' navigation functions properly:
1. Open the CFC chart containing the channel driver block.
2. Right-click the interconnected I/O pin (e.g. PV_In on Pcs7AnIn) and select Go to I/O Module.
3. Verify that STEP 7 HW Config opens automatically.
4. Confirm that the distributed station (e.g. ET 200M rack) is selected in blue, and the specific analog input module in the rack is highlighted with a distinct background box.
5. In CFC, verify that the module driver status word displays live health diagnostics online.

Limitations and Operational Precautions

Never manually type raw memory addresses (e.g. IW 256) onto channel driver blocks if the address does not exist in the configured HW Config rack. Bypassing the hardware configuration causes module driver generation to fail, suppresses hardware diagnostics, and breaks cross-referencing tools. Always allocate addresses via HW Config and select them through the Symbol Table.

Engineer FAQ

Why does 'Go to I/O Module' work on analog inputs but fail on digital inputs?

Ensure that digital input channel drivers are connected to symbolic bit addresses (e.g. I 0.0) defined in HW Config, and that module drivers have been recompiled since the address was assigned.

What does it mean if CFC reports 'Module driver error coming from PDM ASSET'?

It indicates an Electronic Device Description (EDD) or GSD profile mismatch for a smart field instrument. Re-assign the correct GSD in HW Config or re-import the device in SIMATIC PDM.

Can 'Go to I/O Module' navigate to third-party PROFINET devices?

Yes, provided the third-party device is integrated using a certified GSDML file and connected via standard PCS 7 channel drivers.

Does 'Save With Reorganization' fix broken cross-references?

Yes. Executing File -> Save As... -> With reorganization (slow) cleans the internal database indices and can resolve stubborn cross-reference navigation bugs.