A plain G30 command doesn't do any XY movement, it probes at the current XY coordinates and sets the Z height.

installed and configured....works perfectly! 😄

thx for the help

@dc42 said in Microstepping in relation to deviation?:

Deviation visit the root mean square average of the height error at the probe points.

Thank You DC42, Something clicked in my head and I went back and looked at the the repeatably of my trigger height and started messing with the smart effector sensitivity. Correcting this fixed everything. I am around 20um deviation now, Also thank you to everyone else who lent me their guidance.

@synergy41 said in Z axis adjustment:

@synergy41 said in Z axis adjustment:

G31 X0 Y25 Z2.745 P500; Set the zprobe height and threshold
Thank you David,
That seems a lot to me now.
On the other hand if I want to crush one can my 1st layer, I must play on this line: G31 X0 Y25 Z2.745 P500; Set the zprobe height and threshold.
That's right ?
you must increase or decrease the value of Z.
Thank you for everything.

You can do that; however if you want to crush the first layer deliberately, I suggest you either use the "Z offset" facility of your slicer if it has one, or use M290 to send an absolute babystepping command in your start GCode.

Thank you very much now all axis home perfect.

Consider tuning retraction and speeds first without any pressure advance, and then adding some in slowly after that.

I would say it really only starts to make a big difference when you start pushing speeds up around 100.

There was some pressure advance specific test files as well that make it easier to dial in separately.

FSRs don't like heat; but if they are sufficiently well insulated from the bed then it is better to probe with the bed hot in case it changes shape.

on my first test, adding the G29 S2, seems to have worked

Thanks all, that's solved, my old marlin based printer would use the offset homing z, this doesn't so when id lined up the probe with bed centre it was 35mm out ( the offset) all adjusted now and seems fine

That means G92 will set "homed" flag?
That should be exactly what I want, thanks!

Thanks, i must over read there..

but now it works

Now its done. i have ordered the smart effector and the 400 mm arms by Haydn Huntley. i hope the delivery doesnt take too much time and hopefully its gonna improve my prints.

thanks so far for your help! i will keep you guys updated.

Hi, thanks. I am currently running another print. Its probably user error on my part, but if it stuffs up I wont know why (last print was perfect) so I'll upload the gcode off the printer directly.

While I am not sure how to turn it off, your problem might be that you are not saving the values that were generated in the M303 command. This was a problem for me at one point.

Did you send an M500 command after performing the M303? If so do you have an M501 in you config file?

M501 will use the config override file, which is where the values are saved when you send an M500 after performing M303. Make sure M501 is near the end of config.g.

@simonboydfoley said in Z Offset + ABL + Mesh Bed Leveling: What am I doing wrong?:

G1 X10 Y40 Z0 F1500

Don't use Z0 to do the nozzle wipe, try e.g. Z0.1 or Z0.2.

In your M558 command you have F300 which is quite a slow probing speed. Is that value correct for the piezo?

Your Z acceleration is 250 mm/sec^2 which is quite high for a Z axis with 1600 steps/mm. Try 50 or 100.

@saffi said in Y Endstop False Triggers?:

The switch is fixed to the bottom of the moving bed now

Could it be a dodgy connection to the switch which sometimes breaks as the wire flexes?

The reason that I am sure the problem is mostly with the X carriage movement system is that the X tower is the one at the left hand side of the bed where the biggest ripples are. What's happening is that bed probing is performed with alternately increasing X and decreasing X. When probing reaches the left hand edge and reverses direction, the X carriage has to reverse direction. The ripples show that the initial X carriage movement in the new direction is significantly smaller than commanded, indicating backlash.

EDIT: here is a way to check. Position the head e.g. 10mm above the centre of the bed, then send G91 to select relative movement, then use G1 S2 commands to move the carriages. For example, G1 S2 X0.05 should move the X carriage up by 0.05mm, and G1 S2 X-0.05 should move the X carriage down by 0.05mm. Test all 3 towers this way. I think you will find that when you reverse the direction, the X carriage doesn't initially show any movement.

@AaronGreen, I am sorry to hear you are giving up. Have you considered asking your local Makerspace/Hackspace for assistance, if there is one?

Building your own printer and getting it to work well does often require a lot of effort. It took me two redesigns and over £1000 of expenditure to get my Kossel to the state in which "it just prints" - all due to mechanical issues of various sorts - and even now the Titan extruder still gives me problems occasionally (Bondtech extruder on order).

If designing parts is where your real skill lies, then unless you have well over £1k to spend on a good ready-built printer, getting them printed by others instead may be a wise decision.

Good luck!

If you run G29 S1 it will load the heightmap.csv file unless you use the P parameter to specify an alternative filename.

You can check that mesh bed compensation is enabled using M122. Look for "Bed compensation in use: mesh" in the report.