GTX345 and missing traffic targets

The ramblings of our community of aviators.

Moderators: Rick, Lance Murray

User avatar
Boatguy
4 Diamonds Member
4 Diamonds Member
FIRST NAME: Russ
Aircraft: DA40NG
Registration: N454M
Airport: O69

Posts: 361
Joined: Mon Jan 22, 2018 4:48 am
Has thanked: 135 times
Been thanked: 255 times

Re: GTX345 and missing traffic targets

Post by Boatguy »

Rich wrote:
Wed Apr 01, 2020 1:36 am
It also seems like 150 nm is an awfully large distance to be concerned with. It would take a closing speed of 18,000 knots for such a target to be a problem in the next 30 seconds.
A Phenom and a CJ could converge at 800+ kts which would cover the 150nm in about 10minutes. And that's before allowing for data propagation delays.
User avatar
Rich
5 Diamonds Member
5 Diamonds Member
FIRST NAME: Rich
Aircraft: DA40
Registration: N40XE
Airport: S39

Posts: 2393
Joined: Mon Aug 30, 2010 12:40 pm
Has thanked: 64 times
Been thanked: 356 times

Re: GTX345 and missing traffic targets

Post by Rich »

Lance Murray wrote:
Wed Apr 01, 2020 2:18 am
You are still see and avoid. No matter if you have TCAS II, ADS-B, TAS, whatever. See and avoid is the rule when VFR.
Usually this refers to what we've long used. It's more accurately described as "See what small portion of the sky your plane allows you to see out the window with your frail eyeballs, use the radio (hoping others use it properly), and let the Big Sky Principal do the rest'. I can offhand recall two near misses I've had that I know of due to large portions of the sky being blocked by the airframes of both aircraft.

The various technologies above are all enhancements to the concept of "see and avoid", affording visibility you do not otherwise have. You want them to work when you need it most. Yes, it's true that there will be aircraft that will (legally and otherwise) be invisible to these systems and you need to be alert for those. But you do want the electronic systems you do have to work as advertised despite the known limitations.
2002 DA40: MT, PF, 530W/430W, KAP140, ext. baggage, 1090 ES out, 2646 MTOW, 40gal., Surefly, Flightstream 210.
User avatar
Boatguy
4 Diamonds Member
4 Diamonds Member
FIRST NAME: Russ
Aircraft: DA40NG
Registration: N454M
Airport: O69

Posts: 361
Joined: Mon Jan 22, 2018 4:48 am
Has thanked: 135 times
Been thanked: 255 times

Re: GTX345 and missing traffic targets

Post by Boatguy »

I received a clarification from Garmin today that the v3.13 firmware for the GTX345R will drop the target "furthest" away when it is necessary to make room in a full database for a new target.

But to be clear, until an update is issued by Diamond, once our GTX345R has 200 targets within 150nm of our plane, it will drop a 201st target, irrespective of the proximity of the new target to our plane.
User avatar
Brian
2 Diamonds Member
2 Diamonds Member
FIRST NAME: Brian
Aircraft: DA40
Registration: N224BS
Airport: KPIA

Posts: 24
Joined: Tue Aug 10, 2010 9:45 pm
Has thanked: 18 times

Re: GTX345 and missing traffic targets

Post by Brian »

Boatguy wrote:
Tue Mar 31, 2020 11:49 pm
mdieter wrote:
Tue Mar 31, 2020 5:51 pm
For what it's worth, I tried to have the GTX345R software updated on two occasions. In the end we ended up reverting the software to the original version. It is not a simple upgrade when a G1000 is involved.

On the second attempt we got the transponder updated to the latest version via a laptop and USB connection, but then the G1000 would not communicate with the transponder. After more digging, I found that there is a software version manifest that the G1000 keeps that contains validated software versions. The new GTW345 software version was not listed, therefore the G1000 won't communicate with the transponder. It thinks the transponder is invalid. I'm guessing the manifest file has to come from Garmin as a G1000 update. No idea if Garmin has created a manifest file for our aircraft with the proper software versions. My avionics guy didn't seem to know about it.
That's why my avionics shop told me they couldn't do the update.

Based on my conversations with Garmin and Diamond, the software has been available to Diamond since last year, but apparently they can't distribute it without approval from Transport Canada and they have not made that request because they've been focused on getting approvals for new aircraft.

I suggest every Diamond owner sign up with Garmin for updates on their avionics as you'll never get this information from Diamond. At least with the information from Garmin we know we're not seeing all the traffic.
Yeah I'm pretty frustrated with Diamonds lack of support for earlier G1000 aircraft. Every year at Oshkosh for 3 years, starting in 2016, they told me they were going to provide SW to support ADSB in time to meet the mandate. Tomorrow I am getting a GTX345R installed without the promised SW from Diamond. As far as I know Cessna and other aircraft OEM's have supported their early G1000 adopters.
User avatar
Boatguy
4 Diamonds Member
4 Diamonds Member
FIRST NAME: Russ
Aircraft: DA40NG
Registration: N454M
Airport: O69

Posts: 361
Joined: Mon Jan 22, 2018 4:48 am
Has thanked: 135 times
Been thanked: 255 times

Re: GTX345 and missing traffic targets

Post by Boatguy »

Brian wrote:
Thu Apr 02, 2020 6:42 pm
Yeah I'm pretty frustrated with Diamonds lack of support for earlier G1000 aircraft. Every year at Oshkosh for 3 years, starting in 2016, they told me they were going to provide SW to support ADSB in time to meet the mandate. Tomorrow I am getting a GTX345R installed without the promised SW from Diamond. As far as I know Cessna and other aircraft OEM's have supported their early G1000 adopters.
Follow the G1000 "next steps" thread and you'll get regular updates on the discussions with Diamond which definitely have touched on this subject. We had a second video conference with Diamond/Garmin today and another is scheduled for next week. Progress is being made, but there are limitations to Garmin's support for early adopters.
Post Reply