Hi

I have a little question regarding the way the INS was integrated to the 707 that I don't think either manual (CIVA or 707) could answer.
Last night I was flying a short Munich-Istanbul flight using the INS, and during the flight my INS alignment degraded to 94 as it is supposed to, however the plane continued to follow the flightplan flawlessly. At 94, I was expecting the INS to send me on a completely errouneous radial at the next waypoint change, but its being mis-aligned did not seem to affect the flight in any way.

Is the 707 CIVA integration disalignment-proof or does the CIVA INS simply not simulate disalignment induced drift ?

Cheers

Nico

PS : I think I might have made up a few words here, sorry about that, it's the best I could muster up at 4am

This is often caused by not entering the current position "freshly" every time or by using the wrong format.
What does the shift-z view of FSX show exactly and what are you entering then?

If I use your coordinates given in your above post (N 40*51.8 E 017*25.6), it takes me to nowhere


I don't have any addon scenery there but at least a standard airport should show up if that was the place you were using to align the INS.

(N 40*51.8 E 017*25.6)

So I think that you've mixed up the format of the coordinates when entering them in the INS and it therefor fails to align.

Glad to hear. Have some nice guided flights now and don't forget updating via DME tuning. Also a good practice for entering coordinates. 

Hi Alex.

From page 22 of 707 manual II - Aircraft and Systems - L17 Doppler-INS Switch. It reads (in part):

DOPPLER
- Autopilot in NAV mode tracks Doppler Navigation System
- Heading Bug on Captain's HSI controlled by HSI Heading Selector
INS
Inop if Delco Carousel IV-A INS is not installed.
If installed:
- Autopilot in NAV mode tracks CIVA INS
- Heading Bug on Captain's HSI controlled by CIVA INS

See the image for what it looks like. Click to open the cover and then click the switch and make sure it is in the DOWN position.

Mark

Hi Alex.

This is how I do it:
I press Z (default keyboard short) to activate the A/P just as I raise the gear.
I use the Trim Wheels on the 2D A/P to set the pitch for a 250 knot climb to 10,000 feet.
After reaching 10,000 feet, I trim the nose down to continue a climb at about 300-310 knots.
After that, I just continually make adjustments in Airspeed and VS for the climb to Cruise Altitude.

Edit: On the A/P I make sure that the Altitude Hold/Elevator Disconnect Switch is in the center position so that when I press Z to turn on the A/P, the Pitch Trim Wheels are in control of the elevators, this means that the Autopilot will hold you current pitch attitude. If it is in the down position (ELEV DISCT) YOU are in complete control of the elevators. The Autopilot cannot be used to change the pitch nor hold altitude. I only switch it to the disconnect position during descents.

Mark

I can't figure out why you are having a problem like this. It works fine for me every time. I cross check distances and time to make sure my plan is no wrong, and once I turn the Autopilot Mode Selector to NAV the aircraft will either turn to intercept the course to the first waypoint or turn directly towards the first waypoint. I can't remember which one it does because I haven't done an INS flight for a while. I've been doing lots of DNS flights.

Mark

paul and mark, i appriciate your help greatly

can i just check i installed the civa ins correctly?
this is my panel config

THIS BELOW =no power, on the 2D panel

[Window00]
file=bg.bmp
background_color=0,0,0
size_mm=1024,768
window_size_ratio=1.00 
position=7
visible=1
ident=MAIN_PANEL
render_3d_window=0
window_size= 1.000, 1.000
window_pos= 0.000, 0.000
gauge00=Captain_Sim.x707.sys!main, 0,0, 2,2
gauge01=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
gauge02=Captain_Sim.x707.tools!icons, 0,532,24,120
gauge03=Captain_Sim.x707.gpws!main, 0,0,1,1
;CIVA
gauge04=../civa/INS!Config,         0,    0,  0, 0, CS707
gauge05=../civa/INS!CduPanelIconB,   0,  652, 24, 24, 11041
gauge06=../civa/INS!AdeuPanelIconB,  0,  676, 24, 24, 11042

[Window01]
size_mm=200,256
window_pos=0.000,0.070
position=0
background_color=0,0,0
visible=0
ident=11001
gauge00=Captain_Sim.x707.tools!ac100,0,0,200,256

[Window02]
size_mm=538,780
window_size=0.25
window_pos= 0.750, 0.150
;position=2
background_color=0,0,0
visible=0
ident=11002
zorder=1
gauge00=Captain_Sim.x707.P04!P04_radar, 0,  0,538,522
gauge01=Captain_Sim.x707.P03!P03_radar, 0,523,538,250
gauge02=Captain_Sim.x707.WXR!wr_display, 93,70,358,358

[Window03]
size_mm=400,283
position=8
background_color=0,0,0
visible=0
ident=11003
nomenu=0
gauge00=Captain_Sim.x707.P01!P01_map,0,0,400,283

[Window04]
size_mm=405,100
window_pos= 0.300, 0.020
;position=2
background_color=0,0,0
visible=0
ident=11004
nomenu=0
gauge00=Captain_Sim.x707.P11!P11_ap,0,0,384,100
gauge01=../civa/INS!CduPanelIconB,    385, 0, 20, 20, 11041
gauge03=../civa/INS!AdeuPanelIconB,    385, 20, 20, 20, 11042

[Window05]
size_mm=349,218
window_size=0.25
window_pos= 0.030, 0.690
background_color=0,0,0
visible=0
ident=11005
render_3d_window=0
gauge00=Captain_Sim.x707.P15!P15_voice, 0,0, 349,218

;CIVA
[Window06]
size_mm=420,223
background_color=0,0,0
window_pos=0.300, 0.160
position=0
visible=0
ident=11041
no_luminous=1
gauge00=../civa/ins!Cdu1,   0,  0, 200, 158
gauge01=../civa/ins!Cdu2, 200,  0, 200, 158
gauge02=../civa/INS!UpdateFlags, 150, 160, 115, 63
gauge03=../civa/INS!CduPanelIconB,      400, 0, 20, 20, 11041
gauge04=../civa/INS!NavModeDual,      270, 160, 50, 45
gauge05=../civa/INS!AdeuPanelIconB,      400, 138, 20, 20, 11042

[Window07]
size_mm=420,158
background_color=0,0,0
window_pos=0.300, 0.450
position=8
visible=0
ident=11042
no_luminous=1
gauge00=../civa/INS!Msu1,   0,  0, 200, 57
gauge01=../civa/INS!Msu2, 200,  0, 200, 57
gauge02=../civa/INS!Adeu1, 0, 60, 250, 101
gauge03=../civa/INS!AdeuPanelIconB,      400, 0, 20, 20, 11042

hi mark,

ok slight confusion on gauge 3 vs gauge 4 entry,

will change that slight value and see what happens

== edit

done that, no difference, still no power