IMDHMIControls LibraryShop main store

How-to

Route an IO-Link master to a ctrlX CORE over EtherCAT

PLC programming Published 7 min read

Short answer

Install the AL1930 ESI in ctrlX I/O Engineering, set channel one to the sensor's documented bytes (4 for a TS2289, 2 for a TP3231), deactivate unused slots, and download until the master reports OP. Cyclic TxPDO bytes feed the PLC, CXA_EthercatMaster blocks read vendor and product ID over AoE with the master NetID, and EoE routing for ifm Moneo or LR clients depends on the master firmware.

On this page
  1. Separate the three data paths first
  2. Install the AL1930 ESI and scan the slave
  3. Set each channel to the sensor's documented bytes
  4. Reach OP before the PLC reads anything
  5. Joining the TP3231's two cyclic bytes into one word
  6. Map the cyclic bytes in the PLC project
  7. Read vendor and product ID over AoE
  8. Route ifm Moneo or LR traffic with EoE
  9. Questions asked

An ifm AL1930 IO-Link master is an ordinary EtherCAT slave to a ctrlX CORE once its ESI is installed. Install that ESI in ctrlX I/O Engineering, set channel one to the sensor's documented input length (4 bytes for a TS2289 temperature sensor, 2 bytes for a TP3231 signal converter), deactivate the unused slots, and download the fieldbus configuration until master and slave report OP. The PLC then reads live values from the cyclic TxPDO bytes, and CXA_EthercatMaster function blocks read the vendor and product ID acyclically over AoE with the master's NetID. Routing an ifm Moneo or LR device through the controller is a third path, EoE, decided by the master's firmware. The job needs the Rexroth PLC app and Rexroth EtherCAT Master app licensed on the ctrlX CORE, with ctrlX I/O Engineering and ctrlX PLC Engineering from ctrlX WORKS on the engineering side.

Separate the three data paths first #

Trace each request from its source to its destination before touching the engineering tool, because the three paths are enabled separately and success on one proves nothing about the others.

  • Cyclic process data: IO-Link sensor to AL1930, EtherCAT process data to the ctrlX CORE, then PLC variables. Live values travel here.
  • Acyclic reads: PLC program through CXA_EthercatMaster function blocks over ADS over EtherCAT (AoE) to the master. Identification such as vendor and product ID travels here.
  • Routed Ethernet: an ifm Moneo or LR client through the ctrlX CORE acting as router, over EtherCAT over Ethernet (EoE). The master firmware decides whether this path exists.

All three ride the same cable and the same master object you create to interface an EFC5610 drive with a ctrlX CORE over EtherCAT, but each has its own enabling condition.

Install the AL1930 ESI and scan the slave #

  1. Open the ctrlX CORE web engineering from the Windows network folder, from ctrlX WORKS, or by entering the controller IP in a browser, and log in.
  2. From the home bar, add a new EtherCAT Master configuration, select port XF50, and name it; the application example uses "ethercatmaster".
  3. Open ctrlX I/O Engineering from its link, right-click the master, and scan for new devices.
  4. Expect the AL1930 to be found but flagged unknown: the scan located the slave, and without its ESI in the device repository it cannot be inserted into the fieldbus configuration.
  5. Download the ESI from the IO-Link master supplier's download area; ifm lists the AL1930 firmware and ESI together, with version 3.1.99 dated 10/2025 in the current listing. Open the device repository from the Tools menu and install the ESI.
  6. Close the repository, scan again, use "insert all newly scanned devices", then apply and OK.

An installed ESI makes the device description available to engineering; it configures no IO-Link channel and proves nothing about the bus. If the inserted project shows bit-level objects where you expected byte mapping, read why ctrlX I/O Engineering shows bits instead of byte mapping nodes before reinstalling anything.

Set each channel to the sensor's documented bytes #

