RE: 6.5.3-beta Firmware for PrusaCORE One/+
Also, found one bug so far (which I've raised in github). The heatsink fan keeps cutting on and off even though the printer is in an idle state.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Also, found one bug so far (which I've raised in github). The heatsink fan keeps cutting on and off even though the printer is in an idle state.
This was a bug before, I think it got fixed in the last firmware. Now it's back.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Sadly I did not store the old values
RE: 6.5.3-beta Firmware for PrusaCORE One/+
You're right, I seem to remember it was in 6.3.x, was supposedly fixed in 6.4.0.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Not sure if the printer should be able to pause on power fails or not--haven't tried. But any error should be the correct one, I think.
There's currently a big windstorm where I live. The power just glitched several times in a 60-second or so interval while I was printing after upgrading today to 6.5.3. When I went to the printer to assess the state of things, the screen was red and claimed there was a chamber maxtemp error. After pressing reset, the chamber temp was only 35C.
I guess I'll be getting a small solar generator to guarantee clean power.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
BSOD isnt fixed, I just got it.
Well they've made some snazzy screen display now with a QR code that just links to the Prusa page regarding the issue. I sent them logs.
Surprised they haven't been able to nail this down tbh.
RE:
BSOD isnt fixed, I just got it.
Well they've made some snazzy screen display now with a QR code that just links to the Prusa page regarding the issue. I sent them logs.
Surprised they haven't been able to nail this down tbh.
That's disappointing.
How were you able to generate logs now? I have always found that the BSOD occurs at such an early stage (in the boot loader) that no logs were written.
Edit: Oh, and could you share that link to the Prusa page? Thanks!
RE: 6.5.3-beta Firmware for PrusaCORE One/+
BSOD isnt fixed, I just got it.
Well they've made some snazzy screen display now with a QR code that just links to the Prusa page regarding the issue. I sent them logs.
Surprised they haven't been able to nail this down tbh.That's disappointing.
How were you able to generate logs now? I have always found that the BSOD occurs at such an early stage (in the boot loader) that no logs were written.
Edit: Oh, and could you share that link to the Prusa page? Thanks!
Yeah youre right, I was trying to get the logs when I posted. The issue occurs too early as you say.
Here's the url:
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Yeah youre right, I was trying to get the logs when I posted. The issue occurs too early as you say.
Here's the url:
Thanks! New and much improved, I see: The BSOD is now black.
Maybe they should not show a message that explicitly asks for log files when there are none. I guess the same BSOD is also displayed for some nasty firmware errors where log files are indeed written. But for the boot loader crash, this screen just adds confusion and lets the user waste time looking for log files.
Better yet, maybe they should fix the darn thing. I can't believe they did not get a handle on this, six months after 6.4.0 alpha. 👎
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Ugh, on the bootloader BSOD. Even though it wasn't officially fixed, I had hoped the code update would have at least shuffled this around a bit.
Clever on changing the BSOD to black. I guess it'll be brown, beige, burgundy, bronze, brass, bistre, buff, Byzantium, bamboo, etc. next.
RE:
Printer seems less noisy after firmware update and input-shaper and phase stepper calibration then before.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Printer seems less noisy after firmware update and input-shaper and phase stepper calibration then before.
Indeed, this "bugfix" is being presented as if it were minor (a single line in the release note), but simply correcting the swapped calibration values could lead to major improvements. I understand why Prusa would not publish a blog post saying, "Hey, we significantly improved print quality and reduced noise", because they cannot really make that claim confidently without clearly explaining what was actually fixed.
Did you see improvements on ringing/ghosting?

