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

Running Success Print script triggering continuously #231

Open
AlexandreJubert opened this issue May 2, 2023 · 14 comments
Open

Running Success Print script triggering continuously #231

AlexandreJubert opened this issue May 2, 2023 · 14 comments
Labels
bug Something isn't working

Comments

@AlexandreJubert
Copy link

AlexandreJubert commented May 2, 2023

Issue

After each print on my queue completes, instead of properly pausing the Success script is getting ran multiple times. I get a notification for it every time.

Expected behavior
The success script is ran a single time.

Script
Here's the only script that is ran on Print Success:

M18 ; disable steppers
M104 T0 S0 ; extruder heater off
M140 S0 ; heated bed heater off
@pause ; wait for user input
@BEDREADY ; make sure the bed is clear before resuming

It's the exact same issue if I remove the @BEDREADY line.

Log files
octoprint-systeminfo-20230502102500.zip
octopi.local-1683037671730.log

Thank you for your help and let me know if I can provide more information.

@AlexandreJubert AlexandreJubert added the bug Something isn't working label May 2, 2023
@Terandium
Copy link

Are you using spool manager?

@AlexandreJubert
Copy link
Author

Yes I am using spool manager.

@Terandium
Copy link

What is the amount left on your spool?

@AlexandreJubert
Copy link
Author

64g

@Terandium
Copy link

Can you try to set your spool used to 0, once done does it still behave the same?

@AlexandreJubert
Copy link
Author

If I set it to 0, my spool change script is getting spammed as well, and it looks like it's triggering then canceling prints in chain.

@AlexandreJubert
Copy link
Author

I run the same pause script on Awaiting Material event

@Terandium
Copy link

To clarify: Set your spool to full again, so it has lots of filament left. (In the spool manager the physical spool can be ignored)

I am asking this as there is a bug that triggers when the spool doesn't contain enough filament to start another print.

@AlexandreJubert
Copy link
Author

AlexandreJubert commented May 2, 2023

I see, I'll try this. One thing to note, the prints I queued uses only 0.67g of plastic each so with 64g left it should have more than enough.

@AlexandreJubert
Copy link
Author

Trying another queue right now I'll report how it behaves on print completion in 10min~.

@Terandium
Copy link

Ah okay, then what I am saying shouldn't be the issue ^^ As it has enough filament left.

@AlexandreJubert
Copy link
Author

AlexandreJubert commented May 2, 2023

Another thing to note here, the awaiting material script was getting spammed in the same way the print success script was spammed.

@AlexandreJubert
Copy link
Author

AlexandreJubert commented May 2, 2023

Alright this time it skipped straight out of the pause and triggered a print right away without pausing or me resuming the queue.

I've attached my latest system info.

octoprint-systeminfo-20230502120736.zip

@Terandium
Copy link

As far as I can tell the success print does get triggered and run, maybe it's empty? Would explain it continuing instantly.
Unsure tbh

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