3 ms·
In the 60s we could do a small amount of basic numerical compute with tubes, relays and crappy germanium transistors. From day one, there were use cases for co
by edg5000 2y ago
In the 60s we could do a small amount of basic numerical compute with tubes, relays and crappy germanium transistors.
From day one, there were use cases for computers, as long as they provided tons of value with very little compute. It took until the late seventies for computers to be cheap and useful enough lower-value small-scale use cases.
Particularly banking could extract a lot of value from, say a 1 Hz CPU, because human computers more of a hassle to deal with than 9000 inefficient tubes or relays In the 60s, using computers to decode h256 video to watch some cooking instructions would be absurd.
Today, we extract value from drones, at a certain cost. The cost is determined by how much of a pain in the ass it is to use. For good PMF you need to get the value to pain ratio high enough.
These are the costs/pain points that hold back further adoption, in my personal experience:
Flight planning:
- Check adjacent land use (recreational, harbor, airport) for regulatory reasons.
- Check NOTAMS and airspace restrictions.
- Obtain airspace clearance (requires a phone call currently I believe)
- Check wheather, esp. wind speed.
- Ensure ground area is controlled and all people are informed.
During operation, continuous observation from operator required in order to detect the following potential issues:
- Battery level critical during RTH (time between low and critically low battery voltage can only be estimated and is affected by battery wear).
- Compass failure. State estimation algos will reject bad compass readings and fall back to GNSS for yaw estimation, so this can be avoided with good code)
- GNSS failure (can always happen due to tall obstacles)
The ground area needs to have no uninvolved persons (unless drone has safe abort system such as a parachute), because the following could cause an unplanned meeting with the ground:
- Battery failure
- Airframe failure
- Collision
- Thrust system failure (prop, motor, inverter)
- Flight controller failure (easy to lock up the MCU with some bad code)
If the above was not a reality, we would see more drones, esp with full autonomy. There are a lot of possible failures that are hard (but not impossible) to automatically detect and mitigate. Effectively constant monitoring by an operator is needed (this can be done remotely from a control room).
- threatofrain 2y agoHere's some thoughts that applies weights to some of the items on your list. - NOTAMS and flight restrictions should be automatically ingested. - FAA restrictions are different for emergency services. - You should have multiple drones in your fleet to deal with low battery problems. - Collision detection is a hard problem and part of why Skydio got so much money. - One point I don't see on your list is dock. IMO a dock is essential to play in the fully automated drone flight space, regardless if you're talking about site inspection or first responders.
- edg5000 2y agoTotally agree on the dock. It really is the cherry on top that gives you 100% automation.