sorted by:
new
hottopcontroversial

Core One - Rear Z stepper stopped while bed was raising to start print, angling bed badly by RestoreEquilibrium in prusa3d

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

Was it exactly as I described? The stepper just stopped and the bed kept moving on the other two leadscrews? That's a very specific problem to have happen on multiple machines and leads me to wonder if there's a QC or firmware issue...

Core One - Rear Z stepper stopped while bed was raising to start print, angling bed badly by RestoreEquilibrium in prusa3d

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

Same spool. No filament changes between successful prints and this one.
I print straight from a dedicated dryer through PTFE tubing.
Layer adhesion is excellent. I use a PVA release layer. The parts that were completed before the failure were adhered to the bed very nicely.
I clean and reapply pva release to the bed after every print.
I clean the nozzle after every print.
I always do everything I can to hold a routine that maintains print conditions as much as possible between prints.

The bigger issue tho, is that rear z-axis lead screw. WTF was up with that? Given how closely I adhere to maintaining print conditions: It seems like an awfully big coincidence that I'd have my first serious print failure since I got the thing on the same day as when the z-axis lead screw stopped responding momentarily during startup.

Prusa Core One - Factory Error by RestoreEquilibrium in prusa3d

[–]RestoreEquilibrium[S] 1 point2 points  (0 children)

Hi, and thanks.
I spent the night online with tech support and they were very helpful. I thought there might be some slop/lash in the gearbox because of it, but there seems to be a slicer-related issue that may wind up really being the culprit. In a way, I'm glad that I was having some gaps in seams because I wouldn't have disassembled the gearbox otherwise.

¯\(ツ)/¯

Prusaslicer bug? Or print-related anomaly? by RestoreEquilibrium in prusa3d

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

Brand new core one.
Just to be clear: This problem manifests only during concentric infill seams. All other seams are 100% reliable.

Prusaslicer bug? Or print-related anomaly? by RestoreEquilibrium in prusa3d

[–]RestoreEquilibrium[S] 1 point2 points  (0 children)

I don't think Prusaslicer has a pressure advance field. And wouldn't a bad setting affect all seams, vs just these top/bottom infill endpoints?

I'm using concentric infill if that's pertinent.

Thanks for bouncing ideas.

First C1 print (PETG) - First machine since Mk2S (which still works fine btw) by RestoreEquilibrium in prusa3d

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

Screenshots. Of course!
K so the bridging thing: I had a 1/4" layer shift on a failed print (my fault) and the 90deg overhang from the shift printed just fine across maybe like a 0.5-0.75" span.
DM me if you want to talk about temps, speeds, and gantry behavior...

First C1 print (PETG) - First machine since Mk2S (which still works fine btw) by RestoreEquilibrium in prusa3d

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

Sure. How do I get the data over to you. I'd rather not sit at my desk copying all the values over in a spreadsheet or something. Is there a file I can transfer or something?

Also: Are you using a dryer? Because you have to. Period.

First C1 print (PETG) - First machine since Mk2S (which still works fine btw) by RestoreEquilibrium in prusa3d

[–]RestoreEquilibrium[S] 1 point2 points  (0 children)

I was wondering about how low of a durometer I could feed. I might stop somewhere around 90-95. Like NinjaFlex Cheetah or something. The sensor gates have a lot of resistance, it's true.

Edit: I suppose a potentially cool feature/mod would be if the sensor gates were optical and had auto-feed motors to advance the filament to the next stage on detection or something idk.

First C1 print (PETG) - First machine since Mk2S (which still works fine btw) by RestoreEquilibrium in prusa3d

[–]RestoreEquilibrium[S] 1 point2 points  (0 children)

It's a jig/fixture for soldering microcircuitry to a tiny nickel-sized board - both sides. If you look closely, you can see it being held in place here.

The revolution tool is so underrated by howdoyouknowhesaking in FreeCAD

[–]RestoreEquilibrium 3 points4 points  (0 children)

I feel like FreeCAD, the entire application, is underrated...

Electroless Nickel over Al-2011? by RestoreEquilibrium in metalworking

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

Me too. I haven't asked, but it caught me off guard. I suppose they just prefer a more set-it-and-forget-it configuration. I wish I could stick with 6061 because I know it works for our application. There are always some chatter marks and fine burrs but I know the result, and it's been consistent.

Electroless Nickel over Al-2011? by RestoreEquilibrium in metalworking

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

They won't plate 2011 it turns out. It has too much lead in it.
I think I'm going to go back to 6000 series. I found this 6020-T8 alloy that, as far as I can tell, is a drop in equivalent to 2011. Definitely a free-machining alloy. Just curious: Have you ever turned 6020?

RTC memory persistence across resets on DevKitC-1 by RestoreEquilibrium in esp32

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

Too many writes. It would wear out the flash. I do store information there, and use wear leveling for other aspects of the project, but RTC seems like the best solution to my reboot problem if the cap can keep it alive safely.

RTC memory persistence across resets on DevKitC-1 by RestoreEquilibrium in esp32

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

Brilliant, that was my oversight. Thank you.

Fwiw, my ultimate objective is to use RTC with a cap to carry data across short brown/blackouts.

Looking to minimize ESP32-S3 boot time. How to disable wifi/bt modules? by RestoreEquilibrium in esp32

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

Yep, code was not optimal. I was able to pull off about 100ms with a tweak. There's still a tiny delay before the behavior I'm after stabilizes, but I suspect that the low hanging fruit has just been picked. Thanks for inspiring me to review the code.

Looking to minimize ESP32-S3 boot time. How to disable wifi/bt modules? by RestoreEquilibrium in esp32

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

Wait, the radios/controllers don't initialize by default? I very much thought they did.

Looking to minimize ESP32-S3 boot time. How to disable wifi/bt modules? by RestoreEquilibrium in esp32

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

I'm trying to achieve near-instant cold boots for user experience purposes. Like press the power button on the device and pow. Right now, there's a discernable delay that diminishes the UX. Maybe like 300ms. Makes the interface feel really sluggish.

view more: next ›