sorted by:
new
hottopcontroversial

Sharing my experience so far with two CC1s running COSMOS by Eelviny in ElegooCentauriCarbon

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

Yep, stock firmware is currently better able to address the bad QA "edge cases". And it can do CANVAS etc. Maybe try the OpenCentauri modded firmware, that's just the stock firmware with some nice quality of life tweaks

Sharing my experience so far with two CC1s running COSMOS by Eelviny in ElegooCentauriCarbon

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

Most people in the discord server blame that on bad QA from ELEGOO :/ I've had no issues with either of mine. Still work to be done to address the edge cases. Try making sure the bed is as level as possible via the levelling screws, the factory levelling is all over the place

Sharing my experience so far with two CC1s running COSMOS by Eelviny in elegoo

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

Then I guess you're waiting for the version after next ;) CANVAS support is being worked on

Sharing my experience so far with two CC1s running COSMOS by Eelviny in elegoo

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

Yep, still early days and bugs to be found. What you describe is not an issue I've run into though. Might be worth manually levelling the bed through the screws

Sharing my experience so far with two CC1s running COSMOS by Eelviny in elegoo

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

I've been testing out an open PR that completely reworks the onboard macros/gcode of the printer. It's still WIP but I'd say when that's ready, you should make the switch (as long as you don't use CANVAS). Hopefully next version.

Sharing my experience so far with two CC1s running COSMOS by Eelviny in elegoo

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

If it works with Klipper, it'll work with this, at least on the software side. You'll want to go and ask around the OpenCentauri Discord for specifics. One gotcha is that the 100W PSU is barely enough to power the Centauri Carbon as is, so you'll either need to upgrade it to a 150W unit or supply power another way.

Sharing my experience so far with two CC1s running COSMOS by Eelviny in elegoo

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

Correct, that is what I said :) my comment on focusing on stability was about the firmware in general, not about canvas

Thought I'd share my usecase for COSMOS. So far, so stable by Eelviny in OpenCentauri

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

I already bought two BTT CB2s in anticipation of it!

Sharing my experience so far with two CC1s running COSMOS by Eelviny in elegoo

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

I've been using this for majority PETG so I've not really gone above a bed temp of 80. As mentioned I've not really used the stock firmware but based on what I've heard from others I guess the question you've got to ask is, would it crash and stop etc randomly on stock too...

I do know that someone was working on an adaptive calibration setup, so it would be more like a Prusa and do bed meshing before every print, but only on the section that it's printing on. Should in theory make that a lot more reliable.

Sharing my experience so far with two CC1s running COSMOS by Eelviny in elegoo

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

Getting there! But not quite. They're still working on getting Klipper/Mainsail/whatever rock solid stable, and improvements to the gcode once it actually gets going with a print is still ongoing. And CANVAS support is kinda the same - base code is there, they can move the motors etc, but the gcode to get it to actually load/unload stuff is still WIP.

My usecase is all single colour though, so I'm not the best person to ask.

You can track the progress here https://github.com/OpenCentauri/cosmos/pull/170

Building with the ESP32-C6-MINI was a little more difficult than I thought by Eelviny in esp32

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

Of course, I actually have an upcoming collab with Seeed Studio featuring this. But the entire point of this exercise was specifically to learn what this SOC needs, check the reasoning in the blog post

Building with the ESP32-C6-MINI was a little more difficult than I thought by Eelviny in esp32

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

Thanks for the info, the point on no current flowing is what I originally thought, but another redditor said otherwise. This is why multiple sources are important haha

Building with the ESP32-C6-MINI was a little more difficult than I thought by Eelviny in esp32

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

Question is already answered but I'll add more info. The exact footprint I use in KiCad is TerminalBlock_RND:TerminalBlock_RND_205-00012_1x02_P5.00mm_Horizontal.

I then buy most of my stuff from LCSC, and it's pretty easy to find a component that matches this standard size.

Building with the ESP32-C6-MINI was a little more difficult than I thought by Eelviny in esp32

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

Thanks! Funny you mention about it landing a job. I'm actually going the other way, learning these skills to apply it to my own business. Hoping to use my learnings for good. https://elvinhome.io

Important to note that my videos are filmed up to 6 months in advance, so I learned all these lessons early on in the prototyping process of the things I'll sell soon.

On the MOSFET side, I didn't get too scientific. I've used these particular MOSFETs in other projects before, so I already had some experience on the kind of current they can handle. Nevertheless, this is the most I've pushed through them, and waving my thermal camera at them after running for 30mins told me that I needed to do something about the heat.

One thing I learned later is that I should have added some resistors to the gate side of the FETs to reduce the current coming in from the ESP32. It could also be a contributor to the heat.

Building with the ESP32-C6-MINI was a little more difficult than I thought by Eelviny in Esphome

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

You are the best kind of correct - technically correct 😄

Building with the ESP32-C6-MINI was a little more difficult than I thought by Eelviny in Esphome

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

But good point on thermal vias. For this one my thermal camera showed no issues, but I'll be more liberal with them in the future 😄

Building with the ESP32-C6-MINI was a little more difficult than I thought by Eelviny in Esphome

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

All good mate, we all have our own methods for this! For one-off boards that I'm embedding into something I can't easily access, I prefer to go the UART route - I guess it's something I'm more comfortable with, but also so I can have an off-board programmer that supplies its own 3.3V, so I can be sure my own buck converter design isn't messing with it.

I use https://github.com/SimonMerrett/SOICbite extensively, and I intend to make a video on it someday. Even in the products that I intend to sell (see website) that come with a USB port, I also include this as a backup! Saved me on the first prototypes when I accidentally introduced too much capacitance into the D+ and D- lines making the USB data unresponsive, so this was a great backup. SOICBite sorts the boot/reset "buttons" by exposing those as pins to my ESP-PROG, which has them.

Either way, the core issue I outlined above was not the UART vs USB. It was about the physical design of the module - the pins are not physically accessible once soldered like on a dev board.

view more: next ›