-
-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty g-code output #2411
Comments
That worked. Thanks for the quick answer. Since this is a laser, and I have it focused, I really don't want Z changing. This has come up in the "Discussions" area as well. If you get a fix in nightly, I'll be happy to test it. |
That solution works, but doubles the number of cuts, first at Z0 and then again at Z0.1:
The lift for the move "G0 Z5", then back to "G1 Z0" is slightly overdone, but not bad. And another problem now. Here is the start of the output g-code:
I have a laser on a new CNC 3018. I'm connecting as "GRBL ESP32". Not sure the difference bewteen "GRBL" and "GRBL ESP32". That "M3 S254" turns on the laser, and leaves it on. It should be "M4 S254", M4 turns off the laser for G0, and back on for G1. That I can fix by hand in the g-code file. |
Also, this is funcky, "Z-0":
|
I would recommend you to run with the plain GRBL profile. GRBL ESP32 was for the now deprecated project https://github.com/bdring/Grbl_Esp32 (the new project is named FluidNC). The main difference is the startup sequence. I will probably remove the GRBL ESP32 profile in the future.
Yes this is a small oddity with how float numbers are handled. It should probably be cleaned up in the future. This has no effect on the machine movement. I have fixed it in the nightly build so that it now only generates one cut if you leave the start depth and target depth equal to each other. |
Closing this as it now works to set start and target point the same and get one layer generated. I also fixed the bug so that you can't set depth per pass to zero which would lead to an infinite loop. |
Thanks! |
Version
2.1.4
Hardware / Firmware
GRBL 1.1
What happened
On both 2.1.3 and the current nightly.
I load this simple ugsd file:
rectangle.ugsd.txt
I see my rectangle, but the visualizer goes blank. . I Export Gcode, and I get this empty g-code file:
rectangle.gcode.txt
What is wrong?
How to reproduce
No response
Operating System
Gentoo
Anything else
Every time
The text was updated successfully, but these errors were encountered: