(Unofficial) Lulzbot profiles are Officially in OrcaSlicer 2.3.0!

General Software
1

Edit: get it here: Release OrcaSlicer V2.3.0 Official Release · SoftFever/OrcaSlicer · GitHub

I’ve done the initial work to get some of this family into OrcaSlicer, so if you have a Taz 4, 5, 6, Pro Dual or Pro S, please give it a try and let me know what you think.

image
image1618×1309 69.8 KB

I’ll try and get the Mini 2 done for the next full release, but that will be the last of these printers I have access to for testing. I do not have access to a sidekick, workhorse, Mini3, Taz 8, or any of the Pro XL/XTs. Also, there is no great way to do the variety of toolhead combinations in OrcaSlicer without cluttering the printer list with the roughly 140 different combinations of printer and printhead currently available, let alone to test them all.

The startup GCODE is as directly translated from CuraLE as possible, as is the end GCODE.

The way print profiles for speed and quality are controlled in Cura and OrcaSlicer are different enough that there’s no way to directly translate them. In general, Cura does quality/speed profiles on a per-filament setting, while OrcaSlicer does quality/speed as a machine setting that gets limited by filament settings. I tried to stick as close as possible for a profile that should just work. OrcaSlicer has the built-in calibration tools that you can use optimize from the standard profiles, so the baseline should get you started.

Features that are notably absent in OrcaSlicer when compared to the Lulzbot-enhanced version of Cura:

Per-filament soften, wipe and probe temperatures. To get around this, all soften, wipe and probe temperatures are based on filament type. In looking in the filament profiles in CuraLE, all filament of the same type uses the same temperatures already, so as a baseline, these will be the same, but a user cannot individually tweak these temperatures per filament in OrcaSlicer.

The exclusion area on the Pro Dual is not enforced upon activation of the second extruder. This means it’s up to you to not try and use the second extruder over there. On the plus side, you can use the primary extruder on the whole bed in dual extrusion mode now. But… the prime tower has a tendency to put itself in the exclusion zone, which is not great, but easily moved into the safe zone. There is a request in to add this feature, but not sure if it’s getting any attention.

There’s no direct USB control available in OrcaSlicer, so you’re either going through octoprint, or to an SD card.

I’m pretty sure you can’t flash firmware from OrcaSlicer.

3 Likes
2

This is fantastic! Not sure if you fixed it in the final version, but the json you posted here a little while back looked to have ASA-AERO listed twice in each temp section, with different temps for each section. No biggie, it’s not a common filament.

3

I think I fixed that.

I’m switching over to regular expressions so I can wildcard out a bunch of the filament options in the next release. It makes it more complex for a beginner to look at and modify, but it’s cleaner code that can be used more readily for things like the filament-specific wipe sequences that Lulzbot is bringing in in CuraLE 5.

I’m waiting on Lulzbot to do the Cura 5.4 release that’s been in development on Github, because I’d still like the startup GCODE to synchronize with the latest firmware, and there’s some particular GCODE extensions Lulzbot has added into firmware that seem to exist solely to get around Cura not having “if-then-else” statements available in profiles (like M8100). I can replicate it in OrcaSlicer without needed the firmware updated.

4

This is great news!! I"m trying to get the cobwebs off of my old Taz4 and get to printing with Orca.

5

Definitely get the firmware updated. I’m pretty sure there’s a bunch of commands that don’t exist in Marlin 1.x that get used in Orca’s standard GCODE commands.

1 Like
6

I just installed 2.3.0 and picked the TAZ 4-5 profile. The print bed and slicer bed are misaligned. Looks like the slicer area is centered at 0,0 and the print bed has 0,0 at the corner.
Error with Slicer bed and preview bed not aligning for lulzbot 4 settings in 2.3.0 · Issue #9090 · SoftFever/OrcaSlicer · GitHub Someone has also logged the issue.

7

Thanks for pointing it out, I’ll update the model. It looks like when reducing the complexity in Orca, it moved the part origin back to lower left.

1 Like
8

I started using the Lulzbot profiles in Orca. I had to dial the retraction back it was set way to fast and to large of an amount for the old Hexagon Print head. Other than that things have been working.

9

What material, and what speed did you settle on? I’ll look into slowing it down.

10

I’m a little late to the party here, but…

WOW!

Orca has made my TAZ 6 units much more reliable with astoundingly improved print quality :smiling_face_with_three_hearts:

