Reset Randoms
Hello people. I bought a factory assembled MK4 and the first thing I did was install the Input Shaper firmware on it. The reality is that 2 out of 3 prints, the printer has reset itself. From what I saw, there is no way to continue printing. Has anyone had these Reset Random failures? They are impressions of between 2 and 5 hours.Thank you
RE: Reset Randoms
I experienced this earlier today for the first time. My MK4 kit has been printing flawlessly for about a month since I built it. I happened to be in my workshop today as it was printing something (I'm having some other printing issues so was watching it for a bit) and it just reset as if someone had pressed the Reset button. When it rebooted it had completely forgotten about the print it was part way through with no way to continue.
RE: Reset Randoms
Pretty sure I've just experienced this again. I had a 3 hour print fail yesterday due to the nozzle catching the print and shifting it all sideways - it had about 30 small objects on the bed to print. Decided to try it step by step today and just print in batches of 4. Sliced in PrusaSlicer and pushed direct to the printer via PrusaConnect from PrusaSlicer. It should have been a 12min print.
Just gone to the workshop to check to discover its literally stopped dead mid-print. The first shot shows the "ready to print" screen that always appears when I turn the machine on, then you can see the nozzle is stopped dead in a part of the bed. Once I manually adjusted the Z-axis you can see the part has come away from the bed with the nozzle:
Feels like there is more to this, as I'm seeing a range of random issues as documented in this thread and this thread.
RE: Reset Randoms
To add, whilst I was typing my last reply I tried sending the print from PrusaSlicer again. Exact same thing happened - the printer stopped dead in the same position and had obviously rebooted on its own mid print.
PrusaConnect is confused:
RE: Reset Randoms
- Did you tray to save the gcode directly on the USB and then plug in and tried to print it ?
There is a Firmware BUG on the 5.0.x that randomly corrupt the transferred GCODE (via Wi-Fi or Ethernet) and when the g-code file that contains garbage is printed, anything can happen. Often the garbage can't be so easily identified since it contains random pieces of other gcode intermixed with the good one!
This can happen or can't. Depends. But when it happens, it can make big damage (e.g. even smashing the axes).
It is not yet solved and there is a long discussion on gitub with developers that are struggling to understand where the bug is.
It seems that the 4.7.2 non IS is unaffected.
RE:
Hey everybody, I've been experiencing this reboots on my MK4 since last week too. I was printing for about a month without any problems with 4.6.4 firmware, then I upgraded to 4.7.2 and at first I've got BSOD several times and now after I downgraded to 4.7.0 and then back to 4.6.4, I get random resets too.
With BSOD its dangerous as the nozzle is left with active heating still touching the printed object.
I print using Octoprint (OctoPi), but after the problems occured, I tried printing directly from USB, which resulted the same.
Today I upgraded to v5.0.0-RC1 and printing just small objects to test it out.
RE: Reset Randoms
It seems that the 4.7.2 non IS is unaffected
Folks have reported corruption with 4.7.x, so I don't think it's safe to assume 4.7.2 is unaffected.
RE: Reset Randoms
It seems that the 4.7.2 non IS is unaffected
Folks have reported corruption with 4.7.x, so I don't think it's safe to assume 4.7.2 is unaffected.
same here, tested 4.7.2. and 4.7.0
RE: Reset Randoms
- Did you tray to save the gcode directly on the USB and then plug in and tried to print it ?
There is a Firmware BUG on the 5.0.x that randomly corrupt the transferred GCODE (via Wi-Fi or Ethernet) and when the g-code file that contains garbage is printed, anything can happen. Often the garbage can't be so easily identified since it contains random pieces of other gcode intermixed with the good one!
Not yet but I've seen that thread and the github issue. Been away so one of my tasks is to do the filediff and then share it via github to see if it helps.
RE: Reset Randoms
Today, I've got 3 failures, first on 5.0.0 RC1 firmware, then 2x on 4.6.4.
5.0.0 RC1 resulting in BSOD, previous versions just reseting the board. And it doesn't matter whether I print directly from USB or via octoprint from my RaspberryPi 4.
I refuse to print anything until this is resolved 😡
RE: Reset Randoms
So, its been a long day and I'm a bit jaded from work, however: I'm pretty sure I'm now getting the random reset on a Gcode file that I've manually saved from PrusaSlicer to my USB drive direct on my Windows PC. I now seem to have 2 files that cause the reset every time I try to print them, one which was sent to the printer via PrusaConnect and one that was copied directly to the USB drive.
Going to do one last test before updating the Github issue...
RE: Reset Randoms
I put mine together more than a month ago and it's worked flawlessly until I installed RC5. I've been running the printer practically non-stop. Is there any reason to not roll back the firmware?
RE:
Similar story to me - my printer worked brilliantly from the moment I put it together but has gone downhill the past week or 2. Really frustrating as I was starting to understand so much more about the whole design -> slice -> print workflow but now feel I'm spending more time problem solving and throwing failed prints away.
I'm about to roll back to 5.0.0 Alpha4 to see if that helps.
Anyway, I've opened Github issue #3219 for my random resets - be useful if others could add their own experiences to see if it helps support to resolve it.
RE: Reset Randoms
I've contacted Prusa support with this problem and they are sending me new xbuddy motherboard as they are unable to find out the reason of this behaviour based on the crash reports.
RE: Reset Randoms
My MK4 was prebuilt and I just received it within the past week. It works fine with 4.7.2 but once I tried 5.0 RC1 the printer will not home Y. Funny how some people are running 5.0RC with no problems and others are having different issues.
RE: Reset Randoms
Interesting that they are sending a new board out - please let us know how you get on once you receive it.
RE: Reset Randoms
Interesting that they are sending a new board out - please let us know how you get on once you receive it.
Of course, I estimate it arrives at Monday. But it would not prove anything, a new printer was just fine for 2 months and then problems started... So even if it behaves first, will see in long term how it ends 😉
RE: Reset Randoms
I rolled back the firmware from RC5 to 4.72. I successfully ran an 1.5 hour print last night and am 8.5 hours into an eleven hour print. I think the firmware is to blame.
RE: Reset Randoms
I've rolled back to the IS 5 Alpha firmware and one of the G-codes that was causing a reset has just successfully printed, however I did notice it was slowing right down whilst printing quite a bit. No other issues though.
I've got another G-code to try and confirm if it was a fluke or if the older firmware fixes it for me.
RE: Reset Randoms
I've rolled back to the IS 5 Alpha firmware and one of the G-codes that was causing a reset has just successfully printed, however I did notice it was slowing right down whilst printing quite a bit. No other issues though.
I've got another G-code to try and confirm if it was a fluke or if the older firmware fixes it for me.
But then, why you do not send the culprit g-code to Prusa ?
They would have a perfect tool to reproduce the issue with the new 5.0.0 RC and fix it. 😉