Hi, I am having a problem in that I can not get the GTN 650 of the GTN 750/650 pair to power on .  I just purchased this and also have had the same problem for a couple of years with the GNS430 of the GNS 530/430 pair I have used up to now.  The 750 powers on just fine and looks fantastic; I just get no response from the 650 from XP Reality.

What is also peculiar to me is that some planes already have a 430 installed in them and I am able to get that unit powered on, just not the XP Reality version,which I would prefer.  So whatever my problem is, it spans both the 530 to 750 series: the main gps powers on and works fine, the secondary unit does not.  I have varied the power on sources for both the XP Reality 430 and 650 but it seems to make no difference.

Can anyone suggest what direction I should take here?  Thank you, CEC

21/12/18 06:24:31.103 02008 -    ] # rxpGtnSim32.dll version 2.5.28.6
21/12/18 06:24:31.102 02008 INFO ]
21/12/18 06:25:28.034 07676 INFO ] GTN 750.1 - TRAINER 6624
21/12/18 06:25:28.043 07676 WARN ] GTN 750.1 process is running as-admin
21/12/18 06:40:19.840 02008 ERROR] no device available for GTN 650.2

 

I have a screenshot of the situation also but not sure how I can attach it here. The 650 window loads fine but just does not power on so far.  Thank you.

 

Edited December 18, 20214 yr by cecarnicom

14 hours ago, cecarnicom said:

Hi, I am having a problem in that I can not get the GTN 650 of the GTN 750/650 pair to power on .  I just purchased this and also have had the same problem for a couple of years with the GNS430 of the GNS 530/430 pair I have used up to now.  The 750 powers on just fine and looks fantastic; I just get no response from the 650 from XP Reality.

What is also peculiar to me is that some planes already have a 430 installed in them and I am able to get that unit powered on, just not the XP Reality version,which I would prefer.  So whatever my problem is, it spans both the 530 to 750 series: the main gps powers on and works fine, the secondary unit does not.  I have varied the power on sources for both the XP Reality 430 and 650 but it seems to make no difference.

Can anyone suggest what direction I should take here?  Thank you, CEC

21/12/18 06:24:31.103 02008 -    ] # rxpGtnSim32.dll version 2.5.28.6
21/12/18 06:24:31.102 02008 INFO ]
21/12/18 06:25:28.034 07676 INFO ] GTN 750.1 - TRAINER 6624
21/12/18 06:25:28.043 07676 WARN ] GTN 750.1 process is running as-admin
21/12/18 06:40:19.840 02008 ERROR] no device available for GTN 650.2

 

I have a screenshot of the situation also but not sure how I can attach it here. The 650 window loads fine but just does not power on so far.  Thank you.

 

Why did you post this message under an old topic that is marked (resolved)?  I highly recommend you open your own new topic with this.  Topics marked (resolved) get few new reads.

Edited December 18, 20214 yr by fppilot

Recommendation accepted, thank you.Answer on my side is because the topic is relevant, I am not particularly familiar with the protocols of this forum, and I did not wish to add a level of repetition which I know is sometimes frowned upon.  I will accept your comment as a courteous suggestion and I thank you.  Wiil do so. CEC

 Hi, I am having a problem in that I can not get the GTN 650 of the GTN 750/650 pair to power on .  I just purchased this and also have had the same problem for a couple of years with the GNS430 of the GNS 530/430 pair I have used up to now.  The 750 powers on just fine and looks fantastic; I just get no response from the 650 from XP Reality.

What is also peculiar to me is that some planes already have a 430 installed in them and I am able to get that unit powered on, just not the XP Reality version,which I would prefer.  So whatever my problem is, it spans both the 530 to 750 series: the main gps powers on and works fine, the secondary unit does not.  I have varied the power on sources for both the XP Reality 430 and 650 but it seems to make no difference.

Can anyone suggest what direction I should take here?  Thank you, CEC

