TimvH

Most likely related to the Device Diagnostics functionality. Double click on your device (PLC), go to the tab "PLC settings". Enable the advanced option "Enable diagnosis for devices". Build your application again.

You should only open de COM port once and then leave it open. This hCom should not keep on incrementing. (off course when you are done communicating, you need to close the COM port)

In your project you selected the "CODESYS Control Win V3" as device, but the device you want to connect to is a "CODESYS Control Win V3 x64". Those are not the same. If you double click on the device during the network scan, you will get information that these are not the same, but that you can change the type in your project to the x64 bit type. Another option is to "right-click" on the device in the device tree of your project and select "update device" then select the x64 type.

See the attached pdf with some notes (screenshots) which I prepared for one of our customers to help them get going. Hopefully this helps for you too.

Add the object "POU for Implicit Checks" to your application, then select "Bounds check". This will create a function which is automatically called each time an array is write accessed. In the function you can handle "out of bounds" situations. By default it will be limited to its lower or upper bound.

Use e.g. the condition: TCP_Connection_0.xActive AND NOT(TCP_Write_0.xDone)

I don't know the root cause... But what could help to continue when it seems to hang, is stop the CODESYS (communication) Gateway. Go to the Windows SysTray, find the icon for the Gateway and then stop it and start it again. This will interrupt the connection between CODESYS and your controller.

You should ask IFM to provide you with the correct version of their controller packages. Then after you have installed this, you can select the correct version of the controller by right clicking on it in the device tree, update device, enable the option "Display all versions" and then select the version which matches your controller. Alternatively you can ask IFM to provide an update package which can update the runtime version on your controller to 3.2.0.0.