I've just tried it at the position from your screenshot, Morten. Don't mind the direction my plane is facing, I haven't parked it correctly at the gate, but the position itself is the same as on your screens.



It works with the normal steps. Which are:

• establish external power
• route the external power through the plane (FE panel setup)
• parking brake on
• startup both INS in stby (MSU)
• enter the current position into both units (your data looks correct)
• switch to DSRTK/STS, delete the error codes coming up after the self test with pressing and holding TEST
• switch both MSUs to ALIGN
• click the upper right screw on the MSU to start the faster alignment
• watch the units going from 9 down to 5, the green 'NAV READY' light will come up
• watch the units going from 5 down to 0 while not starting the engines or moving the plane
• finally, switch both MSUs to NAV, then you can start the engines or move the plane

You screenshots don't show any error codes, so things could be right at your end and the question from jettrader is valid. Maybe you did not use the fast align option and just have to wait some more. If there was a problem, you would get an error code.

Hi CoolP

Good to have you back on this thread and thanks for your great effort in learning us how to deal with this antique show! - As a matter of fact, I saw you the other day mentioned and praised in a CS 707-300 AVSIM review.  

The little thing has now start working here, digging itself all the way down to 05, within 3 minutes!
Profoundly going through your check list here, I realized that the Civas own Quick Guide has an error in their checklist, which turned out to fatally misguide me in my struggle to get things to work!
You  wrote:

- Enter the current position into both units (your data looks correct)

- Switch to DSRTK/STS, delete the error codes coming up after the self test with pressing and holding TEST


The Civa Quick Guide has unfortunately turned those same aspects into a wrong order:

- Check for Action/Malfunction codes moving the Data selector to DSRTK/STS position

- Rotate CDU Data Selector to the POS position

- Enter present position


So, this is what obviously caused the error!  


PS. You need a proper version of Copenhagen Airport!
Here:
http://secure.simmarket.com/scansim-fly-to-ekch-copenhagen-airport.phtml
A nice one with atmospheric effects AND working jetways!  
another company is currently working on their version, properly with their usual "hijacked" credit-jetways, I guess..!

CoolP wrote on Apr 3^rd, 2012 at 8:40pm:


Hey man, don't underestimate yourself!!
Remember them red warning lights I wrote about, that would turn up the minute I entered the position..?!
They now disappear immediately when hitting the test button!

...so what worries me mostly right now, is to actually FLY this mother being forced to rely on this antique and unpredictable contraption...!          

Morten wrote on Apr 4^th, 2012 at 8:25pm:

I would be interested in seeing that too!

There's a tutorial doc in the Civa folder. Step 7 - DUAL DME UPDATING speaks about the dual DME operation, but I think we've described the procedure more or less in this thread already. It starts here. http://www.captainsim.org/yabb2/YaBB.pl?num=1285100008/138#138
A shorter list is here, plus some discussion. http://www.captainsim.org/yabb2/YaBB.pl?num=1285100008/156#156

I think I have way too long explanations there, but the Operations Manual pdf of the Cive gives you a step by step guide.
3 DME  POSITION  UPDATING is the chapter you are looking for I guess. The main item to keep in mind is the need to right click the numbers 7 and 9 while the selector is in DSRTK/STS. This will enter the submode of the DME updating. Leave the elevation data procedure out, that's optional stuff.

The single DME update isn't any different from the dual one, except for the operation of two units of course and choosing different stations for them. If you have one on your planned flight path and one with an offset, you will receive the best accuracy.

Most VORs in FSX range up to the maximum of approx 200nm, so you can tune the one on your flight path being 200nm out to overfly and, again, 200nm out. Gives you 400nm (minus the cone of silence) of usable data thanks to the (unrealistic) sim's accuracy on receiving stations. That's a comfortable range for the subsonic planes I think. That Concorde lady eats those 400nm a bit faster though, same as the fuel.  

The instructions for v1.1 work for v1.3. The VC INS does not work at all. It is still just eye candy at the moment.

CoolP wrote on Jul 11^th, 2012 at 6:09am:
Your saying this leads me to wonder if the other devs that use a variant of the CIVA-INS actually DID get permission from the SIMUFLY (or whoever it is they need to contact).

Markoz wrote on Jul 11^th, 2012 at 12:00pm:

As far as I understood CS, it's not so much about a special permission, but about some vital info to make it work. Their 3D model is beautiful, it just doesn't fully connect to the Civa INS (despite some lights) and this 'how to' on the connection details seems to be missing.

I saw some folks reminding the Civa devs about the open questions from CS, but I didn't notice a response to it. I surely don't know the background, but the Civa forum is a pretty silent place.
DanW wrote on Jul 11^th, 2012 at 1:44pm:

Glad to hear it's working, Dan.