Pulled the trigger - I am dumb - Kate 1.5 coming soon

Clock or the flight timer function in GTX 345 or the 750, starting at taxi. I am not building hours so a few mins less won’t matter a whole lot.
Your 750 will log all your flights automatically. You can download them all to an SD card from the utilities page. FlyGarmin or MyFlightbook.com can read and record them. GP does the same. Easy to add approaches and other details to keep currency records.
 
Your 750 will log all your flights automatically. You can download them all to an SD card from the utilities page. FlyGarmin or MyFlightbook.com can read and record them. GP does the same. Easy to add approaches and other details to keep currency records.

I do the automatic flight logging from GP today, will miss out the long taxi times at times, but I am ok with that
 
Clock or the flight timer function in GTX 345 or the 750, starting at taxi. I am not building hours so a few mins less won’t matter a whole lot.
I use the tach for time-in-service for maintenance but I also write down block times.
 
painfully slow .... but finally the servos have been placed with rivets and wiring complete. from what i have been told the new gizmos have been test fitted with power and nothing went up in flames

upload_2020-5-14_20-30-52.png
 
Wow, that is a clean install... seems like the only thing missing in your new setup is auto-land for the Warrior! I'm curious, does the pitch servo drive the "up elevator" cable?
 
Nice. But I thought the GAD29b would go behind the panel since that's where all the other ARINC429/RS232 stuff lives?
 
Wow, that is a clean install... seems like the only thing missing in your new setup is auto-land for the Warrior! I'm curious, does the pitch servo drive the "up elevator" cable?

honestly, i have no idea which cable its connected to, but good point to check on my next visit...

hmm.. autoland... thinking about it :p
 
Nice. But I thought the GAD29b would go behind the panel since that's where all the other ARINC429/RS232 stuff lives?

the GAD29b has historically been there when i did the dual G5 install. actually it was where the roll servo is now, they moved it and all the wiring were already there. when they put in there, they had mentioned that there are a lot of junk wires under the panel and it just made sense to put it in a clean place. the thought of moving it had crossed my mind, but since it worked just fine and the wiring were already in place, didnt bother
 
Wow, that is a clean install... seems like the only thing missing in your new setup is auto-land for the Warrior! I'm curious, does the pitch servo drive the "up elevator" cable?


Warrior Princess maybe.

Don't make Kate come over there! ;)
 
Just found out that GFC 500 doesn’t have CWS ....
 
CWS - Control Wheel Steering. @WannFly, just switch to heading mode and twist the dial when getting vectors. My AP does not have CWS and I just switch between Heading and GPSS to do basically the same thing. Just need to make sure to move the heading bug first :)
 
painfully slow .... but finally the servos have been placed with rivets and wiring complete. from what i have been told the new gizmos have been test fitted with power and nothing went up in flames

View attachment 85807


I gotta ask, how did you get that picture? The hat rack would have to be removed and the photographer standing in the rear where there isn't really a place to stand, sit or anything but lay down, and that very uncomfortably.
 
I gotta ask, how did you get that picture? The hat rack would have to be removed and the photographer standing in the rear where there isn't really a place to stand, sit or anything but lay down, and that very uncomfortably.

Well, the hat rack has been removed but clearly you haven’t seen me.... but I can tell you right now I ain’t fitting in that space. That was me leaning in about 90 degrees in through the cargo door, then raising my upper body about 30 degrees to take that shot. It was interesting
 
CWS - Control Wheel Steering. @WannFly, just switch to heading mode and twist the dial when getting vectors. My AP does not have CWS and I just switch between Heading and GPSS to do basically the same thing. Just need to make sure to move the heading bug first :)

Yah, but that switch was sure nice with my previous AP... I hear there is no dedicated GPSS mode either... it will do roll steering, in nav mode . Yet to find out.
 
Just found out I don't know what CWS stands for?

You may not have heard that radio call to me, but when we were coming back from KOMA, there was a IFR traffic headed towards me , with 500 feet separation but ATC asked me to turn 20 degrees anyway. Press that CWS button on the yoke, turn whichever way you want, do your maneuvers, let it go and it’s back to AP. That’s how mine worked, I hear in big irons they work little differently. Kinda pauses the AP.
 
Wow, that is a clean install... seems like the only thing missing in your new setup is auto-land for the Warrior! I'm curious, does the pitch servo drive the "up elevator" cable?

Rob - it’s connected to the up elevator cable
 
Yah, but that switch was sure nice with my previous AP... I hear there is no dedicated GPSS mode either... it will do roll steering, in nav mode . Yet to find out.
Yes, NAV mode has roll steering. Not sure why you'd want a separate GPSS mode.
 
