Im trying to use realtime analysis but im getting an error when i want to display the graph
Here is the debug
Solution:Jump to solution
Aah.. two different accelerometers that runs slightly different sample rates.
61 Replies
I had this issue when using safari on a Mac, but when I switched to chrome everything seemed to work
Im using a chromium based browser
as for chrome chrome... since manifest v3... im out:D
ive tried chrome and its the same error
Seems like the peak matching is doing something weird, pearson correlation algorithm fails because the input arrays aren't the same.
@D00M-_ can you send me the contents of
~/printer_data/RatOS ?one sec
could this also affect the graphs im getting?
for belt tension and shapper?
no it only runs when displaying recorded macro data
fun for me XD , ill have to make a post on #fix-my-resonance cuz something is wrong and i cant figure it out
reproduced, looking into it š
thank you
Solution
Aah.. two different accelerometers that runs slightly different sample rates.
so this could impact all my graghs then?
some of my graghs have close to 0 amplitude
No
š
fml+))
I'll take a look at that after
lisan al gaib
Fixed, it's compiling, ready to update in 10 minutes š
Here's the results in the meantime if you're curious š
thanks man
terible graph
just a sec and i'll take a look at the other graph issues
š¦
yeah IDEX is not the easiest to tune
question, when tuning idex 500 whats a median tuning frequency when using realtime analyisis
i managed to get both peaks on x to converge when tuning 60hz
On X?
the graph above is at 85
I'm not sure, 85 seems high. Looks like your main peak here is 90hz.
this is 60 on x
that is much better for sure
im using the pluck and meassure method with realtinme
but y is imposible
In fact i'd probably go with that, that looks decent
this is my latest y
at 75
Y is hard yes. It takes an incredibly small amount of tension to wreck the whole thing.
main peak here is higher than X, too tight
just finished 70
and its climbing
but they are starting to slap when tuning
all belts are
It seems like there might be some belt length issues here
that's normal
i measured them, cut them to size then counted teeth at the end
they should be virtually identical +/- one tooth
Needs to be equal between each attachment point
oh wow
This looks like quite a lot more than that
any recomandations on how to messure?
I think measuring is slower than just either releasing a tooth on the side that has the highest amplitude or capturing another tooth on the one that has the lowest
Then you can see it on the graph
ok ill try that
whats the ballpark accels i should expect ?
Good question, i haven't tuned a 500 myself
I'd expect somewhere in the 6-7k range
As far as recommended accel goes for Y
ok
before i took it apart a rd time
this is where i was at
t0 y was my issue
Both Y's are effed š
those 20hz to 40 where killing it
It's the hardest part
its been my world for the past 4 days :))
I recommend going to #v-core-4 and asking VisualTech, Helge, Mitsuma and Pinky. They have more experience with IDEX tensioning than i have. The majority of my time was spent on software.
Or #v-core-idex rather
great software i might addXD
š
ill try the tooth counting method
and then if still no
ill make a post
was a pride thing and i was very stubborn to get it right=)))
haha i know that feeling
thx for the help tho š and pointing me in the right direction
You're welcome, thanks for reporting the bug! š