(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.

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.