Integrating Third-Party IO-Link Masters and Transmitters via PROFINET into SIMATIC PCS 7

Integrating third-party IO-Link masters (such as IFM AL1100 series) and IO-Link transmitters via PROFINET into SIMATIC PCS 7 is supported via standard GSDML device description files, but the PCS 7 Driver Generator cannot automatically generate module diagnostic drivers for non-Siemens IO-Link hardware. To read pressure and temperature values into an S7-400 controller, engineers must map the IO-Link master's cyclic process data (PZD) input words in HW Config, extract and unpack measurement values using CFC data conversion blocks or SCL functions, and connect the scaled output directly to Advanced Process Library (APL) monitoring blocks (MonAnL). For full automatic driver generation, HART routing, and Maintenance Station integration, standard ET 200SP 4-20mA HART modules are recommended.

IO-Link Integration Architecture in SIMATIC PCS 7

IO-Link (IEC 61131-9) is an open, point-to-point digital communication protocol widely adopted in factory automation for smart sensors and actuators. In process automation with SIMATIC PCS 7 (such as V8.1 or V8.2 with CPU 414-3 PN/DP 6ES7414-3EM07-0AB0 or CPU 410-5H 6ES7410-5HX08-0AB0), process engineers occasionally seek to connect field sensors using IP67-rated decentralized IO-Link masters (such as IFM AL1100 / AL1102) connected over PROFINET IO.

The IO-Link master acts as a PROFINET IO Device, translating point-to-point serial communication from connected transmitters (pressure, temperature, flow) into standardized PROFINET cyclic I/O frames. Each IO-Link port is assigned a configured byte length (typically 2, 4, 8, or 16 bytes of input process data) representing the measurement value and digital sensor status bits.

PCS 7 Driver Generator Limitations with Third-Party Field Devices

The fundamental challenge of using third-party IO-Link masters in PCS 7 lies in the Driver Generator Wizard (Generate module drivers during CFC compilation):

