ILS and runway land assist in PitLab FPV kit: OSD+AP

Hello and happy new year for all of you.

I would like to present new functionality of assisting pilot for landing in hard conditions like fog or night recorded last night by Jwalentek, our test pilot using OSD+AP kit,

On screen are 2 new components. One in the centre of view is envelope of runway with approaches lines, second below is ILS with 2 crossed lines showing relation plane to ideal landing path.

At this moment it is experimental firmware. Final functionality should be available soon.

Views: 2572

Comment by turdsurfer on January 2, 2015 at 9:19am

Ah you thought of that :) What's probably needed is a small Arduino board to translate Mavlink into what the Pitlab OSD needs. I took a quick look at the API file and I didn't see any functions to set coordinates, flight mode, or screen switch channel. I also see that the Pitlab OSD board itself has plugs for various peripherals such as the RC receiver, GPS, current sensor, etc, but with APM/Pixhawk those devices are already peripherals of the autopilot board itself.

I assume that the reason the Pitlab OSD connects directly to those peripherals is because it is also meant to be used stand-alone (without autopilot) as well. I understand that it's difficult to satisfy all wishes for all situations, but if I were to (and could) design such an OSD, then I'd make it require a telemetry connection to either a full autopilot board with peripherals (such as APM/Pixhawk), or else a connection to a telemetry hub with the same peripheral connections.

Comment by Pitlab on January 2, 2015 at 11:25am

Coordinates (GPS longitude and latitude) can be  displayed with command "G". Flight mode has own control, but at this time not accessible from API. The "Auxiliary text" can be used to display mode. Screen channel in my opinion is not necessary. OSD has 4 user definable screens and pilot rememeber his screens. In worst case is only 4 to check.

Peripherals: Yes, the OSD can work standalone. In this mode it read information from sensors (GNSS, current sensor, airspeed, temerature). When is tied with other system, OSD can read that parameters from it.

The OSD has own autopilot (AP). It is doughtier board. The autopilot provide stabilisation in the flight and automatic return to home or to next defined waypoint.

The OSD has also telemetry send to the ground over video channel :-) Receiver of that telemetry is Ground Station. It drives tracking antenna, has 2-channel diversity and 3-channel video splitter. Also can store telemetry on micro SD card for off-line analysis. As you can see it is complete system. :-)

Comment by Marek on January 2, 2015 at 11:55pm

Hello Pit,

IMHO problem has "opposite" direction :)

If your OSD will accept MAVLink (via serial and/or CAN) - you  increase sale of OSD by thousands %.

Comment by Pitlab on January 3, 2015 at 1:14am

Hello Marek

We understand it and have in plans adding MAVLink protocol. But still we have lot of requests from local market where MAVLink is almost unknown and not used.

Comment by Mariusz on January 21, 2015 at 3:44am

Hi Pit,

I was the one requested the MAVLink for OSD :). You should remember our talk in the past.




You need to be a member of DIY Drones to add comments!

Join DIY Drones


Season Two of the Trust Time Trial (T3) Contest 
A list of all T3 contests is here. The current round, the Vertical Horizontal one, is here

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service