Yes, NAV mode has roll steering. Not sure why you'd want a separate GPSS mode.

Don’t need it, in my older AP Nav and GPSS(G5) via heading more emulator were separate . But this is definitely better
 
Ok, think I slightly mis-spoke on the GPSS vs Heading mode. I have more than a passing interest as I was thinking of updating my AP and the GFC500 was on my list of choices. What's different with the GFC500 vs an old analog AP driven by a G5 is the "GPSS" is basically the NAV mode and Heading mode is well, heading. Those are buttons on the AP vs a choice on the G5 (As I understand it from reading the manuals). So still basically the same operationally, have your heading bug lined up with your GPS course as a good habit. Following a magenta line, the bug does nothing. Get vectors from ATC, put bug on new heading. That could be 10 degrees left or an actual heading. Either way dial it in and switch AP to heading mode. When you get told to go direct to original waypoint, hit direct, activate on your new GTN and switch back to NAV mode. If vectors to final, you can use heading mode for the vectors and then approach once established.

Sorry if my first answer confused you, and if there is a GFC500 pro reading this, feel free to correct me.
 
Ok, think I slightly mis-spoke on the GPSS vs Heading mode. I have more than a passing interest as I was thinking of updating my AP and the GFC500 was on my list of choices. What's different with the GFC500 vs an old analog AP driven by a G5 is the "GPSS" is basically the NAV mode and Heading mode is well, heading. Those are buttons on the AP vs a choice on the G5 (As I understand it from reading the manuals). So still basically the same operationally, have your heading bug lined up with your GPS course as a good habit. Following a magenta line, the bug does nothing. Get vectors from ATC, put bug on new heading. That could be 10 degrees left or an actual heading. Either way dial it in and switch AP to heading mode. When you get told to go direct to original waypoint, hit direct, activate on your new GTN and switch back to NAV mode. If vectors to final, you can use heading mode for the vectors and then approach once established.

Sorry if my first answer confused you, and if there is a GFC500 pro reading this, feel free to correct me.

Think you are spot on. That’s how I have running my old AP, in fact since G5 got in, I can’t remember ever turning on the nav mode, the AP permanently stayed on heading mode. I use to switch GPSS on/ off from G5. However, I like the buttons on the 507 mode controller, and have a feeling will use that more than G5.

I may or may not have turned the GPSS mode off without moving the heading bug .... more than once
 
Rob - it’s connected to the up elevator cable
That makes good sense... thanks for confirming. Now I'm going to start designing the servo brackets!
 
CWS - Control Wheel Steering. @WannFly, just switch to heading mode and twist the dial when getting vectors. My AP does not have CWS and I just switch between Heading and GPSS to do basically the same thing. Just need to make sure to move the heading bug first :)
upload_2020-5-16_22-26-31.jpeg

I didn't install the GFC500 this time around. Maybe in a couple years. New interior comes first. But I will miss the mode selector for the G5’s flight director.
 
Last edited:
It does. You have to install the separate audio alert from the 750 main connector to an unswitched unmuted input on the audio panel, then turn on terrain alerting in 750 config and you'll get a 500' callout.

you need the TAWS-B unlock your have 500’ audio alert... And garmin charges about $7k for that unlock...
 
Nice! I have the same. You’re gonna love the 275. It’s better than the G5’s!

Tell me , what do you like better about the 275.. on first glance it seems they put the knob on the wrong side to be a similar logic to the g500txi or gtn750...
 
you need the TAWS-B unlock your have 500’ audio alert... And garmin charges about $7k for that unlock...

That is incorrect. Version 6.50 and later of the GTN firmware has Terrain Alerting functionality without the full TAWS. It doesn't require an unlock and does have all of the same callouts as TAWS (including the 500' callout), except the Negative Climb Rate (NCR) and Excessive Descent Rate (EDR) cautions and warnings.

Screen Shot 2020-05-21 at 6.37.30 PM.png
 
That is incorrect. Version 6.50 and later of the GTN firmware has Terrain Alerting functionality without the full TAWS. It doesn't require an unlock and does have all of the same callouts as TAWS (including the 500' callout), except the Negative Climb Rate (NCR) and Excessive Descent Rate (EDR) cautions and warnings.

View attachment 86054

I do receive a terrain warning, but not a 500’ call out (unless the terrain warning is preset to 500’), but it does not say 500’.... does yours?
I have v6.62.. it is my understanding in calling garmin that the preset for 500’ is taws b...

