Error switching motion fron configuration to operation

[giustola69]

Hello,

I'm trying to configure an axis in a new virtual machine created with Ctrl Works 1.10.3 but I could not switch the motion from configuration to operation. Attached you have the configuration I did and the messages I get.

If I start an old virtual machine made with CtrlX Works version 1.6 it works

Please could you help to to understand why?

Many Thanks

Giuseppe

[Jens_Hellmann · Accepted solution]

This is mostly caused by missing callables in the scheduler (especially the motion callable in ctrlXAutomation task).
If you create a new virtual control there are some files in the configuration that prevent creation of these callables.

To solve this issue you can use the reset function to create an empty solution in “Manage app data” (attention: your changes are lost). The necessary tasks and callables will be created correctly. But you should stop your schedule before …

After that the missing callables should be available.

[giustola69]

Hello,

I tried to do what you suggest but I got and error while doing the Reset command. I tried it on the Virtual Machine I had and I got the 1st errors, then I deleted that virtual machine and create a new one and then tried again to to the Reset command but I got a different error. However in bith case it was not possible to end the Reset command.

Any other advice ?

Many Thanks

Giuseppe

[Jens_Hellmann]

The motion and the sceduler should be stopped before resetting.

motion state --> CONFIGURATION

scheduler state --> CONFIG

Which version of motion app do you use?

[giustola69]

Hi,

I did not stop the scheduler before. Now I tried it again and the Reset command was OK and after that it was also possible to switch the motion to operating mode

Many Thanks

Giuseppe

[CodeShepherd · Accepted solution]

EDIT: When getting the error "Error in system configuration - 091F2020 and sub code 0C56020E":

You do not need to reset your AppData (active configuration). You can also simply add a new task in the scheduler and inster the new callable "motion-high-prio-prep":

 

[ropper]

I had the same problem when I upgeaded to 21.07 but the diagnostic ID I got did not come up when I searched for it. So I'm adding it here.

I got "Error in system configuration - 091F2020 and sub code 0C56020E

[CodeShepherd]

Thanks for the addition.