Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Stop working when using ft_motion. Freeze at start. #26614

Closed
1 task done
stormlyx opened this issue Jan 2, 2024 · 7 comments
Closed
1 task done

[BUG] Stop working when using ft_motion. Freeze at start. #26614

stormlyx opened this issue Jan 2, 2024 · 7 comments

Comments

@stormlyx
Copy link

stormlyx commented Jan 2, 2024

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

Yes, and the problem still exists.

Bug Description

When trying to print a test ring-tower model with changeable parameters in a Prusa slicer, printing stops before it starts, and the printer can only be stopped by resetting.

Bug Timeline

New Bug?

Expected behavior

Printer can print and worked properly

Actual behavior

Fails to home when ft_motion on, and if enable ft_motion after homing in pursa slicer, then printer just stop working.

Steps to Reproduce

Prepare g-code with ringing tower, and enable ft_motion after g28, printer don't work properly
If ft_motion enabled, printer can't home.

Version of Marlin Firmware

2.1.x

Printer model

ender-3

Electronics

btt skr 1.4

LCD/Controller

mks_mini_12864

Other add-ons

No response

Bed Leveling

ABL Bilinear mesh

Your Slicer

Prusa Slicer

Host Software

SD Card (headless)

Don't forget to include

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

Additional information & file uploads

staring g-code
M493 S0
M104 S[first_layer_temperature]
M140 S[first_layer_bed_temperature]
G28
M109 S[first_layer_temperature]
M190 S[first_layer_bed_temperature]
M117 ;Purge extruder
G92 E0 ;Reset Extruder
G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed
G1 X10.0 Y20 Z0.2 F5000.0 ; Move to start position
G1 X10.0 Y200.0 Z0.2 F1500.0 E15 ; Draw the first line
G1 X10.4 Y200 Z0.2 F5000.0 ; Move to side a little
G1 X10.4 Y20 Z0.2 F1500.0 E30 ; Draw the second line
G92 E0 ; Reset Extruder
M493 S11 D0 ; Enable ZVD Input Shaping
archive.zip

@ellensp
Copy link
Contributor

ellensp commented Jan 2, 2024

did you try the absolute latest bugfix as something very similar to this was just fixed #26595

@stormlyx
Copy link
Author

stormlyx commented Jan 2, 2024

Yes, I try it, and nothing is changed

video.mp4

@KALIKALI5
Copy link

How can I help!!

@narno2202
Copy link
Contributor

@stormlyx , I try the latest bugfix following your video step by step and I can't reproduce the error.
Regarding your GCode, It is a bad idea to change the FT_MOTION mode during printing even if it works in theory (ok on my printer).

@stormlyx
Copy link
Author

stormlyx commented Jan 2, 2024

@stormlyx , I try the latest bugfix following your video step by step and I can't reproduce the error. Regarding your GCode, It is a bad idea to change the FT_MOTION mode during printing even if it works in theory (ok on my printer).

Thank you for answer. I tried again compile new bug fix 2.1.x and it work properly. I notice what standard is zv was enabled, and maybe because of it, ft_motion did't work properly.

@thisiskeithb
Copy link
Member

I notice what standard is zv was enabled, and maybe because of it, ft_motion did't work properly.

We don't prevent Input Shaping & Fixed-time-based Motion Control from being compiled together & made available at the same time, but maybe more testing needs to be done around these.

Copy link

github-actions bot commented Mar 3, 2024

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.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants