A value of about 30 seems to work just fine.

Ahh, yes, the plugin looks to be more like what I was expecting. Everything just seems to vague "Choose a shaper that suppresses those frequencies effectively"? How do I know what the shapers do. Does everything have to be trial and error?

It is a funny story. I don't know how but my setup changed from a CoreXY to being Cartesian. So when I told it to move it was only turning 1 stepper at a time. I am still totally in the dark as to how it happened.

@jay_s_uk
Yes, that worked. OK, so now maybe I can start to tweak the settings until it works. -127 definitely causes an instant stall

My D-bot has some fairly bad ghosting so I am hoping that input shaping will be able to help. I have wired up my accelerometer and it is working just fine. Now comes the confusing bit. How do I record any data. Even the official webpage has practically zero detail on how this is done. From the youtube videos that I've watched it looks like I need to do a print. The duet3d documentation simply says "Use command M956 to collect accelerometer data.". Do I add a single M956 at the end of the gcode, after every movement, it doesn't say? Rather than simply relying on trial and error I was hoping that there may actually be a guide showing me exactly what I need to do.

If anyone has setup input shaping then please let me know how I go about collecting data.

thanks

@dc42
Yes, I have read that. It tells me almost nothing. What are all the shapers? Nothing is actually explained.

Ahh, yes, the plugin looks to be more like what I was expecting. Everything just seems to vague "Choose a shaper that suppresses those frequencies effectively"? How do I know what the shapers do. Does everything have to be trial and error?

@dc42
Yes, I have read that. It tells me almost nothing. What are all the shapers? Nothing is actually explained.

My D-bot has some fairly bad ghosting so I am hoping that input shaping will be able to help. I have wired up my accelerometer and it is working just fine. Now comes the confusing bit. How do I record any data. Even the official webpage has practically zero detail on how this is done. From the youtube videos that I've watched it looks like I need to do a print. The duet3d documentation simply says "Use command M956 to collect accelerometer data.". Do I add a single M956 at the end of the gcode, after every movement, it doesn't say? Rather than simply relying on trial and error I was hoping that there may actually be a guide showing me exactly what I need to do.

If anyone has setup input shaping then please let me know how I go about collecting data.

thanks

A value of about 30 seems to work just fine.

@jay_s_uk
Yes, that worked. OK, so now maybe I can start to tweak the settings until it works. -127 definitely causes an instant stall

I have reduced the current to the steppers so that they stall as soon as they start to move. Yet all they do is continue to try to move. I was assuming that they would stop moving as soon as they stall?

OK, I am now on 3.3 and the results are the same. Just lots of belt slipping as the head crashes into the side of the printer.

@dc42 Thanks, I'll give that a try.

@t3p3tony I set it to -64 and it still doesn't stall

M915 X Y S-64 R0 F0

@t3p3tony Yes, that is the document that I have been using