Orca Slicer profiles

[apparle]

I recently Klipperized my SV06 -- thanks for such a great guide!

I know, based on other posts, you don't use Orca slicer, but a LOT of other people are big fans of it and I also prefer to use it.
I used https://github.com/theophile/SuperSlicer_to_Orca_scripts project to convert your Superslicer profiles into orca slicer equivalent. They did have some bugs due to slicer variable differences, and I had to manually fix up the start-gcode & output filename template. I also see a minor warning, which I'm digging into, but it's harmless.
The profiles have been working quite well, and I'm happily printing.

What are your thoughts on adding these OrcaSlicer profiles to the repo - I can clean them up and open a PR ?

Also, I'm considering opening a PR on Orca Slicer github repo itself to make profiles available by default. Of course, only if Orca Slicer is willing to accept it. Are there any licensing constraints I should keep in mind, since I just derived from your repo?

[bassamanator]

Hehe yes, this is a common request, so much so that I re-installed OS last week. Still can't stand the UI, but it is what it is. I just converted my bundles, please find the print settings attached. For some reason the --physical-printer location.ini doesn't extract the printer profiles. Could you help me with this portion? Thanks.

OrcaSlicer_config_bundle.tar.gz

[apparle]

I had used the Super Slicer profile SuperSlicer_config_bundle-SV06-SV07-All.ini, not the Prusa Slicer config. Didn't realize until now that it isn't up to date compared to PrusaSlicer config bundle.

I just tried converting the latest Prusa Slicer profile and that also goes well. There's no need to specify --physical-printer since the config_bundle already has the physical printer details. Also, --nozzle-size doesn't make any different in the output. FWIW, I ran it standalone to not muck around my existing Orcaslicer profiles. Here's my commands:

mkdir -p PS2OS_config/user/default/process/ PS2OS_config/user/default/filament PS2OS_config/user/default/machine
perl ~/tools/SuperSlicer_to_Orca_scripts/superslicer_to_orca.pl --input ~/projects/SV06_klipperize/bassamanator-Sovol-SV06-firmware/misc/PrusaSlicer_config_bundle-2.9.1.ini --outdir PS2OS_config/ --nozzle-size 0.4

It does ask whether to keep compatible_printers_condition - I chose DISCARD and apply to all profiles. We'll fix it later.
Next it asks for which OrcaSlicer printer to associate with - I chose NONE and apply to all profiles. We'll fix this.

Additional fixes that are needed after this:

• For all the machine files, the machine_start_gcode is using wrong variables. Update it to below:

  M104 S0 ; Stops PS/SS from sending temp waits separately\nM140 S0\nM117\nPRINT_START BED=[bed_temperature_initial_layer_single] HOTEND=[nozzle_temperature_initial_layer] CHAMBER=[chamber_temperature]\nPURGE_LINE\n\n;; Guide: https://ellis3dp.com/Print-Tuning-Guide/articles/passing_slicer_variables.html#slicer-start-g-code
  

• For all the machine files, the inherits tag is useful to find relevant stl, image for baseplate etc. that already exists. Modify each machine file to inherit from base machine model name (prepend "Sovol" and remove nozzle). Eg: modify SV06 0.4 nozzle.json to set "inherits": "Sovol Sv06". After some more experimenting, I realize it uses printer_model variable instead to get the right build plate image & model, so that needs to be set correctly to "Sovol SV06" etc. And it is not an absolute requirement.
• For all process files, the filename_format is using wrong variables. Update it to:

  [input_filename_base]-[printer_preset]-[print_preset]-[filament_preset].gcode
  

• For all the process files, update compatible_printers for the corresponding nozzle size machine names. Eg: below is the updated value for all 0.4 nozzle process files. This is also optional.

   "compatible_printers" : [ "SV06 0.4 nozzle", "SV06 ACE 0.4 nozzle", "SV06 Plus 0.4 nozzle", "SV07 0.4 nozzle", "SV07 Plus 0.4 nozzle" ],
  

A lot more renaming could be done to make these play nicer with other Orcaslicer profiles (marlin profiles or other printers). But that makes sense only these are submitted to Orcaslicer's repo itself as new "SV06 Klipperized" profiles.

