Operation

[deltafan 1]

Hey guys, I am having serious issues with the 737. After INS alignment, I click the switch to NAV, and over the next few minutes, the API number that still displays rises past 5-6-7-8 then to 9, leading me to believe that my INS isn't accurate. What's the issue here? I had no action codes throughout the process.Also, when airborne I can't get the A/P to track the INS course. I don't know if this is because the INS is inaccurate or because I'm doing something wrong. I put both the F/D and A/P to VOR LOC and botht he AIL and ELEV paddles in the on position. What is going wrong?Thanks in advance for the help.

[Bob Scott 7,712]

With the CIVA v1.40, you need to initially cycle the MSU switches from off, to STBY, back to off, then to stby or align again, to get around an expired version date coded into the gauge. Also, make sure you don't have the red BAT light on the MSU, which will occur if the INUs lose power. And the align must occur with the parking brake set...if the acft moves during align, it might cause something like this.Please read the TinMouse II readme.doc that came with the original download...in the version 1.0 note section, para 3 it describes how to set up the INS to drive the A/P.RegardsBob ScottATP IMEL Gulfstream II-III-IV-VSantiago de Chile

[strider 0]

I still have a quickly degrading API, even after the on-off-on trick and a complete alignment with no errors. I just ignore the API and the INS seems to fly the aircraft just fine. I have the same problem with a triple unit on the CS 707...with the same workaround...ignore the API as long as you are hitting your waypoints.