Flightstream 510 - Connection Issues
Moderators: Rick, Lance Murray
- CFIDave
- 5 Diamonds Member
- Posts: 2681
- Joined: Wed Nov 07, 2012 3:40 pm
- First Name: Dave
- Aircraft Type: OTHER
- Aircraft Registration: N333GX
- Airports: KJYO Leesburg VA
- Has thanked: 233 times
- Been thanked: 1480 times
Re: Flightstream 510 - Connection Issues
With NXi Phase II, you can have your iPad (or iPhone) simultaneously have a Bluetooth pairing to the FS510 for traffic, weather, AHRS position info, and flight plan sync -- and another Bluetooth pairing to the GMA 1360 audio panel to play music, make phone calls, or to hear Foreflight alerts through the plane's audio system.
The GMA 1360 audio panel can only be paired to one Bluetooth device at a time, whereas the FS510 can be paired with multiple Bluetooth devices.
The GMA 1360 audio panel can only be paired to one Bluetooth device at a time, whereas the FS510 can be paired with multiple Bluetooth devices.
Epic Aircraft E1000 GX
Former DA40XLS, DA42-VI, and DA62 owner
ATP, CFI, CFI-I, MEI
Former DA40XLS, DA42-VI, and DA62 owner
ATP, CFI, CFI-I, MEI
- Rich
- 5 Diamonds Member
- Posts: 4604
- Joined: Mon Aug 30, 2010 12:40 pm
- First Name: Rich
- Aircraft Type: DA40
- Aircraft Registration: N40XE
- Airports: S39 Prineville OR
- Has thanked: 145 times
- Been thanked: 1185 times
Re: Flightstream 510 - Connection Issues
One thing to try with flaky bluetooth connections is to undo the pairing and re-pair. iOS upgrades are suspected of sometimes requiring this action. Not too long ago I had to re-pair my iPhone and my car after two years of zero problems.
2002 DA40-180: MT, PowerFlow, 530W/430W, KAP140, ext. baggage, 1090 ES out, 2646 MTOW, 40gal., Surefly, Flightstream 210, Orion 600 LED, XeVision, Aspen E5
- janders
- 3 Diamonds Member
- Posts: 112
- Joined: Wed Nov 04, 2020 7:45 pm
- First Name: Jon
- Aircraft Type: OTHER
- Aircraft Registration: N75RZ
- Airports: KGYY
- Has thanked: 206 times
- Been thanked: 44 times
Re: Flightstream 510 - Connection Issues
Thanks. I don't recall ever having heard audio announcements for traffic from the panel. Maybe it's a setting I have turned off.
Current E50P owner
Former C172 and DA62 owner
Former C172 and DA62 owner
- Boatguy
- 5 Diamonds Member
- Posts: 1859
- Joined: Mon Jan 22, 2018 4:48 am
- First Name: Russ
- Aircraft Type: DA62
- Aircraft Registration: N962M
- Airports: KSTS
- Has thanked: 1359 times
- Been thanked: 1190 times
Re: Flightstream 510 - Connection Issues
Or perhaps you haven't had any close encounters. Here are a couple of pages from the NXi manual that talk about the aural alerts.
- Attachments
-
- NXi Phase 2 Traffic alerts.pdf
- (302.74 KiB) Downloaded 88 times
- chili4way
- 5 Diamonds Member
- Posts: 523
- Joined: Fri Jun 08, 2018 10:51 pm
- First Name: Paul
- Aircraft Type: DA40NG
- Aircraft Registration: N718NG
- Airports: KADS
- Has thanked: 1060 times
- Been thanked: 482 times
Re: Flightstream 510 - Connection Issues
Fortunately, I've never had a Bluetooth pairing issue with the FS510 or GMA1360 audio panel. The FS510 WiFi connection used to be finicky, but it's only used for doing "Database Concierge" database updates, which I've stopped using*.
I pair my iPad Mini (ForeFlight) to both the FS510 (for flight plan transfers & GPS/FIS-B data) and to the GMA1360 (for music and ForeFlight alerts). I pair my cell phone to my headset for the infrequent times that I need to make a phone call to pick up a clearance.
*The Database Concierge idea sounded great, but it requires transferring the 28-day databases 3 times (Garmin→iPad→FS510→panel) instead of two (Garmin→SDcard→panel). The last two steps of the Database Concierge process combined take a lot of time, too long unless you have your plane connected to a GPU.
I pair my iPad Mini (ForeFlight) to both the FS510 (for flight plan transfers & GPS/FIS-B data) and to the GMA1360 (for music and ForeFlight alerts). I pair my cell phone to my headset for the infrequent times that I need to make a phone call to pick up a clearance.
*The Database Concierge idea sounded great, but it requires transferring the 28-day databases 3 times (Garmin→iPad→FS510→panel) instead of two (Garmin→SDcard→panel). The last two steps of the Database Concierge process combined take a lot of time, too long unless you have your plane connected to a GPU.
- Donkadillapig
- 3 Diamonds Member
- Posts: 98
- Joined: Tue Nov 10, 2020 5:09 pm
- First Name: Steve
- Aircraft Type: DA40NG
- Aircraft Registration: N812LA
- Airports: KFCI
- Has thanked: 155 times
- Been thanked: 80 times
Re: Flightstream 510 - Connection Issues
Thanks everyone for the helpful tips. Turns out it was really just bluetooth jiggery pokery. I repaired/remade the ipad connection and it has held solid now for over 5.2 hrs of flight time.
- Donkadillapig
- 3 Diamonds Member
- Posts: 98
- Joined: Tue Nov 10, 2020 5:09 pm
- First Name: Steve
- Aircraft Type: DA40NG
- Aircraft Registration: N812LA
- Airports: KFCI
- Has thanked: 155 times
- Been thanked: 80 times
Re: Flightstream 510 - Connection Issues
So like all good saga's... this one has come back.
After around 12 hours of solid connections, no issues. Now inexplicably It has thrown a double six again....
My ipad (11pro) is connected to the FS510, shows connected on the panel and on the ipad. data sharing is enabled. Problem is no data is being transferred. No traffic, weather info and no option to send flight plan to the panel or vica versa.
My CFII's ipad works perfectly...
We've tried forgetting my connection (on panel and on ipad) and remaking.. no joy.. It's starting to look like possibly a Foreflight bug maybe? We've also tried force closing FF.
Any ideas or experience out there? Does reinstalling FF sound feasible although I'd be worried about logbook and data/profile loss.
After around 12 hours of solid connections, no issues. Now inexplicably It has thrown a double six again....
My ipad (11pro) is connected to the FS510, shows connected on the panel and on the ipad. data sharing is enabled. Problem is no data is being transferred. No traffic, weather info and no option to send flight plan to the panel or vica versa.
My CFII's ipad works perfectly...
We've tried forgetting my connection (on panel and on ipad) and remaking.. no joy.. It's starting to look like possibly a Foreflight bug maybe? We've also tried force closing FF.
Any ideas or experience out there? Does reinstalling FF sound feasible although I'd be worried about logbook and data/profile loss.
- Rich
- 5 Diamonds Member
- Posts: 4604
- Joined: Mon Aug 30, 2010 12:40 pm
- First Name: Rich
- Aircraft Type: DA40
- Aircraft Registration: N40XE
- Airports: S39 Prineville OR
- Has thanked: 145 times
- Been thanked: 1185 times
Re: Flightstream 510 - Connection Issues
Does it show under "Devices" in Foreflight?
2002 DA40-180: MT, PowerFlow, 530W/430W, KAP140, ext. baggage, 1090 ES out, 2646 MTOW, 40gal., Surefly, Flightstream 210, Orion 600 LED, XeVision, Aspen E5
- Rich
- 5 Diamonds Member
- Posts: 4604
- Joined: Mon Aug 30, 2010 12:40 pm
- First Name: Rich
- Aircraft Type: DA40
- Aircraft Registration: N40XE
- Airports: S39 Prineville OR
- Has thanked: 145 times
- Been thanked: 1185 times
Re: Flightstream 510 - Connection Issues
Opening a case with FF is what I'd recommend. BTW, I just switched to a new iPad Pro 11, which meant installing FF on the new one. The flights, profiles and historical logbook entries all magically appeared on my new device.
But this might not be the same thing. Check with FF before reinstalling.
But this might not be the same thing. Check with FF before reinstalling.
2002 DA40-180: MT, PowerFlow, 530W/430W, KAP140, ext. baggage, 1090 ES out, 2646 MTOW, 40gal., Surefly, Flightstream 210, Orion 600 LED, XeVision, Aspen E5
- Donkadillapig
- 3 Diamonds Member
- Posts: 98
- Joined: Tue Nov 10, 2020 5:09 pm
- First Name: Steve
- Aircraft Type: DA40NG
- Aircraft Registration: N812LA
- Airports: KFCI
- Has thanked: 155 times
- Been thanked: 80 times
Re: Flightstream 510 - Connection Issues
Thanks Rich... no it doesn't show on that devices page as connected in FF, only in the ipad devices/Blue tooth manager.
I'll take your advice I think and open a support case with FF.
I'll take your advice I think and open a support case with FF.