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] FT_MOTION causes violent Y movement #27535

Open
1 task done
vehystrix opened this issue Nov 18, 2024 · 1 comment
Open
1 task done

[BUG] FT_MOTION causes violent Y movement #27535

vehystrix opened this issue Nov 18, 2024 · 1 comment

Comments

@vehystrix
Copy link

vehystrix commented Nov 18, 2024

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

Yes, and the problem still exists.

Bug Description

When I enable FT_MOTION travel moves on the Y axis end violently, causing layer shifts.

My settings:

Send: M503
Recv: echo:; Linear Units:
Recv: echo:  G21 ; (mm)
Recv: echo:; Temperature Units:
Recv: echo:  M149 C ; Units in Celsius
Recv: echo:; Filament settings (Disabled):
Recv: echo:  M200 S0 D1.75
Recv: echo:; Steps per unit:
Recv: echo:  M92 X79.52 Y80.00 Z400.00 E424.83
Recv: echo:; Max feedrates (units/s):
Recv: echo:  M203 X500.00 Y500.00 Z10.00 E60.00
Recv: echo:; Max Acceleration (units/s2):
Recv: echo:  M201 X3000.00 Y3000.00 Z100.00 E5000.00
Recv: echo:; Acceleration (units/s2) (P<print-accel> R<retract-accel> T<travel-accel>):
Recv: echo:  M204 P500.00 R3000.00 T3000.00
Recv: echo:; Advanced (B<min_segment_time_us> S<min_feedrate> T<min_travel_feedrate> J<junc_dev>):
Recv: echo:  M205 B20000.00 S0.00 T0.00 J0.03
Recv: echo:; Home offset:
Recv: echo:  M206 X0.00 Y0.00 Z0.00
Recv: echo:; Auto Bed Leveling:
Recv: echo:  M420 S1 Z10.00 ; Leveling ON
[G29 commands removed for brevity]
Recv: echo:; Material heatup parameters:
Recv: echo:  M145 S0 H205.00 B60.00 F0
Recv: echo:  M145 S1 H240.00 B80.00 F0
Recv: echo:  M145 S2 H220.00 B70.00 F0
Recv: echo:  M145 S3 H230.00 B50.00 F0
Recv: echo:; Power-loss recovery:
Recv: echo:  M413 S0 ; OFF
Recv: echo:; Z-Probe Offset:
Recv: echo:  M851 X-28.50 Y22.00 Z-2.04 ; (mm)
Recv: echo:; Skew Factor:
Recv: echo:  M852 I0.000000 J0.000000 K0.000000 ; XY, XZ, YZ
Recv: echo:; Fixed-Time Motion:
Recv: echo:  M493 S1 A36.00 B29.50 D0 F0.00 H0.00 P1 K26.10
Recv: echo:; Nonlinear Extrusion:
Recv:   M592 A0.00 B0.00 C1.00
Recv: echo:; Input Shaping:
Recv: echo:  M593 X F0.00 D0.15
Recv: echo:  M593 Y F0.00 D0.20
Recv: echo:; Linear Advance:
Recv: echo:  M900 K0.10
Recv: echo:; Filament load/unload:
Recv: echo:  M603 L0.00 U100.00 ; (mm)
Recv: echo:; Filament runout sensor:
Recv: echo:  M412 S1 ; Sensor ON
Recv: echo:; Model predictive control:
Recv: echo:  M306 E0 P40.00 C14.54 R0.2053 A0.1187 F0.1686 H0.0056
Recv: ok

Executing the GCODE

M493 S0
G0 F21000
G0 Y50
G0 Y150

Gives this (expected) result:

MOV_0718_H.264.mp4

Executing the GCODE

M493 S1 X0 Y0
G0 F21000
G0 Y50
G0 Y150

Gives this result:

MOV_0720_H.264.mp4

I'm using the latest bugfix-2.1.x (2024/11/16)

Bug Timeline

No response

Expected behavior

Smooth movement both with FT_MOTION enabled and disabled

Actual behavior

Violent movement with FT_MOTION enabled

Steps to Reproduce

No response

Version of Marlin Firmware

bugfix-2.1.x 2024/11/16

Printer model

Neptune 3 Plus

Electronics

stock

LCD/Controller

stock elegoo LCD

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

Configuration.zip

Send: M115
Recv: echo:M115
Recv: FIRMWARE_NAME:Marlin bugfix-2.1.x (Nov 18 2024 14:24:38) SOURCE_CODE_URL:github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:3D Printer KINEMATICS:Cartesian EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
Recv: Cap:SERIAL_XON_XOFF:0
Recv: Cap:BINARY_FILE_TRANSFER:0
Recv: Cap:EEPROM:1
Recv: Cap:VOLUMETRIC:1
Recv: Cap:AUTOREPORT_POS:0
Recv: Cap:AUTOREPORT_TEMP:1
Recv: Cap:PROGRESS:0
Recv: Cap:PRINT_JOB:1
Recv: Cap:AUTOLEVEL:1
Recv: Cap:RUNOUT:1
Recv: Cap:Z_PROBE:1
Recv: Cap:LEVELING_DATA:1
Recv: Cap:BUILD_PERCENT:1
Recv: Cap:SOFTWARE_POWER:0
Recv: Cap:TOGGLE_LIGHTS:1
Recv: Cap:CASE_LIGHT_BRIGHTNESS:1
Recv: Cap:EMERGENCY_PARSER:1
Recv: Cap:HOST_ACTION_COMMANDS:1
Recv: Cap:PROMPT_SUPPORT:1
Recv: Cap:SDCARD:1
Recv: Cap:MULTI_VOLUME:0
Recv: Cap:REPEAT:0
Recv: Cap:SD_WRITE:1
Recv: Cap:AUTOREPORT_SD_STATUS:0
Recv: Cap:LONG_FILENAME:1
Recv: Cap:LFN_WRITE:1
Recv: Cap:CUSTOM_FIRMWARE_UPLOAD:0
Recv: Cap:EXTENDED_M20:1
Recv: Cap:THERMAL_PROTECTION:1
Recv: Cap:MOTION_MODES:0
Recv: Cap:ARCS:1
Recv: Cap:BABYSTEPPING:1
Recv: Cap:EP_BABYSTEP:0
Recv: Cap:CHAMBER_TEMPERATURE:0
Recv: Cap:COOLER_TEMPERATURE:0
Recv: Cap:MEATPACK:0
Recv: Cap:CONFIG_EXPORT:0
@rondlh
Copy link
Contributor

rondlh commented Dec 9, 2024

FT Motion is in beta, some issues are to be expected.
For me it also doesn't work. Even a basic line move doesn't work correctly.
If I make a move (200, 100) --> (0, 0) the Y-position (0) is reached before the X-position(0). So it's not a straight line, it's like a "J". My X-steps/mm is 160, Y-steps/mm is 100.

@thisiskeithb thisiskeithb added this to the Version 2.1.3 milestone Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants