Failed Calibration

Controllers Smoothie
1

When running the Calibration through the menu on the front of the 3D printer, sometimes it fails to calibrate. We are looking for someone to help or to make a fix to display when Calibration has passed or failed. We want it to not save the failed settings(if they do). If you know of a fix, or need more information, please let me know. I am not super familiar with SmoothieWare so any guidance would be appreciated. Here is sections from my config file that have to do with the settings for Calibration.

Deltabot

In Config:
zprobe.enable true # set to true to enable a zprobe
zprobe.probe_pin 1.29!^ # pin probe is attached to if NC remove the !
zprobe.slow_feedrate 5 # mm/sec probe feed rate
zprobe.fast_feedrate 100 # move feedrate (100 is default)
zprobe.probe_height 5 # how much above bed to start probe, must be 10 or above to avoid cailbration fail

  1. associated with zprobe the leveling strategy to use

leveling-strategy.delta-calibration.enable true # basic delta calibration
leveling-strategy.delta-calibration.radius 95 # the probe radius

custom_menu.calibrate.enable true #
custom_menu.calibrate.name Calibrate_Bed #
custom_menu.calibrate.command play_/sd/Archive_Config_Files/Calibration.gcode #

Calibration.gcode:

M117Calibrating Bed;
G32;
M117Calibration Complete;
M500;
G28;
G4 10;
M117;

Imported from wikidot

2

You would need Smoothie to implement some method for files executed from the menus to report what is output by the file playing. That has not been implemented yet.

3

Is there anyone that could do that, or you know of anyone who could create that? It would help a ton.
I have been using the Terminal in Matter control to run auto calibration using g32, and saving it if it doesnt fail using m500. When it fails I am able to get an error stating calibration has failed. Is there a way to write it up in my Config file to display this error if it occurs, or does that have to be changed in the firmware itself?
This would be an awesome feature to be implemented if anyone is willing to do it.

4

Yes, that is something that needs to be implemented in firmware, at the moment there is no way to do it.
This is part of a long series of improvements we must do to the “play” system, they are planned, but there is so much to do overall, I can’t say when they’ll come.
If you were a company there are contributors I could point you at to pay them to do it, but if you are an individual unfortunately your only options at this point is to do it yourself, find a friend to do it, or wait for the normal firmware development to progress to that point.

Cheers.