sieggie wrote on Jan 11^th, 2012 at 12:43am:


I'll give it a try. I'm still wrestling with adding the GPS or not. I haven't yet, and don't really want to. I think looking at the shift+4 map is cheating enough.

But, nevertheless I am still playing around with the panel layout, so thank you!!

I don't know if that helps. The Civa Operations Manual states.
7 FROM-TO Display
It’s a two digit display where the pilot is able to insert and read waypoints and DME ID numbers:
1) Two non flashing numbers are the waypoints defining the current navigation leg.
2) A single non flashing number in the FROM side of the display, with Data selector in WAYPT position, shows waypoint ID being displayed on data displays.
3) A  single  flashing  number  in  the  FROM  side  of  the  display,  with  Data  selector in WAYPT position, shows the selected waypoint is involved in the leg currently being
shown.
4) A flashing number in the TO side of the display defines the DME station designed for DME updating.

Now when knowing on which side the '0' was flashing, you may get a clue on the mode the unit was in. However, a zero isn't a real waypoint, it's your current position. So you may have ended up on a clueless #1 unit, only knowing about the current position.

Can you perform a direct-to to your waypoint #6?
That would be
WY PT CHG
0-6
INSERT
This forces the unit to fly directly to the #6 waypoint, starting from your current position, hence the 0 'to' 6 entry.

But try this one first.
You may still be in the DME update mode. So things you enter there don't alter anything on the actual flight path, but only on the update stations.
Leave that mode with moving the Data Selector away from WAY PT and DIS/TIME. You'll see if you are out of the DME update mode when the flashing of the digit has stopped.

Hi, vans.
Quote:

Are you speaking about the glideslope indicator? I'm way below the GS on this shot for example. But it works with the Civa INS in the panel.cfg.


Here's a thread on a problem with the indicator not showing up. Does it help?
http://www.captainsim.org/yabb2/YaBB.pl?num=1300469217

vans wrote on Jan 19^th, 2012 at 12:54am:

Moving the gauge to the vc allows the CIVA to work immediately. If you leave it in the window0 section, you must open the Icons tool before the CIVA can be used.

Morten wrote on Mar 30^th, 2012 at 4:17am:


Can you describe the steps on the alignment you followed?

Things to check:
-Be sure the parking brake is set and the engines are off!

-Cancel the warnings you get (maybe due to position disagreement) before aligning

Thanks for trying to help me!

- The 707 starts from Cold'n'dark standard loaded file
- Parking brake is set. Battery and avionics are on.
- Warnings are canceled through pressing the Test Button down (don't know of any further cancellation method) before alignment.

Still the red Warning lamp starts to light up as soon as I have entered the position and when turned to DSRTK/STS the API is still not moving down from 95.

However I did accidentally discover some change when after the warning I'd rotated back from DSRTK/STS to Pos and from Align to STBY and then all back again to DSRTK/STS and Align - then the Warning light disappeared and the API digits now would move down - but not further down than 65 in any case, which obviously is insufficient in order to get a "green ready" light - it should be at least 5 as I've learned.

What the heck is going on?    
 

If you're not paitent to wait the 15 minutes for the align process, you can click the top right screw on the MSU after you set it to Align and it will "fast align" (sort of a cheat)
Yes, mind that one. Highly recommended.

If it stays at a certain performance index and the green 'nav ready' light doesn't come on, you may have entered the coordinates the wrong way. I think this arises with the FSX display format. People often seem to miss a zero ('0') when entering coordinates due to the way FSX 'displays' them by leaving them out. Stating this because that was my major problem on the first attempts and I often see it happening when folks learn the INS.

When using the double INS setup, both units must get the same input data. This sounds easy, but if you mix up some numbers when clicking too fast, errors likely occur.
If you still receive errors, please post a screenshot where we can see the coordinates from FSX and the ones you've entered in the INS. That helps on judging about the data format, means the missing zero and things.

If all of the above isn't helping, reset the INS by deleting the isd file in the Civa folder. You'll get some fresh units on the next FSX start. Maybe the file got corrupted.

how long did you wait during the alignment?