![Rat Rig Community [Unofficial]](https://cdn.discordapp.com/icons/582187371529764864/08375bea6b5b9088b6d4cfc2b6e25fba.webp?size=48){kind=icon}
Generate Shaper graph kills printer
When I try to generate shaper graphs, I get an internal error on command: "test_resonances".
Hplease try to add this to your printer.cfg and try again
H@dyocis
Hohh i see, its a klipper bug
H@miklschmidt found a bug in the klipper CHIPS name parsing
Hid doesnt allow to use other chip types than adxl, so atm idex doesnt support lis2dw chips
or am i wrong?
or am i wrong?
DAhh, ok. I thought I had run shaper graphs since installing IDEX...Hmm. guess not
Hyeah, it looks like current klipper code doesnt allow the use of the orbitool accelerometer chips
DI know I've run it in hybrid
Hthats of course a problem
Hwell, it works in single toolhead mode, but for idex we need to switch between the chips and klipper expects or adds the adxl345 prefix to the chip name
Hbut you need the lis2dw prefix
DMakes since. Well, just add it to the list of problems I've created for myself because I can't leave things stock....lol
Hi will try to file a bug for klipper, but i cant promise anything
DSounds good. I'll test it occasionally and let you know if it gets fixed
DShould I close this post, or keep it open till it's fixed?
Hno, keep it alive please
M@dyocis you can use the realtime analysis tool instead
DI'm doing that as I type!
MAh nice! 
MGENERATE_RESONANCES AXIS=XGENERATE_RESONANCES AXIS=YOtherwise it'll be combined and you won't get the shaper results. You'll get a tension comparison instead.
H@dyocis i shared the finding on the klipper discord with theg guy who coded it, but as i said before i cant promise anything. i wouldnt have high hopes for it to be fixed
DYea, I saw the debacle around the z hop problem a few weeks ago. I don't have high hopes either.
DDo the shaper results get saved somewhere or do I just need to look at the realtime graph? I looked in the input shaper folder, but nothing new is in there
M@Helge Keck looks like this was already fixed https://github.com/Klipper3d/klipper/pull/6726
GitHub
-The current code does not have the option to "live" select a non-adxl345 chips when running TEST_RESONANCES, since it adds the adxl prefix by default.
-Added the ability to &...
-Added the ability to &...
MYou can look at all your macro recordings, just click on "view all macros"
MOr you can click the link in the notification that pops up when it completes
DYea, I figured it out. It's the first time I'm using the macros in the tool, so I'm learning
MThe navigation needs a bit of love 
MWe can update the pinned commit, but i have not had the opportunity to test the past two months of klipper changes
Hahh, was jsut confused bc his logfile clearly showed this error. so its fixed but not part of RatOS atm, got it
Mexactly
DWould the belt comparison macro be GENERATE_RESONANCES AXIS=XY ?
DOr two separate sequences with X in one and Y in one?
MGENERATE_RESONANCES AXIS=1,1and another sequence in the same macro with
GENERATE_RESONANCES AXIS=-1,1For tensioning the Y belts you can do:
and another sequence with
Remember to select the T0 accelerometer for the first sequence and the T1 accelerometer for the second.
and another sequence with
Remember to select the T0 accelerometer for the first sequence and the T1 accelerometer for the second.
MThose are coordinates for a 400mm, change accordingly for a 300 or 500
MIe Y in both and X in the latter.
SI have a similar error after mounting an AXDL345 on my rat rig and I'm not as technically inclined as a lot of other people on here, my printer appears to keep crashing after doing a frequency test - this one occurred after I did the "MEASURE_COREXY_BELT_TENSION" command
BStart your own post please
DAny idea when this fix will be implemented in RatOS? I was hoping that the most recent update would contain it, but I tried it last night and I'm still getting the shutdown when I try to run IS
MAny idea when this fix will be implemented in RatOS?Just pushed it this morning
MAre you on 2.0 or 2.1?
D2.1
MThat works.
MAre you sure you updated?
MPost a debug zip
D