Delta bl touch auto leveling
-
Hello i bought duet ethernet as an upgrade for TLM ,the wiring and the first calibration of the machine was easy to complete and everything went fine.
The problem is with bl touch and the auto-leveling ,i follow these instructions,https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe,https://betrue3d.dk/bltouch-on-duet-wifi-duetreprapfirmware/.
.
So the when the machine powers up bl touch is self tests and everything is ok ,even when i manually touch the bl touch it triggers.
But when i hit the delta auto leveling in DWC the efector goes to the trigger height (set it in config.g) the bl touch pin goes down,but doesn't probe the center waits some ms and the moves to the first tower and suddenly the DWC shows the manaul bed leveling in which i have to move down the z axis until the bl touch triggers and if do that the bl touch after the first trigger goes to error mode (RED led blinks) and even if move to the next point the bl touch doesnt respond 0_1523357488108_bed.g 0_1523357491506_config.g 0_1523357494231_homedelta.g -
Check that you have the correct parameters in your M558 command. You should have P9 for bltouch if you are using version 1.21 firmware, or P5 for older firmware.
-
@dc42 yes all tests that i ve tried is with P9 and with P5 but the results are what i have described above
-
Is there an error message in the GCode Console page of Duet Web Control after you run G29? There should be one, if the G29 command quit early.
-
@dc42 No i tested again the same story, nothing shows up in the console.
I think the problem is somewhere else , my thought is why it shows me inDWC the manual bed leveling . It supposed to do itself right?. -
@tasos said in Delta bl touch auto leveling:
@dc42 No i tested again the same story, nothing shows up in the console.
I think the problem is somewhere else , my thought is why it shows me inDWC the manual bed leveling . It supposed to do itself right?.If it pops up the manual bed levelling prompt, then either the M558 command is not being recognised, or the probe type in it is not supported e.g. you have specified probe type 9 but you are not using version 1.21 firmware.
-
OK i change the P9 to P5 and also Z2 to Z1 and now works
i run mesh and i got thisNumber of probe points: 109
Probe area: 452.4 cm²
Maximum deviations: -0.633 / 0.027 mm
Mean error: -0.273 mm
RMS error: 0.161 mm
I m not sure if this is right