Accelerometer Usage

[jbergene]

@diy-o-sphere switched the wiring from the daughterboard pinouts to the Paneldue pinout with same results.

[DIY-O-Sphere]

@jbergene

M955 P0 I61 C"io0.out+io0.in"               ; Define IO for accelerometer

[jbergene]

@diy-o-sphere M955 P0 I61 C"io0.out+io0.in"
Error: M955: Unknown pin name 'io0.out'

[DIY-O-Sphere]

@jbergene
Sorry, thats for a Mini5+

[jbergene]

@jbergene
update

it worked when removing the Paneldue and disabling paneldue in the config file.
(still using Daughter board pins)

[jbergene]

@jbergene Now I get another issue and that is the Duet2 just reset every time I try to record. It some how manages to record something, but the CSV file is invalid.

Duet also states that the LISD3H is aLIS3DSH which is incorrect. (the board have LIS3DH typed in on it)

[Phaedrux]

@jbergene said in Accelerometer Usage:

Duet also states that the LISD3H is aLIS3DSH which is incorrect. (the board have LIS3DH typed in on it)

Photo of the board?

And can you send M115 to report the specific firmware version?

[oliof]

@dc42 how'd you do InputShaping for IDEX machines? In independent head mode, I guess I can set the InputShaping for each head in tpre#.g, but what about copy mode / mirror mode? I guess to keep with the program, the task here is to build the IDEX machine so a common InputShaping setup for X and U is viable?

[dc42]

@oliof said in Accelerometer Usage:

@dc42 how'd you do InputShaping for IDEX machines? In independent head mode, I guess I can set the InputShaping for each head in tpre#.g, but what about copy mode / mirror mode? I guess to keep with the program, the task here is to build the IDEX machine so a common InputShaping setup for X and U is viable?

For now, yes. In future we RRF may support different shaping on the X and U print heads.

[jbergene]

@phaedrux

[dc42]

@jbergene can you read any markings on the accelerometer chip? You may need to find the correct lighting angle to see it.

[tekstyle]

i got my accelerometer installed using a usb3 cable, i was able to get it working even over 3meters!! i generated the csv files but right now i am stuck at figuring out how to make use of the data. how do i know which frequency to use in M953 Fnn? do i actually need to print something to tune even with the accelerometer? i was under the impression that printing and measure ringing and calculating Hz wS only needed if you dont have an accelerometer to generate the csv files.

[Phaedrux]

@tekstyle See here: https://duet3d.dozuki.com/Wiki/Accelerometers

Having the accelerometer is just the first step. You will need to do some test movements to get readings and then analyze them to determine which frequencies are needed to use with the input shaper.

[jbergene]

@tekstyle thats smart! i will try that

[oliof]

@phaedrux the documentation currently lacks the two crucial sentences, how to find out the dominant frequency of an axis ... but the InputShaping plugin will solve this eventually (-:

[jbergene]

@dc42

8937
c3H
0KK1F?

[CCS86]

@oliof said in Accelerometer Usage:

@phaedrux the documentation currently lacks the two crucial sentences, how to find out the dominant frequency of an axis ... but the InputShaping plugin will solve this eventually (-:

This feature is barely in beta form. You can't really expect comprehensive documentation at this point.

[oliof]

I am not expecting comprehensive documentation at this point. As I wrote I am looking forward to the eventual solution via the InputShaping plugin.

[tekstyle]

@phaedrux i have the accelerometer plugin. i was able to visual the graph for all 3 axis. i just dont know what to look for as the link provided isnt clear on how to interpret the data to figure out which hz to use. or i am just not understanding the content.

[Phaedrux]

@tekstyle No you're right. That part is coming and hopefully will be more automated by the plugin to suggest what it should tune out, among other things.