Sword wrote: ↑Thu Jan 16, 2025 4:35 pm
Use the GRBL output and then "Save to G-code", along with the custom start/end code option in machine settings. Then if you need some further editing of the saved G-code, open it in Notepad++ and make a macro to do any of that. My macro starts at the first line and automatically makes all the needed changes and then saves the file.
ok and other quick question. What gcode would I add to the end of my post processor in Vetric to make the spindle return to my work zero? I did a quick search and I probably just missed it.
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
There are a few ways to do it, but here's a snip of my end of program. I prefer the Z axis to be at the top when finished (Machine Z home), before going anywhere else.
M25 ; Move to Z home
M5 ; Spindle Off
M9 ; Dust Collection Off
G0 X0.000000 Y0.000000
Scott
1 user liked this post
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
Sword wrote: ↑Thu Jan 16, 2025 5:35 pm
There are a few ways to do it, but here's a snip of my end of program. I prefer the Z axis to be at the top when finished (Machine Z home), before going anywhere else.
M25 ; Move to Z home
M5 ; Spindle Off
M9 ; Dust Collection Off
G0 X0.000000 Y0.000000
That's kind of what I was picturing but I've caused issues in Mach4 thinking I knew what I was doing on that one Thank you.
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
RAS introduces a lag that shows itself with Laser applications (XYZ)
when using a diode laser you can compensate for the lag introduced by RAS
with this added feature in version 5.24+ PWM Laser Delay Fine Tuning Parameter 424 added. Useful for compensating
for millisecond delays introduced when using RAS with Clearpath servos.
