gseidel

Hi transcend, most likely cause: one of the motion FBs was not called in each IEC cycle. See https://content.helpme-codesys.com/en/CODESYS%20SoftMotion/_sm_basic_common_errors.html. A different possible error, if you are using buffermode buffered or blending: the execution order of the motion FBs was wrong. See https://content.helpme-codesys.com/en/CODESYS%20SoftMotion/_sm_buffermode_execution_order.html. Best regards, Georg

Dear darwin03, my first guess is that the axis scaling of the last axis (joint 6) is not correct. It should be confiugured so that one technical unit equals one angular degree. From the video, it rather looks like 1 technical unit is a full revolution of the joint. (This holds for all rotary axes used with SoftMotion Robotics: they must be scaled so that one technical unit equals one angular degree.) Best regards, Georg

Hi polyautomacao, hmm, did you tune the PD parameters as shown in the link I posted above? One thing that could cause the behavior are bad parameters. I also don't understand the screen shot: when you hold the encoder to 0, why is the actual position of the DrivePosControl -208? Best regards, Georg

Hi tommyk-mar, do you call SMC_SmoothPath after SMC_NCIntepreter? Both G51 in the G-Code and the function block call are needed. You can see how this can be done in this example: https://content.helpme-codesys.com/en/CODESYS%20SoftMotion/_sm_example_cnc_3.html Best regarsd, Georg

Hi polyautomacao, basically, there are two ways to approach this. My first choice would be to check whether your servo drives supports an external encoder, connect the encoder to the servo and configure the servo accordingly. In this case, you would not need to change anything in the CODESYS application. If that is not an option, you could use SM_DrivePosControl, a drive that closes the position loop in the PLC, and feed it with the external encoder positions. See (0). You can switch your servo drive...

Dear Mr. Kolev, I'm not sure I understood correctly. But this is my take on your question: When the STO of the slave is triggered, store the current master position (e.g. 225 units) After the reset of the slave error, call MC_SetPosition on the virtual master and reset it to the stored position (225 units) Optionally, before MC_CamIn is restartet, move the slave back to the slave position corresponding to the stored master position. (If you do this, no ramping in will be necessary) Restart MC_CamIn,...

Dear Mr. Kolev, can you please explain a little more: what happens at an STO? I assume the slave axes will be stopped and retain their current position? How, then, do you call MC_CamIn after the STO? Do you restart it with a new rising edge, but on the same master position as before the STO? Which StartMode are you using, is the cam slave absolute or relative, master absolute or relative? Are the slave axes modulo or finite axes? Best regards, Georg Seidel

Hi jgalaska, the parameters and their valid ranges are described here (0). In particular, the parameter d1 must be non-positive (<= 0). (0) https://content.helpme-codesys.com/en/CODESYS%20SoftMotion/_sm_trafo_pou_six_dof_robot.html#UUID-5451338b-a728-5c42-0f62-d9735b01d032_id_b18ea4b1b308acfdc0a8646358edc019_id_e7016982df408f59c0a8657d017550b3 Best regards, Georg