Hardware requirements:

You will need a probe switch attached to the machine's actuator, or a bed able to trigger an end stop input when the hotend touches it. (FSRs or another method)

Configuration

Add the following to the config file :

gamma_min_endstop            nc                 # normally 1.28. Change to nc to prevent conflict, not needed on Azteeg X5

zprobe.enable                true               # set to true to enable a zprobe
zprobe.probe_pin             1.28!^             # pin probe is attached to if NC remove the !, Azteeg X5 this is 1.29
zprobe.slow_feedrate         5                  # mm/sec probe feed rate
#zprobe.debounce_count       100                # set if noisy
zprobe.fast_feedrate         100                # move feedrate
zprobe.probe_height          5                  # how much above bed to start probe NB only needed for G32 on delta
zprobe.return_feedrate       0                  # feedrate after a probe, default 0 is double of slow_feedrate (mm/s)

NOTE the slow_feedrate is the speed the probe moves down to find the bed, it returns (probe up) at 2*slow_feedrate or return_feedrate. fast_feedrate is only used for any XY moves done during probing.

G30 will probe from the current position until it hits the bed and the probe triggers, it will report the distance traveled then return to where it started.

G30 Znnn will probe until it hits the bed then sets Z to nnn, this can be used to set the nozzle height if nnn is the probes Z offset from the nozzle in the Z direction. NOTE this is NOT supported for deltas, use on Cartesians only.

G30 Fxxx will run the probe at xxx mm/min overriding the slow_feedrate.

G38.2 and G38.3 are also implemented as documented here

If there are multiple levelling strategies selected the Pn parameter will select which one to send leveling codes to, 0 being the first defined one, 1 the second and so on. eg G29 P1 will send G29 to the second defined levelling strategy.

There are several M670 parameters that can set different settings for zprobe overriding the config settings, these are all saved with M500

All options

Leveling strategy options

Delta calibration

Make sure the the config has delta_homing true set.

Also in the config set :

leveling-strategy.delta-calibration.enable   true            # basic delta calibration
leveling-strategy.delta-calibration.radius   100             # the probe radius
#the initial height above the bed we stop the intial move down after home to find the bed
#this should be a height that is enough that the probe will not hit the bed and is an offset from gamma_max (can be set to 0 if gamma_max takes into account the probe offset)
leveling-strategy.delta-calibration.initial_height 10 # height above bed to stop initial move

Calibration routine

Issuing the G32 command will run the full calibration sequence automatically.

It will cycle several times to converge on a good result.

If the result is good use M500 to save the M666 settings.

What will happen is it will home the probe down to find the bed, then home again then move down to 5mm above the bed (or whatever you set zprobe.probe_height to).

Then it will probe the three towers at the specified leveling-strategy.delta-calibration.radius from the center, and will print out the results, it will set the endstop trims and home, this will repeat 3-4 times, each time the difference between the three probes should get smaller, once it has completed 4 probes or the difference is under 0.03mm it will home one last time then probe the three points to confirm the calibration, then probe the center.

It will also adjust the delta radius (M665 Rnnn) to get the center the same height as the outside points.

Use

These are the different ways to use the calibration routine : 

See http://minow.blogspot.com/ for more details of calibrating a delta.

Delta Grid Compensation

Probes delta_grid.size points in X and Y (total probes size * size) and stores the relative offsets from the 0,0 Z height.
When enabled every move will calculate the Z offset based on interpolating the height offset within the grids nearest 4 points.
Should be used in conjunction with the delta calibration strategy above. First calibrate with G32 then if needed do G31 to set the grid compensation.
NOTE The delta-grid.radius specified should be at least as big as the largest X,Y position likely to be moved to. It gets very inaccurate if you try to print outside of the radius you specified.

Configuration

The strategy must be enabled in the config as well as zprobe.

leveling-strategy.delta-grid.enable         true

The radius of the bed must be specified with…

leveling-strategy.delta-grid.radius        50

this needs to be at least as big as the maximum printing radius as moves outside of this will not be compensated for correctly

The size of the grid can be set with…

leveling-strategy.delta-grid.size        7

this is the X and Y size of the grid, it must be an odd number, the default is 7 which is 49 probe points

Optionally probe offsets from the nozzle or tool head can be defined with…

leveling-strategy.delta-grid.probe_offsets  0,0,0  # probe offsetrs x,y,z

they may also be set with M565 X0 Y0 Z0. NOTE setting probe offsets will make the grid less effective the further the probe is from the head, this is especially true if you are using it to correct geometry errors, as they depend on the actuator position not the head position. So having a probe offset from the head will try to compensate for errors which are offset from where the head actually is. There is no easy way to overcome this other than have the probe as close to the nozzle as possible.

If the saved grid is to be loaded on boot then this must be set in the config…

leveling-strategy.delta-grid.save        true

Then when M500 is issued it will save M375 which will cause the grid to be loaded on boot. The default is to not autoload the grid on boot. NOTE the grid size and the radius is saved in the file, and restored when it is loaded with M375. If the grid size is different from the one in config it will NOT load. If the radius is different, then the radius will be set to whatever was saved overriding the one set in config.

Optionally an initial_height can be set that tell the initial probe where to stop the fast decent before it probes, this should be around 5-10mm above the bed

leveling-strategy.delta-grid.initial_height  10

Usage

Three point platform compensation for Cartesians

Also incorrectly called bed leveling.

Summary

Probes three user specified points on the bed and determines the plane of the bed relative to the probe.

As the head moves in X and Y it will adjust Z to keep the head tram with the bed.

