Duet3 6HC not deploying BL touch for mesh bed leveling

[dc42]

@autopilot-exe , what version is your Duet 3 6HC board?

[Phaedrux]

@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

@fcwilt A possibility that I just considered: the firmware generator tool that I used as a base is v3.2.3. Could the mismatch be from there? i.e, the RepRapFirmware Configuration tool version not being in line with the firmware version?

In the tool you can select the firmware version you want it to generate a config for. The exact version of the config tool isn't important really.

@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

@fcwilt the self test is working, I have it wired correctly according to the documentation. (3.3v: nothing, io7.in: white, GND: black and brown soldered together going to a single pin, io7.out: orange, 5 volt: red)

Can you post a photo of the wiring?

io7 should be ok unless it's a prototype board.

[autopilot.exe]

@dc42 hey, its labeled as V1.0

[fcwilt]

@autopilot-exe

I installed the most recent version of a BLTouch on my 6HC board (running 3.2.2) at IO7.

I powered it from 3.3 volts.

These were the configuration commands:

M950 S0 C"io7.out"
M558 P9 C"io7.in" H2 F120 T9000 R0.2 A1 S0.01 ; 1 reading

M401 worked. M402 worked. G30 worked.

Frederick

[autopilot.exe]

@Phaedrux

So when I took this photo I panicked after seeing the brown wire. To make sure it was connected I took a meter to it and confirmed continuity from the last extensions to ground on both the black and brown wire. It's ugly but functional.

[autopilot.exe]

@fcwilt no ^ before io.7in since you you are using 3.3v?

[Phaedrux]

It would be the yellow wire that carries the servo control signal back to the BLtouch.

[fcwilt]

@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

@fcwilt no ^ before io.7in since you you are using 3.3v?

I didn't even think about if that was needed or not.

I did not have it as you can see.

Frederick

[autopilot.exe]

@fcwilt Just tried both ways. Now pin up and pin down work. Mesh bed leveling does not.

[fcwilt]

@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

@fcwilt Just tried both ways. Now pin up and pin down work. Mesh bed leveling does not.

Does a single G30 work?

Frederick

[autopilot.exe]

@fcwilt confirmed: G30 works

[Phaedrux]

@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

G31 P50 X-63 Y-61 Z2.5

Is the XY offset really that far from the nozzle?

[Phaedrux]

What exactly happens when you send G29? Do you get any error messages?

[autopilot.exe]

@Phaedrux Yep. The E3D tool changer is quite large Had to put it on the side of the plate that it gets mounted to.

[fcwilt]

@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

@fcwilt confirmed: G30 works

Well if G30 works then G29 will work if you have the proper probing pattern configured.

Frederick

[dc42]

@fcwilt said in Duet3 6HC not deploying BL touch for mesh bed leveling:

Well if G30 works then G29 will work if you have the proper probing pattern configured.

...unless you have a mesh.g file that does not in turn contain a G29 S0 command. This is because G29 with no S parameter runs mesh.g if it exists, and executes G29 S0 if it does not.

[fcwilt]

@dc42 said in Duet3 6HC not deploying BL touch for mesh bed leveling:

...unless you have a mesh.g file that does not in turn contain a G29 S0 command. This is because G29 with no S parameter runs mesh.g if it exists, and executes G29 S0 if it does not.

Well you learn something new everyday.

I don't see that information about mesh.g in the Gcode Dictionary though I did find it in the expanded discussion of mesh bed compensation.

Perhaps it should be mentioned in the Gcode Dictionary as well.

Thanks.

Frederick

[dc42]

@fcwilt said in Duet3 6HC not deploying BL touch for mesh bed leveling:

I don't see that information about mesh.g in the Gcode Dictionary though I did find it in the expanded discussion of mesh bed compensation.
Perhaps it should be mentioned in the Gcode Dictionary as well.

Thanks for pointing this out. I have updated the G29 description on the GCodes wiki page.

[autopilot.exe]

@dc42 So if I understand correctly, I need a mesh.g file? I don't currently have one under /sys

[fcwilt]

@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

@dc42 So if I understand correctly, I need a mesh.g file? I don't currently have one under /sys

No you do not need one - it's just an alternate way to handle G29 with no parameters.

If there is no mesh.g file G29 acts just like G29 S0.

You could use mesh.g if you wanted to perform some others commands in addition to G29 S0, either before or after.

But you would have to have G29 S0 somewhere in the mesh.g file to actually probe the bed and create the height map.

Frederick