Error on configuration when restarting

[Wsson]

Hello,
We are having some issues when rebooting the core. We get Error on configuration. I have searched the forum and found some similare cases, but not a solution that has worked for us. The error happens some times, but not every time we restart the core and causes us to not reach operation.
Note that we are using V2.4

I have activated trace for the scheduler and set the logbook to persistent before restarting the core and getting the error.

We also tried to load a empty configuration, then redownload the I/O config, and loading our motion config from an archived config. Then downloading the PLC code. This did not solve the problem.

Thankfull for any help on this issue!

 

[CodeShepherd]

In the logbook the error that motion cannot reach run is mentioned. Did you install a ctrlX OS - Motion app and uninstalled it?

How do you load an empty configuration? It could that your "empty" one already bringing the problem with it. Best way would be to do a reset via the web UI:

ctrlX CORE web UI - reset configuration

Please have a look to "Motion app hangs in Configuration/Running after booting" for information how to reset the scheduler configuration.

[Wsson]

Hello,
Yes, we did a reset first, then a reboot. Then loaded the IO Config from IO engineering. Then we made a backup that we called EmptywIO. And loaded the motion config to it. Loaded EmptywIO to the core and then downloaded the PLC code from PLC engineering.

We have updated our core from V1.20 to V2.4 (Using USB and reboot)

We will try again with the method that you mentioned above.

[Wsson]

Reseting the scheduler configuration using the linked methode did not solve the problem unfortunately.

[CodeShepherd]

So which steps did you do exactly? Did you load any configuration after resetting the scheduler? 

Did you already try uninstalling and reinstalling the ctrlX OS - MOTION app?

We could schedule a meeting doing the steps again together, as this is the way to go. Please send me your contact data in a private message.

[CodeShepherd]

@Wsson Are there any news? Could this issue been solved?