denverpilot
Tied Down
Really this is for @flyingcheesehead but I promised I’d check and did today. The AHRS to ForeFlight works.
I have all the various firmware versions of it all written down if you need them. Most current as of roughly a month ago. Whatever those are/were.
This is, of course, with the 345 Bluetooth disabled and all the data going to ForeFlight via the Flightstream 510’s Bluetooth.
As an aside, I was surprised the majority of the commutation to tablets is done over Bluetooth and WiFi is really only in the FS510 for updates. I would have thought it would be easier for most devices to find and grab the airplanes WiFi, no pairing needed.
Practically, it doesn’t seem matter much.
Now, the oddity and maybe it’s a “works as designed”. Had ForeFlight set up for a direct flight KAPA-KCOS and connected to the GTN. Sent that wimpy flight plan into the GTN wirelessly just to do it.
Flew down there, requested the RNAV and got the RNAV 35L. Used the GTN to add the procedure and activated it with VTF.
iPad asked to accept the route change and I did. Here’s what it appeared to do... ForeFlight inserted the approach ahead of KCOS. Okay fine. Normal.
Then I purposely flew the published missed. The usual suspend at the end of the approach and then accepting the published missed, and the GTN immediately requested the climb and then the turn.
(By the way, that’s just freaking awesomeness for this old steam guy, but y’all knew that.)
It also did its GTN thing and built the hole at ADANE and the entry. God this thing is fun. Haha.
Anyway, looked back over at the iPad and it still had KAPA, the approach, and KCOS as the planned route. It never did the update for the missed or added ADANE.
I’ll have to read some more to see if that’s normal, but anyone flying with Flightstream 210 or 510 hooked to ForeFlight want to comment on how published missed approach stuff usually works or doesn’t work to the tablet for you?
Anyway, what a boatload of fun. Also got to play with the derived/fake “Visual” approaches the GTN will create out of nothing for Runway 28 back at KAPA. Yeah, you can just load the RNAV real approach for that runway in there as a backup in visual conditions, too, but I wanted to see what it did in that Visual mode. Pretty nifty... very easy to get a feel for too high/low and centerline with the ol’ crosshairs right there to glance at with two button presses... Visual button comes up on the screen when you’re headed for an airport, and then just select the runway.
By the way, none of that showed up in ForeFlight either but I wasn’t really expecting anything the Garmin created on its own to properly transfer over.
Leaving ADANE I had typed ADANE KAPA into ForeFlight manually and then pushed that as a “new” flight plan into the GTN. Mostly to prove the two way com was still working for flight plan stuff, since traffic and other things were still working.
Oh and I was doing all of this from the right seat, just because. VMC. Totally able to look outside because this was avionics testing, and buttonology tweaking for me, integrating stuff into my procedures, and not training. Just checking off “let’s see if/how THIS works” kinda stuff. So far no big surprises other than the missed not showing up on the tablet under ForeFlight. Haven’t tried with Garmin Pilot yet. Suspect they’ll behave the same. Data was either sent or it wasn’t.
I have all the various firmware versions of it all written down if you need them. Most current as of roughly a month ago. Whatever those are/were.
This is, of course, with the 345 Bluetooth disabled and all the data going to ForeFlight via the Flightstream 510’s Bluetooth.
As an aside, I was surprised the majority of the commutation to tablets is done over Bluetooth and WiFi is really only in the FS510 for updates. I would have thought it would be easier for most devices to find and grab the airplanes WiFi, no pairing needed.
Practically, it doesn’t seem matter much.
Now, the oddity and maybe it’s a “works as designed”. Had ForeFlight set up for a direct flight KAPA-KCOS and connected to the GTN. Sent that wimpy flight plan into the GTN wirelessly just to do it.
Flew down there, requested the RNAV and got the RNAV 35L. Used the GTN to add the procedure and activated it with VTF.
iPad asked to accept the route change and I did. Here’s what it appeared to do... ForeFlight inserted the approach ahead of KCOS. Okay fine. Normal.
Then I purposely flew the published missed. The usual suspend at the end of the approach and then accepting the published missed, and the GTN immediately requested the climb and then the turn.
(By the way, that’s just freaking awesomeness for this old steam guy, but y’all knew that.)
It also did its GTN thing and built the hole at ADANE and the entry. God this thing is fun. Haha.
Anyway, looked back over at the iPad and it still had KAPA, the approach, and KCOS as the planned route. It never did the update for the missed or added ADANE.
I’ll have to read some more to see if that’s normal, but anyone flying with Flightstream 210 or 510 hooked to ForeFlight want to comment on how published missed approach stuff usually works or doesn’t work to the tablet for you?
Anyway, what a boatload of fun. Also got to play with the derived/fake “Visual” approaches the GTN will create out of nothing for Runway 28 back at KAPA. Yeah, you can just load the RNAV real approach for that runway in there as a backup in visual conditions, too, but I wanted to see what it did in that Visual mode. Pretty nifty... very easy to get a feel for too high/low and centerline with the ol’ crosshairs right there to glance at with two button presses... Visual button comes up on the screen when you’re headed for an airport, and then just select the runway.
By the way, none of that showed up in ForeFlight either but I wasn’t really expecting anything the Garmin created on its own to properly transfer over.
Leaving ADANE I had typed ADANE KAPA into ForeFlight manually and then pushed that as a “new” flight plan into the GTN. Mostly to prove the two way com was still working for flight plan stuff, since traffic and other things were still working.
Oh and I was doing all of this from the right seat, just because. VMC. Totally able to look outside because this was avionics testing, and buttonology tweaking for me, integrating stuff into my procedures, and not training. Just checking off “let’s see if/how THIS works” kinda stuff. So far no big surprises other than the missed not showing up on the tablet under ForeFlight. Haven’t tried with Garmin Pilot yet. Suspect they’ll behave the same. Data was either sent or it wasn’t.