ESC software:

- https://github.com/am32-firmware

- https://github.com/mathiasvr/bluejay

Flight controller (you mentioned these):

- https://github.com/betaflight

- https://github.com/ArduPilot

- https://github.com/iNavFlight

Control link:

- https://github.com/ExpressLRS (also uses ESP32/ESP82 chips)

Radio Controllers:

- https://github.com/EdgeTX

5+ years ago the vast majority of this stuff was proprietary-only and getting into the hobby cost thousands of dollars. Now you could start at ~$500 (big price factor for FPV is the goggles, but cheap analog ones can be had for ~$100).

Though there have been incremental improvements in flight control software, and video subsystems have moved (mostly) from analog to 2.4/5.8 GHz and digital, the overall architecture is pretty similar to what it was 5+ years ago. You have a hobby R/C transmitter and receiver driving PWM outputs (through the flight controller, typically an STM32) to hobby-type ESCs which control the motors. The ESCs are microcontroller-driven and can be reflashed, but painstakingly and annoyingly. Telemetry is typically separate from control, which is separate from video. Everything is very short-range and non-IP.

In comparison, a COTS quadcopter from DJI has a single backhaul from the airframe to the controller which does control, video, and and telemetry. And the video is impressively low-latency. (I'm pretty sure they use a WiFi-type chipset and just spew raw vendor frames, and the receiver picks up what it can, best effort. You could do this with an ESP32 in ESP-NOW mode, I suspect?) I've seen some efforts to reverse-engineer the DJI protocol but I'm not aware of a fully compatible implementation or equivalent in the OSS world.

And at the upper end of the commercial/proprietary space you have systems with out-of-the-box autonomy, multiple backhauls over IP -- so they can use LOS/BLOS radio, LTE, SATCOM, whatever you want -- integration with navigation beacon systems to reduce GPS dependence, hybrid motor/generators, redundant power systems, the whole shebang.

There's no real reason aside from developer interest that this situation exists, as far as I can see. The components are mostly all available. A Raspberry Pi running a decent RTOS would have orders of magnitude more processing capacity than an STM32 and could easily do the sort of multi-sensor fusion that the commercial systems do. LTE modems are cheap. A bigger hexacopter or fixed-wing could easily loft one of the small Starlink dishes, if someone wanted to. Stuff like "perching" (landing and recharging from solar panels) is entirely possible.

But from what I can tell, the cutting edge of open source drones is happening behind closed doors in Ukraine and Iran.

Happy to be corrected if there's new stuff that I'm not tracking, but the gap between the "art of the possible" and current practice seems large.

Lots of opportunity though, is the other way to view it.

> All-in-one PCB: Doesn’t need any 3D printed parts or such

I actually am fine 3D printing and laser cutting stuff at home but I don't have the stuff to make a PCB and don't have the hand skills to do anything more than through-hole soldering.

As someone who has for decades built flying things which could be drone'ified any day of the week, it is sort of also necessary to point out that even before drones became so widespread and commonplace, rcgroups.com has been the ecosystem in which to find oneself.

And indeed, the "model airplane/remote control flight" subject has been prosperous and flourishing as a hobby for decades too .. just feast yourself on the categories here:

https://www.rcgroups.com/forums/index.php

A very earnest exploration of the various sub-forums will reveal some extraordinary designs - some which, indeed, break the 'norm' for what a flying thing should look like, in respect to a more casual view. Magnus, aerostat, Fettler are pretty good search terms...

The repo is mostly made of plain text files, the zip and the bin don't look required for anything so if your feeling paranoid delete them before building!

https://www.bitcraze.io/products/old-products/crazyflie-2-0/

https://github.com/Circuit-Digest/ESP-Drone/blob/main/Firmwa...

I believe this is a violation of the license. Very poor form of Digikey to hire these people.

Although, it looks like 1 unit might be closer to $50 (at least for the suppliers I might use), but $150 for 10.

I think costs could be cut somewhat though. The USB->serial chip is nearly $6, but differently packaged it can be $4.40 for 1 or $3.99/ea for 10, and alternative chips that seem like they should be good enough can be cheaper still. The voltage regulator they chose is $1/ea for 500ma, while the one I would normally go to is $0.22/ea for 1000ma (dropping down to $0.13/ea for 10).

https://www.iaa.ie/general-aviation/drones/drone-register

But one of the parts is apparently already obsolete and unavailable, and two more have minimum quantities above what’s needed here, so it’s not great.

As long the PCBs have no components on them it's very cheap.

I see a screen (light grey on white) which reads something along to "Press & hold" some button to confirm i'm human. Which does nothing, because of adblocking?

Well, f* you then - let me find something different to read :)

OK. Then I'll order my stuff from Mouser in the future.

You know what you can easily do drive a truck into a crowd of people or fill your car with explosives in park it under a building and then blow up the entire building, but people aren’t doing that every day but continue whingeing about drones

With this a lot of damage can be done even without drone. As for weaponized it's not a future, it's a reality in Ukraine for years now. Defense against them is difficult to impossible. A bodyguard who can sacrifice himself may sometimes work.

(EDIT: I'm assuming you are talking about non-military use.)

I find the phone appealing because I want try to make it somewhat autonomous, like im RTS games where you give a unit a command to go somewhere and it figures the path out by itself and avoids obstacles without direct input. The phone has quite a lot of processing power and sensors and IMHO doing it on board will be more interesting. Also, I'm not sure that the connection will be always stable and high bitrate make the drone a thin client.

Still, cramming everything into a main core had tradeoffs. It's a big core to wake up & run, with significant power draw. If you start running a bunch of stuff, it can be hard to meet realtime constraints, to provide reliable processing where needed.

The blanket statement that more cores is more complicated feels too broad. There's times when io cores are much simpler cinceptually, such as when you have realtime needs such as drones might. Subdivision of responsibility & dedicated cores is a powerful way to de-complect concerns. And it can bring huge energy savings.

Multi-core is also the chip making strategy that actually makes sense. We can cram so many transistors onto a tiny tiny chip, but what do we use the transistors for? We can keep trying to build bigger faster single cores, but there's only so much instruction level parallelism and caching we can actually effectively utilize. Having tiny io cores dedicated to specific tasks can use an incredibly tiny amount of extra die space, while providing incredibly low power dedicated processing for specific subsystems. Seems like a win.

Let's resist making broad statements like "you don't need". What's "needed" might not be what's best. We should have open minds to consider advantages & disadvantages. I for one think tiny io cores can later in amazing possibilities, have seen the rp2040 as a huge leap in capabilities (throwback to the Parallax Propeller with wide SMT like behavior) that's enabled a ton of interesting flexibility & novel low power embedded creations to get off the ground.