Switching to performance mode -> z-tilt screws up

Upgraded to 3.1, toolhead and beacon With Mikkels help (thanks👍 ) I managed to set my three z-tilt probe points manually to suitable coordinates. After continuing with further commissioning and tuning, I finally came to the point where I switched to performance mode. I used the configurator to do that ( still not so familiar RatOS2.x). That completely screws up my z-tilt motion. Toolhead moves to weird positions and even bumps into limits - eg. in the front. So I tried a manual approach by adding to printer.cfg: [printer] max_velocity: 800 max_accel: 10000 minimum_cruise_ratio: 0.5 max_z_velocity: 50 max_z_accel: 600 square_corner_velocity: 5 [gcode_macro RatOS] variable_macro_travel_speed: 600 variable_macro_travel_accel: 8000 [bed_mesh] speed: 600 [z_tilt] speed: 600 Same problem. Z-tilt goes haywire with printhead all over the place. So how can I switch my 3.1 on RatOS2.1.0-RC3 to performance mode?
Solution:
this doesn't look like skipping, that looks like loose pulleys
Jump to solution
33 Replies
miklschmidt
miklschmidt2mo ago
debug zip, i'll take a look, your printer should definitely be able to handle those speeds in performance mode, unless you're using non-stock steppers with less torque / velocity ?
BlueDun
BlueDunOP2mo ago
Thank you Sir!
BlueDun
BlueDunOP2mo ago
And I'm using trusty 2226. Theve been serving me well for the last three years on my 3.0 under RatOS 1.X. in performance mode.
BlueDun
BlueDunOP2mo ago
BTW ... observations that trouble me a bit in understanding how RatOS2.X works. Maybe that is associated with my problem: I'm coming from RatOS 1.x and argumenting from that viewpoint: - Why are my printer.cfg and ratOS.cfg lacking includes for steppers and speed limits? Actually, my printer.cfg differst a lot from what I see in the template on github for a V-Core 3 (https://github.com/Rat-OS/RatOS-configuration/blob/v2.1.x/templates/v-core-3-printer.template.cfg) - When I use the configurator to switch to performance mode, the settings for the drivers are not changed. Current remains at 1.1A and TBL,TOFF, HEND, HSTRT remain unchanged as well - Why is the configurator changing my printer.cfg? The way I read the documentation, the configurator updates ratOS.cfg which then becomes the sole include in printer.cfg. But when I use the configurator (like now for switching to performance) it alters my printer.cfg and actually deletes all changes I manually added?
GitHub
RatOS-configuration/templates/v-core-3-printer.template.cfg at v2.1...
The RatOS modular klipper configuration. Contribute to Rat-OS/RatOS-configuration development by creating an account on GitHub.
miklschmidt
miklschmidt2mo ago
yeah those are fine. I was talking about the actual stepper motors though 🙂
miklschmidt
miklschmidt2mo ago
Why are my printer.cfg and ratOS.cfg lacking includes for steppers and speed limits? Actually, my printer.cfg differst a lot from what I see in the template on github for a V-Core 3 (https://github.com/Rat-OS/RatOS-configuration/blob/v2.1.x/templates/v-core-3-printer.template.cfg)
That is handled (and is now much more custimizable) through the motion section on the hardware configuration page. It's inlined straight into RatOS.cfg so it's easy to find and copy / paste from if you need to.
GitHub
RatOS-configuration/templates/v-core-3-printer.template.cfg at v2.1...
The RatOS modular klipper configuration. Contribute to Rat-OS/RatOS-configuration development by creating an account on GitHub.
BlueDun
BlueDunOP2mo ago
Motors are stock from the factory kit
miklschmidt
miklschmidt2mo ago
When I use the configurator to switch to performance mode, the settings for the drivers are not changed. Current remains at 1.1A and TBL,TOFF, HEND, HSTRT remain unchanged as well
The current should change (except if you already changed it manually), but this explains the issue, 1.1 is not enough to run the performance speed settings, and i don't think the 2226 have tuned presets (unless you just select the BTT 2209's which are basically identical).
BlueDun
BlueDunOP2mo ago
Léet me switch to performance again and make a screenshot ... hang on
miklschmidt
miklschmidt2mo ago
if performance mode is enabled you should be able to see a recommendation for 1.6A in the motion configuration (enable "advanced") well that's provided you select drivers that have tuned presets (which the 2226 don't have at the moment, but the 2209 settings should be transferable) i can add them. Just a sec. Actually it should work with the 2206! They're marked as 2209, so should be all good.
BlueDun
BlueDunOP2mo ago
Just went to configurator, switched on performance mode, but current values remain at 1.1 ...
No description
BlueDun
BlueDunOP2mo ago
And regarding the 2226. AFAIK they are identical to 2229 but in adifferent package ...
miklschmidt
miklschmidt2mo ago
Odd, will see if i can reproduce that and fix it. Anyway, set them to 1.6 and you should be good 🙂
BlueDun
BlueDunOP2mo ago
But question ... how can low current values lead to probe points all over the place ??
miklschmidt
miklschmidt2mo ago
Your steppers are skipping
BlueDun
BlueDunOP2mo ago
That much ???
miklschmidt
miklschmidt2mo ago
doesn't take much at all, every time they skip they skip at least 4 full steps and that's a permanent offset
BlueDun
BlueDunOP2mo ago
Ok then ... I'll set the values to 1.6 manually and report back ...
miklschmidt
miklschmidt2mo ago
Of course i can't be sure without seeing a video of what happens, but all you've described so far tracks with that theory awesome 👍
BlueDun
BlueDunOP2mo ago
But what about TBL,TOFF, HEND, HSTRT? Hang on ... just observerd something I went to 2229 in the configurator and now the values are updated.
BlueDun
BlueDunOP2mo ago
No description
BlueDun
BlueDunOP2mo ago
see ... stepper X is updated (2229) but stepper Y not (2226)
miklschmidt
miklschmidt2mo ago
Yeah that makes sense however flipping performance mode on/off should do the same thing to all of them
BlueDun
BlueDunOP2mo ago
Dya think I should give it a go with 2229 settings? That would also take care of TBL,TOFF, HEND, HSTRT
miklschmidt
miklschmidt2mo ago
2209 *. And sure you can do that, it's the same configuration anyway. these should still be applied with 1.6A on 2226 if they're not i need to look into that
BlueDun
BlueDunOP2mo ago
OK, I'll do the following. I stay with 2226 and change current manually. Then I'll check if TBL,TOFF, HEND, HSTRT are updated. And I'll do the same with 2229 selection and see if the printer survives 🤪
BlueDun
BlueDunOP2mo ago
Well ... I can confirm that manually setting the current in the configurator will adap TBL,TOFF, HEND, HSTRT to correct values.
BlueDun
BlueDunOP2mo ago
Well ... the first attempt failed. The behavior seems better at first, but my probe points are "drifting" away from each run to the next one. Clear indication for skipping .... Very strange. I'ts the same hardware as before the 3.1 upgrade and I never had issues in performance mode ... Could it be associated with sense resistor value? The old 1.x version stepper configurations do not specifiy that value. And now I see it specified in RatOs.cfg.
BlueDun
BlueDunOP2mo ago
Alright ... new findings. I went back to conservative settings and printed a temperature tower. And I'm observing layer shifts. Another indication for slipping. I conclude that I'm facing two issues. First: If the configurator is set to 2226 drivers, switching to performance mode will not update stepper settings in RatOS.cfg.. That appears to be a bug in RatOS/Configurator. Second: I observe layer shifts/slipping in conservative mode on a hardware that has been running flawlessly for the last three years under RatOS1.x in performance mode. THAT leaves me clueless at the moment. My first impulse is to order a set of 2209's. But then again ... my hardware ran fine before.
No description
No description
Solution
miklschmidt
miklschmidt2mo ago
this doesn't look like skipping, that looks like loose pulleys
miklschmidt
miklschmidt2mo ago
Check that your pulley's on the motor shafts are properly tightened If you didn't use locktite, they can loosen over time from vibrations. I think this is exactly that. There's not really anything else that can produce this.
BlueDun
BlueDunOP2mo ago
@miklschmidt Maenge tak!! Slipping solved. RatOS rocks🤘🤘 🤘 I'm official supporter now 😉 "2600-Configurator" bug remains. Were you able to reproduce?
miklschmidt
miklschmidt2mo ago
Haven't had the time yet, i've added it to my backlog, will get it fixed once i get the big stuff out of the way! However i think i know why it happens, i believe it only changes the current for the default drivers, so if you change the driver type it'll not make any current changes automatically so as not too cause problems with those drivers. just a safety precaution But i need to double check if my memory is correct, been a while since i wrote the logic
I'm official supporter now 😉
That is very generous of you, thank you ❤️
Want results from more Discord servers?
Add your server