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

Version of the Smart M600 macro as a nozzle change macro? #11

Closed
rawlus opened this issue Apr 5, 2023 · 4 comments
Closed

Version of the Smart M600 macro as a nozzle change macro? #11

rawlus opened this issue Apr 5, 2023 · 4 comments

Comments

@rawlus
Copy link

rawlus commented Apr 5, 2023

I’m not yet that proficient at writing macros with lots of variables passed, but the thought crossed my mind that the way your great smart M600 raises z up high and parks the tool head to hold temp.. with a few variable adjustments could be adapted to a great nozzle change macro..

  1. heat hotend if not at set temp for nozzle change
  2. retract/unload material if present
  3. raise z to max, x to middle, send y bed back to limit
  4. hold temp
  5. resume after pause after nozzle changed
  6. load new filament
  7. end nozzle change

i’m going to try and figure it out but it’ll take me some time…. putting the idea out there in the event there’s interest from others.

cheers.

@rootiest
Copy link
Owner

rootiest commented Apr 5, 2023

Not a bad idea!

I'll see what I can throw together, check back here later!
I will update you when I have something functional.

@rootiest
Copy link
Owner

rootiest commented Apr 16, 2023

Hey, sorry it took me so long to get this done!

I just pushed a commit that adds a NOZZLE_CHANGE macro: 1254240

The new functions are documented here: Smart Filament Change documentation: Nozzle Change

By default it will park in the center of the XYZ axes. But that can be configured to fit your own personal needs.

Try it out and let me know what you think!

I'm going to leave this issue open until you and/or some others can verify it's working for everyone.

@rawlus
Copy link
Author

rawlus commented Apr 17, 2023

very cool. i’ll give this one a try and report back. give me a few days i’m traveling at the moment. cheers.

@rootiest
Copy link
Owner

Alright I am going to go ahead and close this issue as completed.

Thanks for the idea! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants