Jump to content

Sign in to follow this  
herrkaleu

Very disapointed. GNS430/530 issue

Recommended Posts

 Hi everyone

 

i recently bought p3d v2.5 and minstar gns 430/530

 

the problem is that the aircraft doesn't follow the route which I entered.

as well as i want to fly a direct to.

 

dtk value shows the heading to the waypoint. and trk value shows actually 000° and the aircraft fly hdg 000.

 

shouldn't the aircraft follow the desired track DTK??

 

what did i do wrong?

 

can u help me.

 

p3d v2.5 and A2A C182 as well as the Carenado King Air B200.

 

best regards

 

Rico

Share this post


Link to post

Do you know how to use a 430/530 or is this all new for you?

 

Your thread title is incorrect, the 430/530 do in fact work.


Ed Wilson

Mindstar Aviation
My Playland - I69

Share this post


Link to post

Yes i know how it works. Had used rxp for about 1 year.

 

And i would be happy if gns will work for me too.

Share this post


Link to post

I'm willing to bet you have VLOC as the active CDI and not GPS.


Ed Wilson

Mindstar Aviation
My Playland - I69

Share this post


Link to post

Hi.

 

I have of course selected GPS. I switch back to NAV and GPS sometimes. In the GNS is displayed GPS as well as in the NAV GPS Indicator in the aircraft.

Share this post


Link to post

Then you have something else interfering with the operation of the GNS unit.

 

Post your panel.cfg contents here.


Ed Wilson

Mindstar Aviation
My Playland - I69

Share this post


Link to post

Ok.

 

this is now the panel cfg. of the A2A C182.

// Mindstar430
[Window Titles]
Window00=Main panel
Window01=Clipboard
Window02=Mini controls
Window03=Payload and fuel manager
Window04=Map
Window05=Quick radios
Window06=Maintenance hangar
Window07=Pre-flight inspection
Window08=AFK
Window09=none2    
Window10=dbg
Window11=none3
Window12=none4
Window13=GNS 430 WAAS

[VIEWS]
VIEW_FORWARD_WINDOWS=10,20,RADIO_STACK_PANEL,FUEL_PANEL,40,50,51,52,53,54,100,101,102,103,104,105

//--------------------------------------------------------
[Window00]
Background_color=0,0,0 
size_mm=1024,768
position=1
visible=0
ident=10

//gauge00=tester!tester, 420, 50, 400, 1000         //Comment for release

[Window01]
Background_color=0,0,0 
size_mm=322,615
pixel_size=322,615
window_pos= 0.0, 0.2      
position=0
visible=0
ident=20
sizable=0

gauge00=A2A_C182!clipboard,  1,0,322,615

[Window02]
Background_color=0,0,0 
size_mm=392,315
pixel_size=392,315
window_pos= 0.51, 0.2      
position=0
visible=0
ident=RADIO_STACK_PANEL
sizable=0

gauge00=A2A_C182!controls,   1,0,392,315

[Window03]
Background_color=0,0,0 
size_mm=649,689
pixel_size=649,689
window_pos= 0.51, 0.2      
position=1
visible=1
ident=FUEL_PANEL
sizable=0

gauge00=A2A_C182!manager,  1,0,649,689


[Window04]
Background_color=0,0,0 
size_mm=1024,768
pixel_size=1024,768
window_pos= 0.000, 0.2
position=0
visible=1
ident=40
sizable=0

gauge00=A2A_C182!mapscreen,  255,1,770,766
gauge01=A2A_C182!map_settings,  1,50,246,232

[Window05]
Background_color=0,0,0 
size_mm=187,392
pixel_size=187,392
position=6
window_pos= 0.025, 0.9
visible=1
ident=50
sizable=0

gauge00=A2A_C182!radios,  1,0,


[Window06]
Background_color=0,0,0 
size_mm=1024,768
pixel_size=1024,768
window_pos= 0.000, 0.2
position=0
visible=0
ident=51
sizable=0

gauge00=A2A_C182!maint_hangar,  1,0,1024,768


[Window07]
Background_color=0,0,0 
size_mm=1024,768
pixel_size=1024,768
window_pos= 0.000, 0.2
position=0
visible=0
ident=53
sizable=0
nomenu=1
type=special

gauge00=A2A_C182!walkaround,  0,0,1024,768


[Window08]
Background_color=0,0,0 
size_mm=321,321
pixel_size=321,321
position=5
visible=1
ident=54
sizable=0

gauge00=A2A_C182!afk,  1,1,321,321


[Window09]
Background_color=0,0,0 
ident=100
nomenu=1
type=special

gauge00=A2A_C182!keys,  1,1,1,1
//gauge01=A2A_C182!cockpitBuilder, 2,2,2,2 //For cockpit builders only.

[Window10]
Background_color=0,0,0 
size_mm=330,450
pixel_size=330,450
position=5
visible=0
nomenu=1
ident=101
sizable=0

//gauge00=dbg!panel,  144,0             //Comment for release

[Window11]
Background_color=1,1,1 
ident=102
window_size=1.000,1.000
nomenu=1
zorder=100

gauge00=A2A_C182!blackout,  0,0

[Window12]
Background_color=0,0,0 
size_mm=650,624
pixel_size=650,624
position=3
visible=0
ident=103
nomenu=1
zorder=99

gauge00=A2A_C182!engine_details,  1,1,650,624

