I've read all the postings on this subject including simbio's "Installing 3 Adeu and info" and I have modified the panel.cfg file under panel.flight1v to match the instructions in simbio's and other threads.  When running the sim I open Window14 and I get the 3 MSUs and the 2 Adeus, but I only get 2 of the 3 CDUs.  The missing CDU is in the top left postion amoung the 8 positions occupied by the CDU's, CMUs, and Adeus.

My Window00 section calls for the NavModeTriple and I configured Window14 the way the ADEU insertion instruction pdf calls for identifying the 3 CDUs.

I downloaded the 707 from Captain Sim just 4 days ago, so it is the latest version, 1.51 I think.  I'm running FS9.

Can anyone help me identify what I've done wrong in the config file to lose 1 CDU?

If you post here the modified panel.cfg, maybe not the whole file but only the lines you added, we could check for errors.

Marco

Why have you defined CDUs (1, 2 and 3) in both [Window09] and [Window14]?

Those are duplicate gauges which are not correct.
If you want to have CDUs in two places you must use the additional gauges we originally added to be placed in the VC:

For each CDU you could define:

For CDU #1 you have INS!CDU1, INS!CDU11, INS!CDU12
For CDU #2 you have INS!CDU2, INS!CDU21, INS!CDU22
For CDU #3 you have INS!CDU3, INS!CDU31, INS!CDU32

So I'd try to change win09:

[Window09]
gauge01=../CIVA/INS!CDU11,  6,21,245,200
gauge02=../CIVA/INS!CDU21,  543,17,255,202
gauge07=../CIVA/INS!CDU31,  268,288,266,204

hopefully it will work (it should).

Regards
Marco

Trying again to include the images.  For some reason the attachments didn't work the first time.

Well, I've really done it this time.  I made the changes you suggested, and as I noted in an earlier message today, I still had the missing CDU in the stacked view.  But then when I tried to program a flight neither CDU would only accept anything but the latitude entry.  When I keyed in the latitude of the airport and hit Insert, the first time I clicked the key each time, it wouldn't do anything, I had to hit the Insert key a second time, and then it would put the airport position latitude in the CDU.  Then  when I hit "W" for west longitude, nothing happened; it would not let me enter latitude.  I changed airports, same thing. Nothing would allow me to input the longitude and none of the INS programming could go foward.  

I changed the lines in the panel.cfg file I had changed, exited FS9, restarted it, set up a 707 flight, and same thing:  the latitude I had inserted previously was in the CDU as soon as I turned from off to standby, and neither CDU 2 nor 3 would accept longitude.

I removed the modified panel.config file from panel.flight1v and put the original back in (I had save it to another file location), shutdown and restarted FS9--same problem, it wouldn't let me do anthing beyond entering latitude on either CDU.  I changed aircraft, anything I could think of including rebooting the computer, but always came back to the same problem.

Obviously I've screwed up the changes to the confige file, but how can I install CIVA and start over?

Sorry to be such a bother.

Marco,  

The strange thing for me was that after removing the modified panel config file and replacing it with the original one that had only the original CIVA modifications from when I first installed the INS, the screens still showed the ADEU heads that I only entered in a later modification and the CDUs showed the last latitude I tried to enter with the modified config file and would not allow me to enter longitude.  It seemed that FS9 itself had been permanently modified rather than just the panel config in the Legendary_707 aircraft file.

I'm going to do the delete and reenter that you suggested.  I think this INS is a great add-on, and the one flight I made where it was working correctly was excellent.  Unfortunately, my subsequent changes messed it up, so I should have left well enough alone.

Marco, yes I'm sure you are right.  The problem is that in the 707 airplane folder there are 4 panel.cfg files:  pass, passv, flight1 and flight1v.  I'm comparing the contents of each of these files and also corresponding with Captain Sim to learn which file should be modified, or if they all have to be modified.  The panel jpg files in each of these 4 folders look identical to me, so i don't know what the differences are.  As indicated previously, I have deleted the CIVA file , then uninstalled and reinstalled the CS707 addon, and reinstalled CIVA to get a fresh start.  CIVA is such a good program it's worth the effort.  It's boring to fly using GPS.

Thanks for the link to the utility, I'll give it a try.

