CtrlX core X3 profinet device transition in safe-op

[Jesse]

we got a demo of CtrlX Core X3 with profinet slave ports at xf-23 and xf24. the profinet device app and other apps (version 1.16)were installed and licensed. after having XF23 port configured as profinet device and running the transition status is always at Safe-OP mode. 

when checking the scheduler it shows operating.

since the CtrlX I/Os have not been installed yet the Ethercat Master has an error "Topology not OK"

this is the first time to test X3. does the Ethercat master error affect the profinet status?

then I set up a XM22 as profinet master and loaded the device data file. the master can have the device scanned. after having the settings applied in the project and downloaded it showed module not found.  

from that I can guess the issue is from the CtrlX core X3, but after having most settings checked I haven't seen where to change the profinet settings and how to fix it. let me know if I have missed any settings. 

your help will be appreciated.

[CodeShepherd]

Actually there are technical issues in the prototype version 1.16 of the Profinet device app, so that communication cannot be established. We are actually working on this.

[Jesse]

Thank you for answering that. I was wondering if there were something I did wrong. let's wait an update on that.

[CodeShepherd · Accepted solution]

Release of the ctrlX Profinet App is now planned for KW3 2023.

[Jesse]

Thank you. that is a good news.

[POUL]

New app release PROFINET device PND-V-0118.1 in DC APP Pack Paket 18.2 still stay in Safe mode

[CodeShepherd]

It is part of the actual pre series app package 1.18.2 that can be found on the collaboration room. Please have a look to the ctrlX Store area here in the forum  for latest information about the app e.g. where to download.

[JHU1XI1]

I have a similar situation. You can delete the PN node and add it again. You can try the following.

[CodeShepherd]

I talked to our R&D and there are two main reasons why you could get stuck in safe-op:

1. IO data settings of the controller side must fit to the slave. When using a XM22 as controller scanning will find the correct IO structure.
2. There are problems in the Scheduler settings. See Release notes for known ones and how to fix this.