turbo-resin VS embassy

Async Rust does definitely work for non-toy use cases. As a data point, we use Embassy for all production firmware at my startup (https://akiles.app/en), using async tasks for everything: Bluetooth, TCP/IP networking, motor control, user interface (LEDs, keypad), a key-value database in flash, stats collection... Async helps with battery life too since it allows putting the core to sleep when no task has work to do, it allows us to build devices with 1-2 years of battery life.

There's other companies using Embassy in production. Sadly firmwares are usually not open source. There's a few non-toy open-source projects using Embassy though:

- https://github.com/nviennot/turbo-resin

I know this exists, https://github.com/nviennot/turbo-resin maybe they already have something documented?

There has been some steady (but slow) progress on an open source firmware for a few popular printers, with one of the goals being to allow multiple file formats. I believe they're still targeting the Mono 4k and Saturn for their first release, but I haven't checked in on the project for awhile.

Yes!! Here's my Rust 3d printer software: https://github.com/nviennot/turbo-resin

There's a nice Photon Mono 4k reverse engineering project by Nicolas Viennot on GitHub where he fixes the crappy touch sensing in the firmware. The goal is to replace the firmware on a variety of chitu-based resin printers with much better open source firmware.

Backstory: I'm writing TurboResin, an open-source firmware for resin 3d printers. We want to support many printers, and one of the difficulty is to understand the electronic board layout and protocols of each printer.

It's coming https://github.com/nviennot/turbo-resin

This is the last part of the reverse engineering series. At this point we are confident that we can finish the firmware to do a print. The firmware repository is here: https://github.com/nviennot/turbo-resin/

There is a project to produce an open source firmware for resin printers TurboResin - it's at a very early stage (not able to actually print yet, but making progress) In time, it should be able to do something similar to what the RERF does and use different exposure times within the same print to strengthen interior parts while leaving surfaces less exposed for maximum detail, which would be very cool!

That's it in a nutshell. I think the pump idea would work but resin is messy so changing resins would be a pain and you would have to clean the lines. Although if you had control of the printer which this project looks well on it's way to accomplishing: https://github.com/nviennot/turbo-resin then you could use the build plate to mix the resin which would simplify things a lot.

thanks. looked that up. for the curious: https://embassy.dev/

Running the Embassy RP2040 USB CDC ACM serial example takes about 5 seconds on a Pico.

https://github.com/embassy-rs/embassy/blob/main/examples/rp/...

Async solves different problems, you can, for instance, have just a single-threaded CPU and still have a nice API if you have async-await. It might not be so cool at a higher level as Go's approach of channels and threads, but it's cool in embedded, read this:

https://github.com/embassy-rs/embassy?tab=readme-ov-file#rus...

"Rust's async/await allows for unprecedently easy and efficient multitasking in embedded systems. Tasks get transformed at compile time into state machines that get run cooperatively. It requires no dynamic memory allocation, and runs on a single stack, so no per-task stack size tuning is required. It obsoletes the need for a traditional RTOS with kernel context switching, and is faster and smaller than one!"

I'm just toying with Raspberry Pi Pico and it's pretty nice.

Go and Rust have different use cases, the async-await is nice at a low level.

I have not yet dipped by toes in the Rust waters, but reading about the embassy project is actually what piqued my curiosity about using C++ coroutines in embedded. Are you familiar with the project or have you found it lacking?

I think I get the basics (shoutout to the Rust Embedded Working Group!), and I've started looking for the stack I'd be using. I think Embassy is really amazing, as well as the work of the ESP team -- hats off.

> }

And this is how to do it using embassy, which is an async framework for embedded in rust:

https://github.com/embassy-rs/embassy/blob/main/examples/rp/...

> not good for embedded

embassy begs to differ

https://embassy.dev/

async/await is really just a syntax for building state machines in a way that resembles regular code. It's compiled down to the same code that you would write by hand anyway (early on it had some bloat in state size but I think it's all fixed now).

And embedded has a lot of state machines!

You can run multiple executors at different interrupt priority levels (with multiple tasks per executor), which allows tasks on the higher priority executor to interrupt other tasks. Here's an example https://github.com/embassy-rs/embassy/blob/main/examples/nrf...