21/12/18 06:24:31.103 02008 -    ] # rxpGtnSim32.dll version 2.5.28.6
21/12/18 06:24:31.102 02008 INFO ]
21/12/18 06:25:28.034 07676 INFO ] GTN 750.1 - TRAINER 6624
21/12/18 06:25:28.043 07676 WARN ] GTN 750.1 process is running as-admin
21/12/18 06:40:19.840 02008 ERROR] no device available for GTN 650.2

 

I have a screenshot of the situation also but not sure how I can attach it here. The 650 window loads fine but just does not power on so far.  Thank you.

 

On 12/17/2021 at 11:21 PM, cecarnicom said:

21/12/18 06:40:19.840 02008 ERROR] no device available for GTN 650.2

Are you using GTN 650.2 in the panel. cfg file?

Try 650.1.

Are you using GTN 650.2 in the panel. cfg file?

Try 650.1.

1 hour ago, Bert Pieke said:

Are you using GTN 650.2 in the panel. cfg file?

Try 650.1.

If he has the 750 running as 750.1 then he must use 650.2.  Two instances of RXP GTN gauges can be used, but one must be a .1 and the other a .2.

cecarnicom? What option do you have set for power source for the 650?  You can find the power source settings in the Configuration Menu.  Shift + right-click on the top edge of each GTN's bezel.  In some aircraft you may have to perform the Shift + right-click on the top of the bezel of the 2D GTN pop-up.   You can find more information starting on page 5 of the RXP GTN's User Manual.  You can find the User Manual in the Windows Start menu under R, Reality XP, User Manual.

13 minutes ago, fppilot said:

If he has the 750 running as 750.1 then he must use 650.2.  Two instances of RXP GTN gauges can be used, but one must be a .1 and the other a .2.

"You learn something new, every day.." 🙂

Bert, FPPilot,

Thank you very much for the replies.  I have many choices for the power source, and none of them seem to make any difference, although it is also true that I have not tried them all.  My catch all of Always On seems to me like it should cover all bases but I see no difference no matter what I use.  Like I say, the 750 and the 530 have both been fine and tops with no problem, the 650 and the 430 have the same symptom.  This has been going on for a couple of years now every since I have tried to use XP Reality and I am just getting by with the 750 and 530, but I actually need both.  I will include the power info and the panel.cfg file for your reviews, suggestions and leads.  Thank you very kindly, I hope this can be resolved now that I am finally bringing it to attention.  I think the 750 is a marvelous development and I wish to be able to take advantage of the full gauge complement.  I would include a screenshot but do not see that option yet.  CEC

 

Always On
Avionics On
General Panel On
Main Bus
Avionics Bus
Battery Bus
Hot Battery Bus
Gen Alt #1,#2,#3,#4

 

Spoiler

 

_____________________________________________________________________

//*********************************************************
// CARENADO P46350P MALIBU MIRAGE FSX/P3D
// Copyright © Carenado 2013 - All Rights Reserved
//*********************************************************

[Window Titles]
Window00=GPS 530

Window01 = Reality XP GNS Unit 1 (managed)
Window02=XGauge
Window03 = AI Radar
Window04=VoxATC////VoxATC
Window05=VoxATC Recent Comms////VoxATC
Window06=GPS 430
Window07=Reality XP GTN Unit 1 (managed)
Window08=Reality XP GTN Unit 2 (managed)

Window09=ENGINE SETUP
Window10=START
Window11=Toggle_Control
Window12=INFO

 

 

[VIEWS]
VIEW_FORWARD_DIR=-1.000, 0.000, 0.000

//--------------------------------------------------------
[Window00]
Background_color=0,0,0
size_mm=512,512
window_size_ratio=0.600  
position=3
visible=0
ident=0
window_size= 0.300, 0.388
window_pos= 0.530, 0.324
no_luminous=1
zorder=6

gauge00=GPS_530_3D_P46350P!gps_500,  0,0,512,512
gauge01=PA46350P!ToggleCAR530,  0,0,512,30

