RE: 6.4.0-RC Firmware for Prusa CORE One
Damage caused to my bed with RC - failed to retract on bed levelling procedure putting two long smooth lines in my satin sheet !!
RE: 6.4.0-RC Firmware for Prusa CORE One
Jan, you might want to have someone look at https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/4835 too, at least for triage. I'm quite sure it's a bug that was introduced with 6.4
While a nozzle staying at 250º C or whatever for potentially hours on end is not immediately bad, it's not good either. I didn't test beyond probably about an hour, which happened by forgetting that I had to walk from the printer to my laptop and send it the signal to stop heating the nozzle.
Not sure how crispy/crusty things will get inside the nozzle or if the filament simply oozes out quickly and it's just bare metal being heated.
RE: 6.4.0-RC Firmware for Prusa CORE One
Hi. Our DEV team is aware of it.
Just to be sure, try to replicate this issue with 6.4.0 RC.
RE: 6.4.0-RC Firmware for Prusa CORE One
Yes, very much reproduces still on RC. Will comment ticket.
RE: 6.4.0-RC Firmware for Prusa CORE One
Hi. Our DEV team is aware of it.
Just to be sure, try to replicate this issue with 6.4.0 RC.
Same happened to me. I was fortunate to stop it and rehome before it caused any damage
RE: Bluescreen and Puppy Error with 6.4.0 RC?
My Core One never had any startup problems. But since I installed 6.4.0 RC yesterday (I had skipped the alpha version), I have seen the blue "Unknown Error -- unable to show details" screen three times, and the orange "Puppy Error" once. In all cases, powering off and on again led to a successful start, followed by flawless printing.
Has anybody else experienced such random startup issues with the new firmware?
RE: 6.4.0-RC Firmware for Prusa CORE One
Saw two BSOD with alpha but haven't seen anything yet with RC (been running for 2 weeks).
RE: 6.4.0-RC Firmware for Prusa CORE One
My Core One never had any startup problems. But since I installed 6.4.0 RC yesterday (I had skipped the alpha version), I have seen the blue "Unknown Error -- unable to show details" screen three times, and the orange "Puppy Error" once. In all cases, powering off and on again led to a successful start, followed by flawless printing.
Has anybody else experienced such random startup issues with the new firmware?
I've had that orange error a couple of times on 6.4.0 RC, I've even had it in blue which I thought looked pretty sick.
I just press reset and it restarts fine...prints fine also.
RE: 6.4.0-RC Firmware for Prusa CORE One
Yes, that's the message I get too. I was not sure whether it's really caused by the new firmware -- might also have been something physically deteriorating in my printer, and just a coincidence in timing. But if you get the BSOD too now, and have not seen it before just like me, there must be something wrong with firmware 6.4.0 or the new bootloader 2.5.0 that came with it.
RE: 6.4.0-RC Firmware for Prusa CORE One
Yes, that's the message I get too. I was not sure whether it's really caused by the new firmware -- might also have been something physically deteriorating in my printer, and just a coincidence in timing. But if you get the BSOD too now, and have not seen it before just like me, there must be something wrong with firmware 6.4.0 or the new bootloader 2.5.0 that came with it.
I'm suspecting the 2.5.0 boot loader. Reason is that: I only get this on initial startup, I've also seen after downgrading to 6.3.4 from 6.4.0-alpha, i.e. 6.3.4 with 2.5.0 boot loader.
RE:
I believe the changelog is complete, but there might be parameters that are meant for one function, but influence other without anyone noticed it. That is why we will always check errors from the newest build. This is the same for other companies as when you have some issue, you need to have the latest firmware for proper diagnosis of the problem.
I've raised issue 4879 over on GH concerning the BSOD on startup. Please feel free to pile on over there.
RE: 6.4.0-RC Firmware for Prusa CORE One
For context, I experienced the blue "Unknown Error -- unable to show details" screen recently for the first time while running the current firmware, and haven't seen it since.
RE: 6.4.0-RC Firmware for Prusa CORE One
I'm running 6.4.0-RC+11796, also saw a few BSODs (Unknown Error -- unable to show details) but they always went away with power cycling.
The printer is used occasionally, no heavy user.
I just saw a homing failure (belt tensions / gantry are all "in tune"), banged twice more after "retry" then continued printing.
So, no showstoppers among my observations (IMHO).
RE: 6.4.0-RC Firmware for Prusa CORE One
I've reverted to 6.3.4 - RC not only damaged my bed but had filament retract problems. It removed it from the nozzle tube nut left a blob of filament on the end making it impossible to fit through the extruder and forcing me to open the tension lever and cut and remove from there! After the third time it did it I gave up and reverted and it now unloads properly again.
RE: 6.4.0-RC Firmware for Prusa CORE One
Just loaded it again with the same problem of filiment sensor detects filiment when there is none in the extruder.
reverting back to 6.3.3 so I can continue printing...
PS Bambu H2S and D prints circles around the Core One!!!!
Thanks,
Jim
RE: 6.4.0-RC Firmware for Prusa CORE One
I'm getting a strange issue if I run a print after a successful print. The motors seem to work against each other during moves after I hit print. Sometimes it seems to then move the home location placing the purge line in the middle of the bed and printing further back than expected. This only happened on 6.4.0 A and RC.
RE: 6.4.0-RC Firmware for Prusa CORE One
Just loaded it again with the same problem of filiment sensor detects filiment when there is none in the extruder.
reverting back to 6.3.3 so I can continue printing...
PS Bambu H2S and D prints circles around the Core One!!!!
Thanks,
Jim
I think in this case the filament sensor calibration settings may have gotten wiped. Can try just rerunning calibration.
RE: 6.4.0-RC Firmware for Prusa CORE One
I also get crashes, but only when cold-starting the device (powering it up though the power switch). They don't happen regularly, but maybe 1 / 5 coldstarts are giving me this error:
And it also happens with 6.4.0 RC, but i have no picture of it yet.