Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Feature Request: Custom G-code between sequentially printed objects #1065

Closed
c-born opened this Issue Mar 23, 2013 · 3 comments

Comments

Projects
None yet
3 participants

c-born commented Mar 23, 2013

When objects from the plater are completed individually, it could be useful to be able to insert custom G-code before each new object is started.
A couple of things I would like to have been able to add this way:

  1. Wait for bed temperature to return to first-layer temperature
  2. Home Z-Axis

The reason for 2) is a bit of a kludge fix, but on occasion I've left a run of 6 or 9 sequentially printed objects, of over an hour each, to print overnight, only to find that after the first or second the machine hasn't fully returned to Z0, and the remaining objects have been printed on air just above the plate. The proper fix is to find the cause (mechanical slippage, stepper slippage, firmware, something giving it a bit of a knock...) but that could take some time, while re-homing Z would give each object a fresh start.

[Edit: It turned out that there was a slightly tighter region on the Z axis screw which caused the stepper to slip when going up at high speed between objects, although not at normal speed when driving manually. A drop of oil fixed it.
Adding Z-axis home between jobs would also have "fixed' it, but masked the real problem.
I still think the ability to add custom G-code could be useful though!]

o-jasper commented Dec 4, 2013

Seconded, I manually add G28 Z0 at the M107 commands indication the different objects. (not the last M107 command though!)

Collaborator

lordofhyphens commented May 28, 2016

#3275 fixes this. Closing.

@lordofhyphens lordofhyphens reopened this Apr 4, 2017

@lordofhyphens lordofhyphens added this to the 1.3.0 milestone Apr 4, 2017

Collaborator

lordofhyphens commented Apr 4, 2017

@alexrj implemented this in bc96a1a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment