-
Notifications
You must be signed in to change notification settings - Fork 246
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
[BFW-6259] [BUG] Crash leaving tool dock #4240
Comments
Hey, to be clear - this is at the beginning of a multitool print? |
Internal ticket: BFW-6165 |
Hi
Yes it is, at the start up.
Den 8. oktober 2024 kl. 11.11.13, Danol (Daniel Čejchan) ***@***.*** ***@***.***)) skrev:
…
Internal ticket: BFW-6165
—
Reply to this email directly, view it on GitHub (#4240 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/APVVBEUMVUICFBOXEWDPCNDZ2OOTDAVCNFSM6AAAAABPQQYNOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJZGI4TMMZTHE).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@Tillquist be careful, you seem to have publicly posted your address |
@Tillquist I'm failing to reproduce this. Could you please:
|
|
Hi
Here is the gcode
---
Bedst Redards
Morten Tillquist Nielsen
Danol skrev den 2024-10-14 16:25:
@Tillquist [1] I'm failing to reproduce this. Could you please:
* Send me the gcode that's causing this?
* Show me your dock station offsets?
--
Reply to this email directly, view it on GitHub [2], or unsubscribe
[3].
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@Tillquist seems like github doesn't support email attachments. |
so how can i share gcode with you? |
You can for example upload it somewhere and share the link.
…On Mon, 14 Oct 2024, 18:51 Morten Tillquist, ***@***.***> wrote:
@Tillquist <https://github.com/Tillquist> seems like github doesn't
support email attachments.
so how can i share gcode with you?
—
Reply to this email directly, view it on GitHub
<#4240 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA4JITMQ5O7TV5AJOI6PFHTZ3PZALAVCNFSM6AAAAABPQQYNOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJRG43TKOBUGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Here it is Download here The same file runs perfectly fine on firmware 6.1.3 without problems and it is made in Prusalicer 2.8.1 But the link is only valid for 3 days from now |
@Tillquist damn, I thought I have downloaded it, but apparently I forgot. Sorry :( Could you please reupload? |
Can I also ask for the exact tool mapping you used? |
I don't quite understand what you mean? |
Mapping gcode filaments to physical toolheads. The initial sequence suggests that filament 1 is mapped to tool 4. |
Thanks, and the gcode reupload? Sorry :( |
Okay, I was unable to reproduce it on my XL on 6.2.0-alpha2 with your file, but I still believe I have found the cause of the crash and I have a different reproducer. It's down in the motor control code for which we have @wavexx who's expert in that, so I will try passing the issue to him. |
Tanks 😊👍 |
Okay, we've been hopefully able to fix the issue. Please be so kind and try the next 6.2.0 candidate when it comes out and report here if the issue is resolved for you. Thank you for your cooperation :) |
I do that 👍 |
Hello, this should now be fixed in https://github.com/prusa3d/Prusa-Firmware-Buddy/releases/tag/v6.2.0-RC1. Closing the issue. If the problem persists, please let me know and I will reopen it. |
Printer model
XL Multitools
Firmware version
6.2.0-alpha2
Upgrades and modifications
No response
Printing from...
Prusa Connect
Describe the bug
I don't quite know how to describe the error, but watch the video and you can see that the print head moves in the opposite direction than it should normally do when starting to print.
Same gcoder runs fine on firmware 6.1.3 without anything.
Fail with 6.2.0-alpha2 firmware
How to reproduce
Same error the 2 times I have tried 6.2.0 alpha 2, I experienced the same error on 6.2.0 alpha 1
Expected behavior
No response
Files
No response
The text was updated successfully, but these errors were encountered: