Make sure your BuildFlow is running the latest version.
If you are still experiencing issues with your Z-Offset being too high/low even after calibrating it, something may have gone wrong during the calibration process. While it is an uncommon occurrence, it can be quite confusing when you test your new calibration and find that you still need to fine tune it.
Confirm the problem
It is easy to check if something has gone wrong while calibrating the Z-Offset by using the GCODE terminal in the BuildFlow maintenance console.
1. To access the GCODE terminal, access your list of printers at the top of the BuildFlow interface.
2. Click on the "MAINTENANCE" button next to the printer you wish to use GCODE commands on.
3. This will take you to a landing page which will give you the option to access manual controls, system info and troubleshooting tools for you printer. Click on "Maintenance" to reveal the GCODE terminal.
4. Type M851 into the GCODE terminal and press enter. You will see a message like this:
The default for the 'Probe Z Offset' number is 10. If the value that was returned from the M851 command deviates too much from the average (e.g. it returns 0 or 15 etc.), something may have gone wrong during the calibration process. To fix this, follow the steps below:
1. While still in the GCODE terminal, type M851 Z10 and press enter. This will tell the printer that the Z-Offset is now 10.
2. To permanently store the new Z-Offset value, type M500 and press enter. You will see a message similar to the one below that tells you the setting was stored:
3. To confirm that it’s all worked, type M501 and hit enter. This will load all of the printers settings in the GCODE terminal; at the bottom of the response you should see the new M851 value (Z-Offset).
4. Alternatively, you may upload this GCODE file to BuildFlow in the 'Control' section of the maintenance console and let it run.
5. NOTE: Since this only returns the Z-Offset to a default value, you will still have to run a Z-Offset calibration to fine tune your printers performance. You can find the article on how to do that here.