[Feature Request] Option to Act as a Scanner for Eth/IP Remote IO Modules

[TheColonel2688]

The current way of communicating with a Remote IO module via Eth/IP in Codesys is configuring the device in the IO tree, and code is generated. This is really cumbersome and doesn't allow for dynamic connection/configuration while running. It would be really awesome if this library were expanded to allow for connecting to IO Devices from a Function block.

[NothinRandom]

@TheColonel2688 I meant to get back to you on this. The library is set up to handle explicit communication since reading symbolic variable wasn't straight forward. I initially had implicit communication (IO), but removed it because it seemed redundant since Codesys already has it built in. If there's enough people requesting the feature, then I can reimplement it.

[TheColonel2688]

I don't view it as redundant. I would like to use it for Object Oriented IO, and allow dynamic configuration and adding and removing devices during runtime programically

My end goal is to allow users to configure rhe IO mapping on the UI.

[NothinRandom]

@TheColonel2688 are you still having this issue? Do you have the EDS file of the Remote IO module? I'll take a look and see what we can do for communication.

[TheColonel2688]

Oh yeah, absolutely.

I'll try to give you some EDS files.

But just to name some devices, the Main devices we use are the SMC EX260-SEN1 for Solenoid Valves. IFM AL1920 for an IO-Link Master, and Wago 750-363 for remote IO coupler.

This is the last missing piece in the puzzle for doing full Object-Oriented IO, and for having IO be user configurable on our HMIs.