ctrlX I/O Engineering does not read IODD files. The ctrlX environment takes any IO-Link master that meets the EtherCAT Modular Device Profile specification ETG.5001 and provides a suitable ESI, and channel setup happens through MDP objects rather than through an IO-Link device description:

  1. Activate channel one by selecting its process-data size from the sensor data sheet: 4 input bytes for the TS2289 temperature sensor, 2 bytes for the TP3231 signal converter. Those two devices are alternatives on channel one, not one combined definition.
  2. Set every unused channel to "Deactivate Slot", as the application example does.
  3. If the selection offers no exact match for the documented length, choose the next larger size and validate the resulting layout against the device data sheet.
  4. Download the fieldbus configuration.

Reach OP before the PLC reads anything #

After the download, click the EtherCAT bar and confirm that the master and the AL1930 both report OP. The ctrlX CORE Data Layer shows the downloaded fieldbus configuration as a cross-check that the download landed.

Below OP, do not interpret process bytes: a TxPDO value with the bus not operational has no proven source. Work the faults in gate order — physical link and port, then the ESI, then the channel lengths — because each step blocks the next.

Joining the TP3231's two cyclic bytes into one word #

The inputs:

  • TP3231 cyclic process data: 2 bytes, from the converter's data sheet as used in the application example.
  • Channel-one entries selected in the PLC realtime data: TxPDO.input_byte_0 and TxPDO.input_byte_1.
  • Global variables: ByInputByte0 and ByInputByte1 of type BYTE, PDV1 of type WORD, Temperature of type REAL.
  • Test values: ByInputByte0 = 52 and ByInputByte1 = 18, written in debug for this check; they are illustrative inputs, not a measurement.

The rule: the converter's 16-bit process value is the two bytes joined as low byte plus 256 times the high byte, with the data sheet fixing which byte is high; this join assumes the high byte arrives in ByInputByte1.

The arithmetic:

PDV1 = 52 + 256 * 18 = 52 + 4608 = 4660

That is the bit pattern 0x1234 spread across the two bytes. In structured text the join is one line of illustrative code using the documented variable names:

PDV1 := SHL(TO_WORD(ByInputByte1), 8) OR TO_WORD(ByInputByte0);

The test that proves it: write 52 and 18 to the two bytes in debug and read PDV1 = 4660 in the Data Layer viewer.

The decision: while the channel's documented length is 2 bytes, map exactly those two entries and stop at one word, converting to engineering units only with the converter's documented scaling. The TS2289 on the same channel is a different case: 4 input bytes, four entries, evaluated into the REAL variable Temperature. Never apply this 2-byte join to the 4-byte sensor.

Map the cyclic bytes in the PLC project #

  1. From the home bar, open "Configure PLC applications" and start ctrlX PLC Engineering.
  2. Create a new standard project for the real ctrlX CORE in structured text.
  3. Right-click DataLayer_Realtime, choose Edit, then "Online from ctrlX Core"; add the fieldbus realtime data, add the AL1930, add IO-Link channel one, tick TxPDO.input_byte_0 and TxPDO.input_byte_1, and apply.
  4. Add a symbol configuration and a global variable list; declare bAcylicExecute as BOOL, ByInputByte0 and ByInputByte1 as BYTE, PDV1 as WORD, Temperature as REAL, and strVendor and strProductID for the acyclic results.
  5. Publish the variables either by building and ticking them in the symbol configuration, or with a pragma on the global variable list.
  6. Log in to the controller, download, and start the application.

The login shows a security warning because the communication certificate is self-signed; that is expected here, but confirm the target is the intended controller before accepting it. Communication settings are filled in automatically by default. Set bAcylicExecute — the name carries one "c" after the A — with CTRL + F7 or "Write Values" in the Debug menu, and watch the published variables in the Data Layer viewer, refreshing the view when values look static.

Read vendor and product ID over AoE #

  1. In ctrlX I/O Engineering, double-click the AL1930 to open its settings and activate the expert settings.
  2. Open the AoE tab; in this configuration AoE is already enabled when you open it. Save the I/O project, download it, accept the wizard, and record the NetID shown, because the PLC acyclic reads need it.
  3. In PLC Engineering, open the library manager and add the CXA_EthercatMaster library.
  4. Insert the read function block with the input assistant, tick "insert with arguments" to see every IO, and start it by setting bAcylicExecute; strVendor and strProductID then carry the converter's identification.

