FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
12-04-2023 01:03 PM
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.
Solved! Go to Solution.
12-04-2023 02:43 PM - edited 12-04-2023 02:46 PM
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
12-04-2023 03:11 PM
12-04-2023 03:35 PM
Please add the actual configuration too - i need this to crosscheck
12-04-2023 04:30 PM
12-05-2023 07:09 AM
Hello,
sorry but to check this problem i need the whole configuration. Please create a systemreport of your machine and add it here.
12-05-2023 07:40 AM
12-05-2023 10:24 AM
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.
12-05-2023 10:58 AM - edited 12-07-2023 11:01 AM
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?
12-05-2023 11:04 AM
12-05-2023 11:38 AM
the percentage was unintentional. After I changed the unit to N and the speed resolution back to the standard values, the error still persists.
12-06-2023 06:59 AM
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.
12-06-2023 08:25 AM
Hi, yes I tried that, unfortunately it didn't fix the error either.
12-06-2023 08:54 AM
12-06-2023 08:59 AM - edited 12-06-2023 09:01 AM
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, |
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.
12-06-2023 11:23 AM
12-07-2023 11:04 AM
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
12-07-2023 11:21 AM - edited 12-07-2023 11:22 AM
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:
Further more when clicking on a slave the Protocols EoE and SoE were not available:
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.