https://forge.codesys.com/u/drive/activity/2022-09-01T09:10:26.577000ZRecent activity for drive2022-09-01T09:10:26.577000Z2022-09-01T09:10:26.577000Zdrivehttps://forge.codesys.com/u/drive/profile/https://forge.codesys.com/forge/talk/Motion/thread/a7377a8e21/?limit=25#d7fe/576d

Dear Fless thanks for your appreciated answer. SMC_ExtendedVelocityChecks has solved the problem.. thanks for your support

2022-09-01T08:38:52.135000Z2022-09-01T08:38:52.135000Zdrivehttps://forge.codesys.com/u/drive/profile/https://forge.codesys.com/forge/talk/Motion/thread/a7377a8e21/?limit=25#d7fe/576d

Dear Fless thanks for your appreciated answer. when I have added SMC_ExtendedVelocityChecks function to my path preprocessing (befor the normal SMC_CheckVelocities function) the Interpolator couldn't start and it was stuck at the Initialization state. when I tried to use only the SMC_ExtendedVelocityChecks function before Interpolator , the interpolator gave an Error that " there is no SMC_CheckVelocities befor the interpolator "

2022-08-31T14:23:25.601000Z2022-08-31T14:23:25.601000Zdrivehttps://forge.codesys.com/u/drive/profile/https://forge.codesys.com/forge/talk/Motion/thread/a7377a8e21/?limit=25#da25

Hello Dears. I have implemented an Ethercat based G-code motion controller system using HCQ0 form HCFA , the motion systme is 4 axis (X , Y, Z , C ) where C is rotational axis around the z axis .. all of the axis are working just fine whithin the speed and the acceleration that I have specified in Gcode file , but the C axis is always stopping the interpolator by means of avoidgaps functionality because the postion monitoring is discovering high speed of movement that exeeds the SW max speed of the...

2022-08-25T07:51:27.463000Z2022-08-25T07:51:27.463000Zdrivehttps://forge.codesys.com/u/drive/profile/https://forge.codesys.com/forge/talk/Engineering/thread/40bc82454d/?limit=25#f66e/9138

thanks alot for the apreciated support.. " _uiHomingMinCycles = 10 " solved the problem ..it seems that the homing was being acknowledged before it is event started. but how can I set a startup value for this parameter ? so I dont have to set it at each startup

2022-08-23T15:44:03.483000Z2022-08-23T15:44:03.483000Zdrivehttps://forge.codesys.com/u/drive/profile/https://forge.codesys.com/forge/talk/Engineering/thread/4ead12ea9a/?limit=25#d5d3/4a48

thanks for the appreciated reply actually I need a way to save the COE parameters so I dont need to preset the setting at every startup.. how can I do that without writing save command (save) to the 1010 register? beside that , how can I change the homing method without accesing the COE parameters?

2022-08-23T15:44:02.299000Z2022-08-23T15:44:02.299000Zdrivehttps://forge.codesys.com/u/drive/profile/https://forge.codesys.com/forge/talk/Engineering/thread/4ead12ea9a/?limit=25#d5d3/3f96

thanks for the appreciated reply actually I need a way to save the COE parameters so I dont need to preset the setting at every startup.. how can I do that without writing save command (save) to the 1010 register? beside that , how can I change the homing method without accesing the COE parameters?

2022-08-14T17:06:49.921000Z2022-08-14T17:06:49.921000Zdrivehttps://forge.codesys.com/u/drive/profile/https://forge.codesys.com/forge/talk/Engineering/thread/4ead12ea9a/?limit=25#aa9f

Good Day I am using SDP COE Drive as SM_Drive_GenericDSP402 for my eatherCAT based motion control.. but I couldnt save the chnaged COE parameter of the drive by issuing command of save all parameter at the index 16#1010 .. I am getting a warning: [WARNING] SDP_COE_X [Device: EtherCAT_Master_SoftMotion]: Service for Index 16#1010, Subindex 16#1 was not succesfull! Abort code: 16#6090030 any idea about solving this problem to be able to save the COE online parameter?

2022-08-14T17:01:06.423000Z2022-08-14T17:01:06.423000Zdrivehttps://forge.codesys.com/u/drive/profile/https://forge.codesys.com/forge/talk/Engineering/thread/40bc82454d/?limit=25#065a

Hello Dears. I am using SDP_COE as generic DSP402 axis drive.. PLC: HCQ0-1200-D when activating MC_Home FB to start a new homing sequence at the drive , at the fist activation it works just fine bu at the second activation of the same function block it start and ends pretty soon befor even starting a new actual homing sequence at the drive . and tells me the homing is done without even starting it .. at the third activation it works just fine , while at the fouth activation it is not.. it seems that...