[Window01]
size_mm = 100,100
window_pos = 0.000000,0.000000
window_size = 0.358712,0.479195
visible = 1
always_visible = 0
zorder = 99
background_color = 0,0,0
ident = 15531
gauge00 = rxpGNS2!GNS_530_1, 0, 0,100,100

[Window02]
size_mm=253,190
position = 5
Visible = 0
ident = 14991
zorder = 100

gauge00=XGauge!WeatherMap,0,0,253,190

//--------------------------------------------------------
[Window03]
Background_color=16,16,16
size_mm=220,220
window_size=0.2  
position=1
visible=0
sizeable=1
ident=MISC_POPUP_1
window_size= 0.500, 0.500
window_pos= 0.000, 0.000

gauge00=AITX_Gauge_SE!AiTrackerRadarGauge,  0,0,220,220

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

[Window04]////VoxATC
visible=1////VoxATC
size_mm=400,200////VoxATC
window_size=0.3,0.3////VoxATC
window_pos=0.05,0.05////VoxATC
background_color=0,0,0////VoxATC
ident=14077////VoxATC
zorder=5////VoxATC
alpha_blend=0.65////VoxATC
gauge00=VAGauge!VoxATCPrompt,0,0////VoxATC

[Window05]////VoxATC
visible=0////VoxATC
size_mm=400,600////VoxATC
window_size=0.3,0.7////VoxATC
window_pos=0.65,0.05////VoxATC
background_color=255,255,255////VoxATC
ident=14078////VoxATC
zorder=5////VoxATC
gauge00=VAInfo!VoxATCInfo,0,0,400,600////VoxATC

 

 

 

 

 

 

 

 

//--------------------------------------------------------
[Window06]
Background_color=0,0,0
size_mm=524,310
window_size_ratio=0.600  
position=6
visible=0
ident=10010
window_size= 0.317, 0.244
window_pos= 0.525, 0.716
no_luminous=1
zorder=7

gauge00=GPS_430_3D_P46350P!GNS430_nc2,  0,0,528,310
gauge01=PA46350P!ToggleCAR430,  0,0,512,30

[Window07]
size_mm=100,100
window_pos=0.000000,0.000000
window_size=0.216146,0.384615
visible=1
always_visible=0
zorder=99
background_color=0,0,0
ident=15751
gauge00=rxpGTN!GTN_750_1, 0, 0,100,100

[Window08]
size_mm=100,100
window_pos=0.000000,0.384615
window_size=0.216146,0.170399
visible=1
always_visible=0
zorder=99
background_color=0,0,0
ident=15652
gauge00=rxpGTN!GTN_650_2, 0, 0,100,100

 

 

 

//--------------------------------------------------------
[Window11]
Background_color=0,0,0
size_mm=500,261
position=0
visible=0
ident=796
window_size= 0.200, 0.200
window_pos= 0.020, 0.160
zorder=5

gauge00=PA46350P!Control_windows,  0,0,500,261

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

gauge00=PA46350P!ToggleCARINFO,  10,10,400,100

//--------------------------------------------------------
[Window09]
Background_color=0,0,0
size_mm=600,653

window_size= 0.350, .500

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

gauge00=GAUGEP46350P!StartWindowsAircraft ,   0,  0, 600,653

//--------------------------------------------------------
[Window10]
Background_color=0,0,0
size_mm=600,653

window_size= 0.350, .500

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

gauge00=GAUGEP46350P!StartWindows ,   0,  0, 600,653

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

gauge00=GAUGEP46350P!Gauge_Volts_Amps,  7,521,318,279
gauge01=GAUGEP46350P!Gauge_Anum_L,  87,805,328,212
gauge02=GAUGEP46350P!Gauge_Button_Anum,  422,803,600,217
gauge03=GAUGEP46350P!Gauge_Clock,  332,518,279,279
gauge04=GAUGEP46350P!Gauge_ENGINE_DIG,  0,0,462,293
gauge05=PA46350P!GPSVSI,  0,0,2,2
gauge06=CarSoundPA46350P!CarSound,       0,    0,  1,   1

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

