Voron 0.2 - belt comparisons/low vibrations/loud

[slender elm]

Hey all, got my 0.2 mostly built save for the doors etc. now, and I'm seeing some odd results in the belt comparison plot that I'd really like to resolve. In addition to this, I'm getting some pretty severe resonance from the printer at relatively low hz.

Default LDO 0.2 build + ADXL345 sensor, mounted at top of toolhead on Pico toolhead board.
Belt tension was measured by app.

[input_shaper]
shaper_type_x = mzv
shaper_freq_x = 75.4
shaper_type_y = mzv
shaper_freq_y = 66.8

Will follow up with shaketune results due to picture limits

[viscid drum]

what are u using to tension belts?

[slender elm]

Used the app to measure initially, then followed a few rounds of the belt tension comparison from klippain to fine-tune a bit as the tensions weren't quite equal. This is by far the 'best' place it's been in

[viscid drum]

unfortunately u did not click on your flag in #rules so i have no clue where u are from.
best thing to have is the tension meter https://github.com/Diyshift/3D-Printer/tree/main/GT2 Belt Tension Meter

[viscid drum]

and in your input shaper section u are missing the damping_ratio by the way 🙂

[slender elm]

Aha, will add and rerun, ty

[viscid drum]

it wont do much

u have some issue on X

but im not sure what at the moment since it is a V0

[slender elm]

It's worth noting I've not run the autotune yet, but I feel like there are mechanical issues to solve first before that

[viscid drum]

yea autotune wont help here

u can set it up though

[slender elm]

Its all installed, just not yet run or made any changes :)

[median onyx]

What is your goal?
Based upon your cube I am not seeing any resonance.

what I am seeing is slight PA/EM issues

[viscid drum]

i agree with Reth, there isnt any ringing or ghosting visible.
what would be interesting is to have a look at your slicer profile, to determine if u are even printing close to the recommended accel
to give us this opportunity could u please slice the VORON Cube with the settings u used for the cube in this post, export it as a .3mf and tell us which slicer was uesd so we can import it properly please.

if u need help with autotune, ping me and im happy to help

[slender elm]

Honestly ive done no calibration on this filament at all - my query was purely around the graphs, however the rules asked for a cube print. For now its all whatever speeds orca defaults to!

The extreme volume at the 75hz and the odd bump on the x axis seemed weird

[median onyx]

This is the age old question-graphs vs prints.

Go with prints everytime

It is one of the reasons we ask for prints

—- in regards to the volume are you talking audible noise or are you referencing the peak on x at 75 hz

[slender elm]

Sorry for the slow response, had a household emergency. It's a lot of noise, particularly at that 110hz area - I've re-run the belts and set tension etc. again, checked the paths are good and bearings are smooth - and largely getting the same results, if not a bit worse.

I'm going to do some EM & PA tuning and bump up the accelerations and see where I'm at with the print, I just can't shake the feeling something is off with the X axis

[slender elm]

Interestingly, one of the side panels has visible marks from the belt touching it (under a heavy light) - might go some way to explaining some of my belt graph issues

[median onyx]

There is a macro called "excite at freq"
if you click the arrow on the right side you can enter the axis, freq, and time
for your try x axis, 107 hz, for 45 sec
Do this once and just listen.
Then do it another time looking an listening.
and try to find where the noise is coming from if any

[slender elm]

With the default profile in orca but with the acceleration turned up a bit I'm starting to see the effects of this - particularly on that x axis. Will try and find the source of that spike with the excite at freq. This is with panels off to not rub on the belt at all

Belts are looking a touch healthier now

[viscid drum]

could u tell us please which slicer this was exported from so we can properly import it 🙂 ?

[slender elm]

Orca!

[viscid drum]

thanks.
could u please run the vibration test/profile from Shaketune

[slender elm]

Sure thing, will run it now

[median onyx]

can you install TMC_Autotune please

Also, where are getting your run_current from?

In regards to your x-axis, after checking my notes the closest thing I can find is a potential bearing issue.
Can you reduce belt tension by a 1/4 of a nub on both x and y. It might be to much tension causing this

[slender elm]

Haven't tinkered with the config yet, its purely the LDO default one for now. Autotune installed but not run, so will sort that and reduce belt tension, ty

Will also disassemble x afterwards if reduced tension doesn't sort - parts for the tension gauge are in the post & parts are currently being printed

[viscid drum]

If u need help with autotune let me know. It can be tricky with sensorless

[median onyx]

cool thanks for the update

[slender elm]

Tension meter now printed and assembled - will be with the printer again later and will get the current measurements.

[viscid drum]

sounds good 🙂

[viscid drum]

how are things going? any update for us?

[viscid drum]

were u able to get us some measurements with the tension meter?

[slender elm]

Hey, sorry for lack of response - I left it printing a few parts to see how it printed in reality rather than just benchmarks - example attached. Looks like I'm not really having any belt issues that are causing print artifacts and in fact just need to stop tweaking them for the theoreticals and instead move on to actual EM & pressure advance tuning. Both belts were at 2.1 on the tension meter.

[viscid drum]

looks pretty clean 🙂 not seeing ringing

are other prints looking the same?

[slender elm]

Yup, it's serving as a "backup" printer for the 2.4 hence printing parts for that as my tests. Little closer on the EM with this filament until I ran out (just using spare bits here and there for testing purposes!)

[viscid drum]

awesome

[viscid drum]

so i would call this solved and close the post 🙂 do u agree?

[slender elm]

Absolutely, thank you for your help with this!