Motion state (configuration) is different to axis profile state (Booting)

[evan01]

Hi.

My contrlX Motion app shows the error in subject topic.

Even when there is no axes added.

What can be cause?

Thanks!

[Anonymous]

Did you connect the 4 signals at the Axis profile settings?
And in the motion configuration selected the right profile for the Axis?

[Anonymous]

In this case with no Axis, are both Axis configuration and Axis profiles empty?
Otherwise maybe just leave the motion in stop state or disable the motion app?

[Anonymous]

To clearify what I mean:

It seems to me that your configuration still contains a connection to an axis. 

Motion => Axis Profiles => Make sure there are no profiles

Motion => Axis Configuration => Make sure there are no axis

Do the same for the Kinematics configuration and profiles.

After that save the configuration (Configurations => Save button).

In the configuration file you can check if there are axis in the axisProfile and motion folder.

Otherwise download the configuration to your PC and post it here.

With kind regards,

Leon Paridaans, VHE Industrial Automation

[evan01]

 Hi Leon,

My configuration with no axis. Thanks.

[Anonymous]

Indeed no axis nor profiles in the configuration.

Only thing I can think of is just to disable/delete the motion app, as you don't use it anyway?

Maybe the experts can help you out.

[CodeShepherd]

Could you please tell us which error is shown? Or simply do an system report and add it to this topic?

[evan01 · Accepted solution]

Hi CodeShepherd.

It seemed the ctrlX cycle time was changed, even though I am not aware there was a setting of the cycyle time and how was it changed ?

The problem seems to be resolved after correcting the cycle time. :]

[CodeShepherd]

I am not sure how this corresponds but for your information the cycle time settings of the ctrlX CORE and the PLC: