G-code is different than the result
21 Sep 2019 11:54 #145744
by JanPan
G-code is different than the result was created by JanPan
Hi everyone,
I am playing around with CNC systems for some years and am using LinuxCNC for ~1 year now. Today I have a problem I newer realized before:
LinuxCNC doesn't follow the g-code...
The attached image shows a screenshot with the g-code (white) and the way the machine mills the structure (red). I do not understand why the machine doesn't follow the g-code. Did I miss something? I also tried with only 25% feed without success.
The g-code looks like this:
Using
LINUXCNC - 2.8.0-pre1-5206-gb3f7b2519
gmoccapy 3.0.8.2
MESA 7i76e
Thanks for Help!
Best
JanPan
I am playing around with CNC systems for some years and am using LinuxCNC for ~1 year now. Today I have a problem I newer realized before:
LinuxCNC doesn't follow the g-code...
The attached image shows a screenshot with the g-code (white) and the way the machine mills the structure (red). I do not understand why the machine doesn't follow the g-code. Did I miss something? I also tried with only 25% feed without success.
The g-code looks like this:
G00 X20.9082 Y66.4595 Z1.0000
G00 Z0.5000
G01 Z-2.0000 F600
G01 X27.1649 Y92.5446 F1200
G01 X29.9120 Y91.8857
G01 X23.6553 Y65.8006
G01 X20.9082 Y66.4595
G01 Z-2.8200 F600
G01 X27.1649 Y92.5446 F1200
G01 X29.9120 Y91.8857
G01 X23.6553 Y65.8006
G01 X20.9082 Y66.4595
G00 Z1.0000Using
LINUXCNC - 2.8.0-pre1-5206-gb3f7b2519
gmoccapy 3.0.8.2
MESA 7i76e
Thanks for Help!
Best
JanPan
Please Log in or Create an account to join the conversation.
- Todd Zuercher
-
- Offline
- Platinum Member
-
Less
More
- Posts: 4962
- Thank you received: 1369
21 Sep 2019 12:09 - 21 Sep 2019 12:12 #145745
by Todd Zuercher
Replied by Todd Zuercher on topic G-code is different than the result
That is a common mistake of beginners in Linuxcnc.
The default setting for Linuxcnc is G64 with no blending tolerance. This causes the corner rounding you see. Set G64Pn in the preamble of your g-code files, with the n= to some acceptable tolerance.
linuxcnc.org/docs/2.6/html/gcode/gcode.html#sec:G64
The default setting for Linuxcnc is G64 with no blending tolerance. This causes the corner rounding you see. Set G64Pn in the preamble of your g-code files, with the n= to some acceptable tolerance.
linuxcnc.org/docs/2.6/html/gcode/gcode.html#sec:G64
Last edit: 21 Sep 2019 12:12 by Todd Zuercher.
The following user(s) said Thank You: JanPan
Please Log in or Create an account to join the conversation.
21 Sep 2019 13:13 #145748
by JanPan
Replied by JanPan on topic G-code is different than the result
Thank you!
And: Sorry for that question...
Never realized this before.
And: Sorry for that question...
Never realized this before.
Please Log in or Create an account to join the conversation.
- Todd Zuercher
-
- Offline
- Platinum Member
-
Less
More
- Posts: 4962
- Thank you received: 1369
21 Sep 2019 17:09 #145768
by Todd Zuercher
Replied by Todd Zuercher on topic G-code is different than the result
No reason to be sorry. Asking questions is one of the best ways to learn something.
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
25 Sep 2019 22:42 #146200
by andypugh
Replied by andypugh on topic G-code is different than the result
I am not sure that LinuxCNC chooses the best default state really.
On some level, if you tell LinuxCNC that your axes can move this fast, and accelerate that fast, then you are really saying (just basic physics) that you understand that corners have to be rounded at high speeds.
But I doubt that many users _actually_ realise that is what they are configuring.
If LinuxCNC defaulted to exact-stop then people would be less surprised, but then the forum would be full of "Why is LinuxCNC so stupidly slow? Even my old GRBL could do better than this".
On some level, if you tell LinuxCNC that your axes can move this fast, and accelerate that fast, then you are really saying (just basic physics) that you understand that corners have to be rounded at high speeds.
But I doubt that many users _actually_ realise that is what they are configuring.
If LinuxCNC defaulted to exact-stop then people would be less surprised, but then the forum would be full of "Why is LinuxCNC so stupidly slow? Even my old GRBL could do better than this".
Please Log in or Create an account to join the conversation.
Time to create page: 0.067 seconds