GNS530 startup bug + Autopilot indicator lights
-
This seems like the issues I'm experiencing too, may you explain a bit more detailed the two issues you're getting?
-
«the 530 startup bug seems to be there 90% of the time when not starting cold & dark.»
If you are refering to the unit not responding to any inputs, when starting the TBM with systems running; on my setup this happens 100% of the times, unless another session/plane has been running with the GNS first, then sometimes it does not happen.
However, both this bug and the one were the autopilot is failing/lights not showing are cured by cycling the autopilot from the tablet. If doing so at startup, everything works normally here…
Hope this will be fixed. The bug with the GNS not being responsive when starting with engines running was here in the last version, the other one seems new.
-
On my system the 530 start bug doesn't seem to be related to any system using it earlier. Like if I do a flight with 850 (bug happens) then go to main menu, make a new flight with 850 and it can happen gain.
How do you cycle autopilot from the tablet? Isn't there just two choices: which units for NAV1 and NAV2?
I've also noticed that 530 start bug can be reset by changing the unit from tablet but it isn't any faster than just cycling the radio power switch.
-
@esaahonen said in GNS530 startup bug + Autopilot indicator lights:
How do you cycle autopilot from the tablet?
Changing navigation system, and back.
-
-
@esaahonen Btw. you call it an AP-light bug, but I belive it's the whole autopilot that is malfunctioning... ? Not only the lights.
-
For me the autopilot works fine with the GNS530. It works also when the lights don't work. But with the PMS50 GTN750 I've had various problems, most of them non repeatable except for the consecutive direct-to bug I mentioned earlier. It's weird since the same GTN750 works flawlessly in Black Square Analog Caravan.
-
@esaahonen Hmm, last time I did not have lights on the autopilot, it tried to send me to the ground...
-
-
@esaahonen yeah, thats why i belive it’s a bug thats not only affecting the autopilot lights.
-
Could I please get an answer to the question in my first post here? I'm using the 850 almost on daily basis and these problems are pretty annoying.
One more detail about the NAV and HDG light problem: I recently set up Octavi IFR-1 with MobiFlight and when the indicator light problem occurs in virtual cockpit the lights also refuse to work on Octavi (ie. via LVars).
Best regards
-
Sounds like a local problem; I had to redo my system over the weekend, and after a fresh install of the sim and the TBM and multiple flights, I did not have any such AP issues. I am using a 530 and radio combination FWIW. The only oddity I've seen was my first flight after I changed the avionics; the 530 added duplicate waypoints on me, but still appeared to work. I since restarted the sim and have had anything but perfect operations.
Have you opened a ticket with Just Flight about it?
-
@jmarkows I have the same problem as @esaahonen, not only on this installation, but also my past one.
-
We're talking the little green text above each button on the center panel to indicate the active mode, or something else?
I am certain I've seen at least some, if not all of the modes I've used light up on the center panel, as well as ARM, CAPT, etc. on the altitude selector on the pilot's panel, but I want to make sure I'm looking at the same things you guys are.
-
I went and did some practice approaches tonight on VATSIM, and I made sure to cycle each mode at least once. I never did see ARM for NAV or APR (likely a sim limitation with the stock avionics), but I did get the green indicator above all of the modes as appropriate, and TEST turns red.
I am using the WT 530 as the primary and the radio as the second, no fancy GNS here. I have the WT "pointer" mod installed via the Content Manager, but the TBM almost certainly calls the WT avionics natively and doesn't need it.
-
This post is deleted!
