[Firmware 3.2beta3] Can't resume after a filament-error0.g
-
@Krohm-Koala, does normal pause and resume work correctly?
Please post your resume.g file.
-
Hi @dc42, normal pause and resume work perfectly, i don't know why but filament errors resume automatically without calling the resume (it stays at Z pause height).
I've just tested in the last pre-release beta 4.1, exactly the same thing.Here is the resume.g
; resume.g ; called before a print from SD card is resumed ; ; generated by RepRapFirmware Configuration Tool v2 on Tue Dec 25 2018 07:35:06 GMT+0100 (heure normale d’Europe centrale) G1 R1 X0 Y0 Z5 F6000 ; go to 5mm above position of the last print move G1 R1 X0 Y0 ; go back to the last print move M83 ; relative extruder moves ;G1 E10 F3600 ; extrude 10mm of filament
-
Hi @dc42 I've just updated to the 3.2RC1, still act as before, is there something i can do to have more info about what's going on at this moment ? If it can help, could be good I don't know if i'm the only one to have this issue.
-
Can you confirm if this is still a problem in 3.2 RC2?
-
@Phaedrux I've just tested, yes, still a problem in 3.2 RC2.
-
@Krohm-Koala said in [Firmware 3.2beta3] Can't resume after a filament-error0.g:
@Phaedrux I've just tested, yes, still a problem in 3.2 RC2.
Can you confirm that you are running regular RRF on your Duet in standalone mode, not the SBC version?
-
@dc42 Yes I'm running a duet2 wifi with regular rrf standalone (never really fond how sbc works on duet 2 )
-
Are you turning any axis motors off while the print is paused? Resume.g won't be called if any axes are flagged as not homed.
-
@dc42 No i don't turn any axis off, i just move the extruder + some meta code (exactly what i've put in my first post), it's weird that it's resuming directly after the purge is ending (i have a dialog to validate normally before i do anything else but it skip that) and it don't call resume.g
-
Hi @dc42, i've just installed 3.3.1Beta (it goes a lot better when you are doing it right ) and tested a thing, i've put an echo command at the end of my file, and it does not display it at all, even in the console, do you think it can be related to too much M291 or a certain type that made it crash ?
-