Don't worry, those last coordinates shown are normal. These are saved in that .isd file inside the "Civa" folder, like all previous states of the device.
The "autofill" seems to arise if you enter the coordinates in the wrong format, because FSX often doesn't show a "0" (zero) where you have to enter one in the CDU.
So please check your inputs again or give me screenshot with the FSX coordinates and your input on the Civa and I might tell you what was entered wrong in that special case. 
Maybe this helps too. http://forum.avsim.net/topic/326447-civa-ins-issue/page__view__findpost__p__1925...

Glad to hear it works now.

I haven't really tried the deviation when losing the alignment yet, but in another thread we came to the conclusion that, from the numbers, you really lose it fast.
So I would recommend setting up the first DME update process just before starting the engines, so you will get a DME update on the first few miles of the flight where your workload is higher. Later, you can tune in the next station while already being in cruise or closer to it.
Over the ocean, you can't align and so you will lose the accuracy until getting in range of a high alt DME station. Should be around 200nm out from every coast, so enough time to be accurate over land then.

Maybe Lou can tell in more detail how they coped with the lost alignment. I don't think that they flew back to the departure airport then.  
I would shout at the Flight Engineer or so, "that's why you are second officer only!, now I have to fix this".

I'm quoting myself (from p.1, in the Civa integration tutorial).  
Quote:

That Doppler/INS switch is an important one. Saying this because I often forgot it.  

Hey, guys, 1.3 is there, so I'll have to check if the tutorial is still valid and I'll also add instructions for the expansion models. I will mark it as "1.3 ready" later.

Edited:

I used the 1.2 values on a 1.3 install and despite my flub up with the external power things seem to work fine. Are there changes in your civa config that I should update then?

asanal wrote on Mar 6^th, 2011 at 3:32am:

I would love to Sanal.

BUT......I messed up bad. My weather radar, and some other gauges in the VC went missing. I have just run a repair on the 707-300 Base Pack. I'm not sure what I did, but I had a bunch of modified panel.cfg's from v1.2 in the panel folder and I obviously got confused and deleted a newer file and continued editing an older file. I don't stuff up like that very often, but I sure messed this one up good and proper. I have no real idea how or what I really did to set the mistake in motion. All I can say is that you are lucky you never heard my response (the army taught me some very nasty words)! It had my boys looking rather surprised at the commotion I was making.

I had actually posted it in here, but had to delete it because it was really a crazy mess (I hope no one saw and tried to copy it). I can redo it in a while and I'll get it up here soon. Hopefully.

Mark

Edited:

I'm sorry, guys, I don't get the point here.
Is there something wrong with my tutorial (which was updated to 1.3 and the expansions lately) or are you describing something else?  

For the guys who had the 1.2 version of the tutorial before, there aren't big changes, only the AP popup window (which is [Window04]) had been given a "save" gauge entry to make it work for all variants.
If you just use the 707 passenger model, you don't need to change it and therefore can leave out the 1.3 update.
If you are using the variants like Cargo, E-3 or Air Force One, you have to use the new 1.3-aware entry of course.


Mark, to avoid confusion, I suggest to "mark"   your Civa integration more clearly as e. g. "Single Unit integration" or so.
Otherwise a new customer or visitor stumbles upon this thread and gets all kinds of config entries, mixing them up and also (and most of all) asking questions about it, while we don't know to which edit he's referring to.

So I might accidentally answer some question the wrong way since I don't know what thing the guy is using.

Edited:



I have another suggestion, but this needs some approval from CS of course.
We could offer the complete panel.cfg file for each model. To download and to just drop into the corresponding folder.
I've avoided this for copyright reasons, but if it get's approved, I could attach all four (=all variants covered) panel.cfg files for the guys.
They would just have to backup their original stuff first while avoiding any error source there is. I would just have to make sure that those files are always updated to the current 707 build.
So currently, you would find a "1.3 panel.cfg package for Civa Double INS Integration" there.
What do you think?

So under Mark's solution there would be such a download, under mine, and so on. Just drop and forget those files, no need to read, observe or understand anything. So the workload on both sides (customer and "support") would be reduced and the integration would be made very simple.

I've just asked CS for approval, results to come.

Mark,

Thank you. It is working now. I was having lot of problems.

Sanal

Sorry, my mistake I pushed wrong key and posted.
Any reply you have made, has a button that you can press to delete it. You only see it on YOUR replies, no-one elses .

2- I cannot find Civa INS Manual
The CIVA INS manuals should be in the FSX\Civa\Docs\ folder

Mark