AoE is acyclic ADS over EtherCAT; it carries neither cyclic values nor routed Ethernet. Step beyond identification to sensor parameter access and the same dependency appears on every fieldbus: IO-Link ISDU access requires a supported acyclic path. The equivalent procedure on PROFINET is reading IO-Link ISDU parameters over PROFINET acyclic record data.

Route ifm Moneo or LR traffic with EoE #

The ctrlX CORE works as a router to an ifm Moneo or LR device with the ifm firmware that supports EoE, and that firmware condition is the whole decision. EoE carries Ethernet communication through the EtherCAT network and is configured separately from everything above.

Check the installed AL1930 firmware against ifm's release information before you promise a client this path, because working cyclic data and a working AoE read say nothing about EoE. The order for the whole job: ESI, channel bytes, OP, cyclic mapping, AoE NetID, EoE last.

Questions asked

Why does the AL1930 appear as unknown after the EtherCAT scan?

The scan found the slave, but ctrlX I/O Engineering cannot insert any device whose ESI description is missing from its device repository. Download the ESI from the master supplier, install it from the Tools menu, and scan again. An installed ESI only makes the device description available; it configures no IO-Link channel and does not prove the bus is running.

Can I use an IO-Link master from another vendor with a ctrlX CORE?

Yes, when the master meets the EtherCAT Modular Device Profile specification ETG.5001 and provides a suitable ESI file. ctrlX I/O Engineering then configures it through MDP mechanisms, and IO-Link Device Description files, IODD, play no part in that workflow, so every channel size comes from the individual sensor data sheet.

The exact process-data size is not offered in the channel selection. What do I pick?

Choose the next larger size offered for the channel, then validate the resulting byte layout against the device data sheet before the PLC interprets anything. The bytes beyond the documented length are slot padding, and the PLC must not treat them as signal data when it scales the value.

Where does the NetID for the acyclic reads come from?

It is shown in the AL1930's AoE tab in ctrlX I/O Engineering after you activate the expert settings, and you record it after saving and downloading the I/O project. If you recreate the EtherCAT master configuration, read the NetID again rather than reusing the old value, and if the AoE tab shows AoE disabled in a different configuration, enable it before the download or the acyclic reads will fail even with a correct NetID.

Can the ctrlX CORE configure the sensor's parameters as a router?

Yes, for routed clients: an ifm Moneo or LR device can reach the controller's Ethernet side while its traffic rides the EtherCAT network through EoE, but only when the installed ifm firmware on the master supports it. Check that firmware against ifm's release information before promising the path, because working cyclic process data and a working AoE read prove nothing about EoE; it is a separate path with its own configuration.

Keep reading

  • Troubleshooting

    Reading IO-Link ISDU parameters over PROFINET acyclic record data

    If cyclic IO-Link process data exchanges normally, leave out the connect section of IOL_CALL and address the identification and ISDU calls with the hardware ID of the proxy submodule for the target port, read straight from the PROFINET device configuration. A valid connect result such as 8 proves only that a lookup succeeded, not that it selected your port's submodule.

    PLC programming

  • Troubleshooting

    Why MELSECNET II data reads zeros after adding a Modbus card

    The zeros are not a network fault. The QJ71MB91 occupies 32 I/O points, and inserting it ahead of the MELSECNET II module moved that module's start I/O number, so the access code reads the wrong position. Diff the I/O assignment against the map from before the change, re-address the assignment so the MELSECNET II module sits at 0070, and update every instruction that targets it.

    PLC programming

  • Troubleshooting

    Connecting Factory I/O to a local CODESYS soft PLC over OPC UA

    Yes: OPC UA only carries tag values, so the ladder or structured text must run in the CODESYS runtime. Fix the connection in order: prove the engineering path through the Gateway to the runtime first, then the OPC UA endpoint at port 4840, then map each scene point to one variable. Keep Control I/O out of it, because Factory I/O runs one driver at a time.

    Industrial networks