This is my second post in the series called "FlightZoomer 3 Innovation Previews". The first was this one: Maximized terrain awareness for drone pilots

The innovation highlight presented in the video above is the synthetic camera, that offers an FPV experience without many of the disadvantages of a classic FPV approach. In the video 10 advantages of the synthetic camera are listed and demonstrated:

  • No video data transmission needed -> less hardware, less complexity
  • Truly worldwide range if there is nothing more than 2.5G cellular connectivity
  • Highly improved reliability
  • Cut the Gordian knot of zero cost Full HD FPV
  • Principally no yello, no shaking
  • No fog, no clouds, no twilight, never night
  • Adjust the viewing angle during the flight
  • Adjust the camera tilt and yaw angle during the flight
  • Manual snap back view direction control (MSBVDC :-))
  • Integrated optional zero lag gimbal

Of course there are limitations too:

  • Close to the ground the synthetic view lacks accuracy.
  • 3D cities are limited, 100% world wide coverage is only offered as aerial image laid upon an 3D elevation model (which offers still remarkably stunning views, especially when cruising a bit higher)
  • The scenery stays static. You cant observe non-static objects, like traffic, cars,...

The solution is implemented using the MapControl of the UWP programming stack. It offers a comprehensive API to place a camera over the 3D landscape at any place and specify all the parameter, that we need (including pitch and bank angle). B.t.w. this is also the reason, why this solution is not easily portable from Windows to Android or IOS (in fact not doable at all): the Android or IOS map API do not offer the needed capabilities for this feature. Google does not support to place a camera at all at a particular position and altitude and Apple does not support the combination of setting pitch & bank while using 3D maps with an aerial image.

An important detail is the possibility, to additionally feed the video from a real FPV camera into the app. The real camera view can be placed on top of everything else as a small, moveable and resizable overlay. This feature perfectly complements the overall package, FlightZoomer offers.

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • Hi Gustavo

    Currently the software supports this: BT MAVLink, Arducopter, Windows phone 8 or higher for the Sensor device.

    Supporting Arduplane or other flavors of the telemetry connectivity would still require some extension in software and testing (= would not be ready immediately). Arduplane requires slightly different solution where Arducopter uses the GUIDED mode.

    Publically available is version 2.1 (smartphone based groundstation) but if you are interested, I could offer you a beta version of the version 3 cockpit.

  • your development is fantastic ! , congratulations and my respect to your skills .

    i would definitely try the system on my Pixhawk drone , 

    i  would need to buy a phone, is any Window phone that would recommend , does it has to be windows mobile 8?

    just windows phone ?

    may i use the mavlink radio telemetry at the same time using other port for BT mavlink to the phone?

    instead of using BT mavlink, can i use my Wifi telemetry to the  phone ( im using it with an esp8266 + esplink )

    thanks

  • Wow Martin, that's a great idea! As you just said above, you could fly a real drone with just telemetry and no video feed, that's pretty innovative. It would greatly improve "return to home" operations.
  • Hi Guy

    This is an accurate assessment about the use cases!

    For Hobby FPV it could still provide some benefit as supplementary or backup system in case of outages, bad weather. Another cool feature would be setting a "click-to-fly" target on the 3D map. Other than a camera feed, the map based presentation offers sophisticated pixel-to-longitude/latitude/elevation (and vice versa) conversion methods. Exploiting this capability I can see a lot of nice ideas, that could be realized even beyond "click-to-fly".

    For surveying I fully agree with what you write.

    The look&feel goes a bit in the direction of the direction of the Kongsberg Iris UAS, some similar applications could be possible.

    The projecting feature would be very easy doable using the custom tile source feature of the map API. In fact I am using this feature to calculate the terrain elevation map dynamically which is shown on the Navigation Display.

    IRIS UAS
    IRIS UAS is a situational awareness platform developed to provide Unmanned Aerial Systems (UAS) operators with the necessary situational awareness to…
  • It's an interesting concept that will definitely find a few applications.  I have some constructive feedback based on my personal experience and understanding.

    For hobby FPV, the whole point of flying a drone instead of using a simulation is the connection to the real world.  Close ground accuracy, dynamic scenery, weather, and aesthetics play a vital role.  As a result, I think developing it for this market is a dead end.

    For professional surveying, consider it from an actionable information perspective.  What problem does a synthetic camera solve?  The main reason for an FPV camera in my experience is either to acquire information on specific features that can't be gleaned from existing satellite imagery, or dynamic changes to the survey area.  This information is used to adjust the flight plan.  A proper 3D terrain model is definitely valuable during the initial planning stage, but the current regulations in most countries require VLOS operations, so there isn't any additional information provided by a synthetic camera system during operation.  

    Projecting sensor information (LWIR, multi/hyperspectral) onto the map in real time would be valuable, and a neat way to visualise the information.  It's something Procerus Technologies (Now owned by Lockheed Martin) have already accomplished with their OnPoint Vision system, but its terrain model wasn't as sophisticated, and it was heavily priced and subject to export controls.  This would be one application you could explore.

    Another application I think is worth focusing on is as a GCS component for professional BVLOS operations.  It would be a small component of the overall information system required for proper situational awareness, as terrain avoidance is generally managed during the initial planning stage.  However, it would be extremely useful for failure events where you have to ditch.

This reply was deleted.