odm-postprocess VS msp-osd

Hey, this is one of my projects too! I use a DJI Mini 2 along with the Litchi flight control app, which allows doing things like building up waypoint missions for covering a large area. I tried doing post-processing myself with OpenCV image stitching, but found that OpenDroneMap's NodeODM program was really nice to use and produced better results. I then wrote a program[1] to parse the output of the NodeODM results package, and upload it onto my website[2] that displays them using MapLibre.

At this point, I can lay out my waypoint missions ahead of time, grab my drone bag and some coffee, walk out the site, and get the vehicle up within a few minutes. I have three batteries, so that usually translates to somewhere around an hour of flight time with reserves, and over 100 images. When I'm done, I can pull out my computer, upload the day's images to the locally-run Docker container instance of NodeODM, wait for the results to get spit out a bit later, then run my post-process script, scp them up to the VPS hosting my site, and there's the map! The automation has made the process a lot more enjoyable. I'm still hoping to tinker with things making the images separate layers so I can do a time-series of different places, but it's still been fun in the interim. Feel free to reach out if you'd like to chat--I don't see many other people that are also interested in the area!

[1] https://github.com/quietlychris/odm-postprocess

[2] https://cmoran.xyz/geospatial

This week, as most weeks, I split my time outside of the day job and my other hobbies and obligations between Discord collaboration, Ghidra, and VSCode:

https://github.com/bri3d/VW_Flash - Flashing tools for select control modules in VW MQB and now PQ35 platform cars. This week I'm working on old stuff: a simpler exploit chain for older Simos ECUs, as well as tweaks to expand support to older DSG control units used in PQ35 platform vehicles.

https://github.com/fpv-wtf/msp-osd - I pushed a rearchitect of this on-screen-display overlay system for DJI FPV Goggles last week that seems to have sorted out a lot of issues - I switched from just passing through the OSD drawing messages from the Flight Controller to a system where the video transmitter maintains the OSD character buffer and sends a compressed representation of the screen state. This makes the system much more robust to packet loss in situations where the Flight Controller sends delta updates rather than frame-at-a-time.

I only really started publishing Open Source projects a year or two ago, and while they're pretty much my worst code by any objective measure, I've met some great people and really enjoy working on these. It's fun making things that achieve a goal without so much pressure of deadlines, stakeholders, and competing priorities.

The root itself only gives you full file system access. But with it you get to modify them. The root is also perfectly safe and you won't be able to tell them appart from unrooted ones. For example stuff like this -> https://github.com/bri3d/msp-osd gives you basically 'canvas' mode on the DJI Goggles (though it's still in it's early development phase so still has some kinks to work out).

Probably not from DJI. However, the guys that rooted the goggles have MSP displayport going. It's not flight worthy just yet, using it takes out the goggle UI so you can't change channels/do anything. However, it's looking pretty promising.