NOTE The probe does not set the bed height, the probes find the relative level of the bed based on the first probe point, so after you have defined the bed plane with G32, you then set the bed height at the first probe point and use M206 or M306 to set the homing offset. Once saved you do not need to do zprobe or bed height again. In this case it is best to have a Z endstop as well as the ZProbe. the Z endstop is used to set the bed height after the probe.
This is different to other Firmware and is deliberate. This allows people to use temporary Z probes and not have a permanent z probe or know the exact Z offset of the probe in relation to the nozzle.

Configuration

The strategy must be enabled in the config as well as zprobe.

leveling-strategy.three-point-leveling.enable         true

Three probe points must be defined, these are best if they are the three points of an equilateral triangle, as far apart as possible.
They can be defined in the config file as:-

leveling-strategy.three-point-leveling.point1         100.0,0.0   # the first probe point (x,y)
leveling-strategy.three-point-leveling.point2         200.0,200.0 # the second probe point (x,y)
leveling-strategy.three-point-leveling.point3         0.0,200.0   # the third probe point (x,y)

Or they may be defined (and saved with M500) using M557 P0 X30 Y40.5 where P is 0,1,2

Probe offsets from the nozzle or tool head can be defined with :

leveling-strategy.three-point-leveling.probe_offsets  0,0,0  # probe offsets x,y,z

They may also be set with M565 X0 Y0 Z0

To force homing in X and Y before G32 does the probe the following can be set in config, this is the default

leveling-strategy.three-point-leveling.home_first    true   # disable by setting to false

The probe tolerance can be set using the config

leveling-strategy.three-point-leveling.tolerance   0.03    # the probe tolerance in mm, default is 0.03mm

You can save the bed plane so it can be used again without probing again presuming the bed stays flat etc. to do this you must enable the feature

leveling-strategy.three-point-leveling.save_plane   true    #

For this to be effective you must do your Z home to the first probe point defined when creating the plane. Set the Z height to zero at the first probe point,
then the bed plane should be relative from that point on. You save it with M500, although it will not display with M503 as it is not a user settable function.

A nice guide is here. http://reprapme.com/2015/07/z-probing/ although use of an automatic probe deploy is entirely optional, and running a probe every print is also not the recommended way to use this, it is preferable to probe once and save the results, no more probes are required unless something changes on your bed.

Usage

The machine must be homed in X and Y before running the probe.
If you need to set the bed height after probing you must set the height at the first probe point, and save it with homing offsets. (M206 or M306)

Example use :

    G28 (Home XYZ)
    Move Z up to about 30mm and attach probe
    G32
    remove probe.
    M500 (to save probe results)
    Move to the Probe P0 point (first probe point)
    jog down to touch the plate
    M306 Z0
    M500 (to save homing offset)
    G28
    Move to 0,0 check Z height
    Move to P0 check z height ditto for P1 and P2

ZGrid level compensation for Morgans (or multipoint bilinear bed leveling)

NOTE It is fully functional and tested on Morgan machines only.

NOTE this currently does not work on Deltas (use DeltaGrid) and is not well tested on Cartesians. If you want to use it on those platforms please report any problems in the Github issue tracker with a subject [ZGrid] problem summary (Where problem summary is replaced with a summary of your problem).

Summary

Probes a grid of user specified number of points on the bed and populates a data array of offsets to be used with a bilinear offset calculation.

As the head moves in X and Y it will adjust Z to keep the head tracking the bed surface.

Configuration

The strategy must be enabled in the config as well as zprobe.

leveling-strategy.ZGrid-leveling.enable         true

The bed size limits must be defined, in order for the module to calculate the calibration points

leveling-strategy.ZGrid-leveling.bed_x           200
leveling-strategy.ZGrid-leveling.bed_y           200

Also ensure that the max Z is defined and valid for the machine (Gamma end stop section)

gamma_max                                    200              #

The number of divisions for X and Y should be defined

leveling-strategy.ZGrid-leveling.rows           7          # X divisions (Default 5)
leveling-strategy.ZGrid-leveling.cols           9          # Y divisions (Default 5)

The probe offset should be defined, default to zero offset

leveling-strategy.ZGrid-leveling.probe_offsets  0,0,16.3

slow feedrate can be defined for probe speed

leveling-strategy.ZGrid-leveling.slow_feedrate  100

Usage

The machine will home automatically when running the probe.
The machine will then position the head in the center of the defined space for probe attachment (if required)
When ready, trigger the probe manually to start the probe run.

ZGrid file

The Zgrid file is a simple list of offsets prefaced by the Z probe length and the XY probe count. The order is identical to the probing order.

Example:

In the file below, P100 refers to the number of probe points to sample.
The two 10s are the number of rows and columns (X, Y), and the floating point number is the Z home offset.
The rest of the values are the probing offsets (calculated as the travel distance - the home offset). Higher values indicate that the probe moved less before triggering (so the bed at that point is higher), smaller values mean bed is lower.
P100 10 10 20.100
1.725
0.663
0.413
0.725
0.625
0.513
0.375
0.263
…
1.025
0.875
0.956

Using FSRs and proximity detectors as a probe

Setting up FSRs to work reliably is tricky…

To use FSR's with the smoothieboard an aux board is needed to interface the FSR's to the smoothieboard's endstop input. Smoothieware will accept this input as if it was a simple mechanical switch.

JohnSL (Github) has created such a board. It is available via TriD Printing & UltiBots. See John's blog post about the board. This board is powered from the endstop pins.

The Deltabot group is where most discussion on using FSR's is located.
Topics to look for are:

• Alternative boards like the arduino mini.
• WingWong's trinket derived design.
• Mounting of FSR's