Page 2 of 3

Re: GTX345 and missing traffic targets

Posted: Wed Apr 01, 2020 3:42 am
by Boatguy
Rich wrote: Wed Apr 01, 2020 1:36 amIt 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.

Re: GTX345 and missing traffic targets

Posted: Wed Apr 01, 2020 2:22 pm
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.

Re: GTX345 and missing traffic targets

Posted: Thu Apr 02, 2020 5:22 pm
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.

Re: GTX345 and missing traffic targets

Posted: Thu Apr 02, 2020 6:42 pm
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.

Re: GTX345 and missing traffic targets

Posted: Thu Apr 02, 2020 7:06 pm
by Boatguy
Brian wrote: Thu Apr 02, 2020 6:42 pmYeah 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.

Re: GTX345 and missing traffic targets

Posted: Mon Sep 20, 2021 1:46 pm
by Diamond_Dan
Boatguy wrote: Thu Apr 02, 2020 5:22 pm 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.
Has anybody heard any more about this firmware update? I don't see anything on the Diamond tech pubs page.

Re: GTX345 and missing traffic targets

Posted: Mon Sep 20, 2021 10:16 pm
by Boatguy
Diamond has had the fix for perhaps two years. They will include it with a bunch of other software changes in the certification effortfor a production airplane, and then it will be available to us. Diamond does not certify software just to fix bugs, only to bring new features to a production airplane, and the bug fixes come along for the ride.

This is the curse of an airplane that is certified with a glass panel. Airplanes originally certified with steam gauge instruments who add glass later can get the updates from their dealer whenever Garmin issues them.

Re: GTX345 and missing traffic targets

Posted: Tue Sep 21, 2021 5:33 am
by ememic99
Boatguy wrote: Mon Sep 20, 2021 10:16 pm Diamond does not certify software just to fix bugs, only to bring new features to a production airplane, and the bug fixes come along for the ride.
In case that bug causes safety issue such problem should be brought to regulator (FAA, EASA, TC) attention.

Re: GTX345 and missing traffic targets

Posted: Tue Sep 21, 2021 5:40 am
by Boatguy
ememic99 wrote: Tue Sep 21, 2021 5:33 am
Boatguy wrote: Mon Sep 20, 2021 10:16 pm Diamond does not certify software just to fix bugs, only to bring new features to a production airplane, and the bug fixes come along for the ride.
In case that bug causes safety issue such problem should be brought to regulator (FAA, EASA, TC) attention.
The regulators are aware, but they are part, if not most of the problem.

Re: GTX345 and missing traffic targets

Posted: Tue Sep 21, 2021 10:26 pm
by Rich
Not to excuse failing to provide a software update that would marginally improve traffic display accuracy, I don't think there are any standards that exist for ADS-B IN performance or behaviors. In addition:

1. No one is required to have such a function in any aircraft, certainly for part 91 operations. Many of us are operating with totally non-certified equipment to process these signals. It comes down to "do whatever you want".
2. There are lots of exemptions for most US airspace to even have ADS-B OUT/Mode C capability. This is true even in IFR/IMC, BTW.
3. Even part 121 operations very often operate in airspace referenced in item 2, above. As an example ALL airports in Oregon with airline service have these kinds of operations.
4. There are a few ADS-B IN products that are designed to only receive 978 UAT. Some owners are even short-sighted enough to pay to have such devices installed. This is allowed (as is pretty much anything).
5. I've seen malfunctions on some targets. A couple of days ago there was a 1090 plane that was not transmitting altitude. Likely a problem with the altitude encoder.

Just yesterday I had an ADS-B target wink out for a few seconds and then reappear. It was no big deal, as we were in radio contact and it reappeared in short order. Other targets were unaffected.