Personal Data

Username:
getdone
Joined:
2021-04-24 14:52:57+00:00

Projects

  • No projects to display.

Skills

  • No skills entered.

User Activity

  • Modified a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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....

  • Modified a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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....

  • Modified a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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....

  • Modified a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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....

  • Modified a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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....

  • Posted a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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....

  • Posted a comment on discussion Motion πŸ‡¬πŸ‡§ on CODESYS Forge

    Thank you! This help me too.

  • Modified a comment on discussion Engineering πŸ‡¬πŸ‡§ on CODESYS Forge

    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.

View All