They have a neat dashboard at https://observatory.manrs.org/
2,025 karma · joined January 30, 2019
They have a neat dashboard at https://observatory.manrs.org/
There's a few demonstrated here (26-32 seconds in): https://www.youtube.com/watch?v=vBsyFj8bEJk
And here's one that uses the ailerons instead of being able to tilt the motors: https://www.youtube.com/watch?v=L2fgL97rgK0
I could've sworn Peter Sripol built one while on Flite Test too, but I can't find it atm.
Looks like the rocket pendulum fallacy is about expecting meaningful passive stability from the location of the center of thrust vs center of mass, but even 2-rotors need to be able to tilt independently (or deflect thrust) for active control.
Theoretically this could still work even if the center of mass was above center of thrust, but the tilting/vectoring responsiveness would need to be very high. These RC models at least move so slowly that the air resistance of swinging back and fourth really does help dampen oscillations passively, but they all still have active flight controllers that are trying to keep angular velocity at zero without control input.
Tricopters are possible as tilt-rotors, where you have two motors spinning opposite directions on mirrored sides, and the third motor is on the midline in front or back and able to tilt left and right. This allows the vehicle to control yaw despite having an inherent yaw imbalance in hover. I suppose you could do any odd number of rotors this way, and more rotors would mean less inherent yaw imbalance if there's only one extra motor spinning a given direction.
Two is possible if the payload hangs below the props, and the props are able to independently tilt.
One requires collective pitch and still at least a small tail rotor to cancel out the yaw, as a helicopter, but that is far more complex and fragile. But it is the most efficient, as fewer larger props are always more efficient than more smaller ones.
So four just turns out to be minimum to have no moving parts besides the props themselves, and still have full control authority, and the control logic is more straightforward than tilt rotors and such.
Ducted fans might help a little, since they can send the turbulence further away faster, but then you have the additional mass of the ducts, and the inefficiency of accelerating the air to higher speeds, since larger slower props are more efficient (but less responsive), to the point that this is possible: https://www.youtube.com/watch?v=emK-qIbuJ-k
A junior developer will still be much better at vibe coding (in the technical sense) than a senior manager who's never looked at code, but perhaps not as good at choosing what to code in the first place.
Then of course you can add on GPS for absolute position and route planning in 3 dimensions, and a ground height sensor for auto-landing, then you can add distance sensors on the sides for obstacle avoidance... it's all incredibly intuitive from a game programmer perspective. Then you can add in some signal filtering to mask out the range of vibrations from the motors and props being imperfectly balanced.
The hard part seems to be smooth rapid vertical descent. It's impossible to predict how the prop wash will interact with the wind and push the drone around as it descends into its own turbulence. I was tracking betaflight development for a while and was wondering if we'd ever see some kind of prop-wash calibration. Is there some adjustment of PID gains while descending through prop wash that could improve stability?
Hype cycles never last forever, but that doesn't mean all the value has been tapped by any means. The fact that modern GPUs can solve ridiculously complex high dimensional functions is a superpower in every possible field of research.
Also, I did a top-down pixel measurement, where I could see the distance to Tau Ceti as well as the orbit of Neptune. The radius of Neptune's orbit was 32px, while the distance to Tau Ceti was 1152px, for a ratio of 36, when in reality, Tau Ceti is 11.9 ly away, while Neptune has an orbit radius of 30 AU, which means Tau Ceti is around 25,000 Neptune orbits away, so the planet orbit scale is too big (or distance to other stars too small) by a factor of ~694 (25000/36)
Edit: Since this was top-down, the vertical displacement didn't factor into the distance, which also contributed to Tau Ceti appearing too close on screen, so the error is slightly better than that, maybe a factor of 600.
Edit 2: Tau Ceti is rendered at 3.652 pc × 3 world units/pc = 10.956 world units
Neptune’s orbit radius is rendered as 30.05 AU × 0.0065 world units/AU = 0.195325 world units
The rendered ratio is 10.956 / 0.195325 = 56.09 Neptune-orbit radii
The real ratio should be 25,067.5 Neptune-orbit radii
The scale error = 25,067.5 / 56.09 = 446.9×
https://discourse.ubuntu.com/t/an-update-on-rust-coreutils/8...
If the RPI came with any recent mid-tier Snapdragon SOC, it might be interesting. Or if someone made a Linux distro that supports all devices on one of the Snapdragon X Elite laptops, that would be interesting.
Instead, it's more like the equivalent of a cheap desktop with integrated GPU from 20 years ago, on a single board, with decent linux support, and GPIO. So it's either a linux learning toy, or an integrated component within another product, and not much in between.
Besides the overall expansion, some of the wispy cloudy features seem to have changed more qualitatively, some of the curves have shifted shapes and positions in ways more complex than simple expansion, due to magnetic effects.