Cut Path Not Following Gcode
- MakingStuff
- Topic Author
- Offline
- Premium Member
- Posts: 121
- Thank you received: 14
I immediately noticed that there was a problem after my first cut and I'm not sure what is going on here. I have attached an image that shows what is happening. If you look at the image you can see the white line that shows the gcode drawn out and the red line that is the path that the torch took. If you look inside the wrench on the right you can see the the mouth of the wrench was not cut square like the white line shows. The red line shows that there was a shortcut taken and the mouth of the wrench is rounded. This is clearly a software issue because LinuxCNC is showing the correct gcode drawing but the cut path is not the same. Is this a setting that I need to fix, or is there something else going on here?
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
- Posts: 17796
- Thank you received: 5918
Just put that at the top of gcode file.
Please Log in or Create an account to join the conversation.
- MakingStuff
- Topic Author
- Offline
- Premium Member
- Posts: 121
- Thank you received: 14
That is due to low acceleration/fast feed rate and can be eliminated by using G64 P0.1 if using mm.
Just put that at the top of gcode file.
I'm not using mm, I'm using imperial measurements.
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
- Posts: 17796
- Thank you received: 5918
In that case
That is due to low acceleration/fast feed rate and can be eliminated by using G64 P0.1 if using mm.
Just put that at the top of gcode file.
I'm not using mm, I'm using imperial measurements.
G64 P0.005 should be enough for plasma. That is basically the tolerance that the machine should follow, so nothing would go farther than that set tolerance from the actual tool path.
Please Log in or Create an account to join the conversation.
More info here:
linuxcnc.org/docs/html/gcode/g-code.html#gcode:g64
Please Log in or Create an account to join the conversation.
- MakingStuff
- Topic Author
- Offline
- Premium Member
- Posts: 121
- Thank you received: 14
I have one more question. Why do I need this on my new setup, but it wasn't required on my old LinuxCNC 2.7 machine? Is this something new for LinxCNC 2.9?
Please Log in or Create an account to join the conversation.
- Dinuka_Shehan
- Offline
- Platinum Member
- Posts: 346
- Thank you received: 26
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
- Posts: 17796
- Thank you received: 5918
That was changed during 2.7 when the new trajectory planer was implemented. It is in later versions of 2.7, 2.8 and 2.9.G64 P0.005 fixed the problem.
I have one more question. Why do I need this on my new setup, but it wasn't required on my old LinuxCNC 2.7 machine? Is this something new for LinxCNC 2.9?
Please Log in or Create an account to join the conversation.
- MakingStuff
- Topic Author
- Offline
- Premium Member
- Posts: 121
- Thank you received: 14
That was changed during 2.7 when the new trajectory planer was implemented. It is in later versions of 2.7, 2.8 and 2.9.
Ok. Thanks for your help!
Bob
Please Log in or Create an account to join the conversation.
There is a file called imperial_startup.ngc (or metric_startup.ngc) that sets G64 P0.04, it should have been G64 P 0.004. The metric version is correct at G64 P0.1
I will fix this.
Please Log in or Create an account to join the conversation.