hence.persson

Hello. I need to be able from the runtime enable the GPio as we have applications where the GPios isnt controlled from codesys and we have the same codebase.. I have used the DED.Reconfigure before but when trying to enable/disable I get the error not supported.. Am I doing something wrong or is the reconfiguration of GPIO really not supported?

I have tested /dev/ttyUSB That works.

I don't think so BUT you have the possibility to give in/out variables to a visu.. This could be used for example making valve faceplates then connecting them to the corresponding valve object.. If you have your valves in an array you could have a input variable valve no and have the visu connected to the valve array and get a somewhat equal behaviour as you describe..

Winpcap was it.. Needed for control win runtime not needed for rte. Needed at least for profinet unsure about ethernet/ip

Check the profinet task what is the worst case cycle time. Adapt the send clock and the watchdog. You can reduce the reduction ratio probably not that that is at fault.

Regarding win runtime. From what I remember modbus tcp works out of the box. Profinet needs to install a free software don't remember the name. Maybe the same is true for ethernet ip ? I have tested profinet in the demo runtime and that worked but ad I said needed to install some software first.

Thanks for your time trying to help really appreciated. I used to do it like that but the opening of the comport isnt needed that is handled by the modbus server but with the new Codesys you should be able to use the configured Device according to the changelog. But apparently someone missed the possibility to change the number of stop bits. So guessing I will have to revert back to my old implementation.. Example: byInternalUnitID := 10; stInternalComPortSettingsNew.ulBaudrate := SysCom.SYS_COM_BAUDRATE.SYS_BR_9600;...

Interesting but I am configured as an Device then I cant change that setting..