Printer resumed incorrect, 3.4beta3

JayT

Hi,

I am using 3.4beta3 RRF. I have given a 4 day long print and after running for 2 days, it paused due to BTT reporting "Too little movement"

the movement reported was 0, but there was no clog.
when I resumed the print, it was doing random moves.

a) Is there any known bug on 3.4beta3, w.r.t resume of a print? I haven't noticed in 2 day prints or many prints tried before, but recently This is faced this for this 4 day long print .

I donot have DWC on SD card, and M122 on console is too long to read. Can anyone tell me if M122 with any suboption can be helpful here to fetch diagnostics information?

b) is it related to the one reported in the post? someone reported on 3.4beta3
https://forum.duet3d.com/topic/24694/3-4-0beta2-printer-stop-mid-print-with-no-reason-errors/10

Phaedrux

@jayt said in Printer resumed incorrect, 3.4beta3:

BTT reporting "Too little movement"

I assume BTT is your filament sensor?

@jayt said in Printer resumed incorrect, 3.4beta3:

Is there any known bug on 3.4beta3

Not that I know of, but we're up to 3.4 beta 7 now. there have been many fixes. https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta-&-RC

If you're not using DWC, I assume you're communicating via USB terminal? What terminal software? You may need to change your line ending settings to get the entire M122 report.

JayT

@phaedrux :
I have rooted the issue and its not a problem with the firmware version 3.4beta3. X motor stopped and seemed like some over current issue . I have replaced some cables and will confirm if that is indeed the root cause.