Hi Tim,

Ever since the latest SD update where the connection to PF was moved from CONNECTIONS to GO FLYING, I can't get my PF Core to connect to SD and I have to revert to Use Location Services and the iPad's internal GPS.

I have checked the PF Core device and get the customary orange LED for 20 seconds and then the steady green LED which tells me that it has booted correctly and is receiving GPS signals. On the iPad wi-fi status icon, it shows that I am connected to the Butterfly Connect.

I have confirmed SETTINGS - CONNECTIVITY - FLARM and when I select GO FLYING - USE FLARM, I get the message: "Please wait while a connection is established to your external device" but after about 10 seconds I always get the message: "Failed to establish a connection with Butterfly Connect."

I have tried it with airplane mode off (wi-fi still selected) and on; I have deleted SD from my iPad and reloaded it; I have reconfigured the PF Core with my USB stick but all to no avail. My iPad is connected to the Butterfly Connect wi-fi and the PF Core is receiving GPS data but it's just not happening on SD and only seems to have started after the last update.

Do you have any suggestions, please?

Paul

Dear Tim - et al,

With regards to the original problem that I raised at the start of this thread, please accept my thanks for being willing to see if it was my Power Flarm Core that was causing the issues and my apologies for this tardy reply.  For your information, I sent the unit back to Butterfly Avionics who put it on an extended test for three weeks but they couldn't find anything wrong with it.  I connected it back up, played about with it and I'm pleased to say that the connection from my Power Flarm Core / Butterfly Connect Wi-Fi unit to my iPad running SD is now all sorted!  Errr, it was simple operator error! 

Let me explain: The problem was that previous versions of SD didn't seem to alter the 4-digit PIN number that I had inputted to connect my iPad's Wi-Fi receiver to the Butterfly Connect Wi-Fi unit.  But after a particular SD update, it seemed to then use the default Wi-Fi code of 1234 but I never noticed this.  It was only whilst going into to 'Setup' - 'Air Connect Key' and changing the default 1234 to my own unique 4-digit Butterfly Connect Wi-Fi PIN that everything was then OK again and I could go to 'Go Flying' - 'Use Flarm' and instantly obtain accurate location data.  Doh!!

Tim, I'm very pleased to hear that you're looking at more integration of traffic warning with SD but I still have a major gripe with the size of the numerical information (height and distance) that appears next to a FLARM or ADS-B threat.  It is just too small for elderly eyes and it doesn't get any bigger despite zooming in.  Isn't there something that could be done?  The next time it occurs, I'll try and get a screen shot so you can see how small the writing is. 

The big warning (i.e.: "Traffic 1 O'clock") written in yellow inside a black background rectangle is nice and big but only illuminates for a very brief time.  Luckily, I have the optional audio licence with my Power Flarm Core and get to hear the warning which pulls my eyes to the iPad screen. 

For the information of other Power Flarm Core / SD users, my set-up has proved faultless and works continuously.  On another ADS-B note, its great going to FlightRadar24.com (on a PC) and selecting Data/History, entering my aircraft registration and seeing my track-log obtained from my Mode-S / Extended squitter ADS-B Out functionality.  There's no use trying to tell the CAA that I wasn't at 300 feet buzzing my mate's house now!!

Great work, Tim and your team; I've just renewed for a third year.

Paul