I would be pleased if I were wrong and this is something I am missing
 
I do receive a terrain warning, but not a 500’ call out (unless the terrain warning is preset to 500’), but it does not say 500’.... does yours?
I have v6.62.. it is my understanding in calling garmin that the preset for 500’ is taws b...

I would be pleased if I were wrong and this is something I am missing

In my personal airplane I have a G500 TXi that’s doing the terrain duties (feature turned off on my GTNs), but in the GTNs I’ve installed (none with TAWS unlocks), yes, it gives a 500’ call out when descending to an airport. If you look at the most recent pilots guide (http://static.garmin.com/pumac/190-01007-03_r.pdf) you can see the VCO-500 listed in both the terrain alerting (11.5.6.1/11.5.6.5) and TAWS (11.6.6.1/11.6.6.7) sections. The pilots guide does seem to indicate it would only give a 500’ warning outside of 5nm from a runway if you have a radar altimeter, however. I’ve always heard it while on an approach towards an airport, and haven’t tried it outside of that environment.
 
Just found out that GFC 500 doesn’t have CWS ....

So, I thought about that a bit myself, and the real question is - Why would you want CWS?

The majority of the time, I'm using CWS because my altitude is 40' off or something so I'm flying a correction with CWS pressed and then letting go to capture the "new" altitude. I will never need to do that with a GFC500 - It's a digital autopilot connected to a digital EFIS and it will intercept and hold the altitude *perfectly* every time.

The only other thing I use CWS for is an occasional maneuver to look at something on the ground for a few seconds... But on the GFC 500 you can just hit the "AP" button, do your thing, and then hit "AP" again and it'll have the same effect as CWS does, if not better.

If you hit "AP" to disengage the autopilot, it will keep all of its modes and selections, you're just disengaging the servos essentially. If you have a flight director it'll still be operating and telling you to steer back on course. ;) But when you push AP again, you're re-engaging the servos into whatever mode the system was in the whole time, so it's not like you're disconnecting and have to set everything up again.

Yah, but that switch was sure nice with my previous AP... I hear there is no dedicated GPSS mode either... it will do roll steering, in nav mode . Yet to find out.

Ah, but you don't need GPSS. GPSS is essentially a crutch/hack to make old autopilots work with new (GPS) equipment. Old autopilots are merely following a voltage provided by the HSI or CDI indicating whether you're left or right of course. Try to fly a normal T-shaped approach, and they'll never make the turn to final - They'll just find themselves suddenly off course, full deflection, and kinda wander off to wherever. It's a kinda fun thing to try and see what happens!

With GPSS, you have to put the autopilot in Heading mode and flip the switch to GPSS, and essentially the GPS is just feeding the autopilot a fake heading bug that will result in the turn being executed correctly.

But the GFC 500 will have the entire turn calculated for it by the G5 (or G3X Touch) and it will follow that curve perfectly in Nav mode. It doesn't need GPSS, and if you're navigating via GPS, you're already going to have the same or better accuracy, without needing the GPSS crutch.

You may not have heard that radio call to me, but when we were coming back from KOMA, there was a IFR traffic headed towards me , with 500 feet separation but ATC asked me to turn 20 degrees anyway. Press that CWS button on the yoke, turn whichever way you want, do your maneuvers, let it go and it’s back to AP. That’s how mine worked, I hear in big irons they work little differently. Kinda pauses the AP.

With the G5/GFC 500, you won't need CWS to do this. Press the HDG knob on the GMC 507 (the control head for the GFC 500) to sync the heading to your current heading, push the HDG button, and then twist the HDG knob 20 degrees. To do the same as your existing autopilot, you could just hit "NAV" and it'd find its way back onto the course, or you could hit direct to whatever as well.

All this stuff is merely learning how to use the new gear - It doesn't mean that the GFC 500 is limited in any way due to the lack of CWS or GPSS, you'll just use it differently.

you need the TAWS-B unlock your have 500’ audio alert... And garmin charges about $7k for that unlock...

Negative...

I do receive a terrain warning, but not a 500’ call out (unless the terrain warning is preset to 500’), but it does not say 500’.... does yours?
I have v6.62.. it is my understanding in calling garmin that the preset for 500’ is taws b...

I would be pleased if I were wrong and this is something I am missing

I get the 500' callout, and I do not have any unlocks for the GTN nor do I have any glass in my panel outside of the radio stack. If you're not getting it, there's probably one of two things going on: The installer didn't enable the callout in the setup for some reason, or the installer didn't run the wire to your audio panel.
 
