Cancel print resulted in printer loading Filament 2 and leaving Bed and Nozzle temp set to PRINT temps
 
Notifiche
Cancella tutti

Cancel print resulted in printer loading Filament 2 and leaving Bed and Nozzle temp set to PRINT temps  

  RSS
(((GRIFFCOMM
(@griffcomm)
Estimable Member
Cancel print resulted in printer loading Filament 2 and leaving Bed and Nozzle temp set to PRINT temps
  • Pi Zero W 2
  • 0.7.0rc2
  • Mk3s + MMU2s
  • b8fc27fc-6ad2-4a4d-aa7e-ae4a757552a93.11.0-4955
  • v2.5.0 x64
  • Sent a print, then cancelled before it started to print, the printer however decided to load Filament 2 (the print was to be filamnent 1) and then left the bed and nozzle heating on abit like it was going to print but never did.  Seems like the cancel only stops sending data, the printer continue to prepare itself for printing.  I would think if the print is cancelled then the printer heating needs to be set to nothing and the filament to UNLOAD (with an MMU2s)

Many Thanks

Postato : 06/03/2023 9:01 pm
Tojik
(@tojik)
Utenti Moderator
RE: Cancel print resulted in printer loading Filament 2 and leaving Bed and Nozzle temp set to PRINT temps

I would like to see the log from this, but I doubt this would be captured in detail. The MMU is not supported. I was waiting for the MMU firmware rewrite to go bugfixing and feature hunting. The FW is nearing completion so I should start working on that, but there are more pressing issues to address.

Postato : 06/03/2023 9:14 pm
(((GRIFFCOMM
(@griffcomm)
Estimable Member
Topic starter answered:
RE:

Hi

I hear "MMU not supported", however should it not cope with color prints?  the dashboard shows PETG, PETG, PETG, PETG, PETG which i think is expect? as all 5 ports are set to something?  If you need logs, let me know as i can try and collect them.

We still have the Pi ZERO v1 with OctoPrint on it, however i really dont want to have to swap this back for color prints.  Cancel prints in OctoPrint also resulted in some odd stuff happening after, so this bug report is more a report to fix that something odd with network printing as OctoPrint doesn't seem to send ANY code when it cancels, it just stops printing, then you have to clear up the printer like manually unload the filament.  I would think though this should be handed with the CANCEL button, it then does a clean up after like setting it to home and unload the filament ready for the next print.

Many Thanks

Postato : 06/03/2023 9:33 pm
Tojik
(@tojik)
Utenti Moderator
RE: Cancel print resulted in printer loading Filament 2 and leaving Bed and Nozzle temp set to PRINT temps

OctoPrint has the option to add a custom script for cancels and stuff. I just send an M603. Without a log orna way to reproduce I'm unable to help. Does it happen every time you start a color print or was it a fluke?

Postato : 06/03/2023 9:48 pm
Tojik
(@tojik)
Utenti Moderator
RE: Cancel print resulted in printer loading Filament 2 and leaving Bed and Nozzle temp set to PRINT temps

Oh, right, you cancelled while heating. Will try what that does

Postato : 06/03/2023 9:49 pm
(((GRIFFCOMM
(@griffcomm)
Estimable Member
Topic starter answered:
RE: Cancel print resulted in printer loading Filament 2 and leaving Bed and Nozzle temp set to PRINT temps

I dont often cancel prints so really not an expert at it, ive have generally with OctoPrint when its cancelled it sets the bed and nozzle to NILL (0) heating.  The filament just stops, so i generally have to unload it manually, ive not had it swap randomly though.

Many Thanks

Postato : 06/03/2023 9:57 pm
(((GRIFFCOMM
(@griffcomm)
Estimable Member
Topic starter answered:
RE: Cancel print resulted in printer loading Filament 2 and leaving Bed and Nozzle temp set to PRINT temps

Yes, on this occasion it was cancellsd while the first heat was running, i would think this is MOST times we cancel, for one of some of the below problems spotted during a first heat:

  • Error in the design to the point ANYTHING printed will be a waste of time
  • A wrong color was used in the Slicer
  • Want to add more (or remove) before the print starts, either a design change (remove part) or one is required faster (only currently have 1 printer so cant just spin another one up for the faster required part).

All the above generally results in a cancel print BEFORE it started printing, but the print was already sent.

Many Thanks

Postato : 06/03/2023 9:59 pm
Tojik
(@tojik)
Utenti Moderator
RE: Cancel print resulted in printer loading Filament 2 and leaving Bed and Nozzle temp set to PRINT temps

Yup, it just sucks to be me in that scenario, as when I send the heat and wait for temperature (one gcode for bed, other for the extruder) the machine covers its ears and starts screaming "lalalala not listening" with the only other option being a reset. I have a plan to work around this but the code is not in a state where that could be achieved easily. Cancel while heating is on my to do list.

Postato : 06/03/2023 10:16 pm
(((GRIFFCOMM
(@griffcomm)
Estimable Member
Topic starter answered:
RE: Cancel print resulted in printer loading Filament 2 and leaving Bed and Nozzle temp set to PRINT temps

UPDATE on this.... we noticed it does the same if we stop the print on the LCD control panel as well (during a print), again it will wonder off, unload filament x then load filament x+1, however i also noticed it does actually turn off the nozzle heater which then means you get a jam as filament is loaded with no head in the nozzle.  I wonder if this is an MMU issue and not PrusaLink?  The nozzle heater is turned back on again at some point but too late (after a filament is loaded with lots of clicking of the gears unable to push solid plastic through an unheated head).

Many Thanks

Postato : 08/03/2023 4:03 am
Condividi: