mk3s+ with mmu2s jamming on unload at end of print with smart compatibility

[JoHnEyAp]

If this is a feature request describe it here

___REPLACE_THIS__FEATURE_REQUEST_DESCRIPTION_GOES_HERE

Version of Octolapse

Octolapse Version: 0.43

Version of OctoPrint

OctoPrint Version: 1.91

When you ran into the problem, did you have diagnostic logging enabled?

Diagnostic Logging was Enabled: yes

What were you doing when the problem occurred

1. setup octolapse correctly for prusa slicer v2.6 (verbose, profiles etc)
2. sliced a benchy with default settings, besides the changes required.
3. settings for stabalization are center left
4. settings for trigger is smart compatibility

What should have happened?

Benchy should have printed just fine, the artifacts may be a result of the smart compatibility choice. The filament should have unloaded without jamming.

What happened instead?

On the smoke stack of benchy their is a long tail. When the print finishes, the filament should unload without error and without ramming.

Operating System running OctoPrint and Octolapse

OS Name: Raspberry Pi 4b 8gb
Os Version: Raspberry Pi 4b 8gb

Printer model & used firmware incl. version

Printer Model: ___Prusa mk3s+ with MMU2S
Printer Firmware Version: mk3s - 3.12.2, MMU2S - 3.12.2

Browser and version of browser, operating system running browser

Browser: google chrome
Browser OS: windows 10 PC

Link to the gcode file you were printing when the problem occurred

Link to Gcode File: ___REPLACE_THIS__GCODE_FILE_LINK_GOES_HERE

Link to settings.json

Link to settings.json with all passwords removed: ___REPLACE_THIS__SETTINGS_JSON_LINK_GOES_HERE

Link to plugin_octolapse.log

Link to plugin_octolapse.log: LINK_GOES_HERE

Link to octoprint.log

Link to octoprint.log: ___REPLACE_THIS__LINK_GOES_HERE

Link to contents of Javascript console in the browser

Link to javascript console output: ___REPLACE_THIS__LINK_GOES_HERE

Screenshots and/or videos of the problem:

Screenshot/Video Links: ___REPLACE_THIS__LINKs_GO_HERE

Please consider becoming a patron

If you like this project, please support my work by becoming a patron, and consider adding a 'star' to the repository. It takes a lot of time and effort to maintain the project and respond to issues. The cost of test prints, software, cameras, printer parts, etc. can quickly add up, so every bit helps.

You can find various videos and tutorials by subscribing to my Youtube channel. You can also follow me on Twitter.

[JoHnEyAp]

So the issue is still here after formatting the sd card. I have found that it is related to the smart triggers, they do not work.

by using classic--->layer height--->only when lifted, this works just fine.

the smart triggers are causing horrible jams, the last one required disassembly of the hot end as a large piece got stuck.
it is definitely the smart triggers as I have 0 issues without octolapse and just octoprint or sd card, and now, so far, 0 issues with the above settings.

perhaps I'm using the smart triggers wrong, but even default is causing these issues.

I'm pretty sure its related to prusaslicer 2.6 or fw 3.12, i havent updated to 3.13 yet, but its beeping at me

I currently have automatic slicer configuration turned off, but i will enable it as i feel confident its working to my expectations

if i can provide any more info or help in anyway, please let me know, this is a great tool and i would love to see the bugs squashed

[FormerLurker]

I think I saw your issue on Reddit and responded. My MMU2 is not with me know, and i won't have access for a good long while (possibly late winter, but maybe not until spring). Can you try an older version of prusa slicer? I'm 99% sure it's related to the end gcode, so if there are some changes to the defaults there, it might make figuring this out easier.

[JoHnEyAp]

Yes that’s me for sure. I will try that and also think its the same thing…..this made mk4 compatible along with tree supports….ill try it out and let you know the results……would you prefer email or back to Reddit?

…

On Wed, Nov 8, 2023 at 11:09 AM FormerLurker ***@***.***> wrote: I think I saw your issue on Reddit and responded. My MMU2 is not with me know, and i won't have access for a good long while (possibly late winter, but maybe not until spring). Can you try an older version of prusa slicer? I'm 99% sure it's related to the end gcode, so if there are some changes to the defaults there, it might make figuring this out easier. — Reply to this email directly, view it on GitHub <#918 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYVKRU7IZI444XA4BOQGV4LYDPKEZAVCNFSM6AAAAAA2M3RKYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBSGQ4TAMJYGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[FormerLurker]

Here is better. It's easier to track issues and code changes and stuff.

[JoHnEyAp]

Hey, I haven't forgotten about this. I had xmas orders and now family in town, I'll be back at it Jan 4th. Before I start again, do you want me to change anything with your current suggested setup? A few new prusaslicer versions have released, I'll try an older one like u said, but what about newer? Just wanted to let you know why I haven't replied....I should have sent this much earlier and I apologize for that Thanks again for everything

…

On Thu, Nov 16, 2023, 2:20 p.m. FormerLurker ***@***.***> wrote: Here is better. It's easier to track issues and code changes and stuff. — Reply to this email directly, view it on GitHub <#918 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYVKRUZ5FFUJO6RJ3MG6MXLYE2GSNAVCNFSM6AAAAAA2M3RKYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJVGQYDMNZTGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>