[BUG] 2.1.3 beta 3 g29 and g34 are not working properly with FT Motion

[SFRSKZ]

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

No, but I will test it now!

Bug Description

g29 and g34 is not working

Bug Timeline

after beta 3

Expected behavior

No response

Actual behavior

No response

Steps to Reproduce

I send G28 via OctoPi, it homes as it should. Then I send G29. It moves to the front left corner, probes the first point, and then the Z axis moves up to around 180 mm and stops, so it fails. The same thing happens with G34: it doesn't move to the next probing point.

I used WinMerge to make sure I didn’t miss any settings, and I’ve double-checked everything to see if I did something wrong. Version 2.1.2.5 works perfectly, so it’s not mechanical.

Version of Marlin Firmware

2.1.3 beta 3

Printer model

prusa mk3 bear upgrade

Electronics

skr 3 ez tmc 2226 xy 2209 2xZ and e

LCD/Controller

lcd 2004

Other add-ons

No response

Bed Leveling

ABL Bilinear mesh

Your Slicer

None

Host Software

OctoPrint

Don't forget to include

• A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

Marlin.zip

[ellensp]

Whenever there are homing or leveling issues, we now ask everyone to follow a standard procedure to gather more information so that we're not just taking stabs in the dark. Here is the boilerplate:

• Download Marlin bugfix-2.1.x to test with the latest code.
• Enable DEBUG_LEVELING_FEATURE and M114_DETAIL and re-flash the firmware.
• Connect to your printer from host software such as Cura, Printrun or Repetier Host.
• Send M502 and M500 to ensure your Configurations are applied.
• Issue the command M111 S247 to enable maximum logging.
• Perform a G28 to do your standard homing procedure.
• Do a G29 to probe the bed. This will also enable bed leveling.
• Do some of the moves that revealed problems before. Take notes.
• Copy the log output into a .TXT file and attach it to your next reply.

Repeat this procedure, if needed, to demonstrate inconsistencies. From these logs we should hopefully get a better idea of what's going on with your machine.

[SFRSKZ]

Whenever there are homing or leveling issues, we now ask everyone to follow a standard procedure to gather more information so that we're not just taking stabs in the dark. Here is the boilerplate:

• Download Marlin bugfix-2.1.x to test with the latest code.
• Enable DEBUG_LEVELING_FEATURE and M114_DETAIL and re-flash the firmware.
• Connect to your printer from host software such as Cura, Printrun or Repetier Host.
• Send M502 and M500 to ensure your Configurations are applied.
• Issue the command M111 S247 to enable maximum logging.
• Perform a G28 to do your standard homing procedure.
• Do a G29 to probe the bed. This will also enable bed leveling.
• Do some of the moves that revealed problems before. Take notes.
• Copy the log output into a .TXT file and attach it to your next reply.

Repeat this procedure, if needed, to demonstrate inconsistencies. From these logs we should hopefully get a better idea of what's going on with your machine.

i just tested bugfix it s still same. will do rest

[SFRSKZ]

Whenever there are homing or leveling issues, we now ask everyone to follow a standard procedure to gather more information so that we're not just taking stabs in the dark. Here is the boilerplate:

• Download Marlin bugfix-2.1.x to test with the latest code.
• Enable DEBUG_LEVELING_FEATURE and M114_DETAIL and re-flash the firmware.
• Connect to your printer from host software such as Cura, Printrun or Repetier Host.
• Send M502 and M500 to ensure your Configurations are applied.
• Issue the command M111 S247 to enable maximum logging.
• Perform a G28 to do your standard homing procedure.
• Do a G29 to probe the bed. This will also enable bed leveling.
• Do some of the moves that revealed problems before. Take notes.
• Copy the log output into a .TXT file and attach it to your next reply.

Repeat this procedure, if needed, to demonstrate inconsistencies. From these logs we should hopefully get a better idea of what's going on with your machine.

here is the log

g29.txt

[SFRSKZ]

max z height movement according to log is 11.9 but in reality it goes way higher. z microstep is 16 and z step is 400 so it shouldnt do that behaviour right?

[SFRSKZ]

2.1.2.5 g29.txt

tried same with 2.1.2.5 and it worked

[SFRSKZ]

i think using ft motion and input shaper together is causing this problem. i turned off input shaper and now probing is working as it should.

[narno2202]

If FT_MOTION is the motion system, INPUT_SHAPING_X, Y or Z have no effect as the stepper ISR loop is not the same. If tuning off input shaper means turning off FT_MOTION (M493 S0), the failure is probably related to the probe timing. Try enabling DELAY_BEFORE_PROBING.

[thisiskeithb]

If Input Shaping and FT Motion are incompatible, then there should be a sanity check to prevent users from enabling both.

[narno2202]

As I am currently trying to fix the Biqu Microprobe with FT_MOTION, I totally forgot that FT_MOTION is disabled in Marlin when we use G28, G29 and G34. If FT_MOTION is active, input shaping functions are never called. So my previous comment is not valid.

[narno2202]

I apologize, FT_MOTION is disabled for homing or probing when there is a Biqu microprobe. Last post regarding FT_MOTION and INPUT_SHAPING_X, Y or Z is still correct, try to enable DELAY_BEFORE_PROBING.

[narno2202]

@SFRSKZ , can you try https://github.com/narno2202/Marlin/tree/FTM_Microprobe_generic and post feedback?