If you hit "AP" to disengage the autopilot, it will keep all of its modes and selections, you're just disengaging the servos essentially. If you have a flight director it'll still be operating and telling you to steer back on course. ;) But when you push AP again, you're re-engaging the servos into whatever mode the system was in the whole time, so it's not like you're disconnecting and have to set everything up again.

Thanks, i did not know that. I guess i am still in my old way of doing things and just need to get used to the new / better way.

On a diff note, I hear she is ready. Doing ground check today and hopefully test flight tomorrow.. if WX gods smile
 
flyingcheeshead covered it well. I'd add one thing to using AP to disengage. Spend some time when it doesn't matter seeing what happens when you re-engage. You might get surprised by what the AP chooses to do. An example is getting vectored on your way to a waypoint in IFR. Let's say you get sent around a build up or traffic and then ATC gives you direct to the waypoint you were going to. The AP will try to get you back on course, not head direct to the waypoint. It seems obvious, but it can surprise you. In IFR, getting vectored, I'd move to heading mode, use the heading bug for the vector. When getting sent back direct, hit "Direct" on the GTN, activate and go back to Nav mode. You can do the same thing if you use disengage and re-engage. Basically, if you are not on top of the Magenta line, it's going to try and intercept, not go direct to the next way point.

Long answer, but I learned the hard way.

Good luck on getting finished and the weather to go and fly it.
 
Cws is a great feature.. you can use it to recapture or temporary course deviations to go around a cloud or traffic... without ever taking your hand off the yoke.. in a single button maneuver.. the one described above, takes 3 steps and takes longer to perform.. particularly in a heavy workload moment and/or turbulence
 
The lack of CWS on GCF-500. I could not care less. Seriously. Push "HDG" and turn the knob.
 
I do receive a terrain warning, but not a 500’ call out (unless the terrain warning is preset to 500’), but it does not say 500’.... does yours?
I have v6.62.. it is my understanding in calling garmin that the preset for 500’ is taws b...

I would be pleased if I were wrong and this is something I am missing

The basic GTN can do the 500 callouts all by itself with no Garmin autopilot or EFIS or the expensive TAWS or other enablement cards.

IIRC there are three different setting in the system configuration menu, Terrain Awareness without audio, Terrain Awareness with audio, and TAWS.

upload_2020-5-29_9-50-22.png
 
Last edited:
Ah, but you don't need GPSS. GPSS is essentially a crutch/hack to make old autopilots work with new (GPS) equipment. Old autopilots are merely following a voltage provided by the HSI or CDI indicating whether you're left or right of course. Try to fly a normal T-shaped approach, and they'll never make the turn to final - They'll just find themselves suddenly off course, full deflection, and kinda wander off to wherever. It's a kinda fun thing to try and see what happens!

With GPSS, you have to put the autopilot in Heading mode and flip the switch to GPSS, and essentially the GPS is just feeding the autopilot a fake heading bug that will result in the turn being executed correctly.

But the GFC 500 will have the entire turn calculated for it by the G5 (or G3X Touch) and it will follow that curve perfectly in Nav mode. It doesn't need GPSS, and if you're navigating via GPS, you're already going to have the same or better accuracy, without needing the GPSS crutch.

Just a point of clarification.... technically the GFC500 and other modern autopilots (S-tec 55X, 3100, Trutrak) are following GPSS, they just natively understand it direct from the ARINC 429 feed. Older completely analog autopilots have no means to natively understand the GPSS commands, so there are emulation boxes that take in these digitally provided roll steering commands and convert them to analog heading voltages. This is what is provided by the G5+GAD29B. A G5 as part of a GFC500 system magically uses GPSS when following a GPS navigator's inputs, without needing to do any special selections. This is how it does all the turn anticipation and such when following GPS on a flight plan.

I get the 500' callout, and I do not have any unlocks for the GTN nor do I have any glass in my panel outside of the radio stack. If you're not getting it, there's probably one of two things going on: The installer didn't enable the callout in the setup for some reason, or the installer didn't run the wire to your audio panel.

I worked with David offline and this is exactly what we determined. Both that the Terrain Alerting was not on, and that the installer did not interface the alert audio from the GTN to the audio panel.
 
Both that the Terrain Alerting was not on, and that the installer did not interface the alert audio from the GTN to the audio panel.

is there a easy way to determine those? i am yet to fly and the WX is not looking great today, so will see. i did a ground check yesterday and the only thing i couldnt get to work was GTX 345 audio and added it to the squack list. not sure if thats a cabling issue or just a config issue. couldnt verify terrain callouts on the ground
 
Back
Top