[BUG] (Coordinates suddenly shifted in 2.0.9.4, 2.1 and bugfix-2.1.x)

[unclej84]

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

Yes, and the problem still exists.

Bug Description

A previously running gcode suddently turned a movement in the wrong directions - position reportings show strange jump in position values. So instead of moving down to a wanted z-position the gantry on the ender style printer moves up into the frame and collides. In 2.0.9.3 the gcode works as intended

Bug Timeline

working: bugfix-2.0.x (18.02.2022 20:05), not working releases 04.06.2022

Expected behavior

No change in coordinates without any action

Actual behavior

Moved up instead of down

Steps to Reproduce

Simply running attached gcode via terminal or sd-card - same result in both cases - the gantry moves up instead of down

Version of Marlin Firmware

2.0.9.4 / 2.1.0 / bugfix-2.1.x

Printer model

Creality Ender-3 V2

Electronics

Octopus V1.1

Add-ons

dual lead screws

Bed Leveling

UBL Bilinear mesh

Your Slicer

Prusa Slicer

Host Software

SD Card (headless)

Other things to include

• [X] A ZIP file containing your Configuration.h and Configuration_adv.h.
• [X] Log output from the host. (M111 S247 for maximum logging.)
• [ ] Images or videos demonstrating the problem, if it helps to make it clear.
• [X] A G-Code file that exposes the problem, if not affecting all G-code.

Additional information & file uploads

configuration.zip Test.gcode.zip Console_Octoprint.txt.zip serial.log.zip

[raincons]

I also have this bug on bugfix-2.1.x, 2.1.x and 2.0.x branches. My printer is Cartesian custom Prusa i3, electronics is Atmega2560 + RAMPS. The bug occurs when UBL is enabled. I found a temporary workaround - undef SEGMENT_LEVELED_MOVES in configuration. I'm assuming the bug is related to changes: https://github.com/MarlinFirmware/Marlin/commit/1d12e72bf697f7e3cb63995a20ba9e98fbce3eb9

[SlevinSkrreeek]

Same here with voxelab aquila on bugfix-2.1.x and UBL enabled. undef SEGMENT_LEVELED_MOVES fix the problem.

[unclej84]

Did you experience any negative influence upon setting the undef?

[github-actions[bot]]

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.

[unclej84]

@rainberd, @SlevinSkrreeek have you tried 2.1.1? Is it fixed there?

[raincons]

I can't reproduce on bugfix-2.1.x (e49c3dc)

[SlevinSkrreeek]

@rainberd, @SlevinSkrreeek have you tried 2.1.1? Is it fixed there?

Sorry, didn't find time to rebuild the firmware recently

[unclej84]

The current bugfix-2.1.x (aaf34fa) seems to work for me too. Hope the next released version will stay the same

[github-actions[bot]]

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.