I’m doing a multipass engraving on some stone tile, and the Glowforge suddenly stopped a quarter of the way through.
No error messages. No button color. It seemed like it thinks it’s done. Any idea what’s going on?
I’m doing a multipass engraving on some stone tile, and the Glowforge suddenly stopped a quarter of the way through.
No error messages. No button color. It seemed like it thinks it’s done. Any idea what’s going on?
Did it overheat and need to cool down? (It will pause for a while until the temp comes back down.)
(there will be a small “cooling” message in the app next to the Print button)
Nope, there was no message that I noticed. It looked like it went back to a “ready to print” state.
And now I can’t seem to start any projects, even older basic ones (simple cardboard cutouts). When I define the material, it prepares it, gives me a time estimate, and when I’d expect the button to start flashing, the print window disappears from the screen and the button never flashes.
I’ve had that happen to me a couple of times when my Wifi got sketchy, but not the pause…that’s usually a cooling down thing.
Try turning the machine off, moving the head slowly underneath the lid camera, and turning it back on and letting it run through the complete calibration again. Then try one of your older files that you know has worked. You might need to do it a couple of times, but it usually comes back up shortly.
It looks like you have a pro. That behavior is similar to what happens if the interlock on the back of the machine (above the power cord) isn’t making good contact. Might check that.
Agree with @jbmanning5
Had the same thing happen to me on an early unit. Check the staple in the interlock to make sure it is seated. Maybe put a piece of masking tape over it if it is loose.
The staple seems tight. It’s sticking out a little bit, but it doesn’t move and feels firmly in.
Well, I did a few things, and it at least seems to be willing to flash the button at me:
¯_(ツ)_/¯
Time to do more pew pew.
Thanks for the answer @jbmanning5, that’s right.
@Slipshod, I’m going to close this thread - if the problem reoccurs, go ahead and post a new topic. Thanks for letting us know about this!