6.5.3-beta Firmware for PrusaCORE One/+
Summary
- New features and improvements
- Bed LED progress indicator [C1L]
- Tuned parking position during purging [C1, C1+, C1L]
- Vent grille linked to filament preset [C1+, C1L]
- Preload all MMU slots at once [MMU]
- Bootloader update
- Fixes
- Fixed input shaper axis assignment on CoreXY printers
- Fixed layer shifts during high-speed curved moves
- Fixed crash/BSOD on M501 (restore settings) (#4912)
- Fixed gearbox alignment test showing wrong status when skipped
- Fixed chamber fans showing "Auto" instead of "Disabled" when not in use [C1, C1+, C1L]
This beta release introduces firmware 6.5.3 for the Prusa CORE One L, CORE One, MK4S, MK4, MK3.9S, MK3.9, MK3.5S, and MK3.5.
For MK4S, MK4, MK3.9S, MK3.9, MK3.5S and MK3.5, this is the first 6.5.x release, meaning all features and improvements from firmware 6.5.0, 6.5.1, and 6.5.2 are also included.
MMU3 owners please note: you need to upgrade the firmware in your MMU3 unit to version 3.0.4 (https://github.com/prusa3d/Prusa-Firmware-MMU/releases/tag/v3.0.4&sa=D&source=docs&ust=1773131390056718&usg=AOvVaw1-toj-3WO51cdOwPWjwVd X" rel="nofollow">download link).
Bed LED progress indicator [C1L]
The CORE One L bed LED indicator now shows the progress of your print, starting from the left and gradually changing from white to blue.
Tuned parking position during purging [C1, C1+, C1L]
The parking position on CORE One and CORE One L has been adjusted so that purged filament flows unobstructed to the bottom, reducing potential debris on the print bed.
Vent grille linked to filament preset [C1+, C1L]
The vent grille now automatically opens or closes based on the target chamber temperature set in the active filament preset. This ensures optimal thermal conditions during printing.
Preload all MMU slots at once [MMU]
The new menu item Filament MMU - Preload All now asks for the filament type only once and applies it to all slots. This is handy when you want to load, for example, five PLA filaments.
Bootloader update
The bootloader has been updated to version 2.6.0. This creates the necessary foundation for the upcoming INDX upgrade.
Fixed input shaper axis assignment on CoreXY printers
The input shaper X and Y axis parameters were swapped on CoreXY printers, meaning the shaper configured for X was actually applied to Y, and vice versa. This also prevented users from disabling input shaping on only one axis. Both issues are now resolved.
Fixed layer shifts during high-speed curved moves
Layer shifts could occur during high-speed printing with curved moves. The motion system has been improved to address the issue.
Note: Please be aware that not all layer shifts have been caused by this issue.
Release notes
https://github.com/prusa3d/Prusa-Firmware-Buddy/releases/tag/v6.5.3-beta
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Should I update or wait ?
RE: 6.5.3-beta Firmware for PrusaCORE One/+
I just did the update and the first print of half an hour in two colors completed without any problems.
Now I’m starting a print of more than 3 hours in one color to see how that goes.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
I'm an early adopter so I'll update tonight. What I really want to know is more about the input shaper values. Is the wrong data being applied to the X and Y and nobody knew, or is this more of a labeling issue, but somehow the appropriate data was still correctly applied? Did it affect use of the accelerometer?
RE:
As far as the input shaper, I think it would have only mattered if there was a large difference and it was using a different shaping filter. For example if was ZVD 56hz for Y and ZVD 59hz for X and they were swapped around, I doubt there would be a noticeable difference. If was 46hz MVD vs 59hz ZVD then maybe.
I've installed it and so far OK. Hopefully the bootloader BSOD has been fixed.
What is interesting is that they fixed a g-code bug I reported awhile back that was supposed to have already been fixed in 6.4.0.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
I'm an early adopter so I'll update tonight. What I really want to know is more about the input shaper values. Is the wrong data being applied to the X and Y and nobody knew, or is this more of a labeling issue, but somehow the appropriate data was still correctly applied? Did it affect use of the accelerometer?
My understanding is that it was the former: Accelerometer measurements worked, but then the calculated X input shaping (typically faster) was getting applied to the Y axis, and vice versa.
RE:
Seems the RGB status bar showing print progress doesn't work. It just stays a solid blue during the print. Will try a couple of more prints then raise an issue on github for it.
RE:
Seems the RGB status bar showing print progress doesn't work. It just stays a solid blue during the print. Will try a couple of more prints then raise an issue on github for it.
It's only for the Core One L. Not sure why; I was under the impression that the Core One uses individually addressable LEDs too. (But might be wrong about that.) Maybe there's just too few LEDs for meaningful progress display?
RE:
Seems the RGB status bar showing print progress doesn't work. It just stays a solid blue during the print. Will try a couple of more prints then raise an issue on github for it.
If you mean C1 or C1+ (it's not clear from your text, but since you're writing about C1/C1+ in the thread, it probably is) the color bar that changes color only applies to CORE/L, which probably has a bar created by programmable LEDs. Those are not on C1 or C1+.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
It's only for the Core One L. Not sure why; I was under the impression that the Core One uses individually addressable LEDs too. (But might be wrong about that.) Maybe there's just too few LEDs for meaningful progress display?
C1 and C1+ use ordinary strips of tri-color LEDs where they all light up the same color. LEDs are not programmable.
RE:
Seems the RGB status bar showing print progress doesn't work. It just stays a solid blue during the print. Will try a couple of more prints then raise an issue on github for it.
It's only for the Core One L. Not sure why; I was under the impression that the Core One uses individually addressable LEDs too. (But might be wrong about that.) Maybe there's just too few LEDs for meaningful progress display?
Ah OK, missed the C1L. Probably because there are only 5 LEDs across the whole bar and not individually addressable. Wonder if this is upgradeable in some way? I wouldn't mind having a visual status bar. I'm assuming it would need a firmware patch as well.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Hopefully the 2.6.0 bootloader fixed the BSOD issues on startup.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Ah OK, missed the C1L. Probably because there are only 5 LEDs across the whole bar and not individually addressable. Wonder if this is upgradeable in some way? I wouldn't mind having a visual status bar. I'm assuming it would need a firmware patch as well.
It would probably be upgradeable, even the power transistors on the expansion board to power the colors on the LED strip could be canceled. But that's not necessary, the signal could also be transmitted using the existing HW. FW modification would of course be necessary. Inspiration would be found in the FW for C1L. But the question is this: Would it have any benefit at all in terms of effort? Maybe Pruša will offer it in some update to C1++.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Hopefully the 2.6.0 bootloader fixed the BSOD issues on startup.
No updates in the Github cases yet...
RE: 6.5.3-beta Firmware for PrusaCORE One/+
. But the question is this: Would it have any benefit at all in terms of effort? Maybe Pruša will offer it in some update to C1++.
Not really. It would be a fun mod none-the-less.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
given that we can queue jobs remotely, think we'll ever get remote firmware upgrades? still user-controlled of course
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Updated new firmware and redid calibration of input shaper
X Axis MZV 46Hz
Y axis ZVD Herz
Whatever this means, 20Hz difference would seem much if attached to wrong axis. Will have to make an print today and see which effect firmware and calibration will have
RE: 6.5.3-beta Firmware for PrusaCORE One/+
Updated new firmware and redid calibration of input shaper
X Axis MZV 46Hz
Y axis ZVD Herz
Whatever this means, 20Hz difference would seem much if attached to wrong axis. Will have to make an print today and see which effect firmware and calibration will have
What were the results of the previous calibration? With the new beta firmware I also get a similar result. With 6.4.0 firmware I had values of 94/96hz ZVD which in this case if X and Y were swapped it shouldn't make a difference.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
With 6.4.0 firmware I had values of 94/96hz ZVD
Are you sure you are not getting these mixed up with the belt frequencies? Those numbers seem very high.
RE: 6.5.3-beta Firmware for PrusaCORE One/+
With 6.4.0 firmware I had values of 94/96hz ZVD
Are you sure you are not getting these mixed up with the belt frequencies? Those numbers seem very high.
Yes, early morning for me. 64/66hz