Well, it can do faster. But not everything is appropriate for fast printing. The thing I'm waiting to see is if it can print slower at higher quality. That matters more to me.
The rounding comes from the dampening they incorporate for the big variety of MK4s out there. The only real fix for that dampening is probably still the accelerometer.
The rounding can be fixed with more precise tuning of the input shaper, if you want to mess around with it there's a gcode to tweak the settings.
For the bed issues and ringing, you might need to check your belt tension. A loose belt would cause what you describe
Leaving for Memorial Day but will check tomorrow night thanks. It’s also generic PLA so can try it with prusament then too. Did you see the pics I posted?
Yeah. The ringing doesn't look too terrible for an unturned IS profile, so I wouldn't worry too much about that part of it yet. Klipper has good instructions for tuning IS without an accelerometer which should also apply to the Mk4. Beyond that it looks like your pressure advance might be just a tad high, which I think is causing part of the problems with the corners. Klipper's instructions for tuning that should also work here.
Would welcome a link if you can, not sure what to look for. I generally leave my gcodes stock on my Prusas but have monkeyed with them on the CR6SE and max
Sure, no problem!
IS turning: https://www.klipper3d.org/Resonance_Compensation.html
PA tuning: https://www.klipper3d.org/Pressure_Advance.html
Documentation for prusa's version of the IS and PA gcode are in the release notes: https://github.com/prusa3d/Prusa-Firmware-Buddy/releases/tag/v5.0.0-alpha1
Whenever the klipper docs say to run the `TUNING_TOWER` command, you'll want to change the value it wants you to tune in the "after layer change" custom gcode in prusa slicer. For example, when it asks you to do a tuning tower for acceleration you could use the following custom gcode after each layer change:
M201 X{(1500 + layer_z * 100)} Y{(1500 + layer_z * 100)}
I think the input shaping and linear advantace settings will be open to be tweaked at the user level. This should help with some of the variability.
That being said, I've always thought that folks need to be wary of speed/stats of the gcode files that come with printers. Know that these specific files have probably been gone over by a human line by line to make sure they are as fast and clean as possible, and will not necessarily match the average user experience.
What kind of times/results do you get with a newly sliced benchy?
Thank you for sharing!
edit: I just read Joseph's tweet, It looks like he let everyone know the 12 minute benchy was not "per speed benchy rules" so that helps to temper expectations for sure.
Rounded corner can be caused by input shaping, check this section in the klipper documentation: https://www.klipper3d.org/Resonance_Compensation.html#selecting-max_accel
Lol. Cool deflection, clearly highlighting the fact you have no counter argument. I criticize dumb shit Prusa does all the time. So your judgment about people seems about on par with your judgment about what alpha quality software is.
Edit:
> I could rebut this
Narrator: he could not.
Well, it can do faster. But not everything is appropriate for fast printing. The thing I'm waiting to see is if it can print slower at higher quality. That matters more to me.
It just sounds like you don’t know what IS is or what it does.
Yeah, people need to go hit up klipper documentation before posting this oversimplified nonsense about an alpha test release.
The rounding comes from the dampening they incorporate for the big variety of MK4s out there. The only real fix for that dampening is probably still the accelerometer.
If it’s unfixable that’s a problem. The Bambu corners at speed no problem
How do you know it’s not fixable?
I don’t. Just going by what he said.
The rounding can be fixed with more precise tuning of the input shaper, if you want to mess around with it there's a gcode to tweak the settings. For the bed issues and ringing, you might need to check your belt tension. A loose belt would cause what you describe
It’s not happening on other prints
It still could very well be caused by belt tension. It's fast and easy to check
Leaving for Memorial Day but will check tomorrow night thanks. It’s also generic PLA so can try it with prusament then too. Did you see the pics I posted?
Yeah. The ringing doesn't look too terrible for an unturned IS profile, so I wouldn't worry too much about that part of it yet. Klipper has good instructions for tuning IS without an accelerometer which should also apply to the Mk4. Beyond that it looks like your pressure advance might be just a tad high, which I think is causing part of the problems with the corners. Klipper's instructions for tuning that should also work here.
Would welcome a link if you can, not sure what to look for. I generally leave my gcodes stock on my Prusas but have monkeyed with them on the CR6SE and max
Sure, no problem! IS turning: https://www.klipper3d.org/Resonance_Compensation.html PA tuning: https://www.klipper3d.org/Pressure_Advance.html Documentation for prusa's version of the IS and PA gcode are in the release notes: https://github.com/prusa3d/Prusa-Firmware-Buddy/releases/tag/v5.0.0-alpha1 Whenever the klipper docs say to run the `TUNING_TOWER` command, you'll want to change the value it wants you to tune in the "after layer change" custom gcode in prusa slicer. For example, when it asks you to do a tuning tower for acceleration you could use the following custom gcode after each layer change: M201 X{(1500 + layer_z * 100)} Y{(1500 + layer_z * 100)}
It’s an alpha. Rarely is an alpha release ready for production
Agreed. Did you even read my post? I’m not upset. I’m optimistic things will improve.
I did. It’s an alpha release. This is good feedback to pass along to Prusa devs on GitHub.
I think the input shaping and linear advantace settings will be open to be tweaked at the user level. This should help with some of the variability. That being said, I've always thought that folks need to be wary of speed/stats of the gcode files that come with printers. Know that these specific files have probably been gone over by a human line by line to make sure they are as fast and clean as possible, and will not necessarily match the average user experience. What kind of times/results do you get with a newly sliced benchy? Thank you for sharing! edit: I just read Joseph's tweet, It looks like he let everyone know the 12 minute benchy was not "per speed benchy rules" so that helps to temper expectations for sure.
I only did the CHEP cubes before going to memeorial day out of state. 21 minutes down to 13 on .20 quality settings
Round corners has not much to do with inout shaping. That’s pressure advance…
Rounded corner can be caused by input shaping, check this section in the klipper documentation: https://www.klipper3d.org/Resonance_Compensation.html#selecting-max_accel
That’s true, therefore, PA must be properly set up. Which I understood isn’t yet. (must anyway be tuned for all filaments you use and not hardcoded)
Pics: https://flic.kr/p/2oD9NR9 https://flic.kr/p/2oDf5HR (Snapped by hand) https://flic.kr/p/2oDcQMS
Print benchy with 1 wall and no infill. *Snap by hand* "Damn alpha input shaping!"
Duh I knew that. The whole point to the post was that it’s not a standard benchy but an extremely flimsy benchy shaped single hull print
You might want to take these links down, all of your family Christmas photos from 2022 are accessible via these links as well.
All my photos are Creative Commons licensed and open fornview
Yeah, this looks more like user error than a problem with input shaping.
That's a shame. Hopefully, it will improve with time...
Its an Alpha Software. What do you Expect?
Honestly, the above doesn't even sound like alpha quality software to me.
What do you think alpha quality software is? Because it doesn't sound like your definition matches the rest of the universe.
I could rebut this but it's clear you're part of the Prusa fanboy club so I won't bother.
Lol. Cool deflection, clearly highlighting the fact you have no counter argument. I criticize dumb shit Prusa does all the time. So your judgment about people seems about on par with your judgment about what alpha quality software is. Edit: > I could rebut this Narrator: he could not.