[Window13]
window_pos=0.739583,0.000000
window_size=0.260417,0.194444
visible=0
ident=15431
nomenu=0
zorder=99

// This is a popup GNS 430, GPS #1, instance #2, ident 15431 (from ident= line above)
gauge00=MPI_GNS!GNS430,0,0,100,100,1:2:15431	

//--------------------------------------------------------
[Vcockpit00]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$reticle

gauge01=A2A_C182!code_c182t_r, 1,1,1,1
gauge02=A2A_C182!status1,2,2,2,2
gauge03=A2A_C182!damage,	3,3,3,3
gauge04=accusim_xml!code_s,	4,4,4,4
gauge05=A2A_Accusim!lua,	5,5,5,5
gauge06=A2A_Accusim!AVS,	6,6,6,6
gauge07=A2A_Accusim!events,	7,7,7,7
gauge08=A2A_Accusim!random,	8,8,8,8
gauge09=A2A_Accusim!storage,	9,9,9,9
gauge10=A2A_C182!code_c182t_m, 1,1,1,1
//gauge11=gps!gps_500,	0,0,1065,675
gauge11=C182!avionics, 0, 576, 1024,447
gauge12=A2A_C182!annunciator, 1, 454, 854,120
gauge13=A2A_C182!number, 794, 0, 228,77
gauge14=A2A_C182!aoa_indexer, 993, 79, 29, 58
gauge15=A2A_C182!GPS_MINDSTAR_430, 1, 1, 1, 1

[Vcockpit01]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$reticle1

gauge00=C182!lightmap, 0, 576, 1024,447

[Vcockpit02]
Background_color=0,0,0 
size_mm=512,512
visible=1
pixel_size=640,640
texture=$gps

// This is a virtual cockpit GNS 530.  I think the 530 is GPS #1, we can fix that
// if I'm wrong.    GPS #1, instance #1 (because the VC must always be instance #1), and 
// since the VC has no ident= line, we use -1 for the ident.

gauge00=MPI_GNS!GNS430, 0,0,512,216,1:1:-1

[Vcockpit03]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c1_l

gauge00=C182_Illumination!c1, 0, 0, 1024, 1024

[Vcockpit04]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c2_l

gauge00=C182_Illumination!c2, 0, 0, 1024, 1024

[Vcockpit05]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c5_l

gauge00=C182_Illumination!c5, 0, 0, 1024, 1024

[Vcockpit06]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c7_l

gauge00=C182_Illumination!c7, 0, 0, 1024, 1024

[Vcockpit07]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c9_l

gauge00=C182_Illumination!c9, 0, 0, 1024, 1024

[Vcockpit08]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$vc_gxml_l

gauge00=C182_Illumination!vc_gxml, 0, 0, 1024, 1024

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



Share this post


Link to post

Ok, looking at your panel.cfg shows nothing odd there.

 

At this point I'm going to have to suggest you ask A2A about it, because the actual autopilot is theirs and not ours. I am, of course, assuming you have their very latest version installed.


Ed Wilson

Mindstar Aviation
My Playland - I69

Share this post


Link to post

Okay. But the problem is still within the carenado b200. I will remove both aircraft and mindstar and reinstall again. Maybe tomorrow and i will tell what happens.

 

Thanks for your help so long.

Share this post


Link to post

I can not assist with Carenado. They don't like to work with third-party avionics. They have been asked many times to support the G1000, as example, and have repeatedly refused to do so.


Ed Wilson

Mindstar Aviation
My Playland - I69

Share this post


Link to post

But this wasn't told on the mindstar website. it was pronounced to operate with any aircraft.

at the moment i am still in touch with the support team. no succes at the moment. tried to use it in the standard Maule in p3d. no succes.

 

i'll keep you informed.

Share this post


Link to post

Just to be clear, at the risk of telling the OP what he already knows:

 

Several conditions need to exist before your autopilot will follow a gns route:

1. You need to have NAV selected on the AP

2. On the gns, you need to have GPS selected on the CDI button (not VLOC).

3. And you need to have a route loaded in the gns, or a direct-to, or something that the gps can point to.

 

If you try and manually fly the route, do you get the expected response on the NAV 1 cdi? That is, is this an ap issue or a gps/nav issue?

 

Thanks, Bruce.


ASEL, Instrument.

KBJC, Colorado.

Share this post


Link to post

Hi

 

 

 


Several conditions need to exist before your autopilot will follow a gns route:
1. You need to have NAV selected on the AP
2. On the gns, you need to have GPS selected on the CDI button (not VLOC).
3. And you need to have a route loaded in the gns, or a direct-to, or something that the gps can point to.
 

 

these conditions were all given

 

 

So, here are some updates.

 

i testet the gns now on an fsx installation. same issue.

 

then decided to make a clean and fresh windows and fsx environment. and what happend? it works.

Now i will create my flightsim system new. clean windows and a clean p3d. but now i got the problem that my activations are exeeded. Now i have to look what i can do. i asked the support if there is any problem of reinstalling. but he said there is no problem. but now i have no activations left.

 

so i am trying now to figure out if the gns will work within my new installation of p3d.

 

so long

Rico

Share this post


Link to post

Tell support you have run out of activations... they'll correct it.


Ed Wilson

Mindstar Aviation
My Playland - I69

Share this post


Link to post

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  
×
×
  • Create New...