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

6/27/2016 2:52 PM

Shane

Joined: 4/21/2010

Posts: 1709

Re: No Heartbeat

John,

I see you bug report. If you get a chance to retest and enable the ADS-B Logger, touch Menu -> About -> Connected Devices -> then Check the Enable ADS-B Logger in the WiFi Device selection list. Once complete with the test, go back in and un check that Logger. Then send the bug report and use with the defualt or select and use the ADSBraw file. This really provides a clear view of waht is happening from the NavWorx.

In the meantime, we'll dig and see what can be determined from this log.

Shane Woodson
Vice President | Adventure Pilot LLC.

6/28/2016 10:36 AM

John Miller

Joined: 9/12/2010

Posts: 644

Re: No Heartbeat

I sent a bug report with the log for the flight from KAJO to KRIR June 27th around 10:30 AM. By the way how do you delete all these logs that have accumulated?

I reviewed the log myself just now and I keep seeing "Input string not in correct format." That can't be good.

As I mentioned, the WiFi signal from Navworx was constant and strong even though I got the heartbeat message.

My next test will be with friends that use Foreflight and Wing X using the IFLY trial version. That should establish if it is the Android Tablet/phone or the IFLY app.

By the way it even gave me an "out of Range" while I was near KRAL that has a tower. I fly indicated 2 towers, but noted "out of range" at the same time.

Also, I did not know you could tap on the ADS status instrument box and it will take you driectly to the detailed status information without doing Menu> About> Selected Device.

Don't think I ever saw this in the users manual.

6/30/2016 5:55 PM

John Miller

Joined: 9/12/2010

Posts: 644

Re: No Heartbeat Modified By John Miller on 6/30/2016 6:03:58 PM

Shane:

Did another test today. I have sent the log of this flight from KAJO to KHMT done June 30 at about 9 AM.

Started receiving while in the KAJO run up area. A tower is nearby.

During almost all of the flight things were functioning properly until the last part on approach to KHMT at 3,000 MSL.

I got "Out of Range," but when it touched on the ADSB status box the status screen said I had two towers.

Then on the 45 I got "No heartbeat." Yet I still could see some targets...then they faded.

I had no heartbeat on downwind, final and touchdown.

During taxi to the restaurant It flopped back and fourth between "No Heartbeat" and "Out of Range." I had no towers at this time.

I got he same indications simultaneously on my Android phone and tablet, so I now suspect something with the IFLY software.

I will try to find someone with Wing X, Foreflight or any other Nav app that works with Navworx to fly with me and confirm my suspicions regarding IFLY software.

7/2/2016 11:10 AM

Brian

Joined: 9/7/2011

Posts: 4453

Re: No Heartbeat

John, a month ago, I fixed a bug for v9.7 (and this fix is in the latest beta), where we were mistakenly calling "Idle" as "Out of Range". So simply having an "Idle" tower (i.e. a lapse in receiving data for short-time), for v9.6 would instead show you the text "Out of Range".

Beta testers can download the beta version of 9.7 and validate this fix.

Thank you for reporting this issue.

Brian Knox, Sr Software Engineer