That is normally due to the fact that the present position has not been entered correctly or at all.
When entering the present position do not press the INSERT key twice after latitude, press it just ONCE, then enter longitude, press it again, and the INSERT light will extinguish.

No warning light, and the LAT/LON are entered correctly, and are reading correctly in the display. I have gone through this multiple times with the same result. The alignment will continue until the accuracy reads 6, then it stops. I haven't been able to try it at another airport yet to see if it's just Bermuda or the scenery I have for there that's the issue or if it's something else.

> For installations to multiple aircraft do you put the gauge in each aircraft's folder, then reference that in
> the panel.cfg? Or should you just leave the one gauge file and reset your PPOS each time?

Keep the gauge file where it is, it cannot be moved elsewhere.
But you could use the fifth parameter of the INS!config gauge to have different .ISD files (where the ins saves its data) for different aircrafts. See PanelIntegrationManual.pdf, Configuration Files chapter.

> civa 1.50 build 1117

Version 1.50 is build #2242, what's 1117?

Could you please provide us the exact lat/long the plane is parked at, plus the exact keys sequence you type in the CDU to "program" the present position?

Also note that deleting the .ISD file does not bring any advantage, only disadvantages.

Marco

Hello again..
Well Marco and everybody, I have just finished a nine waypoint flight,on the 734 fs9, from Seattle rwy 34,landing 16.WITH NO PROBLEMS as far as the INS alighnment,and the rest of the operation.
The secret Marco and everybody,is the dumn INSERT key!!!(you had mentioned that Marco
I was pressing it only ONCE!! ,never mind if the light was still on after pressing,I ignored it,and kept inserting the data,using the remote,and there was no problem.
At time 13:06 (Athens lt) after the threshold position rwy 34 KSEA was entered
(engines runing parking brake on) at 13:13 reached sts 6 and at 13:20 sts 5
and ready nav lt came on...
After landing I checked the accuracy (dist/time) and both showed 1 nm to the present pos.(3 hrs flt) not bad ...
Thank you
All the best
Ioannis

hi,
the ramp position LAT and LONG are part of a UNIQUE insertion entry.
Unlike waypoint insertion,where it's possible to change only LAT or LONG and after LAT or LONG insertion you can notice the INSERT light going OFF,If something goes wrong in any part of ramp LAT and /or LONG insertion the complete insertion must be carryied out again starting from the beginning.
That's the why the INSERT Light doesn't go off after the LAT insertion but you have to insert both LAT and LONG to obtain the INSERT light extinguished.
About the Alignment stop at API 6 this isn't an issue but the normal INS behaviour.
It's due to a Ramp position not inserted or not accepted by the INS because wrongly made or for a pending ACTION&MALFUNCTION code.
As written on the Operation manual you can first switch the MSU selector to ALIGN or NAV and before or at API6 insert the ramp position,because till API 6 the INS doesn't need to know the ramp position.
Pushing twice the INSERT button after LAT insertion is considered a wrongly made insertion and moreover cannot be recognized because,as said above, the INSERT light remains on until the LONG will be inserted.
When you have this alignment stop at API6 make this little ck list:
1-With Data selector on DSRTK/STS ck ACTION&MALFUNCTION codes and eventually clear it by TEST button pushing.
2-Reinsert the complete ramp position paying attention to push once the INSERT button after the LAT insertion.
Hoping this helps Gianfranco

Hi,

I'm using the CIVA with the Dreamfleet 727. I had also problems with the alignment of  the INS. There always apeared the ACTION&MALFUNCTION codes:

02-63 Randomly failure and

04-57 Taxi during alignment
(Although the parking-brake was set and the throttle on idle.)

I have found out, that the best way to keep away ACTION&MALFUNCTION codes, is to initiate the alignment only with running the APU (before starting engines) . After finish of the alingment, I start the engines and now everything works well.  

Best regards !
Dietmar

Hi Vic,

I am very surprised, that the aircraft is crrawling with throttle on idle even with parking brakes set. But it is very important to know that. So this explains the behavior of CIVA very well, and this to know bewares us of fustrated waiting of failed alingment.

Thanks for Your reply !
      Dietmar