Moved to own topic from this one.
Did you update your system or import an configuration (app data) from older version?
What is happening before the restart? Does it work and you manually restart or doeas it restart on its own?
How does the Scheduler look before and after reboot?
You could try to reset your scheduler configuration so it will be auto generated with correct settings:
Switch system to setup and send {} to "scheduler/admin/cfg/reset-programs" via the data layer. Afterwards delete and add your EtherCat master to also get the correct scheduler settings for this app. To be sure you could save your active configuration (app data) afterwards.
Afterwards use the create button under save and send { "configurationPath": "", "id": "", "phase": "save" } to permanently store the new configuration. As EtherCat master is installed also delete your master instance and create a new one to generate corresponding scheduler configuration.
For further investigation as mentioned in the former post:
- switch on the traces (see e.g. here how to do so)
- save your active configuration (app data)
- set logbook to persistent
- reboot
- create system report ("?" symbol on the right top in your crlX CORE web UI)
Hello,
We solved the issue on one core,
we tried to duplicate the systeme by a backup restore procedure, and we're getting the same problem where the app motion hangs in configuration, we tried to reset scheduler and recreate the Ethercat app configuration and we're getting the same error.
attached the system report.