FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
09-08-2023 12:48 PM
Currently trying to use MC_FixedStop, however I'm recieving "internal Error occurred".
I've attached screenshot of all inputs/outputs from the function block.
I've also attached a diganostic log as well as systemreport (in case required).
Setup:
Single ctrlX drive sales demo with integrated CORE
V1.20.x
S-0-0124 = 20
Max torque limit +- 400% in the drive
DETAILED_DIAG_INTERNAL_ERROR |
|
16#C560270 |
Internal Error occurred |
09-12-2023 09:24 AM - edited 09-12-2023 09:51 AM
Hello,
in the diagnosticLog there are not enough informations to see the problem but you can enable the traces for axisprofile and motion.core and motion.drivecommands
you can do this settings here in the datalayer
If you then reproduce the problem you can download the log again with the traces. Then there should be more information about this.
On possible error could be, that you did not configure the torque in your IO-Configuration and map it to you axis in the axisprofile.
09-12-2023 09:57 AM
I tryed it on my system and got an error like this if the commanded velocity is lower than S-0-0124.
09-12-2023 01:20 PM
I have enabled the additional traces and recreated the error (see attached).
I didn't have S-0-0084 Actual torque configure, this has now been included in the mapping. However I still recieve the same error.
I have also performed the following:
10-26-2023 11:23 AM
Error 090F2040 - C560270 mentioned above can be found in our online documentation.
Could do me a favour and also switch on the traces of the motion core generate error again and create a system report?
I guess your problem could be related to a topic already under investigation.
10-30-2023 10:01 AM
Please also open the traces of motion.drivecommands and comm.axisprofile to make sure to find out the reason.
a month ago
@ChrisLarkin Are there any news? Could this issue been solved?