-
Notifications
You must be signed in to change notification settings - Fork 245
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] Numeric Error Accumulation Causing Layer Shifts #4465
Comments
Same nasty issue on Mk4S. 6.2.0 - firmware How could be something like that even released for public? is the Alpha 0.1 release ? |
The accumulation bug is not a regression. You're possibly attributing it something it didn't cause. |
@murk-sy Sorry to hear about that. As a workaround, try using different infill if possible or downgrade the firmware. Yes, we would like to receive your G-Code for our internal testing. Did you observe this on other printers, or just MINI? |
@CZDanol I can't say for sure it's the issue mentioned, but considering it happens on previously working gcode, I think it's safe to say it's a regression of some sort. @danopernis Sent an email with both gcodes to [email protected], title "Prusa-Firmware-Buddy Issue 4465: Numeric Error Accumulation Causing Layer Shifts". Total 24MB but hopefully there won't be issues receiving it. I've only noticed the issue on Minis, haven't had much prints on the XL with any decent amount of gyroid infill since 6.2. After cancelling the print I believe there were skipped steps on both axes, but I don't remember 100% for sure. Side note: If there will be an alpha of this fix sign me up. I print the gcodes in question in bulk anyway so printing a bunch of parts into stock is not an issue. |
Gcode B with cubic infill works without any issues (everything else including versions being the same). @pepa1367 I don't believe yours is related, as you're using grid infill and while similar, the offset between failed prints is not the same. If I had to guess it's most likely a nozzle crash due to failing supports/overhangs. But you could post the gcode just in case. |
@murk-sy it is possible that your issue is a regression. But the numeric error accumulation is not a regression, it has been in the firware for some time, we have just identified it now. |
Printer model
Mini+
Firmware version
6.2.0
Upgrades and modifications
Filament sensor
Printing from...
USB drive
Describe the bug
This is a known issue from release notes, but I believe it is a regression as it started appearing on known good gcode.
Was not an issue on 6.2.0-alpha2, can't say for sure about 6.2.0-RC1.
On 2 different gcode files so far I've encountered consistent layer shifting, of course using gyroid (that I usually use).
Gcode B (on Mini 3)
![Image](https://private-user-images.githubusercontent.com/1211672/410988381-826fa296-bcc9-4c13-be49-3fd362383b98.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyMzg0ODQsIm5iZiI6MTczOTIzODE4NCwicGF0aCI6Ii8xMjExNjcyLzQxMDk4ODM4MS04MjZmYTI5Ni1iY2M5LTRjMTMtYmU0OS0zZmQzNjIzODNiOTgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTFUMDE0MzA0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDlhNTVmYmE2YzkyZGVlNTQwNzNlOTJmZTQ4MzJmNGQ2YjMxMGY5ODIyYzUyOTc4NjQ4MTE2NjQ1M2RiNzM3NSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.KwH12YSuVqGywUZO895JgsSrFlzhD6Ur7huwzLfLHD0)
This one was sliced recently and failed both times it was printed.
The shift is by exactly the same amount.
Gcode A (on Mini 2)
![Image](https://private-user-images.githubusercontent.com/1211672/410990657-3dc94fc6-9bd0-40cb-9c94-9efe9673ed4c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyMzg0ODQsIm5iZiI6MTczOTIzODE4NCwicGF0aCI6Ii8xMjExNjcyLzQxMDk5MDY1Ny0zZGM5NGZjNi05YmQwLTQwY2ItOWM5NC05ZWZlOTY3M2VkNGMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTFUMDE0MzA0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MTFkMDcwNzA5OWY3NDk2YWEyOGRmMWI2YTc2NWI4OThjZGFjMzhlZWJhZDllZTRkZWJhMGEyOTNiNThiOWMzMCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.eB352VESJUN2LriEWBDnuAEo7GcNguPXRKuBpgHnSGs)
This one was sliced on Prusaslicer 2.8.1 and was printed a dozen or so times on both Mini 2 and Mini 3 before the current stable version, without any layer shifting. This is the main reason why I believe it is a regression of some sort.
How to reproduce
Gcode in question can be provided privately to Prusa devs if needed
Expected behavior
No response
Files
No response
The text was updated successfully, but these errors were encountered: