Skip to content

Bot is left if unknown state if a job is stopped #119

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

Open
Jnesselr opened this issue Feb 6, 2014 · 2 comments
Open

Bot is left if unknown state if a job is stopped #119

Jnesselr opened this issue Feb 6, 2014 · 2 comments

Comments

@Jnesselr
Copy link
Contributor

Jnesselr commented Feb 6, 2014

Should there be a file that is run when the machine is stopped to do things like turn off the heater? Maybe only when the bot is put offline?

@www0xx
Copy link

www0xx commented Oct 21, 2014

Yes, that would be nice.

This morning I noticed that the stepper motors are not put offline as well. Personally I would like to turn off both heaters (or set lower temperatures) and issue a motors off.

Some people issue a retract command as well before the hot end is shut down in order to be able to remove their filament after things have cooled down so something that could be edited would be nice.

Wether something like this should be bot based (every bot possibly different commands), print queue based (every print queue different commands) or server wide is difficult. I'm using marlin on all my printers and could get away with anything.

@Jnesselr
Copy link
Contributor Author

I'm thinking bot based, but I think that depending on the slicing settings,
that may change too. For now, I think having the ability to edit the start,
error, and end code will be good. I'll work on the error code part for now.
On Oct 21, 2014 7:26 AM, "W" [email protected] wrote:

Yes, that would be nice.

This morning I noticed that the stepper motors are not put offline as
well. Personally I would like to turn off both heaters (or set lower
temperatures) and issue a motors off.

Some people issue a retract command as well before the hot end is shut
down in order to be able to remove their filament after things have cooled
down so something that could be edited would be nice.

Wether something like this should be bot based (every bot possibly
different commands), print queue based (every print queue different
commands) or server wide is difficult. I'm using marlin on all my printers
and could get away with anything.


Reply to this email directly or view it on GitHub
#119 (comment)
.

@Jnesselr Jnesselr modified the milestone: 1.0 Apr 22, 2015
@Jnesselr Jnesselr removed this from the 1.0 milestone Sep 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants