Can someone tell me if the PN IO device mode works on any Codesys runtime? So far I have tried Pi, Linux ARM on a iot2050, IOT2040 runtime, Exor eX707 and now Control win V3. I am attempting to connect them as a slave to an S7-1200 CPU. So far I havnt even the slightest glimmer of hope that it will work.
My latest attempt is Control Win V3. Codesys version is 3.5.19. Win10pcap is installed. Below is the log file from the "Codesys Profinet Device". I am totally at wits end here on this but REALLY need it to work!
I was searching here and found that Edwin had left a link to a different version of pcap. I downloaded and installed and this is my new log file. Still no PN device however.
hm -> Ip change not allowed - means you have not set your Windows Adapter name in the configuration file
c:\ProgramData\CODESYS\CODESYSControlWinV3x64\xxxxxx\CODESYSControl.cfg
Can someone tell me if the PN IO device mode works on any Codesys runtime? So far I have tried Pi, Linux ARM on a iot2050, IOT2040 runtime, Exor eX707 and now Control win V3. I am attempting to connect them as a slave to an S7-1200 CPU. So far I havnt even the slightest glimmer of hope that it will work.
My latest attempt is Control Win V3. Codesys version is 3.5.19. Win10pcap is installed. Below is the log file from the "Codesys Profinet Device". I am totally at wits end here on this but REALLY need it to work!
Since 3.5.19.0 we recommend NPCap please uninstall Win10Pcap. Then it will work on Control Win
and for the other device you need:
https://content.helpme-codesys.com/en/CODESYS%20PROFINET/_pnio_runtime_configuration_device.html
the syssocket setting in the config file on windows and Control Win disable the firewall to bring it up and running.
Last edit: eschwellinger 2023-04-04
npcap is not free so make sure you have a license.
Note that in earlier versions, win10pcap did not work, only winpcap.
I was searching here and found that Edwin had left a link to a different version of pcap. I downloaded and installed and this is my new log file. Still no PN device however.
hm -> Ip change not allowed - means you have not set your Windows Adapter name in the configuration file
c:\ProgramData\CODESYS\CODESYSControlWinV3x64\xxxxxx\CODESYSControl.cfg
[SysSocket]
Adapter.0.Name="Ethernet"
Adapter.0.EnableSetIpAndMask=1
Then next step is to scan the PN device on the PN Controller to have the same IO sizes/configuration
it would say.