Success Can Be Frustrating…

UPDATE 2:30 PM, Pacific:  All back to normal.  Nothing to see here.  Move along ….

Apparently FlyQ EFB 3.0 is being downloaded and used at record levels .. I say this because the folks who provide the radar and satellite weather maps tiles to us, saw a massive spike in usage and decided to stop providing the tiles without warning (we apparently exceeded our usage allowance — by a lot).  We’re on the phone with them now and hope to have this resolved very soon.

This applies to radar and satellite weather weather downloaded from the Internet only for use in FlyQ EFB and FlyQ Online; ADS-B radar is not affected (and there is no ADS-B satellite).  METARs, TAFs, Winds Aloft, etc. are also unaffected as we process that data ourselves.

Sorry for the problem.

Thanks, Steve

15 thoughts on “Success Can Be Frustrating…

    • No known issue, Hank. Thousands have done so today. Check the Updates tab and, if you don’t see FlyQ EFB listed, “pull down” the App Store page to force it to refresh. Should look just like the screenshot shown on the blog entry about v3 release.

      Thanks, Steve

      Liked by 1 person

  1. Success comes with it’s challenges , I hope all of us FlyQ users understand, i sure do coming from the IT world I understand, keep forging forward. Put another notch in the data stream, it indicates unexpected success!

    Like

  2. Steve, I flew today 1.2 hrs on Hobbs with new update. I had on Merlin with WiFi. Cloud Ahouy didn’t save & tracking only worked for the last 9 minutes of Flight..? Greg

    Like

    • You have to export the track to Cloud Ahoy using the Action button. It’s not automatic. In terms of the track, look at all your tracks. If your iPad went to sleep or you swapped to the home page or another app during the flight, you may have multiple tracks. We’re doing some work to automatically “glue” these multiple tracks together in those cases and that will be in the next minor release.

      Liked by 1 person

  3. Used 3.0 on a 1.6 hr flight VFR cross country just yesterday dodging late afternoon deteriorating coastal weather … 3.0 with my Stratux was great keeping me posted and “situation-aware” with weather overlays and observations from controllers. A great flight with a barely VFR ILS 13 approach into KCRP using the overlaid approach plates. Now as to the new tracking feature .. I thought I flew a lot straighter than what I saw! We have very patient and tolerant ATC personnel in this part of the country. Well done on 3.0 on the Ipad … seems to process/update faster too. Thank you.

    Liked by 1 person

      • At that time I didn’t know how to save the plot … but .. if Rimsky-Korsakov’s “flight of the bumblebee” brings anything to mind that’s what it looked like – but in really slow motion in the 172.

        Like

      • Ha! Well, your flight of the bumblebee was automatically recorded, unless you turned the feature off. Tap any of the 5 status bars at the upper right of the screen then select Flight Recorder. Should be there. Then find the bumblebee and click the Action button (box with an arrow coming out) and post to Facebook, Twitter, email, whatever.

        Like

  4. I am unable to get V3.0 to work at all when it is connected to my Dynon Skyview system. It will immediately freeze or abort. Restarting of Fly Q will immediately freeze or abort at the Fly Q flash screen when connected to Dynon Skyview Wi-Fi. Works great when flying the desk on my home network. Apple I-Pad 5th gen with 128 GB.

    Like

    • Hi Kurt. Yes we just became aware of this and have already fixed it for the next release. We did test the Dynon support before release but a change was made after the test that, unexpectedly, caused the problem. Love to get you as a beta tester to test th fix and, in the future, ensure this doesn’t happen again.

      Like

    • No but the fixed version will be out next week. Email support@seattleavionics.com if you want the beta to see it even sooner. In the meantime, just don’t connect to the Dynon and it will work fine. Sorry for the issue. As I wrote earlier, we tested this early in the v3 process and found no problems. A change made late caused it and no beta testers (400 of them) reported it.

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s