Skip to content
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

Output optimalisation #15

Open
JBSchueler opened this issue Feb 17, 2017 · 1 comment
Open

Output optimalisation #15

JBSchueler opened this issue Feb 17, 2017 · 1 comment

Comments

@JBSchueler
Copy link

I noticed that every move instruction has a speed argument which is always the same.
e.g.:

; Generated with:
; "Raster 2 Laser Gcode generator"
; by 305 Engineering
;
;
;
G28; home all axes
G21; Set units to millimeters
G90; Use absolute coordinates
G92; Coordinate Offset
G00 X0.0 Y0.0
M03
G01 X0.1 Y0.0 F288
M05
G00 X0.4 Y0.0
M03
G01 X0.6 Y0.0 F288
M05
G00 X0.8 Y0.0
M03
G01 X0.9 Y0.0 F288
M05
G00 X1.1 Y0.0
M03
G01 X1.1 Y0.0 F288
M05
...

If the speed is always the same it can be set once at the beginning

e.g.

; Generated with:
; "Raster 2 Laser Gcode generator"
; by 305 Engineering
;
;
;
G28; home all axes
G21; Set units to millimeters
G90; Use absolute coordinates
G92; Coordinate Offset
G00 F288
G01 F288
G00 X0.0 Y0.0
M03
G01 X0.1 Y0.0
M05
G00 X0.4 Y0.0
M03
G01 X0.6 Y0.0
M05
G00 X0.8 Y0.0
M03
G01 X0.9 Y0.0
M05
G00 X1.1 Y0.0
M03
G01 X1.1 Y0.0
M05
...

Not only saves this disk space (uhm..., who cares nowerdays ), it saves also a lot of unneeded serial communication and processing on the GBRL interpreter.

@JBSchueler
Copy link
Author

The option to set the spindle speed for G00 is not needed.
We only want to control G01 (when the laser is on!).
G00 is already been set in the configurations of the GRBL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant