Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
Im running a PC with Codesys Control V3. I have used version 3.17.0 and 3.19.0. For some reason I cannot get Profinet to work as either a controller (not shown in attachment) or as a device (shown in the attachment). My only clue is the Profinet_IOTask not running. I have absolutely nothing else to go on. It does not run either as controller or device.
I did the export of the proper GSDML files with each version I tested as a device. Im trying to run it as a device under the Siemens processor (what the customer wants). There is one other strange "clue". If I search "accessible devices" in Siemens, the PC device shows up as accessible.
When testing as the Master (controller), I disconnected my BK-9103 from the 1200 processor and run it under the PC. This did not work either. It was basically the same as what you see here with the green, grey, and red symbols in all the same places (with of course Profinet controller rather than device).
As a "control", I have a Raspberry Pi with Codesys that I put an IO unit from Odot on it. It took off and ran without issue.
ANY and ALL help would be appreciated! Ive lost count of the number of version changes Ive made here all with the same result. I REALLY REALLY need this to work!
Just as a follow up I decided to try with my Exor ESmart panel. As you can see here, I have the exact same issue with the Exor as I do with the Windows PC. Version on the Exor is 3.5.16.30.
Im running a PC with Codesys Control V3. I have used version 3.17.0 and 3.19.0. For some reason I cannot get Profinet to work as either a controller (not shown in attachment) or as a device (shown in the attachment). My only clue is the Profinet_IOTask not running. I have absolutely nothing else to go on. It does not run either as controller or device.
I did the export of the proper GSDML files with each version I tested as a device. Im trying to run it as a device under the Siemens processor (what the customer wants). There is one other strange "clue". If I search "accessible devices" in Siemens, the PC device shows up as accessible.
When testing as the Master (controller), I disconnected my BK-9103 from the 1200 processor and run it under the PC. This did not work either. It was basically the same as what you see here with the green, grey, and red symbols in all the same places (with of course Profinet controller rather than device).
As a "control", I have a Raspberry Pi with Codesys that I put an IO unit from Odot on it. It took off and ran without issue.
ANY and ALL help would be appreciated! Ive lost count of the number of version changes Ive made here all with the same result. I REALLY REALLY need this to work!
Just as a follow up I decided to try with my Exor ESmart panel. As you can see here, I have the exact same issue with the Exor as I do with the Windows PC. Version on the Exor is 3.5.16.30.
EDIT: I finally got a clue. I had an error box that my Profinet stack was not running. All I could come up with in help was this: https://help.codesys.com/webapp/_pnio_runtime_configuration_device;product=core_ProfinetIO_Configuration_Editor;version=3.5.16.0 .
Unfortunately to me these instructions are "cryptic" to say the least.
Last edit: tsimpson 2023-03-30