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

How to ignore Commands #796

Open
iplayfast opened this issue Jan 18, 2020 · 3 comments
Open

How to ignore Commands #796

iplayfast opened this issue Jan 18, 2020 · 3 comments

Comments

@iplayfast
Copy link

iplayfast commented Jan 18, 2020

I've got a project that is a sand table. The idea is a ball bearing is dragged through sand on a tabletop. This works fine, however, I want to send it 3d printer gcode files, where there are move relative commands or other commands that grbl doesn't know. It gets stopped in its tracks. What I would like is an option where any commands it doesn't understand it is just ignored. (z axis, heater and so on).

Do you think this is possible?

@zeevy
Copy link

zeevy commented Jan 19, 2020

If those commands does not produce alarm or crtical errors on grbl side then those can be ignored on the gcode sender gui you are using

@doppelhub
Copy link

I don't completely understand what you're describing, but unknown grbl commands can be formatted/removed prior to sending them to grbl (i.e. on the host layer). The simplest method is to format non-g-code commands into comments '(' and ')'.

@iplayfast
Copy link
Author

Yes I know that is one option. The request was to ignore unknown commands in the grbl firmware. I'm getting critical errors, when sending 3d printer gcode to the grbl. I think it has to do with temperature settings. Which now that I think of it, ignoring wouldn't help, because the code sender waits until the proper temp has been reached. I think this issue should be closed. Sorry for wasting your bandwidth.

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

3 participants