Error scaling AxisProfile 091F0007/0C580401

[V_A]

Hello,

I use a CtrlX7 and after updating the MotionApp I get the error that I can't get rid of even if I change the units in the profile.

[Michael_A]

Hello, may be some checks have been added in the new version. Please add your actual configuration and a parameterset (all Parameters) of the drive that is connected to profile MA1001_HubStap

For more information you can try to activate traces for the axisprofile and then add the Diagnostic_log again.

Regards

Michael

[V_A]

Hello Michael_A,

attached is the parameter set.

[Michael_A]

Please add the actual configuration too - i need this to crosscheck

[V_A]

attached is the configurations.

[Michael_A]

Hello,
sorry but  to check this problem i need the whole configuration. Please create a systemreport of your machine and add it here.

[V_A]

Hello,

hier is the systemreport.

[Michael_A]

Hello, on the first look the configuration seems to be ok, but in the drive i can see some problems with SMO-configuration. It could be possilbe that this can cause such an error. Can you test to deactivate the SMO on your drive and check if this error still occurs?
Before you start the test please enable the traces for motion.core and axisprofile in the trace settings, save the configuration and try to start up the system. Please send the diagnostic-log after the test.

[CodeShepherd]

EDIT: As far as I know torque unit in the drive in percent is not supported by the ctrlX MOTION currently. As it also cannot be chosen on motion side.

Only percentage setting is currently supported.

Is there a reason you changed the resolution of the speed?

[V_A]

the error reappears. Even if SMO is disabled.

[V_A]

the percentage was unintentional. After I changed the unit to N and the speed resolution back to the standard values, the error still persists.

[Michael_A]

Hello, after changing the values in the drive, did you restart the control or switch from Operating to Setup and back to Operating?
This is necessary because axisprofiles only do this checks while booting.

[V_A]

Hi, yes I tried that, unfortunately it didn't fix the error either.

[V_A]

I have now tried to uninstall and install the Motion app and these errors occurred. Maybe this is the cause?

[CodeShepherd]

In the system report attached above we can see the problems mentioned in my post above:

Inconsistent scaling type on drive and control side

Please check profile MA1001_Hub, the scaling type of velocity, position and acceleration do not match with each other, position: -1, velocity: -1, acceleration: -1

Could you add a new logbook export or system report after trying to switch up ctrlX MOTION from configuration to running? Then we can check what is happening now.

[jacaré]

Here are the new log files. The first one directly after boot. The second one after tried to switch the axis from Configuration to Run.

[jacaré]

after installing ctrlX WORKS 1.20.5 we downloaded the same IO config into the core and it worked. So could be that in the previous version there was a bug or the installation was somehow faulty

[CodeShepherd · Accepted solution]

Together we found following:

The axis were not visible in the EoE tab of the EtherCat master in the ctrlX CORE web UI and master configuration was missing:

ctrlX CORE web UI - EtherCat master - EoE setting missing

Further more when clicking on a slave the Protocols EoE and SoE were not available:

ctrlX CORE web UI - EtherCat slave information - missing protocols

As a result the ctrlX MOTION was not able to read out and check the scaling settings of the drive while booting up.

Everything was correctly configured in the ctrlX IO Engineering project. The reason seemed to be a problem with the installation of ctrlX WORKS. After uninstalling their current version and installing the latest LTS version 1.20.5 the IO project was again loaded to the ctrlX CORE and the machine was working like expected.