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] Marlin 2.1.2.4 causes layer shift one every layer only on COREXY machine. #27348

Open
1 task done
YHamud opened this issue Aug 11, 2024 · 6 comments
Open
1 task done

Comments

@YHamud
Copy link

YHamud commented Aug 11, 2024

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

No, but I will test it now!

Bug Description

Everything compiles fine and when used on a standard cartesian machine it works flawlesly. I took the same files and enabled corexy and made some other changes refering to the machine size, leveling sensor, etc. Compiled fine, everything works, but it causes layer shifts on each layer. It's like the calculations for the corexy motions are wrong.

I've been using the bugfix (2.1.3) from the begining of the year without major issues, but wanted to try the latest oficial release.

Bug Timeline

New bug

Expected behavior

I expected it to not produce layer shifts.

Actual behavior

It produces layer shifts in diagonal on each layer.

Steps to Reproduce

No response

Version of Marlin Firmware

2.1.2.4

Printer model

TwoTrees SP5V3

Electronics

MKS Robin Nano V3.1

LCD/Controller

TS35

Other add-ons

No response

Bed Leveling

ABL Bilinear mesh

Your Slicer

Prusa Slicer

Host Software

None

Don't forget to include

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

Additional information & file uploads

CONFIGURATIONS_MARLIN.zip

@thisiskeithb
Copy link
Member

thisiskeithb commented Aug 11, 2024

I've been using the bugfix (2.1.3) from the begining of the year without major issues, but wanted to try the latest oficial release.

bugfix-2.1.x is more than 1.5 years ahead of any tagged release at this point since releases are no longer snapshots of the bugfix branch. This includes more hardware support & many fixes.

Please download bugfix-2.1.x to test with the latest code and let us know if you're still having this issue.

@YHamud
Copy link
Author

YHamud commented Aug 16, 2024

I've been using the bugfix (2.1.3) from the begining of the year without major issues, but wanted to try the latest oficial release.

bugfix-2.1.x is more than 1.5 years ahead of any tagged release at this point since releases are no longer snapshots of the bugfix branch. This includes more hardware support & many fixes.

Please download bugfix-2.1.x to test with the latest code and let us know if you're still having this issue.

Thanks for your reply.

It works well with bugfix (configuration file version 2.1.3), that's what I've been using. But then I have another problem, everytime I try Z babystepping during the first layer the machine behaves funny. Sometimes the nozzle goes back on it's trajectory very slowly then rushes to the last position, other times the bed lowers a lot then comes back up.

@ucirello
Copy link

I'm seeing something similar:
image
Archive.zip

@ucirello
Copy link

I can confirm that with 12a2e5a (current HEAD of bugfix-2.1 it works correctly.

@houseofbugs
Copy link
Contributor

Im in the process of upgrading our UF2 code base to 2.1.2.4. Tested on 2 CoreXY machines (One of mine and one of my remote guys) and neither are able to reproduce this issue over dozens of prints. I'd suspect driver current and/or sense resistor settings being the culprit here.

@ucirello
Copy link

@houseofbugs

I'd suspect driver current and/or sense resistor settings being the culprit here.

Possibly? In terms of Configuration.h and Configuration_adv.h both RSense and current were the same before and after. I wonder if the internals reading these values may have changed somewhere.

In any case, there was a lot of noise in the diff when I transposed the configuration from 2.1.2.4 to bugfix-2.1.x, so it's not impossible that I may have unintentionally change some parameter.

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

4 participants