Hello again - sorry!

 

Following your swift and excellent support to get my GNS re-activated for prepar3d, I can't for the life of me get the Carenado c208 AP to follow the GNS in NAV mode.

I've installed the GNS into the panel.cfg following your example from the website. Panel.cfg inserted here.

 

Both the 530 and 430 are set to GPS via the CDI button, and the NAV flag appear on the VOR 1 and 2 in the Caravan. Also the NAV/GPS switch in the Caravan responds to the CDI button on the GNS.

 

Even if I position the A/C on the route using HDG mode, and press NAV on the AP, the A/C wonders off in any given direction (can't find a pattern), and continues straight ahead in that direction.

 

I've tried several different routes and airports, but same result. My setup is as follows:

 

Sitting on, say, ENAL, I let the GNS start up. I go to FPL and enter ENML on the next vacant spot in the active FPL. On the MAP page I can see the route, and the LEG is active. In air I've tried DCTs and activating the LEG again, but no luck...

 

It's like something else than the Mindstar GNS in driving the AP NAV mode - could it be the default GPS? - how can I cut that thing out?

 

 

Any suggestions?

 

Last time I had the GNS installed in the Duke, everything worked perfectly, but of course that was in p3d v2.3, if that's of any importance...

 

I also experience some anomalies, like when selecting DCTs, and procedures, and loading a LEG to be active, the page with the confirmation "load active LEG or X/Y leg/procedure" just hangs. I can see on the 430 that the changes take place immediately and I just have to press FPL or CLR on the 530 to return the MAP or FPL page, and the changes are in effect.

 

Any suggestions?

 

PANEL.CFG:

//*********************************************************
// CARENADO C208B GRAND CARAVAN
// Copyright © Carenado 2010 - All Rights Reserved
//*********************************************************

[Window Titles]
Window00=GPS
Window01=Manual
Window02=Control Windows
Window03=Exit Manager
Window04=Info
Window05=FCDU




//--------------------------------------------------------
[Window00]
size_mm=456,520
window_size=0.5
position=8
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident=GPS_PANEL

gauge00=MPI_GNS!GNS530, 0, 0, 456, 331, 1:1:225
gauge01=MPI_GNS!GNS430, 0, 331, 456, 189, 2:1:225


//--------------------------------------------------------
[Window01]
Background_color=0,0,0
size_mm=700,814
window_size_ratio=1.000 
position=0
visible=0
ident=793
window_size= 0.380, 0.589
window_pos= 0.620, 0.160

gauge00=C208Manual!manual,  0,0,700,814


//--------------------------------------------------------
[Window02]
Background_color=0,0,0
size_mm=851,453
window_size_ratio=1.000 
position=0
visible=0
ident=796
window_size= 0.480, 0.341
window_pos= 0.010, 0.410
zorder=0

gauge00=GCCB!Control_windows,  0,0,851,453


//--------------------------------------------------------
[Window03]
Background_color=0,0,0
size_mm=351,456
window_size_ratio=1.000 
position=0
visible=0
ident=60
window_size= 0.190, 0.329
window_pos= 0.010, 0.070

gauge00=GCCB!Doors,  0,0,351,456


//--------------------------------------------------------
[Window04]
file=info.bmp
size_mm=555,139
window_size_ratio=1.000 
position=0
visible=1
ident=142
window_size= 0.290, 0.097
window_pos= 0.350, 0.020




[Window05]
size_mm=93,216
position=8
visible=0
ident=24477
gauge00=FCDU!ACARS,1,1,93,216

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

gauge00=GCCB!Airspeed,  2,4,164,164
gauge01=GCCB!Attitude,  170,4,164,164
gauge02=GCCB!Altimeter,  341,3,164,164
gauge03=GCCB!rmi,  1,174,165,165
gauge04=GCCB!Horizontal Situation Indicator,  169,173,168,168
gauge05=GCCB!Vertical_speed,  340,173,167,167
gauge06=GCCB!vor2,  1,343,164,164
gauge07=GCCB!Turn_Coordinator,  169,343,162,166
gauge08=GCCB!DME_screen,  333,351,176,68
gauge09=GCCB!Panel_annunciator,  333,428,175,65


gauge10=FCDU!FDR,1,1,1,1

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

gauge00=GCCB!Airspeed2,  10,3,165,165
gauge01=GCCB!Attitude2,  182,3,155,164
gauge02=GCCB!Altimeter2,  345,2,164,164
gauge03=GCCB!Turn_Coordinator2,  5,172,171,170
gauge04=GCCB!Directional_Gyro,  179,173,162,162
gauge05=GCCB!Vertical_speed2,  344,172,167,167
gauge06=GCCB!clock,  205,408,99,99
gauge07=GCCB!suction,  104,408,99,99
gauge08=GCCB!voltamp,  3,407,99,99
gauge09=GCCB!Annunciator_Panel,  3,344,362,53
gauge10=GCCB!fuelflow,  307,407,100,100
gauge11=GCCB!Fuel_Quantity_Left,  410,408,100,100
gauge12=GCCB!vs,  371,343,136,60


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

gauge00=GCCB!torque,  289,228,112,112
gauge01=GCCB!prop_rpm,  289,116,108,108
gauge02=GCCB!itt,  288,2,109,109
gauge03=GCCB!ng,  401,116,106,106
gauge04=GCCB!psi_oil,  399,2,110,110
gauge05=CarenadoG430!GNS430_nc1,  2,161,282,150
gauge06=GCCB!Radios2,  2,64,284,95
gauge07=GCCB1!RadioAdf,  2,382,270,67
gauge08=GCCB1!RadioTrans,  2,313,276,67
gauge09=GCCB!Autopilot,  2,2,280,60
gauge10=GCCB!AOM,  1,450,272,59
gauge11=GCCB!AOM_Lights,  274,466,207,42
gauge12=GCCB!anti_ice_amps,  289,342,69,68
gauge13=GCCB!Fuel_Quantity_Right,  404,229,104,104
gauge14=GCCB!ng,  406,  344 ,100,100
gauge15=GCCB!Hours,  288,413,82,50
gauge16=GCCB!Toggle_GPS,  63,181,157,93


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

gauge00=GCCB!Oxygen,  115,3,110,109
gauge01=GCCB!compass,  228,3,85,54
gauge02=GCCB!temp,  3,3,109,109
gauge03=GCCB!RadarAltitude,  3,116,146,146
gauge04=GCCB!Annunciator_Test,  317,3,54,54
gauge05=WX_Gauge!WXGauge,  154,116,356
gauge06=GCCB!atc,  375,3,54,54
gauge07=GCCB!Drag,  60,60,0




Day=255,255,255
Night=255,255,255
Luminous=255,255,255

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

 

 

Gauge03 in [vcockpit03] is a GNS430 from Carenado.

 

Also, what is an FCDU ACARS? Cuz that sounds like a Flight Control Display Unit...

Arh - I see, and should I comment that out?

Edit: did you mean to write gauge 5?

 

The FCDU is facaptain, but that should not try to drive anything...

 

Thx

 

Mas

Sorry, yes... meant #5... It shouldn't be there if you're going to use our GNS units.

 

I don't own this addon, so my assistance isn't going to be me loading it up... I'll apologize for that up front.

Don't apologize - that's fair enough. I disabled the default entry, but to no success.. I'll try a re-install, and if that doesn't do anything I'll try and contact Carenado...

 

Regarding the other anomalies - do you think they could be because Carenado is interfering or could it be related to a bad install..?

 

Mas

An update - re-installed, and gauge 5 still commented out.

 

Starting up at ENAL rwy 07, programming DCT ENKB. After TO same problem - pressing NAV on the AP, and the A/C wonders off. When't into the p3d flightplanner, and quickly activated a DCT gps route ENAL-ENKB, and pressing NAV now made the A/C steer towards ENKB - don't know if that can be a lue as to what is confilcting with the Mindstar?

 

Mas

Ok, I've purchased said aircraft and done some testing.

 

I was able to replace the 430 in the panel.cfg with our 430 unit and get the autopilot to follow the GPS course.

 

So... based on that, I'll state it's indeed possible to get the Caravan to work with our units. Carenado really hates 3rd party avionics... a lot. I assume this to be true because they refuse to support 3rd party avionics.

 

However... doesn't mean I can't sort through all of this.

 

First and foremost... their aircraft is designed for a single GPS unit, a Garmin 430. There is nowhere in the VC to put any other unit. So... based on that... your install needs to be a wee bit different.

 

The first thing I did was modify the aircraft.cfg so that I had a unique aircraft for our avionics:

 

[fltsim.6]
title=C208B Grand Caravan Mindstar
sim=C208B
model=
panel=ms
sound=
texture=Blue executive
kb_checklists=C208B_CHECK
kb_reference=C208B_REF
atc_id=N6909T
ui_manufacturer="Carenado"
ui_type="C208B Grand Caravan"
ui_typerole="Single Engine TurboProp"
ui_createdby="Carenado"
ui_variation="Mindstar"
description="xxx"
atc_heavy=0
atc_airline=
atc_flight_number=
atc_id_color=0000000000
visual_damage=1

Then I created a new folder in the "Carenado C208B Grand Caravan" called "panel.ms". Then I copied all the files from the "panel" folder to the "panel.ms" folder.

 

I then modified the panel.cfg file in the "panel.ms" folder as follows:

 

[Window00]
Background_color=0,0,0 
size_mm=1040,1187
window_size_ratio=1.000  
position=0
visible=0
ident=11013
window_size= 0.350, 0.533
window_pos= 0.010, 0.460
zorder=0

gauge00=MPI_GNS!GNS430,  0,0,1040,431,1:2:11013
gauge01=MPI_GNS!GNS530,  0,432,1040,,2:1:11013

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

gauge00=GCCB!torque,  289,228,112,112
gauge01=GCCB!prop_rpm,  289,116,108,108
gauge02=GCCB!itt,  288,2,109,109
gauge03=GCCB!ng,  401,116,106,106
gauge04=GCCB!psi_oil,  399,2,110,110
gauge05=MPI_GNS!GNS430,  2,161,282,150,1:1:-1
gauge06=GCCB!Radios2,  2,64,284,95
gauge07=GCCB1!RadioAdf,  2,382,270,67
gauge08=GCCB1!RadioTrans,  2,313,276,67
gauge09=GCCB!Autopilot,  2,2,280,60
gauge10=GCCB!AOM,  1,450,272,59
gauge11=GCCB!AOM_Lights,  274,466,207,42
gauge12=GCCB!anti_ice_amps,  289,342,69,68
gauge13=GCCB!Fuel_Quantity_Right,  404,229,104,104
gauge14=GCCB!ng,  406,  344 ,100,100
gauge15=GCCB!Hours,  288,413,82,50

See if that helps.

Wow! Support above and beyond everything - will try this out tonight! Many thanks!

 

Mas

Ok, things didn't go as smooth as I'd hoped. And let me say that I'm kinda emberassed to bother you again, because this is most likely a carenado issue, as you've stated, so I deeply appreciate any time you may devote to this..

 

I followed your instructions, and everything appear good - I select the Mindstar caravan. I see the pop-up with the 430 on top and the 530 below. I see the 430 where the default used to be. I can setup a flight, but damn it, when I press that NAV button, the A/C flies straight North..

 

I'm so frustrated now that I'm thinking I'm operating the unit in some wrong way...

 

I also reinstalled the caravan, but same result...

 

Sigh... If you guys have anything more up your sleeve, I'll be happy to try it out... Otherwise I'll be happy to take a good advise on some other similar aircraft that can handle the Mindstar;-)

 

