Notifiche
Cancella tutti

Crash detected, now strange behavior  

  RSS
gnat
 gnat
(@gnat)
Noble Member
Crash detected, now strange behavior

Last night I wasn't paying attention and tried to print a gcode that had a couple parts starting about 3 layers off the plate which resulted in a mess and a crash detection.

When it detected the crash it moved the extruder all the way to the left and the plate all the way back. In trying to get the extruder out of the way so I could remove the plate I told it to calibrate Z by mistake. It went through that process OK, but the remnants of the parts (only 3 or 4 layers worth) were in the way for the middle calibration point. It didn't complain, but I figured it probably wasn't correct so I re-ran the calibration after I got the plate cleaned off.

I've done two prints since then and noticed three things not working as it previously did.

The first is that the initial line that is laid down at the front edge of the plate is no longer printed. It goes through the process as if it should print, but no material is deposited.

The second issue is that when printing the brim, only part of it is printed during the first layer pass. It does come back and complete it on the second pass though. Previously the brim was the first thing laid down and it never went back to it again.

Finally, when done it used to move the extruder all the way to the left and raise it to roughly the halfway point and it would also move the bed almost all the way forward. Now, however, it is moving the bed all the way back and extruder appears to be getting left where it was last needed.

Other than the noted odd behaviors, it seems to be printing fine (e.g. no extrusion issues, Z still seems good, etc..).

Any ideas what I did to mess it up and how to get it back to it's previous operation?

MMU tips and troubleshooting
Postato : 11/01/2019 4:47 pm
--
 --
(@)
Illustrious Member
Re: Crash detected, now strange behavior

I'd recommend a full factory reset and then run the wizard. At least you'd know you aren't dealing with an incorrect calibration constant hanging around.

Postato : 11/01/2019 6:38 pm
gnat
 gnat
(@gnat)
Noble Member
Topic starter answered:
Re: Crash detected, now strange behavior


I'd recommend a full factory reset and then run the wizard. At least you'd know you aren't dealing with an incorrect calibration constant hanging around.

Thanks. The wizard starting dragging the sheet of paper around for the right front and right rear calibrations though so now I need to go fiddle with things 🙁

So much for my days of a Prusa assembled and perfectly functioning printer 😥 😆

MMU tips and troubleshooting
Postato : 11/01/2019 8:35 pm
--
 --
(@)
Illustrious Member
Re: Crash detected, now strange behavior

Check there is no "ooze" stuck to the end of the nozzle - that's messed me up a few times, nozzle looks clean but there's a small nip sticking out that I have to trim with a razor blade. If the nozzle is clean, adjust the PINDA probe down a fraction, quarter or half a mm should do it. It'll change your Z-cal that amount, so you'll need to remember that when dialing in Z (go slowly to avoid grinding the nozzle into the sheet).

Postato : 11/01/2019 8:56 pm
gnat
 gnat
(@gnat)
Noble Member
Topic starter answered:
Re: Crash detected, now strange behavior

First time doing a live Z calibration, so that took all afternoon and evening 🙄

I'm not sure I have the Z dialed in just right yet, but it seems to be behaving as expected again.

Additionally after doing all the live Z tests, I ran a .05 treefrog from the factory card and that is the best looking .05 print I've done to date. Previously such prints from my .4 nozzle were really "hairy" and even the .25 nozzle results didn't wow me. Maybe it wasn't as dialed in from the factory as I thought...

MMU tips and troubleshooting
Postato : 12/01/2019 6:08 am
Condividi: