Activity for getdone
-
getdone modified a comment on discussion Engineering 🇬🇧
I ran a X-Y gantry using codesys CNC. All codes and setting were same, except of feeding speed. And in a low speed, the SMC_Interpolator ran well with a continuous piSetPosition output; but when the speed exceeded a certain value, the piSetPosition changed stepply, showed in the attached picture. I tried several tests, here are the results: When cycle time was 1ms, the feeding speed <5 mm/s, ran smoothly. And speed > 5 mm/s, ran stepply. When cycle time was 2ms, the feeding speed <15 mm/s, ran smoothly....
-
I ran a X-Y gantry using codesys CNC. All codes and setting were same, except of feeding speed. And in a low speed, the SMC_Interpolator ran well with a continuous piSetPosition output; but when the speed exceeded a certain value, the piSetPosition changed stepply, showed in the attached picture. I tried several tests, here are the results: When cycle time was 1ms, the feeding speed <5 mm/s, ran smoothly. And speed > 5 mm/s, ran stepply. When cycle time was 2ms, the feeding speed <15 mm/s, ran smoothly....
-
I ran a X-Y gantry using codesys CNC. All codes and setting were same, except of feeding speed. And in a low speed, the SMC_Interpolator ran well with a continuous piSetPosition output; but when the speed exceeded a certain value, the piSetPosition changed stepply, showed in the following picture. I tried several tests, here are the results: When cycle time was 1ms, the feeding speed <5 mm/s, ran smoothly. And speed > 5 mm/s, ran stepply. When cycle time was 2ms, the feeding speed <15 mm/s, ran smoothly....
-
I ran a X-Y gantry using codesys CNC. All codes and setting were same, except of feeding speed. And in a low speed, the SMC_Interpolator ran well with a continuous piSetPosition output; but when the speed exceeded a certain value, the piSetPosition changed stepply, showed in the following picture. I tried several tests, here are the results: When cycle time was 1ms, the feeding speed <5 mm/s, ran smoothly. And speed > 5 mm/s, ran stepply. When cycle time was 2ms, the feeding speed <15 mm/s, ran smoothly....
-
I ran a X-Y gantry using codesys CNC. All codes and setting were same, except of feeding speed. And in a low speed, the SMC_Interpolator ran well with a continuous piSetPosition output; but when the speed exceeded a certain value, the piSetPosition changed stepply, showed in the following picture. I tried several tests, here are the results: When cycle time was 1ms, the feeding speed <5 mm/s, ran smoothly. And speed > 5 mm/s, ran stepply. When cycle time was 2ms, the feeding speed <15 mm/s, ran smoothly....
-
I ran a X-Y gantry using codesys CNC. All codes and setting were same, except of feeding speed. And in a low speed, the SMC_Interpolator ran well with a continuous piSetPosition output; but when the speed exceeded a certain value, the piSetPosition changed stepply, showed in the following picture. I tried several tests, here are the results: When cycle time was 1ms, the feeding speed <5 mm/s, ran smoothly. And speed > 5 mm/s, ran stepply. When cycle time was 2ms, the feeding speed <15 mm/s, ran smoothly....
-
Thank you! This help me too.
-
In the "Trace Configuration" - "Advanced Trace Setting", for the option "Measure in every n-th cycle", its help says, "Data recording in every n task cycle", which means the time interval should be "n x task cycle time". But I found in the trace data file, the time interval of the data recording was same with the value of this option, rather than the time "n x cycle time". I don't know if it is a bug, and glad to let you know this thing.
-
In the "Trace Configuration" - "Advanced Trace Setting", for the option "Measure in every n-th cycle", its help says, "Data recording in every n task cycle", which means the time interval should be "n x task cycle time". But I found in the trace data file, the time interval of the data recording was same with the value of this option, rather than the time "n x cycle time". I don't know if it is a bug, and glad to let you know.
-
I am coding a gantry application, and be confused about the interpolation cycle time. There is an option in "CNC settings" - "Preinterpolation" - "Cycle time". Its help says, "Cycle time [µs]: here the interpolation time can be set. Default value is 20000µs""Interpolation time and cycle time have to match for identical behavior of CNC editor and online application. This applies for the task that calls the interpolator." And for FB SMC_Interpolator, there is a input "dwIpoTime". Its help says, "This...
-
I am coding a gantry application, and be confused about the interpolation cycle time. There is an option in "CNC settings" - "Preinterpolation" - "Cycle time". Its help says, "Cycle time [µs]: here the interpolation time can be set. Default value is 20000µs""Interpolation time and cycle time have to match for identical behavior of CNC editor and online application. This applies for the task that calls the interpolator." And for FB SMC_Interpolator, there is a input "dwIpoTime". Its help says, "This...