strange error en 3.5.1

Tinchus

Dont ask me why, but in my case I found this: I lauched THE SAME gcode again and the only difference I tried was commenting the power failure configuration on config.g:

; M911 S21.0 R23.5 P"M913 X0 Y0"

MY resurrect-prolog.g file has this:

M116 ; wait for temperatures
G91 ;
G1 E-1 F200;
G1 Z5 F80;
G28 X0 Y0;
G90;
M83 ; relative extrusion
G1 E2 F3600 ; undo the retraction that was done in the M911 power fail script
M25 ; pause

I know: a M226 should not triggered this file right? so it makes no sense to me why7 would affect or cause this behaviour. Thing is: I commented out the M911 command on config.g, rebooted printer, launched the same gcode again, pause was made as expected, I changed the filament and print was resumed without problems.

droftarts

@Tinchus Any time you pause a print from SD card, the state of the print is saved to sys/resurrect.g. It shouldn't actually run any command in that line, but yes, it may be a reason for the error.

When it ran the M226 before you made this change, did the print actually pause, ie move off the print, before the print was cancelled? Or was it cancelled straight away?

Ian

Erinell

@droftarts said in strange error en 3.5.1:

Could you try adding M400 to the beginning of pause.g?

Just tried this and nop, same issue.

The problem is apparently appening randomly to me, sometimes it works and sometimes it doesn't.
the steps are :

M226 triggered
printer go to pause position
(do a manual filament swap or something else)
resume print
the printer go back to print position
the print stop with the error and heaters (bed and nozzle) turn off

Tinchus

@droftarts The first try with M226 did the pause correctly as expected: it paused and moved off the print as pause.g instructed. I changed the filament, did some manual extrusion to purge the old color from the nozzle, and when I press resume, it was then that the error poped out and the print was cancelled.

Before that, I did another try , this time I was using kisslicer, the M226 was also executed well, filament was changed, and then the print resumed well too, but the print failed because of another problem (the resume script that kisslicer uses had a mistake of my responsability).

It was on between these prints that I noticed than from the print with kisslicer and the print attemp with superslicer, the only difference (apart from the gcode generator, but the M226 was in the same layer so...) was me introducing the M911 command on config.g ans so I decided last night to remove that command and try again.

But in short: M226 seems to be excuted correctly, pause.g is executed, the error pops out when resuming the print.

droftarts

@Tinchus @Erinell Thanks for the reports, this is one for @dc42 to have a look at.

Ian

dc42

@Tinchus please install RRF 3.5.2-rc.1 and confirm (or otherwise) whether the issue still exists.

Tinchus

@dc42 I truied, did the sudo apt steps but that version is not released?

T3P3Tony

@Tinchus it is now! please give it a go.

Tinchus

@T3P3Tony ok, updating now. Any particular border suation instructions you may wanna me to try?

Tinchus

@T3P3Tony I got this:

Incompatible software versions

The installed software versions do not match. Please operate your setup only at equal versions to avoid potential incompatibilities and unexpected errors.

Please check out the docs on how to upgrade your Duet software components.

T3P3Tony

@Tinchus how are you upgrading?

also refresh the browser then check what versions are installed for the various components on the system tab of DWC.

br7408

Is this issue confirmed fixed with the update? I'm on 3.5.1.

I did an M600, where I had my printhead move into position for a filament change on my filament-change.g

For filament-change.g I have an M291 to resume, followed by an M24.

I tested it on a small 7 layer test print to verify, and it worked flawlessly.

On a very large and expensive print, after filament change, on resume it returned to 5mm above the resume point, then dove the extruder deep into the print and then stopped. Time and expensive material wasted.

Also got the "Error in GCode file line XXXX" and "Axis X is already in use by a different motion system. "

Those errors were not present on the test print either.

Tinchus

@T3P3Tony Sorry forr delay in answering Tony, I as out of office. Update seems to have corrected the failure. Im not sure 100% because I have done only 3 attemps and were partial attemps, I have not tried to amke it fail. For now I guess it is solved, but I have noticed during these test another problem, I will create a separate post for this now (it is an unload problem)