Using IO-Link Terminal 750-1657 with PFC200

CODESYS
1

Hello.

I am programming a 750-8212 with several classic I/O terminals using CODESYS 3.5, and so far this works fine.

Now I wanted to connect a flow meter via IO-Link to read out the totalizer. For this, I purchased a 750-1657.

I downloaded IO-Check, used it to identify the IO-Link master on the PLC, and configured it with the IODD file. There, I can immediately see the sensor’s process data.

In CODESYS, I can add the 1657 to the K-Bus (but only by selecting the byte length); however, it then remains completely non-functional and empty—no I/O image is present, and I see no payload data. I can load the IODD file into CODESYS via the device repository, but I don’t know how to get it into the device tree. No matter where I try, the IO-Link device does not appear when I select “Attach Device.”

Which crucial step am I missing here?

2

Attached are two CODESYS sample projects and an application note from WAGO’s Download Center under the Learning Materials link.

a2019002_en__CDS3_WagoAppIOLink.pdf (519.6 KB)

WagoAppIOLink_Example_02.project (843.7 KB)

WagoAppIOLink_Example_01.project (1014.9 KB)

3

Thank you for your reply, John!

I managed to solve the issue with the help of the example projects.

It took me the whole weekend but now I have the live data in form of a bytes array that I can split and build some REAL values from them so I have the data I need. I hoped this would be a bit more comfortable but it works.