#Did orca change ironing?

1 messages · Page 1 of 1 (latest)

chrome folio
#

Did orca change something recently in regards to ironing? I never had issues before on my Bambu lab p1S machines. Now any time I use ironing the nozzles clog and I lose an entire print. Literally every time. New nozzle, new hotend, lower temp, higher temp, lower fans, higher fans, open doors, closed doors - nothing fixes it. This just began happening recently… not the prior 8 months I owned these machines. Printing PETG - same exact brand and type I’ve been printing since I’ve owned these machines.

visual grove
#

is it the nozzel clogging or is it heat creep and its blocking in the cold end

sturdy wagon
sturdy wagon
chrome folio
chrome folio
# visual grove is it the nozzel clogging or is it heat creep and its blocking in the cold end

Been printing 15 years. Not sure what the difference is between a clogged nozzle and a heat creep clogged nozzle. Both are clogged and require I disassemble the hotend, heat it, clean the crap out of it and reinstall it. Seems to be a heat creep issue… but as my post states, no mater what variable I change it doesn’t fix it which is leading me to believe that orca changed the behavior of the machine during ironing

#

I don’t run PETG on my other machines except for PETG cf which irons at a higher speed than my standard PETG

#

I mostly run PPA-CF. It never clogs, never has heat creep issues…

#

Im also running one of my machines now with the same file that just clogged my other machine, but from Bambu studio (which I haven’t used since a month after buying the machines) to rule out software

sturdy wagon
chrome folio
#

No, I haven’t updated the firmware on my Bambu lab machines in ages. I keep them on older versions to use orca and Bambu studio combined

#

Or rather the Bambu app and orca

visual grove
chrome folio
#

There isn’t debris in the nozzle. There is a physical blockage from heat creep preventing any filament from extruding. Nothing has changed on the cold end. This didn’t happen the first 500 hours on these machines. Now it’s clockwork. They can’t iron to save their own lives without a damn clog

visual grove
chrome folio
#

Nope. I’ve even changed to brand new hotends, changed fans, changed nozzles… as I stated originally. Complete swaps, keeps happening on all 3 of my machines. Same filament as always.

visual grove
#

can you post one of your 3mf files thats causing the issue

chrome folio
#

For whatever it’s worth, it’s printing to completion with Bambu studio

#

Same exact file, same exact settings, just Bambu studio vs orca… they definitely changed something with ironing behavior

visual grove
#

which version of orca slicer are your using?

chrome folio
#

If this file prints several more times without issues on Bambu studio, I’m gonna have to stop using orca.

sturdy wagon
#

Are you using the default system profiles with no changes, or are they modified user presets?

chrome folio
#

I use 100% of my own created profiles. Not some amateur using presets. The question doesn’t explain why all of the sudden this issue arose despite not changing my settings or filament or machines…

I have since repeated the file several more times via Bambu studio with zero issues. This is a huge disappointment for me because I sincerely prefer orca, but cannot tolerate algorithmic changes to ironing within the software causing constant and repeated failures across my machines. If you had any idea how many dozens of hours or kilos of wasted filament I had on my last print job, you would be disgusted to learn it was almost all caused by an Orca update.

queen vessel
#

blaming orca is the wrong way still, it won't magically update and change stuff like that silently

sturdy wagon
chrome folio
# queen vessel blaming orca is the wrong way still, it won't magically update and change stuff ...

Enough of the fanboy mentality, seriously. I’m not loyal to any software or brand but already expressed my preference is orca. I updated orca. With the update came unnecessary changes to the algorithm for ironing which is now evidenced by comparing the same file printed multiple times from Bambu studio which had zero failures compared to orca with a 100% failure rate after ironing. Sorry to hurt your feelings or ego or whatever, but the results are what they are and it sucks because again, I prefer orca…

#

After testing all other variables as my first post stated, the only other variable I hadn’t tested was the slicer.

#

Slicer side by side print testing now confirms that the same files printed from orca fail.

sturdy wagon
#

Sadly, not all changes will satisfy the needs/desires of all users, and in some cases may break specific workflows or render previous tuning no longer effective. That doesn't make the change wrong, it just makes it a change. If nothing ever changed, we would never progress, and would still be printing with the same processes and quality from 15yrs ago, and I don't think any of us want to be back there.

queen vessel
chrome folio
chrome folio
# sturdy wagon Sadly, not all changes will satisfy the needs/desires of all users, and in some ...

I never said it had changed on its own I said it had likely updated as I couldn’t recall if I had done the update or not between the last job and this one. Based on the version I’m running, it appears I did. Ironing wasn’t broke… it didn’t need fixing. Updates shouldn’t break workflow or functionality, they should simply improve upon it or we are just going backwards instead of forwards… not to mention creating a lot of unnecessary waste of time, materials and energy with failures that shouldn’t be happening.

sturdy wagon
# chrome folio I never said it had changed on its own I said it had likely updated as I couldn’...

Just semantics in the wording. Saying "it might have updated" would infer that you had no control over it rather than saying "I might have updated it." While normally such doesn't matter, in troubleshooting and asking for help it very much does because the differences each lend to a very different understandings of what has happened.

Changes can certainly be expected to change workflow, especially where workflow is individual to the user. While it may have broken it for one user, it may have improved it for others. The same frustrations and arguments get made every time any software changes its UI (e.g. think Windows, Android, Apple, etc). Workflows have always been dependent on the systems and procedures available, and when those change, so must the workflow, often discovering that it has become better with the change. But like I said, that's not true for everyone.

visual grove
#

Still waiting for your 3mf file that was causing you issues

queen vessel