Sign in to follow this  
jellef

Carenado A36 Bonanza GNS430 lower rows buttons inoperative

Recommended Posts

I have been updating a number of my planes in P3D v4.5. With the Carenado A36 Bonaza I have a problem in the VC gauge that most of the knobs are functioning (on the left and right side of the bezel), only not the bottom row: CDI, OBS, MSG, FPL and PROC. Whatever I tried, I can't get it to work. I found no answer on the other forum items. The knobs on the popup (2D) gauge do work correctly.

I have 2 versions of the Bonanza: the original one supplied with the P3D package and a newer version bought from Carenado. Both versions have the same problem. Most other Carenado planes do not have this defect.

Anyone with an idea how to solve this?

Cheers, Jelle

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

i have a pair of 430's in my FSX Carenado A36, one above the other.  In my setup the top 430 is fully accessible.  The lower 430 matches the description of your issue.  From top to bottom my related center stack is:  Audio Select Panel, Autopilot, GNS 430 unit 1, GNS 430 unit 2.  One suggestion I will make is when the Carenado A36 is loaded into the sim, press Shift+3.  Uncheck the box for Instrument Reflections and see if that helps.  Please report back on results so others may see.

Edited by fppilot
  • Like 1

Share this post


Link to post
Share on other sites

Mine is working OK in V4.5.

panel.cfg:

[Window01]
Background_color=0,0,0
size_mm=500,500
window_size_ratio=1.000  
position=8
visible=0
ident=794
window_size= 0.320, 0.500
zorder=0

gauge00=rxpGNS2!GNS_430_1,  0,0,500,250,A36
gauge01=rxpGNS2!GNS_430_2,  0,251,500,250,A36

 

[Vcockpit03]
....

gauge00=rxpGNS2!GNS_430_1,  165,67,339,171,A36
gauge01=rxpGNS2!GNS_430_2,  165,247,339,171,A36
gauge02=BA36!gem,  8,354,154,154

ini file:

[GNS_430_1.A36]
; show screen only gauge if true.
nobezel = false

popleft = 794

[GNS_430_2.A36]
; show screen only gauge if true.
nobezel = false

popleft = 794

 

  • Like 2

Share this post


Link to post
Share on other sites
40 minutes ago, Bert Pieke said:

[Vcockpit03]
....

gauge00=rxpGNS2!GNS_430_1,  165,67,339,171,A36
gauge01=rxpGNS2!GNS_430_2,  165,247,339,171,A36
gauge02=BA36!gem,  8,354,154,154

Hi Bert,
Would you post your complete [Vcockpit03]?  In the A36 in FSX I had added 430_2 as an additional Vcockpit entry (09).  When I used your lines to amend my 03 to include both 430_1 and 430_2, and of course fully eliminated my VC09, my result in FSX is that 430_2 works fine in the popup, but stays dark in the VC. 

430_1 is okay throughout,

Share this post


Link to post
Share on other sites

Hi @jellef
P3Dv4.5. My buttons in the VC all work fine. Both units 1&2. When you hover your mouse over the buttons does it change into a hand cursor?

Here is my panel.cfg. In the VC I have both GNS_430_1 and GNS_430_2. Clicking anywhere in the VC either 430 1 or 2 opens up a single popup window containing both units.

Spoiler

[Window Titles]
Window00=GPS
Window01=Toggle_Manual
Window02=Toggle_Control
Window03=EFD1000
Window04=INFO

//--------------------------------------------------------
[Window00]
Background_color=49,49,49 
size_mm=500,520
window_size_ratio=1.000  
position=0
visible=0
ident=794
window_size= 0.255, 0.420
window_pos= 0.000, 0.580
zorder=0

gauge00=rxpGNS2!GNS_430_1,  0,0,500,260
gauge01=rxpGNS2!GNS_430_2,  0,260,500,260
gauge02=BA36!Toggle_GPS,  83,38,331,428

//--------------------------------------------------------
[Window01]
Background_color=0,0,0 
size_mm=700,700
window_size_ratio=1.000  
position=0
visible=0
ident=793
window_size= 0.421, 0.681
window_pos= 0.520, 0.020
zorder=5

