RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
Interesting. A search said the reset button is soft and doesn't wipe the eeprom where the power panic print state data is flashed in the power supplies last moment of consciousness...
So after resetting/power cycling after the BSOD, I guess the print didn't resume?
No, no option to resume...after I reset the BSOD it just went to the normal Home Screen. I made an attempt at editing the gcode trying to print the final 3% but it must've been midway through a layer when the power went off so my attempt didn't end well 😂
I can see why a reset (withthe button) on the BSOD didn't restart the print, it would have been interesting to see the result of pulling the plug out of the outlet instead of resetting...
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
In the next release please expose chamber temperature telemetry for the Prusa Core One via:
- PrusaLink local API (/api/v1/status)
- Printer log output (consistent, timestamped)
It is already there in the app and intermittently logged in the log file as part of the "C@:" string, but the logg file is not consistent and shown only a block of temp data and for a long time only prints "[INFO - Marlin:10] busy: processing".
Would be nice to have for analysing fan performance and consistency and other things.
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
I am pretty sure that there is a play between hw and sw to determine when a restart will trigger a print to resume and when not... but trying to find this logic in the fw code is well beyond what I can spend my time doing... I may end up running a test for this during the holiday and see if I can get something ...
Interesting. A search said the reset button is soft and doesn't wipe the eeprom where the power panic print state data is flashed in the power supplies last moment of consciousness...
So after resetting/power cycling after the BSOD, I guess the print didn't resume?
No, no option to resume...after I reset the BSOD it just went to the normal Home Screen. I made an attempt at editing the gcode trying to print the final 3% but it must've been midway through a layer when the power went off so my attempt didn't end well 😂
I can see why a reset (withthe button) on the BSOD didn't restart the print, it would have been interesting to see the result of pulling the plug out of the outlet instead of resetting...
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
I don't blame you. Interested to hear the results of your test. Thanks.
RE:
I am having a lot of nozzle cleanup failures since upgrading to 6.4.0. Didn't experienced them before.
Is there an option to have the printer keep beeping while requiring attention? Currently it just does nothing and sits quietly.
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
I had no problems with the RC, I did have a BSOD with 6.4.0 in the middle of a print. That was extremely irritating.
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
I had no problems with the RC, I did have a BSOD with 6.4.0 in the middle of a print. That was extremely irritating.
Did you ground the motors (many comments in multiple threads in the forum)? So far this kind of crashes are all ascribed to static buildup that can be eliminated easily.
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
I have a core one assembled unit… I really didn’t think I needed to make any modifications related to something like that. it was a very long print job and it failed at 80%.
So printed it in the H2D with PLA supports and it was totally fine and worked like a champ. can’t afford to take a risk on multiple day prints when the units just gonna blow up close to the end of a print….
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
I have a core one assembled unit… I really didn’t think I needed to make any modifications related to something like that. it was a very long print job and it failed at 80%.
So printed it in the H2D with PLA supports and it was totally fine and worked like a champ. can’t afford to take a risk on multiple day prints when the units just gonna blow up close to the end of a print….
It seems "hit or miss" whether the X and Y stepper motors are grounded in a given Core One. The motor chassis may be grounded via the four mounting screws which hold the motor and its mounting block to the CoreXY frame -- but if the paint layer on the CoreXY frame is too good, then there is no ground. Which seems to cause problems only for prints with long, straight moves: The fast, extended belt movement can then cause enough static buildup to eventually cause a discharge.
The easiest way to ensure grounding is to insert a star washer under at least one of the four mounting screws for either motor. Then tighten the screws securely to pierce the paint layer.
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
Alas, this is a known deficiency of the current vore one platform. As @jurgen commented, easy to fix: star washer and optionally scratch a little the paint under the screw head. So far all that had the problem had it disappear after the mod.
I have a core one assembled unit… I really didn’t think I needed to make any modifications related to something like that. it was a very long print job and it failed at 80%.
So printed it in the H2D with PLA supports and it was totally fine and worked like a champ. can’t afford to take a risk on multiple day prints when the units just gonna blow up close to the end of a print….
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
So a star washer under the motor screws... can do. Let's give it a whirl.
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
Just one screw per motor...
So a star washer under the motor screws... can do. Let's give it a whirl.
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
Is the grounding "mod" for just the X and Y motors on the print head gantry, or does it also need to be done for the Z-axis motors in the bottom of the chassis?
Neal
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
Is the grounding "mod" for just the X and Y motors on the print head gantry, or does it also need to be done for the Z-axis motors in the bottom of the chassis?
Neal
Only needs to be done for X and possibly Y. In my case the Y motor housing was already grounded (most likely by accident). The X motor was not so I scraped away some of the powder coating with a Dremel tool.
As an aside, I really wish Prusa relabel these motors as A and B instead. This should cause less confusion since in a CoreXY system both motors turn when moving in exclusively an X or Y direction.
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
Is the grounding "mod" for just the X and Y motors on the print head gantry, or does it also need to be done for the Z-axis motors in the bottom of the chassis?
Neal
I don't know if it is necessary for the Z motors (reading through the explanation of the why it wouldn't apply to the Z motors because there aren't any belts to pick up static on the Z motors), but if so it would take more than just a star washer under one of the mounting screws. This is because the Z motors have the plastic "shock absorber" piece between the motor and the printer's frame. One would need to add a grounding strap between each motor and the frame.
See my (limited) designs on:
Printables - https://www.printables.com/@Sembazuru
Thingiverse - https://www.thingiverse.com/Sembazuru/designs
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
Did Prusa publish a guide for the motor grounding fix?
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
Did Prusa publish a guide for the motor grounding fix?
No. Because to my knowledge, they have never acknowledged it's an issue.
RE: 6.4.0 Firmware for Prusa CORE One + & CORE One
The release notes do not indicate if any tasks need to be performed after installing this firmware.
For example, are there any settings or calibrations that need to be performed after I update the firmware?
Or is it simply: Update and use it?
After updating, run the new belt tuning wizard. It's not mandatory but it's always good to check belt tension. Like checking the air pressure in your car tires.
I hardly ever check the air pressure in my tires 🙁
Thanks for reminding me 🙂