There’s really no comparison. Cura LE is positively ancient at this point and Orca beats in in virtually every way. It’s MUCH faster, easier to use and more feature rich.

Anybody who’s still using Cura should WAKE UP (like me, haha) and give orca a try to see what they’ve been missing!

Huge thanks to @Wrathernaut for their efforts in making this happen :smile:

Would love to also see support for Moarstruder, Dual v3 and maybe even the mini 1, 100% willing to help test new profiles.

Edit: FWIW - I’m using Orca with a small farm of TAZ 6 single extruders connected to repetier-server

11

Better late than never.

IIRC, the moarstruder is the same steps/mm and such as the standard extruder, so the only major difference would be in the filament profiles regarding max volumetric flow. You can easily do that with Orca’s max flowrate calibration tool, and create a filament variant for your Moarstruder.

Dual v3 might be worth doing, but all the dual extruders for the legacy printers have had enough issues that trying to figure out if it’s a profile issue or just fighting against physics and geometry would be a pain.

Mini1 would be easiest, but it seems that the current official firmware for it is bugged, and I don’t know if lulzbot will fix it anytime soon. If somebody gets the latest official firmware and 3rd-party software with a 4th-party profile isn’t printing right, blame is coming. So long as it’s broken on CuraLE with their firmware, it’s clear they need to deal with it, rather than some unpaid hobbyist.

12

You’re probably right about the dual. I wanted it to be awesome, have achieved some stunning prints with it, though most of the time… just want to throw it off the top of a tall building :zany_face:

I keep a mini around for quick desktop prints, maybe should look into replacing it with a bambu dual to scratch those itches.

No plans to retire my TAZ units, still aquiring them! They are excellent farm machines.

Thanks again for your contributions. Orca is just so much better! 3D printing is new again, hah!

13

Problems with Dual v2 and v3 are the usual heat creep which makes them poor with PLA, but major problem is the geometry. Even with perfect Z alignment between the two nozzles, the bed isn’t perfect, so at some points the nozzle-to-bed distance is going to be different, and you are going to run into something already printed. Plus, when you’re up and away from the bed, you now have 2x the chance of a nozzle running into a warped overhang, overextrusion, or other print defects. The sledgehammer solution of the Pro Dual printhead works, but that thing weighs almost 1.2 kilograms!

14

Truth. None of the fixes fully solved this for me.

In other news…

I just found this selkies container for orca and got it setup on my (3d) print server… now I can run Orca in a browser from anywhere! Pretty cool :smiling_face_with_sunglasses:

Screenshot From 2025-12-09 20-32-23
Screenshot From 2025-12-09 20-32-231920×1200 176 KB

15

Have found that orca with the taz6 config will allow me to slice a plate with motion outside the bounds of travel. A short way into the print, it’ll hit the y end-stop and throw off the layer alignment.

Tested the same Gcode on several printers. It’s not a mechanical issue.

Not a huge deal, as I can just take stuff off the plate…

Any ideas on how to resolve?

16

Software endstops in the Marlin firmware should be preventing that motion, even if the slicer is sending those commands.

But you can reduce the area in Orca as well in the printer config by adjusting the printable area:

image
image1023×672 45.6 KB

17

Done! Thanks for the quick resolution @Wrathernaut :grinning_face:

My machines are running drunken octopus. That may have been a contributor.

18

I have a Taz Workhorse. What do I have to do to make a profile for it? :slight_smile: I assume that there are differences in firmware and start/stop gcode.

Thanks!

JimE.

19

Comparing Cura’s startup for both the 6 and Workhorse, I don’t see anything in the startup GCODE for the Taz6 that won’t work for the workhorse as well.

The firmware handles everything that’s done differently, like homing direction and both rely upon the firmware wipe. Some versions used manual wipe commands in gcode, but in current firmware for the workhorse and Taz6, both are just issued the “G12” command to handle wiping the nozzle.

Just confirm the max Z height (cura says a workhorse has 285 of Z) and do your standard calibrations with the filament and I think you’re good.

The reason I did not make a profile for it, is I do not have access to a workhorse to confirm that it’s working.

20

The starting and ending gcode looks a little different. I’ll see if I can port it. Gotta find lists of variables for CuraLE and Orca :slight_smile:

JimE.

(attachments)

TazWorkhorseStartingGcode.gcode (4.27 KB)
TazWorkhorseEndingGcode.gcode (1.44 KB)