I'll keep getting an error while I command with one of my two axis when I try to turn it. And it feels like the moment the second axis gives an error is random. one time he gives an error message after a position of 6 and the other time after a position of 170 and than to position of 84, it feels really random. I've even had a few times that he just turns correctly to his position
To give you an idea of what I am trying to do I will briefly explain what needs to be done. A cable must be wound on a drum(x-axis). the cable is guided through a traverse(y-axis). The y-axis must follow the x-axis.What I have done now, I determine to which position the x-axis should go to get a correct cable length. then I send the x-axis to that position with arAxisCtrl_gb[X_Axis.AxisNo].PosMode.Position and right after that I send the y-axis to a certain factor of the actual x position. I get the actual position from Posistion_X := arAxisStatus_gb[X_Axis.AxisNo].Data.ActualPosition.
I have already looked into the error codes but that doesn't help me.
The x-axis rotates normally but the y-axis gives an error message every time it is rotating. See pictures to see the error codes and a bit of the code i use.
Solved! Go to Solution.
The error on your pictures means:
Cause/Remedy 1: Cause: An invalid status was returned. Remedy: Make sure that the correct status is reached in the PLC Open state machine.
Please have a look in the diagnostic log of the control to see if there are more information available and send a screenshot or export.
The error codes are a bit confusing to us because we do not know what you are commanding exactly.
There is for example also a gantry command set in the system that does absolutely not fit to the application described.
There are also a lot of motion object reset without an error pending.
And also a lot of abort commands.
Could you please switch on the system trace of the motion app, create the error and download another log file with all additional information active? Then we can have an exact look which commands are sent when.
After checking with you directly please remark following hint:
Note, that this application can/will lead to strange movement. The motion command always plan with an end velocity of 0 mm/s (full stop at the target position). This means, when a motion with a length of 15 µm is commanded and the acceleration is 25 mm/s², it will only get to a velocity of ~0,875 mm/s. When you have a higher initial velocity (because its a non-buffered command), this will lead to an overshoot. This means, the ctrlX MOTION breaks with the allowed limit deceleration, changes the direction and moves back to the target position.
Currently, there is no way implemented to command cyclic set points to the ctrlX MOTION.