Why PCS 7 V9.0 SP3 Does Not Generate Drivers for ET 200SP IM 155-6AU01
PCS 7 V9.0 SP3 UC03 did not generate module drivers for the reported ET 200SP station because 6ES7155-6AU01-0CN0 appeared only in the Standard catalog profile, not the PCS7_V90 profile. Siemens' V9.0 SP3 Released Modules list marks whether each module supports the module wizard (W). Check the exact IM and every I/O module against that list; a GSD import alone does not establish driver-wizard support.
Table of Contents
- Why the module-driver wizard skips this station
- Check the release-specific wizard support
- Choose a supported engineering path
- Do not substitute a similar IM without checking hardware
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Why the module-driver wizard skips this station
The reported PCS 7 V9.0 SP3 UC03 project uses ET 200SP interface module 6ES7155-6AU01-0CN0. The engineer found it in the Standard hardware profile but not in the PCS7_V90 profile; the other station with 6ES7155-6AU00-0CN0 generated drivers. GSD availability in the Standard catalog does not, by itself, establish PCS 7 module-driver wizard support.
Check the release-specific wizard support
Siemens' PCS 7 V9.0 SP3 Released Modules List Manual defines a W property for modules supported by the module wizard. Check the exact interface-module article number and every I/O module against the list and the installed hardware catalog profile for the target PCS 7 release. Do not conclude that 6AU01 is equivalent to 6AU00 because the article numbers are similar or the device appears in a generic STEP 7 catalog.
Choose a supported engineering path
If the exact interface and all attached modules are supported by the PCS 7 profile and marked for module-wizard support, configure those exact parts using the PCS 7 profile and regenerate the drivers. If not, use a documented released configuration compatible with the physical hardware, or leave wizard-generated driver connections out and separately engineer the I/O status/diagnostics according to Siemens and device documentation. The thread's alternative is therefore conditional; it does not establish a safe replacement module or a validated manual status implementation.
Do not substitute a similar IM without checking hardware
Before replacing the configured interface module, verify its compatibility with the actual ET 200SP station, firmware, BusAdapters, and I/O modules. Hardware catalog substitutions can change supported modules, diagnostics, and configuration behavior. A driver-generation workaround does not justify changing the physical station design.
Verification
After using an exact released configuration, compile the AS and confirm the expected channel-driver and module-diagnostic connections are generated for the specific I/O. Verify module status and signal behavior on the actual intended hardware or an approved test setup. A warning-free compile does not prove that every physical channel is wired, scaled, or diagnosed correctly.
Limitations and Operational Precautions
The ticket does not enumerate the ET 200SP I/O module article numbers, firmware/GSD revisions, or the exact module-driver warning. The Siemens V9.0 SP3 released-module list applies to that release; the installed PCS 7 V9.0 SP3 UC03 profile and complete physical station still need checking. No manual status-word values or direct-I/O workaround were verified for this station.
Engineer FAQ
Does finding a GSD under Standard mean PCS 7 will generate its module drivers? No. The ticket and release-list distinction show generic catalog visibility and PCS 7 module-wizard support are separate.
What does the Released Modules W property mean? Siemens defines W as “Module wizard is supported.”
Can I substitute IM 155-6AU00 for IM 155-6AU01? Only after confirming exact hardware and I/O compatibility for the physical station and release; similar catalog names are insufficient.
What if the exact IM is not wizard-supported? Use a documented released hardware configuration or engineer without generated drivers only with a validated device-specific diagnostic design.
Does successful module-driver generation prove correct operation? No. Verify hardware status, channel values, ranges, quality, and diagnostic response.
Technical References
- PCS 7 Released Modules (V9.0 SP3) List Manual, 07/2021, A5E41674051-AE; Appendix A defines
Was “Module wizard is supported.” - PCS 7 Readme V9.0 including SP1, section 3.3.2 directs users to the released-module manual for approved AS hardware (the ticket's UC03 build is later; use its applicable release documentation).