Sebastian Scholz

There's a lot of radiation, there's a lot of events, and it can fail at any moment.

And so our component needs to be as reliable as possible.

And for that, we decided to have actually no code whatsoever on this product itself.

But that doesn't mean that Rust isn't involved at all.

In fact, all of our test equipment, we have a dedicated microcontroller and setup for testing our equipment, is still 100% written in Rust.

or as much as possible.

And so, but the actual drag cell that we're developing right now is purely based in electronics.

The version that we're doing right now in the future, so the version we're doing right now is for small satellites, but in the future, the next big project will likely be a larger version of it.

using a lot more complicated hardware which will require once again software and for that we're going to be able to reuse most of the codes that we've written for the alpha satellites so all of the software stack the different bootloaders that we have the onboard data handling system most of it can be rewritten and so it can be repurposed basically the hardware is going to change a bit but it's

Because we split up everything into multiple crates, we have a crate specifically for drivers of the hardware.

So that is the thing that mostly is going to change.

But other logic on top of that can stay the same.

In fact, that's one of the reasons why we split up

The organization of our code into so many crates, we have, I think, 59 crates in total in our internal crate registry.

Not all of them are directly related to the onboard data handling system.

Some of them are also for the test equipment on ground.

But splitting up the codes into well-defined little bits allows us to reuse most of them in space.

It was kind of the idea from the very beginning.

Well, I think that Rust itself is an amazing tool, and the Rust community is doing an amazing job in providing it, in caring for it, and also providing no-STD crates.

That's very important for our purpose.