> Why then setting the LAT that's shown by INS but not true one?
(text actually modified but not altering the actual question)
> e.g N51.20.7 becomes like N53.26.4
Not sure 100% but you may be "falling" in one of the many "traps" we have implemented in the FS gauge, trying to, but of course, not even near to, simulating the behavior of the real unit when wrongly managed.
If this is true then the INS gauge is probably taking the error accumulated in the last flight (if any, of course), plus the wrongly/partially entered present position error, and applying all these "wrong" inputs to the last known reliable position (if any, of course, otherwise it estimates it applying, to the position reported by FS displaced by a random lat/long offset [as FS reported position is EXTREMELY precise, something not compatible with an "ancient" navigation system]), and I believe what you're saying could be compatible with such condition.
Again I'm not 100% sure of what I'm saying and it would take me several hours to check source code to confirm (and I have no such time, sorry). But since CIVA is widely used and such serious bug would have been already reported and fixed several years ago, I'd more easily believe you're following the alignment procedure in the correct way. No problem with this, a LOT of users had problems getting it aligned and "ready to go", so simply report here in the forum where you are (I mean where the aircraft is standing STILL, lat/long) and the exact sequence of keys you're using to enter the Present Position into the INS, this will very probably let us understand more.
> and POS is wrong error.
Could you also kindly let us know exactly which Action and Malfunction Codes are you dealing with? Any chance they're 06-41 which in fact is only a WARNing and could be easily "cleared" by pressing TEST twice?
Marco
(edited to correct spelling errors but I'm sure many were left behind...