X/Y MOVEMENT HESITATION
- Thread starter rcrclr
- Start date
Ok. Then its's the same issue I have. See this thread for answers but maybe not all answers from @masso-support about it.
Adjust THC voltage during feed
Adjust THC voltage during feed
The M667 and M666 is on strange places.
N0060,N0100: Two M666 before the first cut even started? That should not do any harm though.
N0190: After the first Torch on there is M667 without feed. Should also be ok but I recommend a feed.
N0240: Before Torch off there is a new M667 with feed?? Should be M666!
And there is no move up before rapid move which I recommend.
N0280: Then there is a M666 after rapid move? Strange place.
N0530: And no M666 on the end of last cut. Might be bad because Z-axis wont work properly when THCis on.
I agree that there should not be any hesitation in this file, but maybe it works better if M666 and M667 is in the right positions. Did you maybe mix up M666 and M667 in the sheetcam rules?
N0060,N0100: Two M666 before the first cut even started? That should not do any harm though.
N0190: After the first Torch on there is M667 without feed. Should also be ok but I recommend a feed.
N0240: Before Torch off there is a new M667 with feed?? Should be M666!
And there is no move up before rapid move which I recommend.
N0280: Then there is a M666 after rapid move? Strange place.
N0530: And no M666 on the end of last cut. Might be bad because Z-axis wont work properly when THCis on.
I agree that there should not be any hesitation in this file, but maybe it works better if M666 and M667 is in the right positions. Did you maybe mix up M666 and M667 in the sheetcam rules?
The post processor with THC already have some builtin rules to turn off THC on short cuts an small arcs. And maybe its interference between your rules and the post processor that causes the problems. It may be better to choose the post processor without THC and control M667/M666 only by the sheetcam rules. You just have to add a rule to start the THC somewhere in the beginning of the cut.
And Massos post processor with THC don't turn the THC off at the end of the cut. I don't know why because THC is said to block other Z movement. Maybe M5 implicitly means M666 and M5 to Masso.
And Massos post processor with THC don't turn the THC off at the end of the cut. I don't know why because THC is said to block other Z movement. Maybe M5 implicitly means M666 and M5 to Masso.
was going through the opener.tap file and at what line number are you getting the delay?
the gcodes looks ok and multiple M666 etc should not cause any issues.
what's your controller software version?
the gcodes looks ok and multiple M666 etc should not cause any issues.
what's your controller software version?
so was this file opener.tap made using sheetcam rules?
at what line number you get the delay?
at what line number you get the delay?