OrcaSlicer icon indicating copy to clipboard operation
OrcaSlicer copied to clipboard

Add Prusa Core One

Open liberodark opened this issue 1 year ago • 7 comments

Description

Have extract Core One from Prusa Slicer.

Screenshots/Recordings/Graphs

image image

Tests

Now need time for test that on Core One.

liberodark avatar Feb 26 '25 20:02 liberodark

Hi, @rcloran

Have made a python script for extract information for prusa. Can you check profile if you have time ?

Best Regards

liberodark avatar Mar 02 '25 08:03 liberodark

There's also been some work going on in #8504

rcloran avatar Mar 02 '25 14:03 rcloran

Hi,

There's also been some work going on in #8504

I just saw this issue. For my part I have already made good progress. But I would like to actually try a collective effort to make the best PR possible and maybe be able to add it in Orca Slicer 2.3.0.

Best Regards

liberodark avatar Mar 02 '25 20:03 liberodark

@liberodark we have been working on a standalone profile for the C1 on the discord: https://discord.com/channels/1137181739773603922/1341526631465881762

We have a working start/end gcode that works with the chamber temperature control in OrcaSlicer (Orca doesnt have a concept of "minimal" and "nominal" and thus we have a few workarounds in place)

You are more than welcome to implement our work into this profile to get it merged in.

bwees avatar Mar 19 '25 23:03 bwees

Also, I added some margins to the core one picture so it doesnt look squished if you would like to use this picture instead: COREONE_cover

bwees avatar Mar 19 '25 23:03 bwees

Hey, I've got a Core One and I'd be happy to collaborate on and test out print profiles. I've also got 0.4 HF and 0.6 HF nozzles, and PLA, PETG, PCTG, ASA, TPU, PC, PC-CF, PP-CF, PET-CF, and PA612-CF filaments that I intend to tune well.

combin8tor avatar Mar 30 '25 22:03 combin8tor

Also, minor nitpick: instead of "Prusa COREONE" it should be "Prusa CORE One" throughout this PR.

combin8tor avatar Mar 30 '25 22:03 combin8tor

Also, minor nitpick: instead of "Prusa COREONE" it should be "Prusa CORE One" throughout this PR.

If we take what is done on the Prusa side, it is indeed COREONE. But you can change it in the search menu.

liberodark avatar Apr 03 '25 13:04 liberodark

If we take what is done on the Prusa side, it is indeed COREONE. But you can change it in the search menu.

It's listed as "CORE One" all over their website and Prusa Slicer. Where are you seeing them calling it "COREONE"?

combin8tor avatar Apr 07 '25 07:04 combin8tor

If we take what is done on the Prusa side, it is indeed COREONE. But you can change it in the search menu.

It's listed as "CORE One" all over their website and Prusa Slicer. Where are you seeing them calling it "COREONE"?

It is used throughout the macros and dependencies in the profile. We also discovered many checks in the printer's firmware that rely on "COREONE" to be in the profiles (particularly printer_model) so we should not change it.

Look at this settings file and ctrl-F for "COREONE" to see all of the dependencies on it (over 1000!).

bwees avatar Apr 07 '25 13:04 bwees

It's listed as "CORE One" all over their website and Prusa Slicer. Where are you seeing them calling it "COREONE"?

It is used throughout the macros and dependencies in the profile. We also discovered many checks in the printer's firmware that rely on "COREONE" to be in the profiles (particularly printer_model) so we should not change it.

Look at this settings file and ctrl-F for "COREONE" to see all of the dependencies on it (over 1000!).

Oh, I'm not saying that "COREONE" or whatever designation should not be used internally, but to an end user the name of the thing is "CORE One" so the display name should be that.

combin8tor avatar Apr 07 '25 14:04 combin8tor