Note -- since I've just done conversion from Prusaslicer config bundle just now, I've not run these myself. I'll start testing them to see if they work as well as my old Superslicer converted profiles over next few prints (not sure how many days).

[apparle]

Doing some testing, it seems like the gcode times are much faster for profile derived from SuperSlicer_config_bundle-SV06-SV07-All.ini vs. profiles derived from PrusaSlicer_config_bundle-2.9.1.ini. I see there's big differences in acceleration numbers.
Since Superslicer profile is outdated, @bassamanator did you choose to slow down the PrusaSlicer numbers for some reason?
For me the faster SuperSlicer derived profiles have printed fine for PLA at least.

[bassamanator]

I don't remember slowing anything down. However, from what I remember, my SS config bundle had more print profiles bundled within, and maybe even a 24mm3/s profile. Are you sure that's not the one that you tested?

Looking at your previous post, this process is not at all as straight forward as I was hoping it would be, and one that would be difficult to maintain.

BTW the user mjonuschat, who initially ported over the SS profiles to PS, also ported them over to OS. Reminder, all these profiles are based off of the Ellis SS print profiles. I wonder if you might want to start there and make adjustments for the SV06XXX's?

[apparle]

Looking at your previous post, this process is not at all as straight forward as I was hoping it would be, and one that would be difficult to maintain.

This can be automated -- in fact I did write a script to do this. But it's a combination of shell scripts + perl one liners. Let me create some PRs to the original conversion script github itself, so it doesn't have to be a separate script. And then come back and generate PR here to do fully-automated profile conversion.

[apparle]

I modified the script to completely automate the conversion and generate a single orcaslicer config bundle that can be imported.
I've opened a PR theophile/SuperSlicer_to_Orca_scripts#43 to get this merged, but in the meantime here's my git repo: https://github.com/apparle/SuperSlicer_to_Orca_scripts.git

With this change, you can generate files using this command, without even installing OrcaSlicer. It does need an additional input file printer_models_map.json but it is simple static name mapping.

perl SuperSlicer_to_Orca_scripts/superslicer_to_orca.pl --input PrusaSlicer_config_bundle-2.9.1.ini --nozzle-size 0.4 --compatible_printers_condition KEEP --skip-link-system-printer --printer-models-json printer_models_map.json --output-config-bundle OrcaSlicer_converted_from_PrusaSlicer_config_bundle-2.9.1.orca_printer.zip

This should produce a single .orca_printer config bundle which anyone can import into their installations of OrcaSlicer.
@bassamanator try this to see if it's simple enough.

I haven't yet tracked down the weird speed difference between SuperSlicer file vs. PrusaSlicer file, but both work fine. I'll chase that down later.

[bassamanator]

$ perl superslicer_to_orca.pl --input PrusaSlicer_config_bundle-2.9.1.ini --nozzle-size 0.4 --compatible_printers_condition KEEP --skip-link-system-printer --printer-models-json printer_models_map.json --output-config-bundle OrcaSlicer_converted_from_PrusaSlicer_config_bundle-2.9.1.orca_printer
Can't read printer_models_map.json: No such file or directory at superslicer_to_orca.pl line 201.
Error in command-line arguments.

It's seems that printer_models_map.json is necessary for the build?

Do you have a OrcaSlicer_converted_from_PrusaSlicer_config_bundle-2.9.1.orca_printer ready to go btw? Please attach if possible.

[apparle]

It's seems that printer_models_map.json is necessary for the build?

If you specify --printer-models-json printer_models_map.json in the command then it'll fail when file is absent. Either remove that option altogether, or just download the attachment from my previous comment and place it there.

I'll upload my version of the bundle later today.

[apparle]

Here's my converted file:
converted_PrusaSlicer_config_bundle-2.9.1.orca_printer.zip

[bassamanator]

This is brilliant work! Will test tomorrow.

[bassamanator]

I went ahead and generated a new bundle using the latest PS bundle, 2.92, that I uploaded a couple of days ago. I did make several changes, however, I think these bundles have translated quite well, so they're good to go on this repo.