Mas

Ok...

 

1 - You've entered a flight plan into the 430?

2 - The 430 shows the CDI in GPS mode?

3 - The NAV flag is not visible on the HSI?

1. yes

2. yes

3. YES it is - sorry that I've missed that initially - I had it backwards (embaressed!!)

 

I have taken some screenshots just to see if you can spot anything important:

Each shot should have a description/explanation - http://s354.photobucket.com/user/mas618/library/Mindstar%20vs%20Caravan

 

Mas

Ok... with the 430 (it's the primary GPS) set in GPS mode and a flight plan entered... the NAV flag should not be visible in the HSI. The fact that it is visible tells me something is interfering with control of the GPS DRIVES NAV1 capability of the sim.

 

While you are trying to work through this I'm seeing a lack of basic understanding regarding GNS settings. The primary GPS (the 430) is the one the HSI is connected to. The secondary GPS (the 530) it doesn't know exists. To get the autopilot to track the GPS (the 430), the mode on the GPS should indicate GPS and not VLOC. VLOC tells the HSI to track whatever signal is coming from the NAV1 radio.

 

Out of curiosity, once you've entered your flight plan... close the popup and see if the NAV flag goes away when the 430 is in GPS mode. If that doesn't change anything... then you have something not quite right with your Caravan.

Whaaaaaatt....!? Ok - this is wierd - in a good way!

 

Sorry about the cock-up on the CDI issue - I did know that it should be in GPS mode to track - I was just switching VLOC/NAV mode on both units to see if it did anything...

 

But - it works now, and the only difference, was that because of all the testing, I saved a flight with the caravan sitting on 07 in ENAL, with all avionics off - including battery and everything. This way, I wanted to make sure that I started everything up correctly, and also to see if having the GNS start up from completely off would do anything. And guess what, it did... Why and how - beats me... Now selecting GPS on the CDI and putting A/C in NAV mode will have it track the route, while going to VLOC will have it chasing the VOR 1 radial... SWEEEET!

 

But whats more sweet is your support - I thank you for that, I find it superb, and will let anyone who asks know it!

 

Thanks again

 

Mas

Sounds like you were using a saved flight all this time? I was not, which would indicate there was something wrong with your saved flight settings??

 

As for our support... please don't spread wild rumors... we already have a reputation in these forums of being an evil mega-corporation simply because we use our own navigational data.

 

Enjoy your flying and have a wonderful holiday season.

In fact I was - with the aerosoft Airbus and their panel state loaded... Could be that was the culprit..

 

And I will try to spread roumers, even though I know how dangerous it can be to mess with peoples hard-coded beliefs... I was a witness to that cirkusshow when you guys introduced realnav, and the fact that you are still here in this community shows enough in my book...

 

You enjoy the holidays as well!

 

Greeting

 

Mas