FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
02-17-2023 05:07 AM
Hello,
use X3 worksV1.18.1 Motion App1.18
MC_MoveVelocity Speed control, limit S92, when the locked rotor reaches the torque stop, then execute MC_ Stop ,HCS01 Error F2037。
What are the good solutions?
No such problem was found on the XM controller.
Solved! Go to Solution.
02-17-2023 07:21 AM
See also help of F2037. Could you give us a complete parameter save of all drive parameter or at least the parameter stored in P-0-0010 and P-0-0011?
Could you check if function ML_AxsFixedStop is working for you?
02-17-2023 08:06 AM
hello,
1.The attachment is a parameter,
2.This function has some disadvantages for customers to meet their needs,
strAxsFixedStop.In.Position:=rPos;The position command can only support absolute values,
In this way, every time the position value needs to be updated, the size of the customer's workpiece will be inconsistent, and the operation will be very troublesome.
The customer wants to be the same as XM.
02-17-2023 11:43 AM
Did you try to use "DriveVelMode" = true at the MC_MoveVelocity to switch the drive from positioning mode to vel mode? Please beware that the cyclic data channel and the drive operation mode needs to be set accordingly (See also ML_AxsVelocity). The false parameter is a new feature that was not existing in MLC.
02-17-2023 01:05 PM
02-17-2023 02:08 PM
ML is the same functionality as MC. difference is that first is a function and second is PLCopen standard.
In my opinion there should be no difference between MLC and ctrlX CORE. I will try to get more information about your problem. Please tell me how you get the information of torque reached from our drive to the PLC.
02-17-2023 03:07 PM
I didn't read the torque data, just limited the torque S92, and then carried out speed control.
02-17-2023 03:19 PM
I can describe the working process of XM control, limit torque S92, and then conduct speed control.
When I reach the torque (S92), the feedback speed of the motor becomes 0, and the driver displays E8260, executed MC_ stop,no Error.
Same working process, X3 MC_ Stop,Error F2037.
02-17-2023 03:27 PM
Could you please do a record with the drive oscilloscope including the parameter P-0-0115, P-0-0116, S-0-0047, P-0-0047, S-0-0051. Set trigger to error F2037 using 30% pretrigger and choose maximum recording speed (<=2ms). Afterwards send and export or parameter save of all parameter again? Hopefully we can see what is going on in this moment.
02-17-2023 03:55 PM
Ok, I will get these parameters according to your method. Thank you very much for your support.
02-22-2023 11:58 AM
03-01-2023 04:25 PM - edited 03-01-2023 04:26 PM
We checked your data as for now this behavior as expected. There are two workarraounds possible to achieve what you want to do.
03-02-2023 01:48 PM
Hello,
Thank you very much for your support.
We currently recommend this solution to customers.
I want to know the following: speed control mode torque limit. There may be many such applications. Do we have plans to optimize?
05-09-2023 09:29 AM
@JHU1XI1: The function axsSetIpoPosFromActPos is now available with early adopter release 1.20. Please feel free to test it and give some feedback.
Best regards, Michael