There we go, can you hear me, okay?
All right, so I have a lot of slides that we're gonna go fast here.
Hi, how are you?
My name is Ramon Roche, I represent Drunkless Foundation
and I'm part of the Linux Foundation.
Here's some information about me.
I'm still in the Abel contributor,
but I'm the general manager for Drunkless Foundation.
I've been working for more than a decade in robotics.
I'm a colleague of the Rosero Robotics Group
together with Kim over there.
And I'm also the colleague of the Spacer Linux
Initiative under the LESA project.
So I'm here to talk to you about the Open Source UV
ecosystem Drunkote.
What is Drunkote?
Well, like the Linux Foundation, we're a nonprofit
that hosts aerobodics projects.
But we're really all focused on the collaboration
within companies and making sure that the open source
projects is aligned with the drone industry
making sure that there's relevant funding,
but also I'll go in the milestones for those projects.
So we have a cool ecosystem.
We have industry standards like Pixoc,
open hardware, open standards.
We have a map link, which is the messaging protocol,
which a lot of the older open source projects
and also companies that are not even open source are using.
We have industry members like an XP,
out there.
We have another 18 members within Drunkote.
We're part of the industry associations,
like the Open Source Robotics Alliance,
Legends Foundation, and the Open CV Foundation.
And we have quite a few projects.
Here's some of our members.
We started in 2009 at ETA's Zurich.
The project started, but Drunkote itself started in 2014
within very successful so far.
I just ran numbers.
We have around 30,000 contributors.
We have around 100 key repositories.
It's estimated that we have a billion in project value.
We have around 60 million lines of code already.
Just last year we have 1900 contributors.
And those are the projects that we have.
The Explorer, Pixoc, Mapping, Map, SDK,
program control.
In between a bunch of tooling in order to be able to develop
and earn it to facilitate the lives of the developers,
which is something that we all like.
Some of the applications I'm going to go fast
because this you might have already seen.
This is the really package delivery for Walmart.
I'm not being an inspection in a vertical and thick of landing platform.
It's in a photography.
This is like a $100,000 camera on the drone.
So you've got to ensure that the drone is safe.
Because the camera is way more expensive.
Very commoditized platforms.
The vertical thick of an landing.
Also underwater.
Beals to put robbers above surface.
You name it, right?
How are all these applications possible?
Well, thanks to the PX for other probably,
which is like at the center of the community.
I don't have a lot of time, so I'm just going to lead you read it,
but I'm going to give you the highlights.
How are we on time?
Two minutes?
Good.
All right.
So we are running a couple of nuttics arts us.
We are a modular architecture.
We have a middle work.
We are a DDS compatible.
Our middle work is called U-Orpe.
We are introducing the concept of modules within the arts us.
So all of the different components of PX4 are basically different apps.
They talk to each other through the middle work.
We're paralyzed.
We are a threat safe.
We have a lot of great hardware support.
We support custom bills.
You can make it fit into any type of hardware.
A small big.
We estimate that we have more than a million vehicles using PX4 already.
And already told you about the developers.
Some of the cool stuff of PX4.
There's flight modes.
It's a concept that is maybe familiar with you.
We have flight tests.
It's an API that helps you build flight modes.
We have parameters that expose the behavior to the end user.
There's an events interface.
You might want to subscribe to the location.
You might want to subscribe to different events.
Across different modules.
We support all of that.
We have control location.
It's a really cool feature.
That translates to trust and part commands.
And to actuator commands.
So that you don't need to actually.
In your controller.
You don't need to.
Hard code the geometry.
You can translate that through the controller.
Care API.
We have a native raw support.
We also have another cool project.
Which is pick sock.
I don't know how to make this point through work.
I think you this.
And there's more than 30 manufacturers.
We're working with PX4 right now.
PX4 gets developed within drum code.
There's a special interest group.
If you want to help develop a hardware.
Please join us.
We support a bunch of sensors.
A manufacturer is based on STM32.
But we now have the IMX support and also wrist life.
And 20 seconds.
And that's it.
We also have gimbal support.
Debuggers.
Smart batteries.
The connectors are also standardized within drum code.
So we have a great community.
We also have a program control.
Which is a mission planning software.
You can do all the things that you need to do in the drone.
Native raw support through microx rcgdds.
And we also have to say no picko support.
Thanks to Peter over there.
Simulation.
Casivo.
Classic.
All right.
Thank you.