Robo3d AUTOLEVEL Not Working
-
z endstop triggers when homing however fails to run bed probe sequence
-
when i try g30 it says not enough axes homes
-
@sleepless said in Robo3d AUTOLEVEL Not Working:
when i try g30 it says not enough axes homes
In order to execute G30, the X and Y axes need to be flagged as having been homed. So either you hadn't homed X and Y between turning on the printer and sending G30, or you did something else (e.g. turned the motors off using M18 or M84) that caused them to be flagged as not homed.
-
ok i had to change g30 z0 to z-2now its doing autohoming, guess its time to calibrate the z height
-
as you can see the auto level doesn't seem to be working very well, Do you think i need to run a mesh grid calibration? -
@sleepless said in Robo3d AUTOLEVEL Not Working:
Do you think i need to run a mesh grid calibration?
It's a good way to see your bed topography even if you don't use the compensation feature.
Did you end up getting a probe?
-
no i did not get the probe yet. mainly because i havent seen a design for the robo x carriage that houses the bltouch and i dont have time to design it at the moment
-
Does your print bed have levelling screws? If so then I suggest you do true bed levelling adjustment before you run mesh probing. See https://duet3d.dozuki.com/Wiki/Using_the_manual_bed_levelling_assistant.
-
Not sure what I did but its working again : ) and dialed in
-
.png](/assets/uploads/files/1548801743104-screenshot-32-resized.png)
image url) -
Hi can you point me to some literature about clearing the compensation and running the calibration sequence in as many points as possible?
-
@sleepless Here's the relevant docs on mesh bed compensation
https://duet3d.dozuki.com/Wiki/GCode#Section_G29_Detailed_Z_Probe
https://duet3d.dozuki.com/Wiki/GCode#Section_M557_Set_Z_probe_point_or_define_probing_grid
https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensationThe way to maximize the grid area is to take the size of your bed, and subtract the G31 X and Y offsets to get the area of the bed reachable by the probe. Then you can enter a M557 command into the gcode console with a really small grid spacing. The system will determine that it's too small, and suggest a new grid spacing that should maximise your probe points.
-
@phaedrux thanks ill try this out
-
ok so it turns out it was a mechanical issue. One of the endstops was a little loose so it would move when triggered. I tightened eveything up and now its looking much better
