Integrating Third-Party GE Fanuc RSTi-EP PROFINET IO with CPU 410-5H

Integrating third-party GE Fanuc (Emerson) RSTi-EP remote I/O with a SIMATIC PCS 7 CPU 410-5H over PROFINET IO is fully supported via standardized GSDML device description files. However, engineers must account for two critical architectural constraints: first, third-party PROFINET devices typically support only S1 single interface associations (not S2 system redundancy), meaning they cannot connect redundantly to both controllers in an AS 410-5H pair; second, PCS 7 automatic module driver generation does not support third-party hardware. Field signals must be processed using elementary channel drivers (CH_AI, CH_DI) with driver generation bypassed or mapped directly to peripheral addresses.

PROFINET IO Integration Architecture: Siemens AS 410-5H and Third-Party I/O

The SIMATIC PCS 7 AS 410-5H controller provides integrated high-performance PROFINET IO interfaces compliant with open IEC 61158 / IEC 61784 fieldbus standards. Because PROFINET is vendor-agnostic, third-party remote I/O platforms—such as the GE Fanuc (Emerson Automation) RSTi-EP modular distributed I/O family—can be integrated directly onto the automation network without requiring proprietary hardware gateways.

Device profiles, module parameters, channel diagnostics, and input/output byte structures are defined via the manufacturer-supplied GSDML (General Station Description Markup Language) XML file. Once installed in STEP 7 HW Config, the RSTi-EP head station and its digital/analog I/O slices are parameterized identically to native field devices.

System Redundancy Constraints: S2 Redundancy vs S1 Single Interface

When integrating third-party I/O into redundant AS 410-5H systems, a vital architectural distinction governs network topology:
1. PROFINET S2 System Redundancy: A PROFINET device establishes two concurrent Application Relations (AR)—one primary AR to the active CPU and one backup AR to the standby CPU. Siemens ET 200SP HA and ET 200M support S2 natively, ensuring bumpless failover.
2. PROFINET S1 Single Device Association: Standard commercial remote I/O systems, including GE RSTi-EP, typically support only S1 associations. An S1 device can only communicate with a single controller.

In a redundant AS 410-5H plant bus ring, an S1 device must be assigned to either CPU 0 or CPU 1. If the master controller fails or is switched over, communication to the S1 device is interrupted. To achieve redundancy with S1 devices, plants must deploy an intermediate redundancy gateway or media converter supporting S2 to S1 translation.

Comparison of I/O Engineering Strategies in SIMATIC PCS 7

The table below contrasts engineering approaches for handling third-party PROFINET I/O in SIMATIC PCS 7:

Engineering MethodCFC Driver BlockModule Driver GenerationPros and LimitationsStandard Channel Drivers (CH_AI / CH_DI)CH_AI, CH_DI from Classic LibraryBypassed (EN_R_I = FALSE)Recommended: Normalizes raw values into process signals; manual status byte management.Direct Peripheral AddressingCustom SCL / Elementary logicNoneLow memory overhead; requires manual scaling, filtering, and wire-break logic.Native APL Drivers (Pcs7AnIn / Pcs7DiIn)Pcs7AnIn, Pcs7DiInUnsupportedFails: @ diagnostic generator aborts because hardware ID is unrecognized.Third-Party PROFINET Proxy / S2 BridgeStandard APL or vendor blockVendor-specificEnables dual controller connections for non-redundant S1 hardware.

Step-by-Step HW Config and CFC Engineering Procedure

Install Manufacturer GSDML File: Obtain the latest GSDML file from GE Fanuc / Emerson for the RSTi-EP network adapter (e.g., GSDML-V2.3-GE-RSTi-EP-*.xml). In STEP 7 HW Config, select Options -> Install GSD File... and browse to the extracted XML.
Insert Device in Hardware Configuration:
- Expand the PROFINET IO catalog under PROFINET IO -> Additional Field Devices -> I/O -> GE RSTi-EP.
- Drag the head station onto the CPU 410-5H PROFINET subnet.
- Populate the rack with the required digital and analog I/O slices, noting assigned I/O address ranges (e.g., PIW 512, PQW 512).
Configure PROFINET Device Name and IP: Assign a unique PROFINET Device Name and IP address. Use PLC -> Ethernet -> Assign Device Name to flash the name to the physical RSTi-EP adapter.
Configure CFC Signal Processing:
- In CFC, instantiate CH_AI for analog inputs or CH_DI for digital inputs.
- Connect the peripheral address directly to parameter VALUE (e.g., PIW 512).
- Set parameter MODE = 16#80000203 (for 4-20 mA) to provide a valid good-quality status byte.
- Connect the output of CH_AI to downstream APL blocks (MonAnL, PIDConL).
Compile and Download: In CFC, select Compile -> Changes Only. Ensure that compilation proceeds cleanly and download changes to the CPU in RUN mode.

Verification

Verify integration through the following steps:
1. Inspect the physical GE RSTi-EP network adapter: confirm that the PWR, RUN, and BF (Bus Fault) LEDs indicate healthy PROFINET cyclic exchange (solid green RUN, dark BF).
2. In STEP 7 HW Config, go online: verify that the RSTi-EP station and all configured I/O slices report status 'Module available and OK'.
3. In CFC test mode, inject an analog current signal into the field terminal: confirm that CH_AI.V tracks the field milliamp value accurately with status 16#80.

Limitations and Operational Precautions

Do not attempt to enable automatic module driver generation on third-party GSDML racks. The PCS 7 driver generator (Generate module drivers) only recognizes Siemens hardware families (ET 200M, ET 200SP HA, ET 200iSP); running driver generation against third-party devices generates compilation warnings and leaves channel drivers disconnected. Always configure transmission cycle times (send clock >= 2.0 ms) to avoid overloading third-party communication processors.