G29 fails on Duet3 with toolboard
-
Please upgrade both boards to 3.2 final and re-test.
-
Thanks DC42,
I upgraded to 3.2.0 an now the bltouch will deploy but not retract. M401 and 402 commands work after a full power reboot and before a G32 or G29. During a G32 it will work fine for 2 points, on the 3rd it did not retract. I did another power cycle tested with m401 and 402 at least 6 times cycles without issues. Did another G32 and this time it did not deploy on the 4th probing move. I already replaced the bltouch.
-
@jdumoulin
check the wiring. the cables that come with the bltouch often the cause for problems. -
Can you post your config,g?
Is the BLtouch connected to the tool board?
Can you verify that the firmware update was applied to the mainboard and tool board by sending M122 and M122 B1?
-
Please post your config.g and deployprobe.g files.
It may help to add a short delay between deployment and probing, either by using the M558 R parameter or by adding a G4 delay command at the end of deployprobe.g.
-
I'm not 100% but seeing as you are on RRF3
Should you not be using the following commands ?
M280 P0 S10 ; Deploy Probe PinM280 P0 S90 ; Retract Probe PinInstead of the M401/M402 commands
I think those are more suited to the newer firmware
And you can also re-set the probe using M280 P0 S160
-
@JayJay said in G29 fails on Duet3 with toolboard:
Instead of the M401/M402 commands
those commands execute the retract and deployprobe scripts.
-
@Veti said in G29 fails on Duet3 with toolboard:
@JayJay said in G29 fails on Duet3 with toolboard:
Instead of the M401/M402 commands
those commands execute the retract and deployprobe scripts.
Yes I know that, but if you read some info on setting up a BL-Touch it says that using M401/M402 is depriciated and that you should use M280 (with switches) instead.
-
@JayJay said in G29 fails on Duet3 with toolboard:
but if you read some info on setting up a BL-Touch it says that using M401/M402 is depriciated
can you point to the duet documentation where it says that?
-
@JayJay said in G29 fails on Duet3 with toolboard:
@Veti said in G29 fails on Duet3 with toolboard:
@JayJay said in G29 fails on Duet3 with toolboard:
Instead of the M401/M402 commands
those commands execute the retract and deployprobe scripts.
Yes I know that, but if you read some info on setting up a BL-Touch it says that using M401/M402 is depriciated and that you should use M280 (with switches) instead.
It's not deprecated, it's just that when using BLTouch you should not explicitly use M401 and M402, except to test the deploy and retract macros. Whereas when using other types of probe that need to be deployed, it makes sense to use M401 at the start of mesh probing or calibration, and M402 at the end.
-
@Veti said in G29 fails on Duet3 with toolboard:
@JayJay said in G29 fails on Duet3 with toolboard:
but if you read some info on setting up a BL-Touch it says that using M401/M402 is depreciated
can you point to the duet documentation where it says that?
in future can I kindly request that you do not edit/quote me with only a part of what Isaid, as your change does not reflect the full context of what I said, you need the whole context of what I posted.
And possibly my choice of word "deprecated" was not the best choice.
The documentation has changed, there used to be specific wording noting that there was a change from using M401/M402 to use M280
And as pointed out by by DC42 highlights another instance where the documentation is lacking context, the documentation says to use M280 and goes so far as specifically telling you to place those commands in your deploy/retract files in the root of the sys folder.
Now common sense would dictate that if the documentation is listing M280 and NOT M401/402 and that documentation had previously advised to now use M280 instead of M401/M402 that would technically mean M401/402 is no longer really used (or mentioned) so it would be logical to assume the word "depreciated" would come into effect.
And now further confusion with @dc42 stating that:
it makes sense to use M401 at the start of mesh probing or calibration, and M402 at the end.
There is NO specific mention of using M401/M402 in the documentation Mesh Compensation
And no specific example (as is usually the case) given for carrying out any probing using M401/M402.
So I am Sorry but the documentation really needs to be majorly overhauled as it is, things are littered all over the place and that leaves many users unsure about what to follow because of so many inconsistencies, conflicting info and ambiguity.
Commissioning & Testing (RepRapFirmware 3)
To test the setup with the nozzle maybe a 100mm up from the bed you can check if the trigger signal is reaching the Duet by attempting to extend the pin by using the following command:M280 P0 S10
If all is well the web interface should report a value of ”0” or "N/A" in the Z probe column when the pin is extended. You can then lightly touch the extended probe pin to check that the value in the Z probe Column changes to “1000”
You can retract the pin again with
M280 P0 S90
the above two commands are also what should be in /sys/deployprobe.g and /sys/retractprobe.g, respectively.
-
@JayJay said in G29 fails on Duet3 with toolboard:
And now further confusion with @dc42 stating that:
it makes sense to use M401 at the start of mesh probing or calibration, and M402 at the end.dc42 said that with
Whereas when using other types of probe that need to be deployedit is documented in those that need it e.g
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Touch_Mi -
@Veti said in G29 fails on Duet3 with toolboard:
@JayJay said in G29 fails on Duet3 with toolboard:
And now further confusion with @dc42 stating that:
it makes sense to use M401 at the start of mesh probing or calibration, and M402 at the end.dc42 said that with
Whereas when using other types of probe that need to be deployedit is documented in those that need it e.g
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Touch_MiYes But the OP is operating a BL-Touch NOT something else, therfore it would be reasonable to assume that the OP wouldnt be following a guide for something else, and the OP wrote that he had used M401/M402 hence my reason for mentioning it.
And as @dc42 has stated above you shouldnt explicitly use M401/M402 with a BL touch and the fact that the BL touch documentation doesnt mention using M401/M402 it would be resonable to assume that the as the OP was using them might be having an effect on what is happening to the OP's machine.
And bringing other non relevant documentation into the mix can only lead to further confusion.
Anyway back to trying to help the OP's overcome his issue.
I had a spurious issue with my toolboard acting up which was cured by making sure the firmware between board and toolboard matched. I ended up having to manually tell everything to update using the M997 command for the mainboard and M997 B switch to update the toolboard. that cured my issues.
if that doesnt work then we need to see full copies of the following files
config.g
homeall.g
bed.g
deployprobe.g
retractprobe.g -
@JayJay Just for the sake of clarity.
M280 commands are servo control commands. The BLTouch uses a servo to deploy and retract the pin. For the BLTouch you put the M280 commands in deployprobe.g and retractprobe.g
M401 and M402 call the deploy and retract macros. That's all they do. When using a BLTouch (probe type P9) G30 will call M401 and M402 automatically.
In the days before the P9 probe type specifically for the BLTouch, you had to manually deploy and retract the probe before sending G30. Using the base M280 servo commands was common, however M401 and M402 were added so that the firmware could actually keep track of the state of the probe as being deployed or not.
So yes, using M401 and M402 in your homing files when using a BLTouch isn't needed anymore because probe type P9 takes care of deployment and retract automatically. But behind the scenes it's still just using M401 and M402, which is just calling deployprobe.g and retractprobe.g which just contains the M280 servo commands.
I hope that gives some historical context and explanation on why things are the way they are.
