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] (bug summary) losing settings #1364

Closed
mips42 opened this issue Oct 14, 2024 · 9 comments
Closed

[BUG] (bug summary) losing settings #1364

mips42 opened this issue Oct 14, 2024 · 9 comments
Labels
bug: False alarm? It is not a firmware bug or the bug cannot be confirmed.

Comments

@mips42
Copy link

mips42 commented Oct 14, 2024

Did you test with a precompiled firmware?

Yes, and the problem still exists.

Bug Description

Ender 3 V2, 442 board with Touch sensor, Version 20240122, randomly loses Z offset. Firmware seems to be crashing / resetting for no apparent reason.

Bug Timeline

Within last week

Expected behavior

Expected Z offset to remain saved even when machine is off for prolonged periods.

Actual behavior

randomly loses Z offset. Firmware seems to be crashing / resetting for no apparent reason.

Steps to Reproduce

So far, there is no set procedure to reproduce the error that I can find.

Version of Professional Firmware

Ender3v2-422-BLTUBL-MPC

Printer model

Ender3v2

Electronics

4.2.2

LCD/Controller

POLISI3D

Other add-ons

No response

Bed Leveling

UBL Bilinear mesh

Your Slicer

Other (explain below)

Host Software

None

Additional information & file uploads

Currently slicing with Creality print 5.1

@mips42 mips42 added the Bug: Potential ? Is it a bug? confirmation or more user feedback is required label Oct 14, 2024
@mriscoc mriscoc added bug: False alarm? It is not a firmware bug or the bug cannot be confirmed. and removed Bug: Potential ? Is it a bug? confirmation or more user feedback is required labels Oct 15, 2024
@mriscoc
Copy link
Owner

mriscoc commented Oct 15, 2024

I use that version, Ender3V2-422-BLTUBL-MPC-20240125 and don't have this problem.

@mips42
Copy link
Author

mips42 commented Oct 15, 2024

okay, Good. I guess. I do. I am now checking Z before every print because I never know when the setting is going to change. While this mitigates the problem, it foes not solve it.

@mriscoc
Copy link
Owner

mriscoc commented Oct 15, 2024

Maybe the motor drivers of your printer don't support the increased speed and acceleration of the new firmware. In that case it is better to return to the stock firmware.

@mips42
Copy link
Author

mips42 commented Oct 15, 2024

I suppose its possible but I'm not sure why it would affect only the Z offset. I might switch back but Id miss the viewable mesh.

@mriscoc
Copy link
Owner

mriscoc commented Oct 15, 2024

Each driver is independent, in the case of Z axis during the home and leveling operations the axis changes the direction several times.

@mips42
Copy link
Author

mips42 commented Oct 18, 2024

Add-on: after a successful print yesterday, I went to exit back to the main screen and the control knob was non-responsive. After about 5 seconds of this, the system rebooted and the z-offset was reset to zero. I dont know if this helps or not.

@mriscoc
Copy link
Owner

mriscoc commented Oct 18, 2024

the z-offset was reset to zero

Only the Z-offset was affected or all the settings returned to default?

@mips42
Copy link
Author

mips42 commented Oct 18, 2024

Not sure I understand. The Z offset is all that I am changing so, Yes?

@mriscoc
Copy link
Owner

mriscoc commented Oct 27, 2024

Several limits were implemented in Marlin which restrict what values are valid for the probe offsets, so if your current probe offsets values are out of those limits they are considered invalid and they are not taken and saved.

Related to:
MarlinFirmware/Marlin#26774
MarlinFirmware/Marlin#26267
MarlinFirmware/Marlin#26397
MarlinFirmware/Marlin#26417

@mriscoc mriscoc closed this as completed Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug: False alarm? It is not a firmware bug or the bug cannot be confirmed.
Projects
None yet
Development

No branches or pull requests

2 participants