Input Shaping Plugin Issue

rmark1

Hi,
I am having issues with the Input Shaping Plugin. It keeps telling me that my axis are not homed, yet they are.

I am using:
Board: Duet 2 Ethernet (2Ethernet)
Board: Duex5
Tool: Duet3D Accelerometer
DWC: 3.4.6
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.6 (2023-07-21)
Plugin: InputShaping-3.4.1-b1

The ACC. is being recognised, but I cannot get past this constant request to home the axis. I have looked everywhere I can think of to make sure I have correctly setup the plugin and the Acc., but no joy.

Anyone able to help??

Many thanks,
Richard.

Input Shaping 1.png

Input_Shaping.g

zapta

@rmark1 did you home all axis including z?

rmark1

Hi @zapta
Yup, I even made sure all were at zero as well. If I click on the "Home All" button in the window they are all homed and the window remains with the same "Machine not homed" message. It really beats me as to what is wrong, unless the plugin is not working properly.

Cheers,
Richard.

rmark1

Just found the 3.4.6 version of the plugin, uninstalled old version and installed new one - no difference, sigh!

Richard.

chrishamm

@rmark1 Please share your config.g.

rmark1

@chrishamm
I have started to split it out into more manageable chunks so I have uploaded the various bits. I have previously uploaded the file I use to enable the accelerometer (input_shaping.g) but have included it below..

Thanks,
Richard

config.g
config-axes.g
Input_Shaping.g

tas

@rmark1 You have created your accelerometer in input_shaping.g but you require one more step.

You need a second call to M955 so set the orientation of the sensor, sample rate and resolution.

For example:
M955 P0 C"spi.cs2+spi.cs1"
M955 P0 I25 S5000 R10 ; S5000 is 5000Hz sample rate. R10 is 10 bit resolution.

That may be your problem.

rmark1

@tas
Ah, I thought that I only needed to leave it at the defaults. I will give it a try later today.

Many thanks,
Richard.

chrishamm

@rmark1 I guess the UV axes are not visible and not homed. That may be the culprit. I'll work out a fix.

rmark1

@chrishamm
Sorry, been busy of late, not been able to test anything yet.

Did you manage to work out a fix?

Thanks,
Richard.

chrishamm

@rmark1 Sorry, it's been a while before I could get back to this. I just released Input Shaping plugin v3.4.7 (to be used with DWC 3.4.X) which should fix the problem you faced.