gauge00=A36Manual!manual,  0,0,700,700

//--------------------------------------------------------
[Window02]
Background_color=0,0,0 
size_mm=380,174
window_size_ratio=1.000  
position=0
visible=0
ident=796
window_size= 0.201, 0.123
window_pos= 0.020, 0.160
zorder=5

gauge00=BA36!Control_windows,  0,0,380,174

//--------------------------------------------------------
[Window03]
Background_color=32,32,32 
size_mm=520,1024
window_size_ratio=1.000  
position=0
visible=0
ident=795
window_size= 0.200, 0.761
window_pos= 0.770, 0.210

gauge00=EFD1000_A36!EFD1000_pfd,  1,0,513,1022
gauge01=BA36!Toggle_EFD,  0,0,513,100

//--------------------------------------------------------
[Window04]
file=info.bmp 
size_mm=419,181
window_size_ratio=1.000  
position=0
visible=1
ident=142
window_size= 0.200, 0.115
window_pos= 0.020, 0.040

//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$ASP1000

gauge00=EFD1000_A36!EFD1000Config,  0,0,10,10
gauge01=EFD1000_A36!EFD1000_pfd,  0,0,257,512

//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_2

gauge00=BA36!RPM_Digital,  231,145,213,99
gauge01=BA36!Annunciator_Panel,  2,2,508,25
gauge02=BA36!Ignition Switch,  320,185,68,68
gauge03=BA36!Panel_annunciator,  0,145,230,86
gauge04=RadioA36!RadioAudio,  0,57,451,87
gauge05=APBK_A36!Autopilot,  0,377,512,134
gauge06=RadioA36!RadioAdf,  0,246,512,104
gauge07=BA36!annunciator_test,  478,77,30,30
gauge08=BA362!GPSALT,  0,0,5,5

//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_4_N

gauge00=rxpGNS2!GNS_430_1,  158,68,350,169
gauge01=rxpGNS2!GNS_430_2,  159,248,350,169
gauge02=BA36!gem,  8,354,154,154

//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$ASP1000_N

gauge00=EFD1000_A36!EFD1000_pfd,  0,0,257,512

//--------------------------------------------------------
[Vcockpit05]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_2_A

gauge00=BA36!Annunciator_Panel_OFF,  2,29,508,25

//--------------------------------------------------------
[Vcockpit06]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_4_A

gauge00=DIGTTRANS_A36!transponder,  170,428,340,83

//--------------------------------------------------------
[Vcockpit07]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_5

gauge00=BA36!Clock,  6,37,496,434

//--------------------------------------------------------
[Vcockpit08]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_4_O

gauge00=BA36!Auto_taxi_onoff,  3,170,30,24
gauge01=BA36!Alt_Load,  172,2,167,65
gauge02=BA36!Bus_Volts,  342,2,167,65
gauge03=BA36!Trim,  114,226,54,124
gauge04=BA36!Toggle_Gps,  247,92,189,112
gauge05=BA36!Flap_lights,  87,266,23,81


Day=255,255,255
Night=1,31,28
Luminous=255,255,255

  RealityXP.GNS.ini

Spoiler

[GNS_430_1]
; is the master device if true.
MasterDevice = true
LinkCrs = true
UseCrossFill = true
FuelType = AVGAS
; connects to: 'PFC_STACK','PFC_430','PFC_530' or any '#PID' (#D002 for PFC_430)
; no value connects to first found, 'OFF' disables connection.
HardwareDevice = 
; hardware selector number or -1 to disable.
HardwareIdx = -1
LinkHsi = false
AutoNavGps = false

[GNS_430_1.DEFAULT]
; show screen only gauge if true.
nobezel = false
; screen only border size (pixels).
border.size = 0
; screen only border color (#RGB or #RGBA).
border.rgba = #000000
; display mouse tooltips if true.
tooltips = false
; enable mouse clickspots if true, disable if false.
usemouse = true
; enable alternate click-spots (left CCW, right CW, middle Push) if true.
usealtmouse = false
; auto-resize dimension (width,height)
refsize = 
; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).
popleft = 
; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).
popright = 
; adjust brightness (0 to 100)
brightness.bezel = 100
; offset brightness (-100 to +100)
brightness.screen = 0

