faint flume
I was setting up sensorless homing according to the vorondesign docs and it seems to stutter oddly in place while homing, but moves fine afterwards, does anyone know what could be causing this?
For additional information I've attached a video, and I am using the Octopus 1.1 with TMC2209 drivers, my sensitivity is currently 1 for testing
languid wadi
can you also upload a klippy.log file so we can see your settings?
wicked bear
I was setting up sensorless homing according to [the vorondesign docs](https://d...
Have u seen the reply above?
faint flume
oop, I'll get on that right away, ty
wicked bear
oop, I'll get on that right away, ty
its always the best that once u create a post or ask something, that u are actually around to reply, so we get this solved ASAP and dont have to wait and wait and wait 😉
faint flume
faint flume
its always the best that once u create a post or ask something, that u are actua...
I apologize greatly, here it is
wicked bear
I apologize greatly, here it is
all good, just be around in the future 🙂 it also helps if u click on your flag in #rules so we know your timezone
faint flume
all good, just be around in the future 🙂 it also helps if u click on your flag ...
done
oop, no external emojis :((
languid wadi
so, casual observations as i work my way through your log
driver_sgthrs = 1 is saying that you want stallguard to be the least sensitive possible, so it should ram into your endpoints very hard. the fact it's not is puzzling.
run_current= 1.4 is quite high for a stock voronf
wicked bear
1 with 2209?
languid wadi
indeed
wicked bear
interesting 😄 havent seen that one yet
languid wadi
the range is 0-255, 255 being the most sensitive, so a breath of wind should trigger stallguard
faint flume
I figured initially it was the sensitivity, which is why I have it turned all the way down
I'll turn the current back down, the current solved another issue, but if it's a little high, that's worrying 😅
languid wadi
contrary to the guide, i would generally suggest new-tuners start somewhere in the middle e.g. around 120
wicked bear
I'll turn the current back down, the current solved another issue, but if it's a...
the current solved another issue
Which issue?
faint flume
Let me see if I could recreate it
languid wadi
everything else, from a sensorless point of view, looks ok-
diag pins configured appropriately
homing speed more than rotation distance
homing overrides present
virtual endstops configured
faint flume
So, this is the motor stalling, maybe the belts are too tight? I've checked and checked my belt routing
wicked bear
So, this is the motor stalling, maybe the belts are too tight? I've checked and ...
post pictures of both A and B drive from the back so we can see the belt route please
how did u tension belts?
phone app? by feel? etc
languid wadi
we need a bot command for "the thing"
faint flume
faint flume
how did u tension belts?
phone app? by feel? etc
Just by feel
wicked bear
Just by feel
thats not a good way to measure
get yourself the belt tensioner https://github.com/Diyshift/3D-Printer/tree/main/GT2 Belt Tension Meter many vendors, see github, in the US sell them
languid wadi
you don't appear to have done "the thing"
wicked bear
where are the M5 screws?
faint flume
hm, must've happened when I was rebuilding the thing.. good catch
wicked bear
my current bet is on too tight belts
faint flume
I'm going to make a stop by West3D as I'm only a half hour away from it
Need to grab a few things, including that tensioner
wicked bear
also your Z chain doesnt look correct
please compare it with the manual and CAD
chain, not belt. sorry
faint flume
Yeah.. it's not, I had that realization last night, I'll fix it once I get back, thank you
Should I ping anyone once back?
languid wadi
spitz and i are both europe based so may be asleep
faint flume
Alright, thank you for all your help
dull zodiac
The z belt clips might also be backwards. Hard to tell in the image though.
wicked bear
Alright, thank you for all your help
its been 19 days, how are things going? Do u have an update for us?