No Automatic Driver Block Generation: The PCS 7 Driver Generator natively recognizes only Siemens decentralized peripherals (ET 200M, ET 200SP, ET 200iSP, ET 200pro) that utilize official Siemens driver libraries. For third-party GSDML devices, the wizard cannot instantiate MOD_1, Pcs7DiIn, or Pcs7AnIn diagnostic blocks.
Manual Process Value Extraction: Engineers cannot simply connect the raw hardware address (e.g., IW 512) to the PV_In input of an APL Pcs7AnIn channel driver block, because Pcs7AnIn expects a structured signal containing an interconnected diagnostic driver (MOD_1).
Loss of Automatic Quality Codes: Because no diagnostic driver exists, the signal lacks automatic Quality Code (ST = 16#80 Good, 16#00 Bad) generation upon bus loss unless manually implemented in user logic.

Comparison of IO-Link vs Standard 4-20mA HART in PCS 7

The following table compares third-party IO-Link integration with standard ET 200SP 4-20mA HART in PCS 7:

Engineering FeatureThird-Party PROFINET IO-Link (e.g. IFM)Siemens ET 200SP 4-20mA HART (6ES7134-6TD00-0CA1)Driver Wizard SupportUnsupported (treated as classic STEP 7 raw I/O)100% Fully Supported (auto-generates MOD_1, Pcs7AnIn)Signal Integrity & StatusRaw integer bytes; manual quality code handlingAutomatic NAMUR NE43 limit evaluation and IEEE quality codesPDM Device IntegrationNo HART routing through third-party masterFull HART routing and parameterization via SIMATIC PDMMaintenance Station (MS)Requires custom technological proxy blocksAutomatic asset management and diagnostic faceplatesEngineering EffortHigh (requires custom SCL/CFC decoding)Low (native drag-and-drop hardware configuration)Field CablingStandard unshielded 3-wire M12 cableStandard 2-wire shielded twisted pair

Step-by-Step Procedure to Integrate Third-Party IO-Link via PROFINET

Follow this procedure to successfully read third-party IO-Link sensor data into PCS 7:

Install GSDML File in HW Config:
- Download the official GSDML file for your IO-Link master (e.g. IFM AL1100) from the vendor's website.
- In HW Config, select Options -> Install GSD Files... and import the XML description.
Configure IO-Link Master on PROFINET IO Subnet:
- Drag the IO-Link master from the hardware catalog (PROFINET IO -> Additional Field Devices -> I/O) onto the PROFINET subnet.
- Assign device name, IP address, and modular submodules for each active IO-Link port (e.g., 2-byte input for Port 1 pressure transmitter, 4-byte input for Port 2).
- Note the assigned peripheral input addresses (e.g., PIW 512, PIW 514).
Decode and Unpack Process Data in CFC:
- In CFC, place a word-to-integer conversion block or custom SCL decoding block connected to the hardware input (PIW 512).
- If the vendor transmits the measurement as a 14-bit integer with 2 status bits, apply a bitmask (WORD_TO_INT and division by scaling factor, e.g., divide by 10.0 for 0.1°C resolution).
Connect to APL Monitoring Block (MonAnL):
- Bypass the channel block Pcs7AnIn and connect the scaled REAL value directly to input PV on MonAnL (FB1845).
- Configure PV_OpScale (e.g., 0 to 100 bar or 0 to 150 °C) and engineering unit on MonAnL.
- Build custom communication watchdog logic using GET_DIAG or device link monitoring to force PV_Li.ST = 16#00 (Bad) if the PROFINET master disconnects.

Verification

Verify sensor data reading and visualization in PCS 7:
1. In HW Config, switch to Online view and verify that the IO-Link master shows a green status with zero diagnostic bus errors.
2. Open the CFC chart online and monitor the decoded REAL output. Compare the CFC value against the local digital readout on the physical IFM transmitter.
3. Disconnect the M12 cable from the sensor. Confirm that the status bits trigger appropriate alarm handling in CFC.
4. Open the WinCC OS faceplate for MonAnL. Confirm that the process value, engineering unit, and limit alarms update accurately in real time.

Limitations and Operational Precautions

No PDM HART Parameterization: Third-party IO-Link masters connected to PCS 7 cannot route EDD parameterization from SIMATIC PDM. Sensor parameters (zero, span, damping) must be configured using vendor proprietary software (e.g., IFM moneo|configure or web server).
Byte Order (Endianness) Differences: Many third-party IO-Link sensors transmit process values in Little-Endian (Intel) format, whereas SIMATIC S7-400 CPUs operate in Big-Endian (Motorola) format. Bytes within the process word must be swapped using the CAW instruction or SCL conversion.
Compendium Part A Compliance: Integrating field devices without PCS 7 driver wizard support deviates from standard PCS 7 architecture documented in Compendium Part A. Document all custom scaling blocks thoroughly for maintenance staff.

Engineer FAQ

Can I use Pcs7AnIn with an IFM IO-Link master?

Not directly without manual workarounds. Pcs7AnIn requires an interconnected module driver (MOD_1) generated by the PCS 7 driver wizard. Because the wizard does not recognize third-party IO-Link masters, Pcs7AnIn will report bad signal quality (QBAD = 1) unless diagnostic inputs are artificially forced. It is cleaner to feed scaled values directly into MonAnL.

How do I know the process data structure of an IO-Link sensor?

The process data structure (bit assignments, integer scaling factor, and status bits) is documented in the sensor's official IODD (IO Device Description) manual provided by the sensor manufacturer.

Would it be better to use ET 200SP 4-20mA HART instead of IO-Link?

Yes, for process automation facilities standardizing on PCS 7. ET 200SP 4-20mA HART modules (6ES7134-6TD00-0CA1) provide 100% automated driver generation, full SIMATIC PDM calibration routing, and native Maintenance Station integration.