Are you still tweaking settings? If not, then please create a PR containing a bundle created from the PS-2.9.2 bundle and get your contributor badge. Please name the bundle OrcaSlicer_config_bundle-2.9.2-DEV.zip

[apparle]

Should I also add the json file above as OrcaSlicer_printer_model_conversion_mapping.json used during conversion, so it can stay on the repo, and you / I / anyone-else doesn't have to maintain in separately on the side?

[bassamanator]

Yes please. Please put the bundle itself in misc/, create a new folder misc/orcaslicer-related and put the ancillary files there (including the perl script). If you're up to it, you can create a README.md simply stating the following (or anything that you like):

Generate an OS bundle by running: perl superslicer_to_orca.pl --input PrusaSlicer_config_bundle-2.9.2.ini --nozzle-size 0.4 --compatible_printers_condition KEEP --skip-link-system-printer --printer-models-json printer_models_map.json --output-config-bundle OrcaSlicer_converted_from_PrusaSlicer_config_bundle-2.9.2.orca_printer.zip

Please be sure to create the bundle itself using PS, not SS because I haven't worked on the SS bundle in well over a year.

[bassamanator]

No pressure btw, do this when you can. I just want you to get your contributor badge because this will be a big help to many of my users, and has been for me as well, I've been using OS for the first time all week and I actually like it now!

I'll also be mentioning the OS bundle in the main readme. Thanks again!

[apparle]

I've created a PR (#211).
I'm glad you this useful. I've found your SV06 repos quite useful to understand my printer quickly, and I'm glad I can contribute back to the community :-)

[bassamanator]

Merged, thanks!

I'm curious btw, are you able to export bundles directly from OS? For me it goes a bit wonky when I try to do that. Shouldn't be an issue, I'll just have to bundle things manually.

[apparle]

Yes I've used Export Preset Bundle... but it generated a separate bundle per {printer,nozzle} combo. I didn't experiment with it a lot except a few times I used to reverse engineer the Preset Bundle format for the perl script :-)

What wonky-ness do you observe?

[bassamanator]

It had something to do with my 4 screens + KDE. The window that appears after you click Printer config bundle moves to an unreachable area. In fact the bundles I exported yesterday were generated in an Ubuntu vm. I did solve the issue though, I just have to turn off 2 of my screens and the window remains reachable.

BTW The last commit to @theophile's repo was about a year ago. I think you've become the de facto maintainer of that codebase.

[apparle]

I do see @theophile commenting on the issues few months ago, so he's not completely inactive.
I don't mind maintaining a perl script -- I'm familiar enough with perl. But I don't know enough about PrusaSlicer or OrcaSlicer configs to understand the mappings of new settings added.

If you do come across any that should have been converted as a part of your experiments, send me the names of those variables and I can see how to fix that.

[bassamanator]

Welcome to the I spend my free time working for free so that others might might benefit club.

I'll ping you if I notice any issues with new properties added to PS/SS configs.

I've been printing exclusively with OS these days. I still need to do a side by side comparison, but I think OS Precise Walls bring something new to the table. Scar joints still print better on PS in my experience.

[apparle]

I just tried your latest renamed uploads and I only see a 17mm3 process file, not the 15mm3 process file.
The 17mm3 file is way too fast for my stock printer, it starts making weird noises and generates lot of layer shifts.

[bassamanator]

Unfortunately, OS does not have a way to set a speed limit in the print profiles, so for the OS bundles, I removed the 15mm3 profiles. The speed limits need to be set in each filament's profiles, which is annoying, but I see no work around for this.

[Cornersruns]

The 2.9.1 file uploaded by apparle had 17,,3 and 15mm3 process files, and I found that the 17mm3 process files had layer shifts as well as apparle. Only the 17mm3 process files are imported into Orca from the github repository. There are some big differences in the process files between the 15mm3 and 17mm3 profiles.
It appears the 15mm3 process was not exported from orca.

[apparle]

When you say speed limit, which specific setting are you talking about? There's a bunch of acceleration settings different between the 2 version:
Edit: Ignore this comment, read the next one. It's a more careful comparison.

I just compared the 2.9.2 converted profiles (from my pull request, not your versions). This difference is quite significant.