[GNS_430_2]
; is the master device if true.
MasterDevice = false
LinkCrs = true 
UseCrossFill = true 
FuelType = AVGAS
; connects to: 'PFC_STACK','PFC_430','PFC_530' or any '#PID' (#D002 for PFC_430)
; no value connects to first found, 'OFF' disables connection.
HardwareDevice = 
; hardware selector number or -1 to disable.
HardwareIdx = -1
LinkOto = false
LinkHsi = false
AutoNavGps = false

[GNS_430_2.DEFAULT]
; show screen only gauge if true.
nobezel = false
; screen only border size (pixels).
border.size = 0
; screen only border color (#RGB or #RGBA).
border.rgba = #000000
; display mouse tooltips if true.
tooltips = false
; enable mouse clickspots if true, disable if false.
usemouse = true
; enable alternate click-spots (left CCW, right CW, middle Push) if true.
usealtmouse = false
; auto-resize dimension (width,height)
refsize = 
; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).
popleft = 
; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).
popright = 
; adjust brightness (0 to 100)
brightness.bezel = 100
; offset brightness (-100 to +100)
brightness.screen = 0

 

FUeBdSd.jpg 

Edited by BillS511
  • Like 1

Share this post


Link to post
Share on other sites

Hi Bill,

I copied your panel.cfg and RealityXP.GNS.ini files 1-to-1 and now its works! I will take some time to debug and if I find the cause I will report it here.

Thanks,

 

Jelle

Edited by jellef
  • Like 2

Share this post


Link to post
Share on other sites

Found the cause of the problem: X, Y, W and H parameters of the rxpGNS2!GNS_430_x parameters. Most likely they did not match with the bezel and so the clickspot shifted.

Find a strange problem with the panel.cfg ident parameters. The popleft parameters in the .ini file do not match with 2 separate Windowsxx sections in the panel.cfg. Only the default Windows00 section is found and so it is not possible to configure a undependant popup for both GNS430's. I suspect a problem while loading the panel.cfg due to an error, but haven't found it yet. There is a possible mixup with  the panel for for the old and the new Bonanza. I will try to fix this either.

 

Jelle 

 

Share this post


Link to post
Share on other sites
1 hour ago, jellef said:

it is not possible to configure a independent popup for both GNS430's.

Correct. You'll have to add 2 window sections for each unit as popups:

Unfortunately it appears Carenado hardcoded 2 Vcockpit toggles of the 2 units into the aircraft model. The toggle Ident for both units in the VC is 794 and can be used to popup only one unit.
There is no toggle gauge in the panel file for this that can be removed. It's not gauge BA36!Toggle_GPS. Nor is it the Instrument Reflections option. Whatever it is, it's blocking the RXP popleft= command in the VC.

//--------------------------------------------------------
[Window00]
Background_color=0,0,0 
size_mm=100,100
window_size_ratio=1.000  
position=
visible=1
ident=794
window_size= 0.255, 0.210
window_pos= 0.000, 0.581
zorder=99

gauge00=rxpGNS2!GNS_430_1,  0,0,100,100

//--------------------------------------------------------
[Window01]
Background_color=0,0,0 
size_mm=100,100
window_size_ratio=1.000  
position=
visible=1
ident=
window_size= 0.255, 0.210
window_pos= 0.000, 0.796
zorder=99

gauge00=rxpGNS2!GNS_430_2,  0,0,100,100

Spoiler

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com
// Built Wednesday, April 17, 2019 at 13:19 FSPS Build:22900

[Window Titles]
Window00=RXP GNS 430 1
Window01=RXP GNS 430 2
Window02=Toggle_Manual
Window03=Toggle_Control
Window04=EFD1000
Window05=INFO

//--------------------------------------------------------
[Window00]
Background_color=0,0,0 
size_mm=100,100
window_size_ratio=1.000  
position=7
visible=1
ident=794
window_size= 0.255, 0.210
window_pos= 0.000, 0.581
zorder=99

gauge00=rxpGNS2!GNS_430_1,  0,0,100,100

//--------------------------------------------------------
[Window01]
Background_color=0,0,0 
size_mm=100,100
window_size_ratio=1.000  
position=7
visible=1
ident=15432
window_size= 0.255, 0.210
window_pos= 0.000, 0.796
zorder=99

gauge00=rxpGNS2!GNS_430_2,  0,0,100,100

//--------------------------------------------------------
[Window02]
Background_color=0,0,0 
size_mm=700,700
window_size_ratio=1.000  
position=0
visible=0
ident=793
window_size= 0.421, 0.681
window_pos= 0.520, 0.020
zorder=5

gauge00=A36Manual!manual,  0,0,700,700

//--------------------------------------------------------
[Window03]
Background_color=0,0,0 
size_mm=380,174
window_size_ratio=1.000  
position=0
visible=0
ident=796
window_size= 0.201, 0.123
window_pos= 0.020, 0.160
zorder=5

gauge00=BA36!Control_windows,  0,0,380,174

//--------------------------------------------------------
[Window04]
Background_color=32,32,32 
size_mm=520,1024
window_size_ratio=1.000  
position=0
visible=0
ident=795
window_size= 0.200, 0.761
window_pos= 0.770, 0.210

gauge00=EFD1000_A36!EFD1000_pfd,  1,0,513,1022
gauge01=BA36!Toggle_EFD,  0,0,513,100

//--------------------------------------------------------
[Window05]
file=info.bmp 
size_mm=419,181
window_size_ratio=1.000  
position=0
visible=1
ident=142
window_size= 0.200, 0.115
window_pos= 0.020, 0.040

//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$ASP1000

gauge00=EFD1000_A36!EFD1000Config,  0,0,10,10
gauge01=EFD1000_A36!EFD1000_pfd,  0,0,257,512

//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_2

gauge00=BA36!RPM_Digital,  231,145,213,99
gauge01=BA36!Annunciator_Panel,  2,2,508,25
gauge02=BA36!Ignition Switch,  320,185,68,68
gauge03=BA36!Panel_annunciator,  0,145,230,86
gauge04=RadioA36!RadioAudio,  0,57,451,87
gauge05=APBK_A36!Autopilot,  0,377,512,134
gauge06=RadioA36!RadioAdf,  0,246,512,104
gauge07=BA36!annunciator_test,  478,77,30,30
gauge08=BA362!GPSALT,  0,0,5,5

//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_4_N

gauge00=rxpGNS2!GNS_430_1,  158,68,350,169
gauge01=rxpGNS2!GNS_430_2,  159,248,350,169
gauge02=BA36!gem,  8,354,154,154

//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$ASP1000_N

gauge00=EFD1000_A36!EFD1000_pfd,  0,0,257,512

//--------------------------------------------------------
[Vcockpit05]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_2_A

gauge00=BA36!Annunciator_Panel_OFF,  2,29,508,25

//--------------------------------------------------------
[Vcockpit06]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_4_A

gauge00=DIGTTRANS_A36!transponder,  170,428,340,83

//--------------------------------------------------------
[Vcockpit07]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_5

gauge00=BA36!Clock,  6,37,496,434

//--------------------------------------------------------
[Vcockpit08]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_4_O

gauge00=BA36!Auto_taxi_onoff,  3,170,30,24
gauge01=BA36!Alt_Load,  172,2,167,65
gauge02=BA36!Bus_Volts,  342,2,167,65
gauge03=BA36!Trim,  114,226,54,124
gauge04=BA36!Flap_lights,  87,266,23,81
gauge05=BA36!Toggle_Gps,  247,92,189,112


Day=255,255,255
Night=1,31,28
Luminous=255,255,255

