mid print stall RRF 3.4B2

Nuramori

I noticed this on the toolboard diagnostic. Is this indicative of anything?

"Last software reset at 2021-08-23 15:12, reason: WatchdogTimeout, available RAM 2680, slot 0"

dc42

@nuramori in RRF 3.4 beta 3 I fixed an issue that caused prints to stall in beta 2.

Nuramori

@dc42 thanks, good to know and I’ll install it ASAP. Any idea from what I posted above, if it was similar to the bug you found?

Nuramori

@dc42 unforunately, the issue was not resolved with the latest beta. I just had the same print I listed above, stall again, this time I could not pull any diagnostic, as the window said a reset was needed.

CadetC

@nuramori
What motors do you use for xy, ? I am surprised at the low current you have set for them. Another thing, and here I ask because I can not find any info on M915(stallguard) and T1 parameter - what is it for?

Nuramori

@cadetc I use Moons 0.9 1.5 amp NEMA17's they work great, looking at the torque curve charts and my setup.

The stealthchop stuff that's commented out are from when I was experimenting with it (if that's what you are referring to with the M915 command - it was to set the registers on the driver)

gloomyandy

@nuramori What "window" said that a reset was needed? It would be very useful to be able to see the output from M122 after a stall and before a reset. It may help to hook up a USB console and obtain the m122 from that after the stall.

Nuramori

@gloomyandy It was a dialog box stating that the machine had to be reset to continue - I didn't screenshot it, though I mentioned it in a previous post from me, with the exact wording. When that box comes up, there's no action possible, so I can't execute a M122 command to get data, and a restart wipes the ability to get the info related to the stall.

The original post contains M122 output from both the main board and the toolboard the one time I could perform a M122 command.

If it happens again, I'll try a USB connection to cull out info if possible.

gloomyandy

@nuramori I've tried to find your post with the details of the stalled dialog in it but failed. If you get chance it would probably help to see exactly what that wording was.

Nuramori

Im not sure if this is related, but ever since the following happened, things are now printing well.

After the mid print stalls, I had a temp sensor fault. The sensor itself was fine, so I performed an auto tune with the new beta. The result was notably different than the values I had before (which were generated with beta 2). Once I did that, I then was getting temp faults on the bed. I then auto tuned the bed and that too were notably different values.

Once I used the new values for the heaters, everything has been running perfectly fine. The same gcode has completed without a stall for multiple prints of the same file.