[BUG] Probes with pick-up and drop move sequences need proper support

[nionio6915]

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

I am using a detachable Z-Probe and see different movement behaviors for G29 probing, G35 tramming and when probing a single point via G30. The probe pickup and drop off is different depending on which gcode is being executed. There appear to be different extraneous movements depending on which gcode is being executed, and from what X,Y position they are issued.

It is easier to demonstrate the differences in movement patterns with videos. The tramming deploy/stow is more what I was expecting. There are extranious movements and traverses in G29 at the begining and end. It appears that machine will traverse back and forth to the positions before and after deploy/stow instead of the next movement in the series.

Probe is currently defined as an Allen key probe. The stepwise movement positions were determined manually (G1 X57 Y30 Z15 ...) and entered into the code block copied from a Delta example config.

G29 sequence-
https://photos.app.goo.gl/PDmG4CFRBU4vmH7y6
First move of the deploy is correct: X inline with dock. (0 secs - 15 secs)
skip to 2:20 if you want to skip the majority of the probing
At the end of the stow sequence, it looks like it skips the last position, then high-tails it to the back right corner, then goes back towards the front left corner. . (2:20-2:43)

G35 Tramming sequence
https://photos.app.goo.gl/zLJUegSyyquCxRxW8
There is an extra 'ready' move before the start point of the deploy seqeuence.

Bug Timeline

no previous experience

Expected behavior

I expected the same deploy and stow sequences regardless of the instructions given to the printer. The exact same motions to deploy and retract.

Actual behavior

Extra, unexplained or non-instructed motions occur.

Steps to Reproduce

Run G29
Run G30 X120 Y120
Run G35 S40 or from the LCD display

Version of Marlin Firmware

Buffix 2.0.x 2021-08-16

Printer model

Ender3 Pro

Electronics

Creality 4.2.2

Add-ons

Euclid Probe

Bed Leveling

UBL Bilinear mesh

Your Slicer

Other (explain below)

Host Software

OctoPrint

Additional information & file uploads

see above for links to videos.
Current configs: MarlinEuclidConfigs.zip
I will try to capture M111 output and post as a followup/edit.

[nionio6915]

1. I needed to re-compile with debug support, so a new configs zip file uploaded for completeness.
   EuclidProbeConfigsV2.zip

2. Debug output gathered via M111 S39
   Send: M111 S39
   Recv: echo:DEBUG:ECHO,INFO,ERRORS,LEVELING
   debug09182021.txt

3. I executed the 6 different commands and copy/pasted the output as one file. I was worried the Octoprint terminal buffer would fill up. I separated the groups with comment strings to describe what I was doing. (I screwwnshoted b/c the hastags were messing up the formatting)

I did:
G28 followed by G29
G30 G(halted/crashed)
G35 S40
Tramming wizard from the LCD,
Started Tramming wizard from LCD, then G30 X175 Y175
G30 X175 Y175

4. G30 randomly seem to crash/halt the printer.

test

[nionio6915]

the other odd behavior is Marlin seems to return the carraige to the point where a command was issued, instead of the next command-
If I am at X150 Y150 and issue a G29 command, Marlin will deploy the probe, then return to X150 Y150, then go to the starting point of the mesh pattern

[ChinChillaSPb]

2.0.9.2 - delta auto cal on kossel linear plus says "stow z-probe" probe v2 after 3rd step in sequence

[github-actions]

This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

[nionio6915]

please reopen this. it is unresolved.

1. trying to use the Z-Probe wizard, the printer will pick up the probe then get confused about which way is +Z and -Z
2. Random 'extra' movements are present at the end of operations like bed probing or bed tramming.
3. Carraige seems to go to the first point of operations before probing sequences, then get the probe. On drop off, it will finish then stow, then return to the end point, then go to the next instruction.
4. EDIT: IF you manually deploy the probe with M401, go probe a point, the machine will dock the probe by itself without instruction.
5. EDIT: If you try to run the Z-Porbe Offset Wizard, the machine will travel to the predefined XY location, then deploy the probe, then return to the spot, but instread of probing, it will infinitly move UP in Z, then after it realizes its not triggering the probe, stow the probe perfectly and then halt the printer.

All this behavior is extranious and superflous. RRF and Klipper are more rational in their operations :(

[thisiskeithb]

Please comment within the 10-day period next time so the bot doesn’t close the report.

[github-actions]

This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

[nionio6915]

i hope that one of the devs will pick this up. I think its an easy thing to solve!

[github-actions]

This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

[nionio6915]

reply reply reply

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.