Original build log got locked due to inactivity. Time keeps on slippin’, slippin’, slippin’, into the future…
Anyway, today is a VERY exciting milestone on this drone journey (it’s about the journey, not the destination… right?!).
First, a few definitions:
flight controller: the ‘brain’ of a drone that handles high-urgency tasks like motor speed control, stabilization, object avoidance, navigation, etc. Most commonly based on some variant of the STM32 running a simple real-time OS.
companion computer: a more powerful, higher latency, computer that handles resource-intensive tasks like image processing and storage. In my case I’m using a Pi Zero 2W. Nvidia Jetson is also common for more advanced drones.
MAVLink: de-facto standard communications protocol to talk between drones, drone components, and control stations
The milestone: my pull request adding photo and video recording to Rpanion was merged into the upstream repo!! What that means (sorry, no fun photos this time):
Anyone running Rpanion-server on a companion computer now has the ability to use any USB or CSI-connected camera.
The camera is triggered via MAVLink commands from the companion computer, flight controller, or control station; no GPIO or serial connections are required betewen the camera and flight controller. This also makes it possible to trigger the camera from a button on the RC transmitter.
Above bullet makes it possible for the flight controller to trigger the camera automatically during an autonomous mission - either at a time interval, or when specific waypoints are reached, etc.
GPS coordinates are requested from the flight controller via MAVLink every time the camera is triggered, and (if available), added to the photo metadata to geotag the photos. Besides being fun, this also enables the images to be used to generate a point cloud or orthophoto using photogrammetry.
Something on my quad got messed up during transport the last time I took it out and now only 3 of 4 motors work, so… gotta fix that, then try out the above software!
Hi Dave, My name is Ak. I am a new member at VHS and currently building an x8 drone( octocopter with a co-axial design. I was wondering if i could connect with you for some guidance on this drone build?
I really don’t want to be TOO much of a buzzkill but I feel a duty to mention that flying any motorized RC aircraft in a park is against the bylaws of every municipality I checked–regardless of 250g, proximity to an airport or any other Transport Canada rules. When flying in your own or someone else’s private property, TC rules are in force and municipal bylaws apparently don’t care.
The handful of MAAC-affiliated local clubs do allow legit powered RC aircraft, but they all come with the traditional baggage of MAAC membership and club membership (except on fun-fly days), and most (all?) of them hate multirotors.
Kwads-R-Us seems to be exiting the MAAC affiliation cartel, we’ll see how it goes for them.
Having said all that, as mentioned in the #rc channel header, I really do need enablers to remind me to go fly something, anything, sometime, anywhere.
tbh reminders don’t help, but something like this would: “hey Alex, I’m gonna go fly at this place and at that time, would you like to join?”
I want to get my advanced pilot UAV certification.
How did you get yours? I have registered drone I can use for the certification.
I have talked to some of the MAAC clubs. And they are mostly kit plans with less quadcopters. They have arranged fields and playing fields. The advantage MAAC offers is insurance.
