-
-
Notifications
You must be signed in to change notification settings - Fork 968
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
Orca tool changer support #6087
Conversation
Would it be possible to get build artifacts for this, as it would allow more people to assist in testing, without needing to know how to build with Visual Studio? |
I would love to test this out, but I am no Github genious, and have no idea how to get at it! Someone please point me in the right direction! |
@ccatlett1984 @Hardy786 |
Ooze prevention should work properly now. |
Looks like some setting is not right. Can you compare your configuration with the built in tool changer configuration? |
@SoftFever |
@hliebscher , can you share your start, stop and change gcodes for Prusa XL 5T? |
Perfect! |
5cdfba3
to
aec1a40
Compare
Hi ! So I did some test on Omni3D industrial machines (Factory NET, 500Lite and PRO) and everything is going well so far ! To be honest, I did not go too deep. I just tried printing parts using 2 heads with dissolvable support, not crazy stuff. But I believe that's what most companies are interested in. My coworkers were blown away to see those machines running on OrcaSlicer instead of Simplify. We are all used to slice with Orca at home but at work it's a different story and not for the best lol. |
Using the Windows portable version from this build: https://github.com/SoftFever/OrcaSlicer/actions/runs/10044929494 I had some trouble with a giant prime tower, even though the prime volume in the process settings and for the filaments were set to low values like 5mm³. The problem turned out to be the flushing volumes, which had a multiplier of 1 and were auto-calculated for my white and red filament. |
it shouldn't used the flush volume for tool changer. |
Ah, my bad, I think the problem was caused by using and adjusting my existing printer profile to multiple extruders instead of creating a new one. When creating a new printer profile with the generic ToolChanger I could not reproduce it. Anyway, my printer is a Voron 2.4 with StealthChanger, here is the project file: |
Looks like you are trying to use flush_length variable in your stealth changer, which is not defined in this build. |
I opened a buf related to a crash when using pre-multitool printer profile and converting them to multitool. |
I've got to run somewhere so I can't grab screenshots/logs right now but I am seeing an issue where the "Extra length on restart" value is not utilized unless a prime tower is enabled. I have an IDEX with purge buckets and brushes set up so I want to be able to disable the prime tower and fine tune that extra restart amount to account for the minimal ooze I lost over the purge station. If I haven't uploaded a screenshot/log within the next several hours or so, please poke me in case I forgot. Though I expect it should be easy to recreate if it really is an issue. |
b77d5b1
to
5e2f145
Compare
Merging it first to avoid more future conflicts |
…any MMU with a cutter like Filametrix) (#6241) flush_length variable is now provide correct value based on the flush matrix set by the user. pesudo code in Change filament gcode: ``` ... T1 ; Park head to the purging location G1 X0 Y-5 F12000 ; Purge certain amount of filament into waste bin G1 E[flush_length] F600 ... ``` This PR is based on the WIP tool changer branch #6087 Fixes #4194 #5937 #5912
Just wanted to say that I am currently adding multi-toolhead support to my Voron 2.4. It's my own design, based on the great work of TapChanger/StealthChanger, etc, and haven't gotten to the point of actually making any multi-color prints yet, but was able to test this over the weekend with what I have working, and it worked flawlessly. I'm happy to see that it's been merged, and look forward to seeing it in an official release in the future. I had some potential suggestions for improvement as I was working through configuration, but I'll hold those until I an confident I know what I'm doing. :-) |
Noticed strange movement to the prime tower at the tool change. After printing a layer, active tool touches the corner of prime tower and the proceed to dock. That action produces really nasty stringing. Also when using "no sparse layers" feature, theres smooth Z movement. That also produce strings. Would be nice to have some sharp movement to the side at full speed before moving to correct Z height. |
Description
Add support of tool changer printers.
A new printer model has been added:
Generic ToolChanger
Currently only support tool changer printers like
TapChanger
andStealthChanger
.Support for Prusa XL is still WIP.Prusa XL is supported now🚀GOOD NEWS🚀: Multiple successful prints have been reported; it should be safe to try Discord Thread.
For bugs, please kindly help by logging issues with details and sample projects, then label them as ToolChanger. This will help me track them.
Screenshots/Recordings/Graphs
tool.changer.klipper.mp4
Test
Feedback is welcomed!
For Mac users, please ref to this instruction: https://github.com/SoftFever/OrcaSlicer#how-to-install
Implement #5943 #2050 #5079