How to turn on the GNS 430/530
-
If you have the mod installed, please load the Arrow III, confirm that the GNS 530 is selected on the EFB, end the flight and then start a new one. You should then have the ability to switch the GNS on/off after the battery master is switched on.
-
If you have the mod installed, please load the Arrow III, confirm that the GNS 530 is selected on the EFB, end the flight and then start a new one. You should then have the ability to switch the GNS on/off after the battery master is switched on.
@Martyn said in How to turn on the GNS 430/530:
You should then have the ability to switch the GNS on/off after the battery master is switched on.
May I ask where this on/off switch exactly is? I haven't noticed it yet and other people also report that the GNS530 stays off whenever switching to it via EFB.
-
@Martyn said in How to turn on the GNS 430/530:
We're using the default GNS code so the 430/530 power is controlled by the small 'C' knob.
Just tried that, it only works if you start the flight with GNS530 already selected. Once you switch it to another GNS and back to 530, it stays black no matter what you do.
The buttons seem to work but the screen remains black. GNS430 works fine even if you switch around.
Doesn't seem to be related to the mod either. -
Same problem here, switching to GNS530 causes it to stop displaying (if you try the pop out window with right ALT, it displays the 430, might help catching the bug)
Starting with GNS530 selected works fine, both modded and default versions.@AndrewCZ said in How to turn on the GNS 430/530:
(if you try the pop out window with right ALT, it displays the 430, might help catching the bug)
This was always the case depending on where you click to pop out, you either get the 430 or 530 :)
-
Thanks for the hint. This has now been fixed (GNS 530 screen not visible and incorrect pop-ups).
@Martyn I just got v0.3.0 installed and experienced the GNS530 black screen issue again. I will provide further details later, need more testing to identify the proper scenario that raises this issue but keep it on your radar for this issue is not done yet.
Hangar 101
-
@Martyn I just got v0.3.0 installed and experienced the GNS530 black screen issue again. I will provide further details later, need more testing to identify the proper scenario that raises this issue but keep it on your radar for this issue is not done yet.
@anderson , If the GNS 530 has a black screen it is turned OFF... To turn it ON, just rotate the knob labeled "C".
-
@Martyn I just got v0.3.0 installed and experienced the GNS530 black screen issue again. I will provide further details later, need more testing to identify the proper scenario that raises this issue but keep it on your radar for this issue is not done yet.
@anderson Check battery voltage on the iPad, must be >10V for the Garmin to run (if not, rev the engine for a while with generator on and it recharges). Also, might be turned off (the top volume control, next to COM radio switch, doubles as power switch, turn it at least a bit to the right).
-
Thanks for the hint. This has now been fixed (GNS 530 screen not visible and incorrect pop-ups).
@Martyn I am having the same issue as Anderson. The GNS530 will automatically turn on when the battery reaches 10V (so long as the power switch is in the 'on' position), so I just have to wait for a few minutes with the engine/alternator running before setting it up. Not a huge issue, but would appreciate if y'all could look into it. Please let me know if you'd like me to submit a support ticket. Thanks, Nick
-
@Martyn I am having the same issue as Anderson. The GNS530 will automatically turn on when the battery reaches 10V (so long as the power switch is in the 'on' position), so I just have to wait for a few minutes with the engine/alternator running before setting it up. Not a huge issue, but would appreciate if y'all could look into it. Please let me know if you'd like me to submit a support ticket. Thanks, Nick
@SimPilotX you nailed it. That´s precisely the issue. I got my batteries between 10.1 and 12 and clicked the button "Recharge Battery" and it went down to 8.8 thus turning off the GNS530, when it got back to 10.1 GNS530 was back on. Thank you!
@Martyn I understand the "Recharge Battery" issue depends upon ASOBO fix but please keep it in your radar for a future final fix (if possible). -
The systems.cfg defines what voltage is required for each system/avionics unit to function. Here are updated values which should get the GNS units working at a lower voltage, if you'd like to make the edit yourself ahead of the next update:
circuit.24 = Type:CIRCUIT_GPS:1 #Connections:bus.2# Power:5, 15, 5.0# Name:AS430 ; AS430 30W
circuit.25 = Type:CIRCUIT_GPS:2 #Connections:bus.2# Power:5, 15, 5.0# Name:AS530 ; AS530 30W -
The systems.cfg defines what voltage is required for each system/avionics unit to function. Here are updated values which should get the GNS units working at a lower voltage, if you'd like to make the edit yourself ahead of the next update:
circuit.24 = Type:CIRCUIT_GPS:1 #Connections:bus.2# Power:5, 15, 5.0# Name:AS430 ; AS430 30W
circuit.25 = Type:CIRCUIT_GPS:2 #Connections:bus.2# Power:5, 15, 5.0# Name:AS530 ; AS530 30W -
Hi,
I have this same issue again. My GNS530 won't turn on. Battery is over 10v. Turn the "c" knob but nothing happens...
I tried restarting the flight many times.Is it because of SU6 ?
When I click on the button to swap NAV1 channels for instance, I see on the VOR that I'm changing from a channel with reception and without. So it's actually turned on but the screen is black
-
Hi,
I have this same issue again. My GNS530 won't turn on. Battery is over 10v. Turn the "c" knob but nothing happens...
I tried restarting the flight many times.Is it because of SU6 ?
When I click on the button to swap NAV1 channels for instance, I see on the VOR that I'm changing from a channel with reception and without. So it's actually turned on but the screen is black
-
@majorswitcher Do you have any GNS mods installed in the Community folder? The GNS works correctly here.
@martyn sorry for not replying!
I updated that 3rd party gps and all was good!
