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] Wrong X-axis value after startup #1207

Closed
sfrayy opened this issue Jan 4, 2021 · 3 comments
Closed

[BUG] Wrong X-axis value after startup #1207

sfrayy opened this issue Jan 4, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@sfrayy
Copy link

sfrayy commented Jan 4, 2021

Please, before you create a new bug report, please make sure you searched in open and closed issues and couldn't find anything that matches.

Printer type - [MINI]

Printer firmware version- 4.3.0 RC1

Original or Custom firmware Original

Optional upgrades - Filament Runout Sensor

USB drive or USB/Octoprint
USB

Describe the bug
After powering the printer and staring a print the Auto Bed Levelling starts as usual but the PINDA does not probe at the correct points in X direction. Therefore the first layer gets messed up. The "Test XYZ-Axis" Calibration or stopping and restarting the print fixes this problem. Once fixed, the bug does not reappear until the next restart.

How to reproduce
Turn off power. Turn on power. Print.

Expected behavior
PINDA probes at the correct points.

Video
https://youtu.be/0BhYDexB2rs

@sfrayy sfrayy added the bug Something isn't working label Jan 4, 2021
@sfrayy sfrayy changed the title [BUG] Wrong X value after startup [BUG] Wrong X-axis value after startup Jan 4, 2021
@JohnnyDeer
Copy link

JohnnyDeer commented Jan 12, 2021

Hi @ sfrayy, check out this link and try the steps outlined there, thank you.
#561 (comment)

@sfrayy
Copy link
Author

sfrayy commented Jan 14, 2021

Thank you for your help @JohnnyDeer. A simple firmware reset fixed it for now. I will keep an eye on it and see if it reappears.

@sfrayy sfrayy closed this as completed Jan 14, 2021
@sfrayy
Copy link
Author

sfrayy commented Feb 18, 2021

UPDATE in case you come across the same issue:
The problem reoccured and i realized it appeared only when the printer was turned off for longer periods of time e.g. for a day. A restart after 5 minutes did not produce this bug. I followed the steps according to the linked post and ended up with customer support, who replaced my board. The issue did not occur with the new board, so I guess it was a hardware bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants