Alabeo Aztec - Problem Configuring Reality XP GTN750

[rog943 14]

I am using FSX SE and an Alabeo Aztec and until yesterday I had the Reality XP 530W and all was fine.  I decided to update to their GTN750.  I used the add-on to revert to the default 530 thinking that would be a good plan.

Somehow after that I ended up with the 750 blank screen in the aircraft before I even got the add-on working.  Basically it was the 750 frame with knobs etc but no image on the screen.

I now have the 750 Add-on (I still have the 530 add-on as well).   When I configure to get the unit working I end up with the new screen inside the one I mention above and only two thirds of the screen is visible.  Clicking to get a pop up gets me the 530!  I can post photos but can't see how to here.

Obviously I have done something wrong.

Help please someone!

Edited May 13, 2021 by rog943

[RXP 2,338]

Hi,

4 hours ago, rog943 said:

When I configure to get the unit working

What are you using/doing to configuring the units in the aircraft?

Is this Alabeo own config tool? Is this the RXP GTN Panel Assistant GUI?

Edited May 13, 2021 by RXP

[rog943 14]

First of all thanks for responding and so quickly.  I really appreciate it.

I will try to explain but I'm not a computer person.

The problems started last night after I bought the 750.  Trying to see what has gone wrong I think I may have initially have run an .exe file in the Objects/Aircraft/Alabeo Aztec file which is F1GTN750PA23.exe.  The F1 bit didn't register til I got in to this mess - obviously the wrong file.  And maybe that is part of my problem.

Later I found the Troubleshooting section and I managed to install the Add-in for the 750.  However the Add-in for the 530 is still there - do I need to uninstall that?  Delete it from the .dll file?

When I fire up FSX I get the situation I describe above - neatly fitted in to the space is a 750 panel (the F1 panel?) On top of that is whatever I configure using either of the add-ins.  I can show a 530W or remove that and using the other add-in I can get a 750 which doesn't fit although it seems to work where I can reach it!

I hope that makes sense.  A photo would show what I mean or maybe I could show you in some other way. 

[RXP 2,338]

Ok I might have a clue at what you are describing.

Can you confirm you're using the RXP GTN Panel Assistant (what you reference as "using either of the add-ins" ?) in order to "Replace" Auto-Detected gauges?

And in doing so, you've effectively first "Replaced" the other GTN entries which were configured with the Alabeo tool (F1GTN750PA23.exe), with the RXP GTN instead?

And what you get looks like a smaller GTN screen within a GTN bezel within a larger GTN bezel?

Is this is so, please make sure to expand the options below the GTN model drop down list in the GUI Assistant / Replace panel, in order to select the "NO BEZEL" option. This will effectively replace the VC gauges so that the entire surface is a screen only.

[rog943 14]

Some progress!  The screen is now just one screen.  However the unit displayed is a 530.  I tried to see what the GTN Panel Assistant could offer but when I select it from the drop down menu it now doesn't appear.  The 530 does but with 750 nothing happens. 

[rog943 14]

After a reboot the assistant reappeared and I have managed to get the 750 in the panel albeit too big.  It extends beyond the right hand edge.  

[fppilot 4,358]

A check of the Alabeo web page for that model indicates both RXPs you were tinkering with are supported.  That normally means that Alebeo provides a panel configuration tool with the model.  What has likely occurred is multiple configurator edits to the model's panel.cfg file located in the model's panel folder.  That panel.cfg file is a text file in construction.  You can open it and view in with Windows Notepad or Wordpad.  I have two recommendations.  One is that you open that panel.cfg file with one of the two Windows apps I mentioned.  Then copy and paste the contents here for us to look at.  If you do so please use the "Spoiler" feature here.  Click on the eyeball icon  above and it will provide a window.  Paste into that window.  Doing that provides a window that can be opened and closed as we read it.  That helps keep the message compact.

The second recommendation, and it could save you time overall, is to completely remove/uninstall the aircraft model, checking that all remnants are gone, including any in an .....FSX/Alebeo/Aztec folder if any.  Then reinstall.  Read the Alabeo documentation (if any) and consider first how to use any configuration tool they provide and see that result before attempting other steps.

[Bert Pieke 7,584]

I would one more time run the F1GTN exe file and load the plane.

That should give you a black GTN screen in the panel.

Then, using the RXP assistant, replace the two instances of F1GTN by the RXP GTN 750.

For the Popup window, no special options required,  for the Vcockpit entry, add the NO BEZEL option.

If you complete that, the airplane should reload and the RXP GTN appear.

Edited May 13, 2021 by Bert Pieke

[Bert Pieke 7,584]

7 minutes ago, fppilot said:

A check of the Alabeo web page for that model indicates both RXPs you were tinkering with are supported. 

What I read is:

Flight1 GTN 750* integration
Reality XP GNS530* integration (only for FSX)
Alabeo GNS530

[rog943 14]

Thanks Bert.  My only hesitation last night was the reference to F1 750 integration - not not RXP.  I thought I'd try anyway!   F1 only sell the 650/750 package which I don't need or want to pay a lot more for.  

I'll send the info about the panel.cfg file first.

Thanks again.

Edited May 13, 2021 by RXP

[rog943 14]

Just an update.  I ran the F1GTN.exe again and it gave me the black screen.  I now have the correct screen.  I will still send the cfg file as the controls on the bezel don't work.

After all this can I ask if I will be able to get the display onto my iPad like I had with the 530?  I use spacedesk to achieve that.

[rog943 14]

Spoiler

//*********************************************************
// ALABEO PA23 AZTEC F 250 FSX/P3D 
// Copyright © Carenado 2016 - All Rights Reserved
//*********************************************************

[Window Titles]
Window00=NONE
Window01=AUTOPILOT
Window02=WINDOW MANAGER
Window03=INFO
Window04=ENGINE SETUP
Window05=KNOB INFO

Window07=Flight1 GTN Stack - DO NOT MODIFY
Window08=Reality XP GTNs (managed)

[VIEWS]
VIEW_FORWARD_DIR=-1.000, 0.000, 0.000

// windowssizeX = (window_sizeY * size_mmX / size_mmY) * 9 / 16
//--------------------------------------------------------
//--------------------------------------------------------
[Window00]
Background_color=0,0,0 
size_mm=1,1
position=0
visible=0
ident=0

// windowssizeX = (window_sizeY * size_mmX / size_mmY) * 9 / 16
//--------------------------------------------------------
//--------------------------------------------------------
[Window01]
Background_color=0,0,0 
size_mm=946,311
window_size_ratio=1.000  
position=0
visible=0
ident=10010
window_size= 0.427, 0.250
window_pos=  0.010, 0.030
zorder=0

gauge00=PA23APALTIMATIC!GAUGE_AP,  0,0,946,311
gauge01=ALPA23!ToggleCAR530,          0,0,946, 32

//--------------------------------------------------------
[Window02]
Background_color=0,0,0 
size_mm=500,237
position=0
visible=0
ident=796
window_size= 0.237, 0.200
window_pos= 0.020, 0.120
zorder=5

gauge00=ALPA23!Control_windows,  0,0,500,237

//--------------------------------------------------------
[Window03]
file=info.bmp 
size_mm=555,131
window_size_ratio=1.000  
position=0
visible=1
ident=10030
window_size= 0.238, 0.100
window_pos=  0.020, 0.020

gauge00=ALPA23!ToggleINFO,  528,0,25,25

//--------------------------------------------------------
[Window04]
Background_color=0,0,0 
size_mm=600,490

window_size= 0.344, .500

position=3
visible=0
nomenu=1
ident=10060

gauge00=GAUGEPA23!StartWindowsAircraft ,   0,  0, 600,490

//--------------------------------------------------------
[Window05]
Background_color=0,0,0 
size_mm=600,490

window_size= 0.344, .500

position=5
visible=0
nomenu=1
ident=10050

gauge00=GAUGEPA23!StartWindows ,   0,  0, 600,490

//--------------------------------------------------------
//--------------------------------------------------------

[Window07]
size_mm=255,800
Position= 0
window_size= 0.058, 0.243
visible=1
ident=14400
zorder=100
gauge00=F1GTN!GTNStack,  0,0,255,870

//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$Panel_1

gauge00=rxpGTN!GTN_750_1, 0, 0,667,794,NO_BEZEL

//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0 
size_mm=512,512
visible=1
pixel_size=513,513
texture=$Panel_2

gauge00=ALASound_PA23!CarSound,        0, 0,  1,  1
gauge01=ALAPA23_G530!GPS_TCAS,           0, 0,  1,  1
gauge02=GAUGEPA23!Gauge_UPDATE_DIG,    0, 0,  1,  1

gauge03=Radar_Aztec_F_250!Radar,       0,  0, 290, 291
gauge04=GAUGEPA23!Gauge_CLOCK_DIG,     292,  0, 217, 215
gauge05=GAUGEPA23!Radio_KDI572_DME,       0, 292, 306, 122

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

gauge00=Comm_Nav_Aztec_F_250!Comm2_Nav2,        0, 0, 496, 204

Day=255,255,255
Night=225,117,89
Luminous=200,200,101

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

[Window08]
size_mm=100,100
window_pos=0.000000,0.126301
window_size=0.216146,0.747398
visible=1
always_visible=0
zorder=99
background_color=0,0,0
ident=15751
gauge00=rxpGTN!GTN_750_1, 0, 0,100,50
gauge01=rxpGTN!GTN_750_2, 0,50,100,50
 

Here's the .cfg file from the a/c file.  

[Bert Pieke 7,584]

1 hour ago, rog943 said:

the controls on the bezel don't work.

That is a separate issue, but fixable... There are topics in this forum that describe how you get the bezel buttons to work correctly.

Sounds like you got the initial problem solved! 😀

Edited May 13, 2021 by Bert Pieke

[Bert Pieke 7,584]

1 hour ago, rog943 said:

Here's the .cfg file from the a/c file.  

Two suggestions:

[Window07]
...
// gauge00=F1GTN!GTNStack,  0,0,255,870

(add the // to comment out this F1 holdover..)

Secondly, do you have two GTN units in the panel?

[Window08]
...
gauge00=rxpGTN!GTN_750_1, 0, 0,100,50
gauge01=rxpGTN!GTN_750_2, 0,50,100,50

If not, delete the gauge01 line.

 

 

[Bert Pieke 7,584]

40 minutes ago, Bert Pieke said:

That is a separate issue, but fixable... There are topics in this forum that describe how you get the bezel buttons to work correctly.

Thinking about it... it sure would be nice if the RXP Assistant would remove the F1Stack and add the F1VC gauge... 😉