GNS530 issue after latest MSFS2020 SU16
-
Hi all
I've noticed my "Secondary GNS530" on TBM850 doesn't show TRK, GS and Distance anymore after last MSFS2020 update SU16.
Primary GNS530 works fine but the Secondary doesn't.
Anyone experiencing the same? Any solutions?
I've already reinstalled the TBM and tryed to switch selected airplanes but still nothing.
Cheers
Vince -
I have the same and just posted on this without noticing this post. Eagerly waiting for a reply
-
Giving this a bump as well. I'm experiencing the same thing with a TDS GTN 750 as primary and the GNS 530 as secondary. None of the data fields are active on the GNS.
This is the only plane I use the WT GNS in, as all the other planes I fly (including Black Square's) support multiple GTNs, so I've no idea whether this is a TBM850 issue or an MSFS/WT issue with the GNS as a second GPS unit.
Any help would be appreciated. Not a major issue, but an annoying one.
-
Giving this a bump as well. I'm experiencing the same thing with a TDS GTN 750 as primary and the GNS 530 as secondary. None of the data fields are active on the GNS.
This is the only plane I use the WT GNS in, as all the other planes I fly (including Black Square's) support multiple GTNs, so I've no idea whether this is a TBM850 issue or an MSFS/WT issue with the GNS as a second GPS unit.
Any help would be appreciated. Not a major issue, but an annoying one.
@tttocs Funny you should mention this. When I started working on the avionics in my next (unannounced) aircraft that makes use of dual GNS 430's and 530's, I immediately started seeing this intermittent behavior again. I've tracked it deep into the code with the debugger, and I have still yet to find the issue. I was planning on bringing it up with WT before I release that new aircraft, because it's been years that I've been trying to track it down.
-
@tttocs Funny you should mention this. When I started working on the avionics in my next (unannounced) aircraft that makes use of dual GNS 430's and 530's, I immediately started seeing this intermittent behavior again. I've tracked it deep into the code with the debugger, and I have still yet to find the issue. I was planning on bringing it up with WT before I release that new aircraft, because it's been years that I've been trying to track it down.
@Black-Square said in GNS530 issue after latest MSFS2020 SU16:
@tttocs Funny you should mention this. When I started working on the avionics in my next (unannounced) aircraft that makes use of dual GNS 430's and 530's, I immediately started seeing this intermittent behavior again. I've tracked it deep into the code with the debugger, and I have still yet to find the issue. I was planning on bringing it up with WT before I release that new aircraft, because it's been years that I've been trying to track it down.
I don't suppose you can also push the WT to put in the few hooks you make use of in your various engine computers, such as the TBM8 one? Last time I flew it there was still some missing integration regarding time and fuel to waypoints.
-
@tttocs Funny you should mention this. When I started working on the avionics in my next (unannounced) aircraft that makes use of dual GNS 430's and 530's, I immediately started seeing this intermittent behavior again. I've tracked it deep into the code with the debugger, and I have still yet to find the issue. I was planning on bringing it up with WT before I release that new aircraft, because it's been years that I've been trying to track it down.
@Black-Square said in GNS530 issue after latest MSFS2020 SU16:
I was planning on bringing it up with WT before I release that new aircraft, because it's been years that I've been trying to track it down.Hopefully it's something that WT can fix going forward. Thanks for the information!
-
this is the part where I slip and and say "buy the TDS and all your problems will be solved"

@SadBucket said in GNS530 issue after latest MSFS2020 SU16:
this is the part where I slip and and say "buy the TDS and all your problems will be solved"

Except... I have the TDS, but the TBM 850 only supports TDS for the first GPS unit - the second will always be the WT GNS530, and it's the second unit where the problem occurs. So, no. The TDS doesn't solve the issue.
-
@SadBucket said in GNS530 issue after latest MSFS2020 SU16:
you can select the KX155B as secondary with the 750. That is what I have been doing.
Of course, but IRL I wouldn't file RNAV IFR routes without a backup GPS unit. And since I fly mostly to smaller airports where RNAV approaches are far more common...
The best solution, of course, would be to have support for a backup 650 or even dual 750s. I note there's an active topic discussing just that.