Hopefully i'm not distracting from main discussion, but i'm having similar issue with .9 degree steppers on a HEVO with titan aero direct drive.

I recently bumped my X/Y steppers to 85% max rating and my printer is crazy noisy now, but my VFA has really gone down.

To verify i'm not just seeing crap, i'm going to run a test again right now with high rating and lower and see if it proves it out... changed so many settings i'm not even sure anymore.

curious if running at 100mm/s keeps the motors out of quiet mode and changes how they algorithm works - as that may explain why super high power ratings may do something similar.

thanks all! got it all figured out. It didn't click that i had it wired in a series with the 2 A:B setup... I put them on 2:4 and i have auto leveling perfection finally! so happy since i'd just done a bunch of motor swaps and new plum connectors for the z rods so it was super easy to get level after fixing this!

Just to update, i swapped out cooling ducts - what a huge difference. I also tossed out this white PLA and used another brand and its now printing perfectly. I had to print the old white much hotter than i thought necessary to avoid jams but in doing so it stressed out a bad cooler. fixed both and happy now

Got my Hypercube Evolution running RRF 3.0RC1 with bltouch, dual z leveling (g29) and so far so good!

took a bit to translate my config over, but i really appreciate the text labels now that i'm seeing them in gcode!

Found out my problem. I noticed one side of my printer was always sagging towards end of print, ran motor unlock and i could rotate left z and feel steps, but right z just spun - i guess my right z motor had failed.

Replaced my right z motor, and now bltouch is happy and i don't have to run g29 between each print... kind of surprised i got the quality i did with that motor having been bad or faulty for so long...

but, i'm back in business... no more crazy drift, nice level bed and great prints again. took the time to move to reprap3 firmware and enjoy it too!

Poked around in a sliced gcode from cura - it passes MIX/MAX as comments in beginning of gcode.

;FLAVOR:RepRap
;TIME:1813
;Filament used: 2.3164m
;Layer height: 0.28
;MINX:124.335
;MINY:124.335
;MINZ:0.24
;MAXX:175.665
;MAXY:175.664
;MAXZ:21.45
;Generated with Cura_SteamEngine 4.12.1

Looking to see if those are values that can be used in start... if not, may be able to write a small plugin that set variables

Is there any guide to figuring out input shaping? I can't really wrap my head around it.

I've got the Duet3d accelerometer connected and lit up and when I make a movement I can move an axis but i'm not sure what to do beyond that and when i think i'm moving multiple axis it just moves on the first and stops so i'm not sure what i'm doing.

@dc42 well, here's the odd thing. I read that link and thought I understood it. I was running 3.5rc1 on Github and it would always just move 1 axis and sit there.

Today, I saw you linked a newer RC1+ build. I installed that, went back to read the input shapping page and put in two movements and I got both movements.

So perhaps, i was hitting a bug in 3.5. Now things make a lot more sense - i thought i was missing a step or needed to click the play button that the second movement had next to it.

Now it complete more than 1 axis and it says motion profile #2 is complete.

Now its time for me to see the data and see what to do next may have more questions but at least this latest build unblocked me.

@dc42 awesome, I may give those a try thx for all your great work on this!

Is there any guide to figuring out input shaping? I can't really wrap my head around it.

I've got the Duet3d accelerometer connected and lit up and when I make a movement I can move an axis but i'm not sure what to do beyond that and when i think i'm moving multiple axis it just moves on the first and stops so i'm not sure what i'm doing.

3.5 rc1 seems long in tail - are there blockers for a stable release or has it gone back to drawing board?

@supernovae

Found the issue, I have some commands to set speed on layers and it shows up as X1500 which the regex catches... maybe i'll try and see if i can limit/exclude it lol

@pcr said in Only probe where printed. Solution here!:

@supernovae

easier solution

• (Cura slicer plugin) To make the macro to work in Cura slicer, you need to install the post process plugin by frankbags - In cura menu Help -> Show configuration folder. - Copy the python script from the above link in to plugins folder. - Restart Cura - In cura menu Extensions -> Post processing -> Modify G-Code and select Mesh Print Size (PLUGIN)

the

M557 X%MINX%:%MAXX% Y%MINY%:%MAXY% S8

Not sure if you can help, but running the python plugin and enabling the M557 in start gcode I always get a huge max X

For example:

looking at the gcode output:

M557 X131.900:1500.000 Y131.900:168.100 S35.000 ; Leveling mesh defined by LevelingMeshOptimizer

Not sure where 1500 comes from.. any idea where to look for in fixing/address that? Or anyone getting this in latest cura?

@phaedrux You were right, it finished - took 5110 seconds

Running 3.4b6 and ran m303 h0 s60 to PID tune hot bed after replacing a failed thermistor and it's been running almost 40 minutes

Temperature just seems to be going up and down slowly

Phase 4 has been 25 minutes itself.

@pcr So awesome! Thanks!!

FYI, if its not loading for you, rename the file to match exactly the class name - it is CaSE SenSiTive "LevelingMeshOptimizer.pl"

Found a post processing script for cura here: https://forum.duet3d.com/topic/14994/f-r-auto-define-m557-mesh-bounds-from-gcode/5?_=1637506151764

It would be nice if we could have the firmware parse this as defining it in every tool i use is a pain