Also, sorry to be such a bother, but now I need more help.  In an earlier posting I wrote that I had to push the Insert button twice to put in latitude.  You correctly pointed out that I should only press it once, which I also knew from the user manuals.  The problem was if I pushed insert only once, the button remained lighted but nothing happened:  the light stayed on and I could not enter latitude data.  This was the same on all 3 CDUs.  If I pushed Insert a second time, the button light went out, but when I pushed the W key to key in longitude nothing happened.

Since then I deleted CIVA file, uninstalled CS707 and all previous flight saves and reinstalled CS707. I ran a test flight without INS,  Everything was okay.
Next, I downloaded CIVA from your website and installed it.  Then I downloaded civa4cs707v1.0.zip from the CS knowledge base and installed it.
I started FS9 to a default Cessna 172 engines running a KSEA, and shut it down, turning off the master and avionics switches. I then chose a 707 passenger plane from the Aircraft section of the dropdown menu, which booted cold and dark.
I turned on the battery and avionics switches, connected the circuit breakers and checked that the avionics were on, which they were.  With the parking brake applied I switched on the 3 CDUs to standby.
Ran the errors test on each CDU, none showed and 0-9-5 were displayed on each one.  I pushed the test button to check each CDU, all lights came on. I Set the selector to 0 and the from/to indicated 01.  The lat and long displays showed all zeros.  I keyed N, and the lat screen remained all zeros and the Insert switch lighted.  The warning light appeared, I turned the knob to test and pushed the test button, got the 06-14 error code, clicked test and the error messages disappeared. I keyed in N and the KSEA lat and then pushed the lighted insert key.  Nothing happened. I pushed it a second time, the light went out and the SEA lat was displayed.  I keyed W and nothing happened, the longitude continued to show default E and all zeros and would not change to W and I couldn't make anymore entries.  I tried the other CDUs, same result.
I exited the flight and went through all the steps again.  This time the KSEA latitude was showing on each CDU as soon as I selected standby.  I Keyed N, lat went to all zeros, I keyed in airport lat again, the insert light came on, I pushed Insert and again nothing happened.  I pushed it a second time, the light went out but I could not enter longitude.

Sorry to be so long and wordy, but I wanted to show in detail the steps I took to determine if I missed a step.

Yes, I am using it according to the manual, I just didn't mention it.  I rotate it to the test position all the way clockwise for the error codes and tests, then CCW back to POS to input current location, and the next position clockwise (I don't have the manual with me right now) to input subsequent checkpoints, although I haven't gotten past latitude input except once after the first installation.
The odd thing is when I did the first installation of CIVA and the ADEU modification, everything worked for one flight.  I've removed and reinstalled every change that I've made since then and have had the insertion problem ever since.
I also have FSX on this computer and have installed an INS on a link from CLSDC10 to your website.  FSX is under a completely separate folder but under the same MS Games folder.  Is it possible there is some kind of interaction between the two installations that's causing a problem?

Okay, I will send and then delete the file you requested; that will be later today.
Yes, I understand about the difference between present position and waypoints and the procedures for enter each.  Last night I did an experimental flight, and while inserting present position into the CDU with the Waypoint/DME selector set to 0, had the same problem, it would show the lat that I keyed in but the insert key had to be pushed twice before the light would go out.  Then it would not accept long. keyed in.  I waited 15 minutes while the alignment took place, and during that time turned the Waypoint/DME selector to 1.  I keyed in present position lat and the insert key worked properly.  I keyed W for long and the CDU accepted it, I was able to key in the long.  I manually inserted two more waypoints successfully.  When I moved the Waypoint/DME selector to 1, then 2, then 3 it showed the correct coordinates for the waypoints I entered manually. By then I had 3 green lights and switched the 3 INSs to NAV, started engines and took off.  When I turned the mode selector  to leg distance and time it showed almost 5000nm for a leg that was not more than a few hundred miles and the time was 900 minutes, but both distance and time were counting down.  The distance and time errors were because the present position keyed in with the Waypoint/DME selector set to 0 was  the latitude for SVMI, but because it would not accept long. the present position at 0 was something like 10*28.3N, 00*00.0E.  Present position set in 1 was correct.  I didn't try connecting the INS to the autopilot.
I don't know if this helps, but that is the latest information.