[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=6143

 

 

Edited by BillS511

Share this post


Link to post
Share on other sites
1 hour ago, BillS511 said:

Correct. You'll have to add 2 window sections for each unit as popups:

Unfortunately it appears Carenado hardcoded 2 Vcockpit toggles of the 2 units into the aircraft model. The toggle Ident for both units in the VC is 794 and can be used to popup only one unit.
There is no toggle gauge in the panel file for this that can be removed. It's not gauge BA36!Toggle_GPS. Nor is it the Instrument Reflections option. Whatever it is, it's blocking the RXP popleft= command in the VC.

I'm afraid you are right. Ident 794 is the only instance that is referred to for a popup. I have configured multiple Carenado (and 1 Alabeo) aircraft meanwhile, they all work with 2 GNS430's with an individual popup with different id's.

One strange thing: when I first tried your solution it worked. Immediately I set it up with an additional window section (deleted the gauge01 from window00) with a different ident, configured the .ini file for it and it worked. When copying the concept to a different plane I editted the wrong panel.cfg and saw it too late. I tried to recover it but never succeeded in getting the desired result. Now I'm seriously thinking I saw something that never could happen. Was it a fata morgana?

I'm not willing to spend many more hours in chasing the impossible. If someone has the solution, please tell us.

 

Share this post


Link to post
Share on other sites
2 hours ago, BillS511 said:

The toggle Ident for both units in the VC is 794 and can be used to popup only one unit.

Three of us have responded and though there may be some small differences the methods used creates one popup window with both GNSs with a window Ident=794 that matches the hard coded ident.  In FSX I have been unable in the VC to get to the lower clickspots on the lower GNS.  All is well and good with both GNSs in the 2D popup window, and the lower unit does display well in the VC.

I had not dusted off the A36 is a couple of years and this topic caused me to pull her out and fly her.  Still a nice aircraft, though I still do not prefer the Aspen EFD as it's tuning knobs can be frustrating. 

Edited by fppilot
  • Like 1

Share this post


Link to post
Share on other sites
8 minutes ago, fppilot said:

In FSX I have been unable in the VC to get to the lower clickspots on the lower GNS

I have no chance to test this in FSX, but in P3D I use this for the VC:

gauge00=rxpGNS2!GNS_430_1,  165,67,339,171
gauge01=rxpGNS2!GNS_430_2,  165,247,339,171

All buttons and knobs (right and left side and bottom) are working.

The only ident working is 794, as used in [Windows00], so it definitely looks like this is hardcoded. I experimented with a different number in [Windows00] and in the popleft call in RealityXP.GNS.ini (both in the GNS_430_x sections). Also the ident=GPS_PANEL does not work.

So the only option left is configuring both 2D cockpit lines in [Windows00] and setting popleft=794 in the .ini file. This shows a good popup for both GNS_430 simultaneous.

Jelle

  • Like 1

Share this post


Link to post
Share on other sites
50 minutes ago, jellef said:

I have no chance to test this in FSX, but in P3D I use this for the VC:

gauge00=rxpGNS2!GNS_430_1,  165,67,339,171
gauge01=rxpGNS2!GNS_430_2,  165,247,339,171

All buttons and knobs (right and left side and bottom) are working.

Would you please post your entire [Vcockpit03] section, including the texture= and any other gauge##= lines?  There may be a change in a texture between the FSX and P3D A36's.

Share this post


Link to post
Share on other sites
11 hours ago, fppilot said:

Would you please post your entire [Vcockpit03] section, including the texture= and any other gauge##= lines?  There may be a change in a texture between the FSX and P3D A36's.

[Vcockpit03]
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_bon_4_N

gauge00=rxpGNS2!GNS_430_1,  165,67,339,171
gauge01=rxpGNS2!GNS_430_2,  165,247,339,171
gauge02=BA36!gem,  8,354,154,154

 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks Jelle.  That VC03 does not work in FSX for some reason.  Both GNS work 100% functional in the dual gauge popup, but in the VC the top GNS (1) stays dark and also in the VC the buttons and knobs do not work on the lower GNS (2).  I expect Carenado changed the texture file from FSX to P3D.  So I am back to my previous setup for FSX.

Thank you again,
Frank P

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this