Explainer
Why a PROFINET IO-device gateway cannot be a controller
Short answer
No. A PROFINET IO device cannot open the cyclic exchange with the Wago 750-8215, because every cyclic exchange is established by an IO controller. Use a gateway whose PROFINET side is an IO controller that imports the machine's GSDML, and the machine program stays unchanged.
On this page
No. A gateway whose PROFINET side is an IO device cannot start anything with the Wago 750-8215 on this machine, because PROFINET gives one role only — the IO controller — the right to establish a cyclic exchange, and an IO device never holds it. Two IO devices on one cable simply wait. What works instead is a component whose PROFINET side runs the IO controller role and imports the machine's GSDML: your Modbus TCP client PLC polls that component, it opens the exchange with the machine, and the third-party program stays closed. Below are the role model, the arithmetic that settles the question, and the decision for each topology you could pick.
The three roles PROFINET allows #
The PROFINET system model — specified in the IEC 61158 and IEC 61784 fieldbus standards — defines three device classes, and only one of them controls anything:
| Role | What it does | Can it open a cyclic exchange? |
|---|---|---|
| IO controller | Executes the automation program, parametrizes IO devices from their GSDML files, reads inputs and writes outputs cyclically | Yes |
| IO device | Distributed field device; provider of input data and consumer of output data, attached to one or more IO controllers | No |
| IO supervisor | Reads diagnostics and sets parameters without taking part in the control loop | No |
A PLC can sit in the device class on purpose: the machine builder configured the Wago 750-8215 as an IO device — the pattern sometimes called an I-Device or smart device — and hands you its GSDML plus a read/write data list, exactly as a drive supplier would. From your side the work is the same as when you control a PROFINET servo drive with cyclic telegram data: import a device description, configure the modules, own the exchange.
Why two IO devices never exchange data #
Cyclic PROFINET data moves inside an application relation, and that relation is always established by the IO controller: the controller parametrizes the device from the contents of its own configuration, then the cyclic frames flow in both directions. An IO device may answer that sequence and nothing more. It never originates a connect, and the model has no device-to-device relation.
Count the roles in the topology that was proposed. The Modbus TCP client PLC has no PROFINET role at all, because its client duty lives on the Modbus side. The gateway's PROFINET interface is an IO device. The machine is an IO device. IO controllers present: 0. Application relations possible: 0. Bytes of cyclic data exchanged: 0.
The gateway asked about here could be made to work only by inverting the design: the Wago project would import the gateway's GSDML, and the third-party program would be extended to control the gateway as one more IO device. That is precisely the change the integration must avoid, so the device-side gateway is rejected on architecture alone.
Where the GSDML file belongs #
A GSDML file describes an IO device to an IO controller, so it belongs on whichever side holds the controller role. In the working design you import the builder's GSDML into the gateway's PROFINET controller configuration, set the device name and IP address the builder documented, and select modules that match the documented read/write list; the machine project is never opened. In the rejected design the same file travels the other way, into the machine, together with program changes. Your condition — no GSDML added to the Wago — is therefore settled by the role choice, not by the file.
Device suppliers generate these descriptions routinely on their side; a GSDML export for a PROFINET IO-device module is the mirror image of the import you perform.
Split the builder's data list the way the model does: cyclic I/O, the bytes that arrive every cycle, and acyclic parameter access, which travels as record data in separate services, as when reading IO-Link ISDU parameters over PROFINET acyclic record data. A gateway can carry the first and be unable to do the second, so check both if the machine's parameters matter to you.
Sizing the Modbus side from the data list #
The gateway's Modbus map has to hold the cyclic bytes, so size it from the builder's list before choosing hardware. Worked example with illustrative numbers: the list specifies 32 bytes of input data and 16 bytes of output data. Total cyclic payload = 32 + 16 = 48 bytes. One Modbus holding register carries 2 bytes, so the input map needs 32 / 2 = 16 registers and the output map 16 / 2 = 8 registers, or 24 registers in total, before any status or diagnostic registers the gateway itself adds.
Odd byte counts round up: 33 bytes of input data would occupy 33 / 2 = 16.5, so 17 registers with one byte unused. Every byte added to the machine's list costs half a register, and a 64-byte input map alone would need 32. The procurement rule is concrete: a candidate gateway in the controller role must let you map at least the documented register count — 24 in this example — with the byte order and word alignment of the builder's list, and must document how it places cyclic I/O into Modbus registers at all.
Three topologies that do work #
First, ask the machine builder to enable one of the other protocols the hardware carries. The Wago 750-8215 hardware also exposes EtherNet/IP and Modbus TCP, but on this machine the builder left those services unconfigured, and a port without a configured service is not a data path. If the builder enables Modbus TCP and publishes a register map, your client PLC reads the machine directly and the gateway disappears from the design — the simplest integration because it has the fewest parts.
Second, keep looking for a gateway that states IO controller for its PROFINET side and GSDML import for its configuration tool; the field on the Modbus TCP side is narrower than for device-side gateways, so verify those two phrases on the datasheet before anything else. The requirement is identical when the plant controller speaks EtherNet/IP instead of Modbus TCP, as in connecting PROFINET IO to a CompactLogix through a gateway: the PROFINET side must hold the controller role, whatever sits behind it.
Third, when no suitable controller-role gateway exists, put the controller role in software: a CODESYS runtime or the PLC vendor's soft controller, running on an industrial mini PC mounted beside the PLCs in the cabinet. It imports the machine's GSDML as IO controller, exchanges the cyclic bytes with the Wago, and serves them to your Modbus TCP client — the same architecture as editing a CODESYS Raspberry Pi PROFINET controller project, on hardware meant to live in the cabinet.
The decision for each case #
- IO-device-only gateway, as asked: reject. It cannot establish the relation, and making it work would force a GSDML import and program changes inside the machine.
- Gateway with PROFINET IO controller role and GSDML import: accept. Configure the documented device name and IP, map the documented bytes — 24 registers in the worked example — and validate every read and write against the builder's list before the machine acts on any output.
- Builder enables Modbus TCP or EtherNet/IP with a published map: accept first. It deletes the gateway and the role question with it.
- Soft controller on a cabinet PC: accept when the gateway search fails. Same GSDML import, same validation, one more component to power and back up.
One limit applies to every case: E-stops and safety interlocks stay in the machine's own safety chain and never travel through a converted protocol link.
Questions asked
Can one PROFINET IO device open cyclic exchange with another IO device?
No. The PROFINET model gives only the IO controller the right to establish the application relation that carries cyclic data; an IO device answers connects but never sends one. A device can serve more than one controller at the same time through separate relations, called shared-device operation, but every one of those relations still has a controller on one end.
Which GSDML revision should I import for the machine?
The one in the file the machine builder supplied. A GSDML file name carries its revision, and the builder configured and tested the machine against that revision. Downloading a newer revision of the same file can change the module catalog and submodule layout the builder's data list was written against, so import the supplied file and keep it with the machine documentation.
The gateway has a PROFINET port. Is that not enough?
No. The connector says nothing about role; the datasheet does. Look for the words IO controller for the PROFINET side and GSDML import in the configuration tool. Some interfaces let you select controller or device mode in configuration; if the sheet names only IO device, the role is fixed and the gateway cannot start the exchange this application needs.
Can the spare Ethernet ports on the machine replace the gateway?
Only after the machine builder enables and documents them. The hardware carries EtherNet/IP and Modbus TCP, but an unconfigured service moves no data, and you cannot open the third-party program to turn one on yourself. If the builder publishes a Modbus TCP register map, your client PLC reads the machine directly and the gateway disappears from the design.
What if I also need parameters, not just the cyclic read and write data?
Parameter access is acyclic: it travels as record data in separate read and write services, not in the cyclic image. The controller side must support record-data reads and writes, and the machine builder must document which parameter indices are exposed. The cyclic sizing arithmetic covers only the byte counts in the data list, nothing more.