The A2A Simulations Community

I recently installed the Mindstar Gns 430 into the A2A Comanche 250. I also updated the real Nav Data. When trying to do a LPV approach the GPS doesnt Identify the approach and only says App. also the LPV glide slope is in active. Not sure if this is a Mindstar problem or a just a tweek to the A2A comanche 250. If anyone has a idea I would love to hear about it.

I sent a email to mindstar and they said the GNS 430 was Waas ready.

thanks in advance
Paul

Did you activate the approach?

Andrew,
yes, approach was activated. Gps sequenced from FAF to first step down then final step down. Crossing DH GPS obs turned to Susp. Localizer was working but not the glide slope.

Flight phase window was APR

approached flown

KSNA John Wayne-orange county Santa Ana, California


RNAV (GPS) Y Rwy 20R

I tried the Mindstar GNS with the default Mindstar C 182. the Glideslope worked....

Now, I need to find out why the A2A Comanche glide slope isn't working with the Mindstar GPS 430.

you would think this should be a easy fix...

after flying LPV approaches using the Mindstar GNS 430 in a c-182, A2A Cherokee 180 and the A2A comanche 250. The only plane so far that the Glide slope does not work is in the Comanche 250. So, for some reason there is a glitch between the Mindstar GNS and the Comanche 250. I guessing its a programming error in the Comanche 250 software. so, if there are any techs that are following this feed..... any ideas now.

thanks in advance
Paul

Hello Paul,

we are just looking at your report now to see if we own the software to test (some team membrs PC's have changed since comanche release) this or if we need to contact Mindstar

thanks,
Lewis

thanks Lewis for looking into it...

Anything new regarding this since last year? I have same issue, have all 4 planes for P3D: 172, 182, Warrior and Comanche 250 all with Mindstar 430/530 integration, WAASENABLED and all settings correct. The Comanche is the only plane that does not show GS on LPV approaches. I also noticed, its the only plane using an HSI vs regular NAV1 gauge for the other 3 planes. Is there a fix for this by now? Are you guys working on this?

Michel.

Sorry it took so long, I've found the issue and we're working on it atm.

Mike, any idea on the timing of a fix (ATM) for this problem?

Hello,

any update on this issue?

I am also impatient for a fix

Not that I wish to interrupt the siesta going on here but I have to ask: Is there a reason why support inquiries take forever to be addressed? We started this thread back in 2015, I chimed in a year later, this is now 2017 and still nothing on the table. It would really be helpful if solutions to known problems could be addressed in a reasonable time frame and posted so we can enjoy the amazing planes to their fullest.

Michel.

I would also point out that the CDI needle is not switching to approach mode when using the LNAV or LPV approach. Needle deviation sensitivity stays on enroute value.

Thank you very much for the fix.
I just had time to try only one Gnss approach so far and it worked nicely.

This message is for Olivier Moens actually.

I saw your reply that the problem with the HSI and Mindstar 530 is solved but I don't see the solution! Can you share the "secret" with me?

Regards, Caesar