gauge00=WX_Gauge_3D_P46350P!WXGauge,  9,9,492,309
gauge01=GPS_530_3D_P46350P!gps_500,  7,337,493,358
gauge02=GAUGEP46350P!Radio_KR87_ADF,  524,670,496,100
gauge03=GPS_430_3D_P46350P!GNS430_nc2,  517,259,497,258
gauge04=DIGTTRANS_P46350P!transponder,  516,529,501,126
gauge05=Radio_P46350P!RadioAudio,  520,8,498,98
gauge06=GAUGEP46350P!Gauge_Anum_R,  381,786,635,229

gauge07=PA46350P!ToggleCAR530,      7,337,493,30
gauge08=PA46350P!ToggleCAR430,    517,259,497,30
//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_3

gauge00=GAUGEP46350P!Gauge_Autopiloto,  0,0,512,119
gauge01=GAUGEP46350P!Gauge_Anum,  0,120,384,177
gauge02=GAUGEP46350P!Gauge_Anum_APSEL,  0,299,384,174
gauge03=P46350P_Cabin_alt!C340_PRESS,  0,0,1,1

Day=255,255,255
Night=223,255,255
Luminous=246,115,119

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

 

 

 

 

Edited December 23, 20214 yr by RXP

9 hours ago, cecarnicom said:

I just purchased this and also have had the same problem for a couple of years with the GNS430 of the GNS 530/430 pair I have used up to now.

As a fellow user (I am not RXP support) I honestly do not know where to start here based on the panel.cfg file you pasted in above.  I see still active default Carenado GNS GPS gauges in [Window00],  [Window06] and [Vcockpit02]. I see an active RXP version 2 GNS gauge in [Window01], an active RXP GTN750 in [Window07] and an active RXP GTN650 in [Window08].

I see no reference to any RXP gauges, either GNS or GTN, in any [Vcockpit##] section.

Somehow you need for this aircraft model to simply start over from scratch.  Based on what I see I am astonished that you have any GPS gauges showing, either Carenado default or purchased RXP.  I

On 12/18/2021 at 2:21 AM, cecarnicom said:

21/12/18 06:40:19.840 02008 ERROR] no device available for GTN 650.2

Hi,

Did you actually purchase the GTN 650 product?

Edited December 23, 20214 yr by RXP

RXP,

Now I am thinking that is a very good question.  Since my installer added on to FSX SE allows me to create windows for each gauge (750/650) I have made an assumption that they are both available within a bundled package.  Maybe this is in error and I appreciate your question.  My order no. is 1530193 Dec 16 2021.  I suspect the 530/430 purchase is the same question.  I am guessing that you will now be able to clarify this issue now and/or answer the question you ask.  Thank you, CEC

Each of the 750, 650, 530 and 430 are separate products and separate purchases.

You'll find an individual download button on our website for each one!

RXP,

Thank you for this information.  It definitely clears up the confusion. 

My only suggestion I have so far, which I  suspect should be directed to Garmin vs RXP, is the limitation to 4 custom data fields; I do not see that being adequate in comparison to the way that the 530 managed that need.  Sub grouping or additional placement should have been possible.  Wind arrow was an unobtrusive addition on the 530, which gave the equivalent of 5 on the main screen, and then the second 530 nav screen had an additional 4, all of which were very useful. So it seems to me that Garmin reduced 9 to 4 unless I am missing something since it is new to me.  Adequate feedback now requires co-use of the 650 or 430 to get to the same level of info. Beyond that, I think great advances on all important fronts.

Merry Christmas, kudos for the 750, great RXP software development there.  CEC

 

Edited December 26, 20214 yr by cecarnicom

Thank you for your kind words!

Actually you can get additional user fields in the GTN devices if you're letting go the transponder and audio panel. They give way to new slots that you can customize IIRC. You might want to explore the different options and the other 7XX and/or 6XX models available.