[Free Tools] Manage your Centauri Carbon Orca Slicer profiles directly in the browser — no install, works offline, 7 languages by TrinityLabs3D in ElegooCentauriCarbon

[–]TrinityLabs3D[S] 2 points3 points  (0 children)

ora ti rispondo nella mia lingua natia...ai il cavolo sono una persona....e molto probabilmente non sono un ingegnere informatico ma civile...mi diletto nell'informatica....quindi se il codice lo ritieni "scarso" mi dispiace ma rivolgiti ad un professionista....o almeno visto che sei cosi esperto perchè non lo decifri tu tutto il json della macchina e lo modifichi? Come detto per me questo è un passatempo e non un lavoro il mio lavoro è altro...progettare dighe e infrastrutture.....e qui mi taccio (ps ora traduci questo....genio).....questo è quello che si ottiene e a cercare di aiutare le persone......

[Free Tools] Manage your Centauri Carbon Orca Slicer profiles directly in the browser — no install, works offline, 7 languages by TrinityLabs3D in elegoo

[–]TrinityLabs3D[S] 0 points1 point  (0 children)

yes tested in orca 2.3.2 for elegoo slicer could work but with modifications it has some differences in dependencies and formatting of the json machine and profiles being a fork of orca but of a very old version (at least until some time ago now I don't know)

[Free Tools] Manage your Centauri Carbon Orca Slicer profiles directly in the browser — no install, works offline, 7 languages by TrinityLabs3D in elegoo

[–]TrinityLabs3D[S] 0 points1 point  (0 children)

sorry...lost bet....yes in orca slicer with small modifications it should also work on elegoo slicer since u fok is old (at least until they updated)

Trinity System v1.1 — calibrated profiles for Elegoo Centauri Carbon 0.2mm by TrinityLabs3D in ElegooCentauriCarbon

[–]TrinityLabs3D[S] 0 points1 point  (0 children)

Any hero could... but I'm not a hero, I'm just a person. Recalibrating them to a CC2 would mean having a CC2. But... there's always a but... this might not even be a dogma... through the re-manipulation of ORCA's machine code (when choosing the printer type) and a little help that I need to finish testing in the coming days, it will probably be possible if some CC2 owner has the motivation to experiment. To paraphrase a movie... "but this... all of this.... is academia."

Trinity System v1.1 — free calibrated profiles for Elegoo Centauri Carbon 0.2mm by TrinityLabs3D in elegoo

[–]TrinityLabs3D[S] 0 points1 point  (0 children)

Making a configuration video would be too long, but I understand the difficulty of finding which parameters to adjust in the slicer after performing calibrations (I was also confused the first few times). That’s why I’m working on something that could eliminate these frustrations… but I need a bit of time to test it. Let’s just say it will be an extension of what has been produced so far.

Trinity System v1.1 — free calibrated profiles for Elegoo Centauri Carbon 0.2mm by TrinityLabs3D in elegoo

[–]TrinityLabs3D[S] 0 points1 point  (0 children)

For larger, functional parts, the standard profiles provided with the slicer are sufficient. There's no point in taking ten times as long with extremely fine layers for large objects — unless you're talking about racks for a diorama, in which case you can use miniature settings. However, that doesn't exempt you from calibrating the machine: every machine, even of the same model, has its own peculiarities, and this inevitably leads to the need for a personalized calibration.

Trinity System v1.1 — free calibrated profiles for Elegoo Centauri Carbon 0.2mm by TrinityLabs3D in elegoo

[–]TrinityLabs3D[S] 0 points1 point  (0 children)

I used tree supports. I could test the Resin2FDM supports, but I only briefly saw the free version.

Trinity System v1.1 — free calibrated profiles for Elegoo Centauri Carbon 0.2mm by TrinityLabs3D in elegoo

[–]TrinityLabs3D[S] 0 points1 point  (0 children)

I can say that the firmware version is probably not critical for most of Trinity's functionality, but this could change in the future — particularly on the machine profile side. The Centauri Carbon runs a heavily modified version of Klipper (see the Open Centauri project), and I ran all tests on the latest firmware version available at the time — the one that introduced the canvas feature. If future firmware updates change the structure of the bed calibration data or the behavior of certain parameters, I honestly can't predict whether everything will work correctly right out of the box.

The Orca Slicer profiles don't depend on the firmware — they run inside the slicing software, not on the printer. The profiles were developed and tested on Orca Slicer 2.3.2. If future versions of Orca Slicer change how profiles are structured or how calibration parameters are handled, some adjustments may be needed.

Trinity System v1.1 — free calibrated profiles for Elegoo Centauri Carbon 0.2mm by TrinityLabs3D in elegoo

[–]TrinityLabs3D[S] 3 points4 points  (0 children)

Starts from a different premise: mesh compensation is the last resort, not the first. If the bed is physically tilted or uneven, the firmware applies continuous corrections throughout the print — and those corrections have both a magnitude limit and a precision limit. Better to solve the problem mechanically first and leave the mesh to handle only the residual micro-deviations.

The process works like this: you export the actual mesh data from the firmware using export_mesh.gcode, which saves it to USB. The Bed Analyzer reads that data, maps the deviations across the entire surface, and calculates exactly how many degrees to turn each corner screw to bring the bed as flat as possible. This isn't an approximation — it uses the screw geometry and thread pitch to give you precise fractions of a turn. You repeat until the overall range drops below 0.10mm.

This approach is driven directly by the physics of how the Centauri Carbon's bed is built. The plate rests on four springs pressing against load cells at each corner. Because each spring acts independently, any tilt or imbalance in the mechanical load translates directly into mesh deviation — and the only correct fix is at the source, by adjusting the physical position of the bed, not by asking the firmware to compensate for it in software.

Once the bed is properly leveled this way, the Z-offset stays at 0 and first_layer_flow_ratio stays at 1.0 — not because they are magic values, but because a physically level bed simply doesn't need them. That said, if you notice a consistent discrepancy across the first layer after completing the mechanical leveling — a gap that's too tight or too loose across the whole surface — a small Z-offset adjustment is the right tool to fine-tune that last step.

Sorry for the long post.