Topics created by cbrunnem2

@cbrunnem2
Ad. 2 - I have M558 just to change probing speed - first fast pass for less acurate, and second slower for better accuracy
Ad. 4 - The closer to leadscrews You probe the better the results will be (more accurate). This has nothing to do with area used for printing or mesh leveling. It is just to make sure bed.g will set left and right bed motors correctly too keep bed parallel to the gantry. G32 is not the same feature as mesh bed leveling. G32 makes sure the bed and gantry are parallel to eachother. Mesh leveling (G29) compensates for bed beeing not perfectly flat.
Ad. 5 - In general it should be fine doing it once, but nothing wrong with doing it more than once
Ad. 6. for homez.g put only homing z there.

; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed Jul 21 2021 18:08:02 GMT-0400 (Eastern Daylight Time) G91 ; relative positioning G1 H2 Z5 F3600 ; lift Z relative to current position G90 ; absolute positioning G1 X100 Y100 F3600 ; go to first probe point G30 ; home Z by probing the bed

that is enough for it.

Then in slicer You have a startup g-code, where You should have:
homing - G28
bed leveling - G32 (this will execute bed.g with probing next to leadscrews, and re-home Z)
mesh compensation enabled G29 S1

Bed probing before each print depends on how stable geometry Your bed has.

i used the input shaper plugging and tried zvd from .1 to .6 at 136 hz and none made it better. see below

whats interesting is that when i use the plugin, when it moves in hte y axis, it appears to be trying to move at 1000mm/s and the y motor skips a lot of steps. my max speed in firmware is 300mm/s and i know its trying to go faster than that.

also, i know the m953 command is working as when i turn it on and send the below command the travel is super weird if i have the smoothing at .99.

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

maybe these are just modes i can't get rid of? i do think that a majority of the vibration the accelerometer is seeing is the physical shaking of the whole printer. the printer itself shakes and is not on the best of surfaces so thats a thing. if this algorithm doesnt cancel out that type of movement maybe that could be put into the wiki?

2021-11-02 22_49_14-My Printer.png 2021-11-02 22_49_24-My Printer.png

@phaedrux hmm this could be the ticket here.

yall are awesome. just needed some good nudging to get to the right path. also fixed some things too that i didnt know needed fixed!

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

Sorry for the inconvenience.