Having a Duet3 6 HC on a CoreXY build
minding to add compatible accelerometer to your bom if you want
print faster than 60-80mm/s

if youre going to add an 1LC toolboard to your printhead, it has an accelerometer inbuild
https://docs.duet3d.com/en/Duet3D_hardware/Duet_3_family/Duet_3_Toolboard_1LC

theres also a guide for orientation by Nuramori:
https://www.dropbox.com/s/hu2w5mk57l4zqpg/Accelerometer Orientation.pdf

With input shaping actually tested are 300mm/s with a tolerance of 0.1 are possible

@norder

• Probe Offsets are correct
• Margin about 15mm, because the limitations added by the printhead dimensions

It was the M parameter or better the P parameter i lack off, so many thanks
i suggested the M one are beginning at zero.
at least i was excepting a gap at end like 270/10.

solved then

Hey,

I had following Problem:

• Printer CoreXY
• Origin at 0 0 / Left Front
  Probe Offset:

G31 P500 X37.50 Y10 Z1.57	

Axis Limits:

; Axis Limits
M208 X0 Y0 Z0 S1                                     ; set axis minima
M208 X300 Y315 Z390 S0                               ; set axis maxima

When i going to probe a point

G30 P0 X37.5 Y10 Z-99999 

Its working like expected, probing a point on Origin as it is possible for the probe.
but when i hit a

G29

with following Mesh

G31 P500 X37.50 Y10 Z1.57			       ; set Z probe trigger value, offset and trigger height
M557 X37.5:300 Y37.5:300 S50                         ; define mesh grid

it is adding the 37.5 to the origin and measure there.
if im define the mesh grid like:

M557 X0:300 Y0:300 S50                         ; define mesh grid

its Skipping all points before 37.5 logically but why the direct probe points are working as expected
and a G29 Going to Origin + 37.5? (basically double the offset and not beeing on the origin as expected)

@dc42
@rogerpodacter

I see theres confusion about the examples, as i mentioned this just examples (picked from the duet doku)
I can now share acutal accelerometer records.
Printer Type: CoreXY

Record no shaping:

Based on what i learned here MZV should suits best in relation to curves

No Shape with MZV curve:

Shaped with MZV

it looks for me pretty well shaped, except a bit the area arround 58Hz-78Hz
So my question that is now remain after i understand most of the whole thing (i guess so, if not correct me in my statements)
Is there any tweaking point on this?

After experimenting a bit i tried modified ZVDDD, if im right this one is lacking because it have a longer frequenzy and give me
almost the same result as MZV?

excuse me again for not beeing clearly enough that i used examples

Edit: Is the MZV Shaper is automatically right on 40Hz, because its the highest peak and the first curve of the shaper, shapes this peak best?

@jay_s_uk
Well... i think thats it for the most basic tuning, didnt get that i was redirected to the old documentation

@dc42
with the infos i now have iam using the input shaping plugin.
before i had it but didnt use it because as i mentioned before.
i think i can discard the command story with the plugin

Than just understanding things here

• Why is ZVD here the most suited
• Why at 46 HZ?

I Know you Ignore the Inital move, but i also can set 73HZ because there alot peaks, something here im not getting. Or it it like the shaper has a static value at which HZ he is compensating and how much?

OK here the ZVDDD sample which looks like better compensation to me as ZVD

Or it is over shaping because it compensate Y and Z of an bed slinger?
If we turn to an CoreXY
is this ZVDDD the better shaper? i mean i can measure X aswell as Y

Hey Guys,

Im lacking of a calibration guide for input shaping, the thing itself is explained but not how to
configure. The three main topics are:

• How to choose the right shaper?
• How to use collected data for analysing?
• How to apply the collected data knowledge for a good result?

Just for info im on RRF 3.4 and later on a Duet3 6HC, SBC setup
Speed settings: (Im not sure about the settings may edit and update my thread when i have acces to my settings)

M566 X1000.00 Y1000.00 Z60.00 E120.00            ; set maximum instantaneous speed changes (mm/min)
M203 X20000.00 Y20000.00 Z180.00 E1200.00        ; set maximum speeds (mm/min)
M201 X10000.00 Y10000.00 Z20.00 E250.00            ; set accelerations (mm/s^2)

So i did 2 Test runs like mentioned:

G1 X-50 G4 S2 M956 P0 S1000 A0 G4 P10 G1 X50 F20000

and

G1 X-50 G4 S2 G1 X50 F20000 M400 M956 P0 S1000 A0

should i modify this commands to get more accurate results to my machine? but ok go ahead
analyse the stuff: (sadly i have no own examples atm, maybe i edit and add it later)

• what should i do with this data? i mean it has no acutally effect on shaping its a sample what should u do to tune your shaping. How?

Tried to adapt from Klipper documentation but the measure method from there is a totally different,
commands are also different.

So i sliced a file with a

M593 P"zvd" F40.5 ; use ZVD input shaping to cancel ringing at 40.5Hz

Ok i get it P"" is the shaper used and F the frequency, theres now the point what do i put in there
in relation of my before collected data?

We have this nice Table

Input Shaper	Shaper Duration	Vibration reduction with default damping factor (0.1)
ZVD	1 / Frequency	± 15% Frequency
ZVDD	1.5 / Frequency	
ZVDDD	2 / Frequency	
MZV	1 / Frequency	± 4% Frequency
EI2	1.5 / Frequency	± 35% Frequency
EI3	3 / Frequency	± -45%...+50% Frequency

Does it mean if i just define the shaper the F will be the dampening factor? for e.g.

M593 P"zvd" F40.5

• Dampening starts at frequency 40.5 +15% = 46,575?

• At a frequency of =>40.5 it will be reduced 15% = 39,425?

• How i set another dampening factor on command?

• Why do not use just an strong input shaper as EI3

I mean the documentation as it is quite good except a bit missing on examples for a full command
at this, but without advanced knowledge the documentation dont give any hints to tune this thing

I Hope to find some help and advise here.

As Phaedrux mentioned follow the instruction there.

Your post read like you're trying to connect to the web panel on Pi which is disconnected to the duet?
It will load forever, wire your sbc setup properly (pi connected to duet) anyway there is no connection to the duet