No Heartbeat - iFly GPS for Android

We have a new Forum! Go here to get started: https://adventurepilot.community.forum.
The new forum is easier to use and much more capable than the old, we hope you will join our community!

Below is a copy of the old forum. This will remain available for a short period so you can access and review the information contained here. To continue a conversation, or start a new one, please register and create a post at our new forum location.

Search

Home

Discussions

iFly GPS for An...

No Heartbeat

5/22/2016 10:09 AM

John Miller

Joined: 9/12/2010

Posts: 644

No Heartbeat

I am using Navworx and it seems to be working very well, but I have a question.

When I fly from KAJO to KHMT in Southern California I actually receive a tower in the run up area. I suspect this is because there is a tower up on the nearby hill that has a VOR on it.

Then when I take off in a direction away from the hill it may say "out of range" untill I get to pattern altitude.

Then it is receiving again almost all the way to Hemet Airport.

However when I get about 6 miles from the airport at 3500 msl it says "No Heartbeat" on my IFLY using an Android tablet.

I check and see that wifi is connected and I get no UAT fail light from the Navworks unit.

Then when I get to the 45 of the Hemet Airport I get the "receiving" notice again.

This route takes me just south of March AFB and I am getting interrigation from their radar on my Garmin 327 transponder.

So what is "No Hrartbeat" telling me?

5/22/2016 8:57 PM

Brian

Joined: 9/7/2011

Posts: 4453

Re: No Heartbeat

Hi John, thank you for posting. The "no heartbeat" indicates that the ADSB device (Navworx) has stopped sending iFly the basic 1 Hz (approx) heartbeat message to say "I'm still here". For most cases, no heartbeat means the connection between iFly and Navworx is severed, or for some other reason the Navworx has stopped sending us data.

One nice feature about iFly is that we do allow you to record your entire Navworx (or any ADSB) session, so that we can duplicate the entire flight here at our office, and tell you for certain what is happening.

Here's how to do this:
1. Just before take-off, do "Menu => About => Connected Devices => Wireless Device => Enable ADSB Logger"
2. Then fly your whole flight, and make note of any issues that you saw.
3. On landing, restart iFly, answer "no" to the prompt for "re-enabling the ADSB logger", so that iFly will *not* overwrite your log with a new one.
4. Then do "Menu => About => Send Bug Report => Select Log => Scroll down and select 'AdsbRaw.bin' file.
5. In your Bug report please briefly tell us the symptoms that you witnessed during your flight.

This is a bit tedious of a process (which we need to simplify), but it does the trick of sending us the file that will enable us to replay your entire flight, by seeing 100% of the data sent to us by Navworx.

I invite you to do this for your next flight, as getting this type of data is very useful to us.

Brian Knox, Sr Software Engineer

5/30/2016 2:55 PM

John Miller

Joined: 9/12/2010

Posts: 644

Re: No Heartbeat

Brian:

I think I had a WiFi dispute due to the fact that my Android phone AND tablet were both set to receive WiFi from Navworx.

Don't know for certain, but since I nolonger have them both on WiFi I havent had a problem.

New Question: I have noticed that when I am in a flight and have the remove ghosts activated I can't see my wingmen. So I have to turn that function off and then I see me following me very closely. I guess I have to live with seeing my image if i want to see my wingmen. How far do they have to be away from me for the algorithm to let me see them with the Ghost eliminator on?

Thanks

5/31/2016 7:23 AM

Cobra

Joined: 4/20/2011

Posts: 2602

Re: No Heartbeat

FWIW, you shouldn't have a problem with multiple devices consuming ADSB information on the same wifi link. Lots of folks are using iFly that way, including myself with an Android tablet and a 720. That's how iFly currently implements flight plan sharing across devices.

5/31/2016 1:24 PM

Shane

Joined: 4/21/2010

Posts: 1709

Re: No Heartbeat

John,

Currently, the filtering logic will filter out a nearby wingman. The thought there was that it would be preferred as you'd probably not want to be alerted constantly that your wingman, known plane, it's to close. There is not iron-clad way to really determine if a nearby plane is a ghost or yourself, unless they are ADS-B out and we can tag that N-Number as "Wingman".

This got me to think it may be feasible to offer a "Assign Wingman" option to the filtering and then if they were ADS-B out, we could show that traffic, yet silence alerts.. Just a thought and I'm not sure of the demand. I'll run it up the ladder here and add it to wishlist.

Shane Woodson
Vice President | Adventure Pilot LLC.

Page 1 of 8

1

...8

iFly GPS Forum

Adventure Pilot LLC