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

Orca tool changer support #6087

Merged
merged 35 commits into from
Jul 29, 2024
Merged

Orca tool changer support #6087

merged 35 commits into from
Jul 29, 2024

Conversation

SoftFever
Copy link
Owner

@SoftFever SoftFever commented Jul 10, 2024

Description

Add support of tool changer printers.
A new printer model has been added: Generic ToolChanger

Currently only support tool changer printers like TapChanger and StealthChanger.
Support for Prusa XL is still WIP. Prusa XL is supported now

⚠️WARNING⚠️ : please proceed with caution. It hasn't been tested on an real printer yet. Please double check with g-code before printing it.

🚀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

  • Occasionally crashes when change printer settings
  • Prusa XL profiles and custom gcode
  • Ooze prevention bug
  • Prusa XL z offset issue when prime tower is used
  • Preheat nozzle(temporary solution)
  • infinite(tall) skirt when both ooze prevention and skirt are enabled
  • skirt/purge cone overlap
  • Document about custom variables

Implement #5943 #2050 #5079

@SoftFever SoftFever added enhancement New feature or request Community testers wanted Looking for community testers and feedback labels Jul 10, 2024
@ccatlett1984
Copy link

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?

@Hardy786
Copy link

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!

@SoftFever
Copy link
Owner Author

@ccatlett1984 @Hardy786
you can download builds here: https://github.com/SoftFever/OrcaSlicer/actions/runs/9876244229?pr=6087
image

@Parozzz
Copy link

Parozzz commented Jul 12, 2024

I was trying this for a Raise3D Pro 3 and this error appears everytime i try to slice.
image

Before i was doing it by enabling the manual filament changed with custom change filament gcode for extruder switching. I have removed everything in it and is still doing it.

I've attached the 3mf file for the project.

OrcaCube.zip

@SoftFever
Copy link
Owner Author

Ooze prevention should work properly now.

@SoftFever
Copy link
Owner Author

I was trying this for a Raise3D Pro 3 and this error appears everytime i try to slice.

image

Before i was doing it by enabling the manual filament changed with custom change filament gcode for extruder switching. I have removed everything in it and is still doing it.

I've attached the 3mf file for the project.

OrcaCube.zip

Looks like some setting is not right. Can you compare your configuration with the built in tool changer configuration?

@hliebscher
Copy link
Contributor

hliebscher commented Jul 12, 2024

@SoftFever
i have a running prusa xl 5 head config including the modified start stop and change gcodes

@Ro3Deee
Copy link

Ro3Deee commented Jul 13, 2024

i have a running prusa xl 5 head config including the modified start stop and change gcodes

@hliebscher , can you share your start, stop and change gcodes for Prusa XL 5T?

@SoftFever
Copy link
Owner Author

Prusa XL 5T support has been added.
I've done manual g-code inspection, looks good.
Looking for experienced testers as I'm don't the machine.
image
image

@SoftFever
Copy link
Owner Author

@SoftFever i have a running prusa xl 5 head config including the modified start stop and change gcodes

Perfect!
I tried to port PrusaSlicer's XL 5T profile and keep the custom g-code as original as possible.
Can you review the profile I just added and let me know if it looks fine?

@Fiodar24
Copy link

Hi !

So I did some test on Omni3D industrial machines (Factory NET, 500Lite and PRO) and everything is going well so far !
I wanted to give you a better feedback but honestly, there is just nothing to say lol, your build works perfectly for me.

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.
Anyway, thank you again for this build ! I can't wait to see it added on the new release of Orca !

@SoftFever SoftFever marked this pull request as ready for review July 23, 2024 10:21
@dotrey
Copy link

dotrey commented Jul 23, 2024

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.
Since the button for flushing volumes is hidden when the SEMM checkbox in the printer settings is not checked, the slicer should probably also force the flushing volumes to be 0.

@SoftFever
Copy link
Owner Author

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. Since the button for flushing volumes is hidden when the SEMM checkbox in the printer settings is not checked, the slicer should probably also force the flushing volumes to be 0.

it shouldn't used the flush volume for tool changer.
What printer are you using? Can you share the project file?

@dotrey
Copy link

dotrey commented Jul 24, 2024

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. Since the button for flushing volumes is hidden when the SEMM checkbox in the printer settings is not checked, the slicer should probably also force the flushing volumes to be 0.

it shouldn't used the flush volume for tool changer. What printer are you using? Can you share the project file?

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:
Multi-Color-Test-Huge-Prime-Tower.zip

@meiliang1123
Copy link

I installed this version to test a Voron tool changer, which appeared to work ok, but when I changed back to Bambu X1C and start a print I get this slicer error... image

image
the same problem, i built from the latest code.

@SoftFever
Copy link
Owner Author

I installed this version to test a Voron tool changer, which appeared to work ok, but when I changed back to Bambu X1C and start a print I get this slicer error... image

image the same problem, i built from the latest code.

The quoted issues have been fixed.
Can you provide a bit more info regards how to reproduce the issue?

@SoftFever
Copy link
Owner Author

I installed this version to test a Voron tool changer, which appeared to work ok, but when I changed back to Bambu X1C and start a print I get this slicer error... image

image the same problem, i built from the latest code.

Looks like you are trying to use flush_length variable in your stealth changer, which is not defined in this build.
You can try this PR instead: #6241

@FlisherOfatale
Copy link

I opened a buf related to a crash when using pre-multitool printer profile and converting them to multitool.

#6208

@yw4z
Copy link
Contributor

yw4z commented Jul 26, 2024

Hi great work, wish i have a mm printer :)

Machine Setup > Toolchanger thumbnail
• Will make a design for later with orca arena thumbnail

Filament Settings > Multimaterial > Toolchange parameters with multi extruder MM printers
• You can use param_toolchange.svg for this

Parameters > Filament for features
Screenshot-20240726173026
basically combined a spool with walls and surfaces icon Screenshot-20240726173102

Parameters > Ooze prevention
Screenshot-20240726173026 - Copy

btw you can tag me when an icon needed

@staal54a
Copy link

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.

@SoftFever
Copy link
Owner Author

Merging it first to avoid more future conflicts

@SoftFever SoftFever merged commit f24c722 into main Jul 29, 2024
14 of 15 checks passed
SoftFever added a commit that referenced this pull request Jul 29, 2024
…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
@webbbn
Copy link

webbbn commented Jul 30, 2024

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. :-)

@SoftFever
Copy link
Owner Author

Hi great work, wish i have a mm printer :)

Machine Setup > Toolchanger thumbnail • Will make a design for later with orca arena thumbnail

Filament Settings > Multimaterial > Toolchange parameters with multi extruder MM printers • You can use param_toolchange.svg for this

Parameters > Filament for features Screenshot-20240726173026 basically combined a spool with walls and surfaces icon Screenshot-20240726173102

Parameters > Ooze prevention Screenshot-20240726173026 - Copy

Thank you. Looks good!
Except the ooze icon feel a bit off.

btw you can tag me when an icon needed

It's not finalized yet ;)

@RNGIllSkillz
Copy link

RNGIllSkillz commented Aug 4, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community testers wanted Looking for community testers and feedback enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.