-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Crash detected after 7x7 mesh bed level #1645
Comments
Mine do same its crash before starting 7x7 mesh points , after last point its go back into home position and on screen say crash detected and restarting mesh leveling again, than printing. |
In addition this appears to cause me timeouts on octoprint (#1642) I have disabled it. |
I see this problem, too. Not every time, but often enough that it is disabled. |
Hi all. @cyberboom2 , @Crowlord , @cosmith71 on which printers did it happen to you? MK3 or MK3S? |
Mk3 |
Mk3
…On Wed, 20 Mar 2019 at 14:09, PavelSindler ***@***.***> wrote:
Hi all. @cyberboom2 <https:/cyberboom2> , @Crowlord
<https:/Crowlord> , @cosmith71 <https:/cosmith71>
on which printers did it happen to you? MK3 or MK3S?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1645 (comment)>,
or mute the thread
<https:/notifications/unsubscribe-auth/AskJCXwHI1jq6fKd4IwHrLNX7qGmpFinks5vYkD7gaJpZM4b4u0a>
.
|
Mk3 makes 3! |
Following along, switching to 7x7 results in the same for me on mk3s,
switched back to 3x3 and works fine.
…On Wed, Mar 20, 2019, 8:33 AM Paul Songer ***@***.***> wrote:
Mk3 makes 3!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1645 (comment)>,
or mute the thread
<https:/notifications/unsubscribe-auth/AtGH1ym6djUBHlrilS_qVPE8m1jDM8kBks5vYlTLgaJpZM4b4u0a>
.
|
I also have a problem with a mk3. Don’t know if it’s related. It skips steps when going to the first point. It might be because of the fat bundle of cables at the back, but I’m not sure. Did not let it go through the mesh bed leveling. Reverted to 3.5.1 to avoid overheating board. Problem is gone, but there is only 3x3 mesh. |
I had this issue every time I started a print. Over the weekend, I had occasion to tear down my hot-end to clear a bit of broken filament. After reassembly of the hot-end, I performed a full Wizard self-test and calibration. Since that time, there have been no further crashes before the mesh bed leveling is started. |
I think the XYZ calibration is the one that fixed the issue |
No XYZ calibration not fixed it i try to do that same problem crashing |
Does this problem remain with the final FW 3.7.0? |
It seems fixed. |
I haven’t experienced it, but that doesn’t mean the issue isn’t still there. You cannot prove a negative.
…--Mark
On Apr 4, 2019, at 1:35 AM, Michal Fanta ***@***.***> wrote:
Does this problem remain with the final FW 3.7.0?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Its been release final 3.7.0 version its been fixed crashing problem
…On Thu, 4 Apr 2019 at 09:43, mgg4 ***@***.***> wrote:
I haven’t experienced it, but that doesn’t mean the issue isn’t still
there. You cannot prove a negative.
--Mark
> On Apr 4, 2019, at 1:35 AM, Michal Fanta ***@***.***>
wrote:
>
> Does this problem remain with the final FW 3.7.0?
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1645 (comment)>,
or mute the thread
<https:/notifications/unsubscribe-auth/AskJCWVX4rKQ8IVgS_3b2YGaI8EZMmjnks5vdbsXgaJpZM4b4u0a>
.
|
https:/prusa3d/Prusa-Firmware/releases/tag/v3.7.0
On Thu, 4 Apr 2019 at 13:14, Vilius Jonaitis <[email protected]>
wrote:
… Its been release final 3.7.0 version its been fixed crashing problem
On Thu, 4 Apr 2019 at 09:43, mgg4 ***@***.***> wrote:
> I haven’t experienced it, but that doesn’t mean the issue isn’t still
> there. You cannot prove a negative.
>
> --Mark
>
> > On Apr 4, 2019, at 1:35 AM, Michal Fanta ***@***.***>
> wrote:
> >
> > Does this problem remain with the final FW 3.7.0?
> >
> > —
> > You are receiving this because you modified the open/close state.
> > Reply to this email directly, view it on GitHub, or mute the thread.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1645 (comment)>,
> or mute the thread
> <https:/notifications/unsubscribe-auth/AskJCWVX4rKQ8IVgS_3b2YGaI8EZMmjnks5vdbsXgaJpZM4b4u0a>
> .
>
|
Environment
Printer: Prusa i3 Mk3 / MMU2
Firmware: 3.7.0-RC1 (Printer) / 1.0.5 (MMU2)
Issue
After detecting the last point in a 7x7 mesh bed level operation, the printer moves to the home position. The display shows "Crash detected", and the 7x7 mesh bed level operation repeats. This second mesh bed level attempt succeeds and the print proceeds.
The text was updated successfully, but these errors were encountered: