search

sir-buckyball / chrome-gcode-sender

A gcode-sender application for Chrome/ChromeOS.
MIT License
61 stars 24 forks source link

jog commands should use G0 instead of G1? #30

Closed secretspy711 closed 10 years ago

secretspy711 commented 10 years ago

its just kind of annoying because G1 is so much slower than G0.

sir-buckyball commented 10 years ago

For now you can speed up jogging with the G1 command by increasing the feedrate. If your machine moves too slow for your taste, consider increasing the default feedrate. It shouldn't affect your jobs as your gcode files would specify the feedrates to use. Once a job is completed however, the feedrate would be set to the last feedrate in the job.

As background, I set jogging to use G1 because grbl boards on machines where the Z axis is a screw, but the XY gantry is belt driven have a known issue where they can lose their positioning if a rapid move is done in the Z axis. G1 was simply the safe command to use.

I will go and add an option so you can choose which type of jog movement is right for you and your machine. I will probably get to it this weekend.

sir-buckyball commented 10 years ago

FYI: release 2014.7.10.0 incorporates these changes and has been pushed to the chrome web store.

secretspy711 commented 10 years ago

awesome, thanks much!

got another one for ya. Been using CAMBAM and it puts a G64 at the beginning of my gcode files/ this is easy enough to automatically suppress, but Makercam does something similar with a G40, which you can't suppress unless you edit the nc file manually. Can you make it simply ignore the gcodes not supported by grbl?

Brian

On Thu, Jul 10, 2014 at 11:30 PM, Buck Clay notifications@github.com wrote:

FYI: release 2014.7.10.0 incorporates these changes and has been pushed to the chrome web store.

— Reply to this email directly or view it on GitHub https://github.com/sir-buckyball/chrome-gcode-sender/issues/30#issuecomment-48695613 .

sir-buckyball commented 10 years ago

I feel that filtering commands from a gcode/nc file before sending them to a machine is somewhat outside the scope of this program. It is also potentially dangerous since each command depends upon the previous command sequence.

I have not tested personally, but it is unfortunate if you are reporting that grbl does not ignore G60 and G40, both of which cancel features not supported (and thus safe to ignore). I should also point out that the codes supported by grbl vary by which version a machine is running (eg., a future version could actually support the commands).

For your workflow, may I suggest using the grep command line utility commonly available on linux/unix/mac systems. It is designed for filtering files and could easily remove troublesome commands for you.