HK GCS now with Heartbeats and Link Lost Warnings/Alarms

You can now define how much time passes before a warning or alarm is shown on the GCS by clicking File, Settings and selecting the Alarm and Warning Timeout on the General Tab. There is also an associated speech event for both warning and alarm as well. You can use {alarm} and {warning} as replacements in the speech string.

For example:
DANGER! DANGER! Telemetry link has been lost for more than {alarm} seconds
{alarm} is replaced with the Alarm Timeout value from the General Tab.

More detail here:

In addition, there are now 6 user definable heartbeats that can be used for anything you'd like. They can be set to fire only once (after connecting) or by seconds or multiple times per second. There are 4 default heartbeats for use with NMEA or MediatTek GPS units and 868 X-Bee's.
Heartbeats are configured by clicking File, Heartbeat Configuration

Download here:

Views: 688

Comment by Zach Bayne on January 28, 2011 at 3:15pm
As always fantastic!
Comment by Andrew Dunlop on January 28, 2011 at 6:17pm

Excellent work Paul.  I've tested the user defined heartbeat output and it works as advertised.  Perhaps we'll see quite a few instances of the HK GCS at the Outback Challenge this year.


Comment by Gary Mortimer on January 28, 2011 at 11:01pm
We are planning to try it with our Attos next week sometime in South Africa, looking forward to it. Love that one of our airframes is inthe model pack (the Firecracker)
Comment by Paul Mather on January 29, 2011 at 5:40am
I hope you'll have an internet connection Gary! I'm still working on a proxy server to cache and validate the GE API without an internet connection.

Comment by Graham Dyer on January 29, 2011 at 9:52am
yeah, we have got internet here, LOL (sorry couldn't resist)
Comment by AVS on January 29, 2011 at 9:59am

@Paul, if you manage to get the proxy stuff working i'll be using your gcs all the time! Sod the google terms and conditions :) If google wants us to use earth for the off-line stuff then they should have made the code interface better.

Great work, keep it coming!

Comment by Paul Mather on January 29, 2011 at 10:04am

@Graham, you know what I the field...not just in South Africa.


@Fab, it took lots of tinkering and back and forth with Dean and Chris from Atto to figure out what was going on. There is very little info out there about the true limitations of GE and the API. I finally found some blog posts of people complaining about the authentication and then I realized what the issue was... a timeout. The only solution I've seen to far is to pay for the Enterprise version of GE....which obviously is not an option.


I've been doing some testing with the heartbeats and the NMEA setup routine is really getting solid. Now I can finally start doing some GPS testing while walking down my street with different GPS units....

Comment by AVS on January 29, 2011 at 10:14am
@Paul, are you still using GE via the plugin?
Comment by Paul Mather on January 29, 2011 at 11:12am
Yes...API Plugin
Comment by AVS on January 29, 2011 at 11:25am

I started with the plugin, it is better and easier than the earth api but not cached and subject to stringent licence rules. You can do it all with the earth GE api using your own local tcp server providing overlays, models, placemarks etc which then just leaves the maps to come from the internet or from the earths std cache.


I guess you could feed the waypoints into your gps sim to force earth to load the correct maps prior to leaving home. However, as far as I can see, with earth, you are then back to a network link and kml. Yes, the network link and kml can be served from ram via your tcp code but it is a clumsy solution and I encountered some deadlocks. You will, no doubt, be better than me with threads and delegates but google doesn't make it easy, so best of luck :)


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

Join DIY Drones

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service