Also, there's quite a few acceleration settings in the printer itself (and as I understand, they take precedence over any thing inside process settings):

[apparle]

I went digging into differences between the version I put on my PR vs. the ones you've uploaded. I just renamed mine (Klipperized_*), imported in a blank orcaslicer install and then used Orca Slicer's own comparison tool for this.

Here's the difference between Printer config file itself. Looks like you cranked up the maximum acceleration and speed, to get rid of the warning that OrcaSlicer shows about machine settings being too low.

Just comparing the converted 15mm3 file vs. 17mm3 process config (with same printer config), below is how things look.

The crazy judders / layer shifting I observed were along Y direction (bed sling movement) while doing infill, so I'm guessing it has something to do with Y acceleration especially with sparse_infill_acceleration = 7000 mm/s2.

I'll try to use the 15mm3 profile's lower acceleration to see if my printer can handle that.

[bassamanator]

I just tried your latest renamed uploads and I only see a 17mm3 process file, not the 15mm3 process file. The 17mm3 file is way too fast for my stock printer, it starts making weird noises and generates lot of layer shifts. -@apparle

Unfortunately, OS does not have a way to set a speed limit in the print profiles, so for the OS bundles, I removed the 15mm3 profiles. The speed limits need to be set in each filament's profiles, which is annoying, but I see no work around for this. -@bassamanator

After seeing the pictures you posted, I now remember that there are many more settings at play than just max volumentric flow rate. I shouldn't have dropped the 15mm3/s profiles.

Fortunately, I backed up my config folder before the drop: OrcaSlicer.tar.gz; /home/bassam/.config/OrcaSlicer. This backup might contain some very minor differences compared to what's currently on the repo.

Will reincorporate 15mm3 profiles when I get back from my trip.

BTW just in case you didn't know, when using appimages, if you create a folder with xxx.appimage.home in the same folder as the appimage, it will put the settings for that appimage in that home folder. I only mention this because you're playing with multiple sets of settings right now, helps to keep them separate from settings that are important. Not sure how things work on Windows though.

# In this example the 2 identical AppImages have different filenames, and each will have their settings stored in their own home folders
➜ tree ~/Applications/
/home/bassam/Applications/
├── OS.AppImage
├── OS.AppImage.home ;folder
├── OS-repo.AppImage
└── OS-repo.AppImage.home ;folder

[apparle]

I use flatpak not appimages, because nicer integration/management in *ubuntu distros. I usually just delete or move ~/.var/app/io.github.SoftFever.orcaslicer/ to create multiple copies of all settings or start afresh.

[bassamanator]

OrcaSlicer_Linux_AppImage_Ubuntu2404_V2.3.0_dev.AppImage.home.tar.gz

Created 15mm3/s speed profiles (you'll find them within the tarball, the appimage home directory), everything should be as is. But when I export the bundles, the 15mm3/s doesn't get exported as is. The OS quirks are quite annoying.

[apparle]

The old android phone that was my Klipper host died, so I'm temporarily unable to use my printer altogether. Still waiting for a RPi to show up before I can try anything.

What are the quirks you're observing?
If you're packaging this as a whole -- why not consider just submitting these profiles to OrcaSlicer upstream? It'll be an easier to maintain path if you just maintain the OrcaSlicer's upstream profiles for "Klipperized SV06".

[bassamanator]

• Exporting the bundles doesn't include the 15mm3 profiles.
• It's often not possible to delete a profile because it's a parent profile. I understand why this might be the case in the background, as in programmatically, however, the user should not be burned with this. For example, PS doesn't stop me from deleting a profile that was a copy of another with minor changes.

I would consider what you're proposing, however, it's too cumbersome to work with OS at its current stage of development.

[apparle]

Just got my Klipper up again.
Looks like you solved the issue by exporting individual files. Personally, I prefer this style of release -- as someone with only 1 printer, I prefer importing only 1 printer's profiles :-)

[bassamanator]

This is not something I have control over actually, OS does what it feels like doing. It also takes me several tries to get the export to export everything successfully, a bug I imagine. It is what it is.

I've mostly switched back to using PS because they do scarf seams so much better. But it's nice to have OS ready to go if needed.