SIMUFLY.COM Discussion Forums

SIMUFLY.COM Discussion Forums
https://www.simufly.com/cgi-bin/yabb2/YaBB.pl
Delco Carousel IV-A INS For Microsoft Flight Simulator >> Delco Carousel IV-A INS For Microsoft Flight Simulator >> The INS Mode selector in the RFP does not work
https://www.simufly.com/cgi-bin/yabb2/YaBB.pl?num=1319458832

Message started by R.C. de Visser - Netherlands on Oct 24^th, 2011, 1:20pm

Title: The INS Mode selector in the RFP does not work
Post by R.C. de Visser - Netherlands on Oct 24^th, 2011, 1:20pm

Hi, Who can help me out I have installed the CDU, Mode selector and ADEU in the RFP 747-206 for testing.

I have installed the CIVA INS version 1.51 as a triple set in the Analog panel

Problem 1:
The Tape-Panel still contains the HDHG INS which does not show the Distance/Time after the inputs of LAT/LON When turnig the knob to dis/time according to the standard procedure sequence of input.

And NO I do not forget to set NAV and Hdg selector and then the INS on RMT After putting the right startsequence from 0 to 1 in the auto mode. I do not see Dis/Time att al except two litted dots.

Problem 2:
The INS NAV MODE selector at the main panel does not work either in the analoge version which as already told contains the CIVA INS Triple installing.

After start-up the RFP742 I turn the knob on the Mode Selector to Stand-by to warm up the system. After 5 minutes, 10 minutes, 15 minutes (and so on) the knob still can not be moved to Align, Nav and the green light (Ready) still not lit while the electrical systems works correctly at the AC itself.

When it works perfectly in the Analoge version then I will install CIVA INS in the Taped Version which I fly the most.

I changed the lines in panel.cfg accorinding to the lines that should be in use for CIVA INS and have disabled the HGHB INS. But the INS NAV mode does not work and the Mode Selector does not work.

When I click on the INS NAV MODE button 1 then the button flips over and after release the mouseclick the button springs back in off position. This occures to all three buttons as I have clicked them.
They don't remain in the ON position.
There should be one on and ther other two should be off in the mainpanel but the are all in the Off position

Her underneith the panel.cfg:

// FS2004 Classic B747-200 Series Analog Panel (c)
// Web Site: www.panelshop.com
// Panel Version 2.2 16 June, 2004 (c)
// Copyrighted. No part of this package may be duplicated or
// distributed without written permission of author
// Panel designed for use with FS2004 Only.
// --------------------------------------------------------------------

[Window Titles]
window00=Four Engine Heavy Jet B747-200
window01=Electric
window02=Radio
window03=GPS
window04=Overhead
window05=Console
window06=INS
window07=Fuel
window08=Secondary
window09=Blank

// --------------------------------------------------------------------
Fixed Window37=Up
// --------------------------------------------------------------------
[Views]
VIEW_FORWARD_ZOOM=0.9
VIEW_FORWARD_DIR=05.5, 0.0, 00.0
VIEW_FORWARD_WINDOWS=MAIN_PANEL,RADIO_STACK_PANEL,20,COMPASS_PANEL
// --------------------------------------------------------------------
VIEW_FORWARD_RIGHT_ZOOM=1.0
VIEW_FORWARD_RIGHT_WINDOWS=30
VIEW_FORWARD_RIGHT_DIR=4.0, 0.0, 45.0
// --------------------------------------------------------------------
VIEW_RIGHT_ZOOM=1.0
VIEW_RIGHT_WINDOWS=31
VIEW_RIGHT_DIR=07.0, 0.0, 90.0
// --------------------------------------------------------------------
VIEW_REAR_RIGHT_ZOOM=1.0
VIEW_REAR_RIGHT_WINDOWS=32
// --------------------------------------------------------------------
VIEW_REAR_ZOOM=0.60
VIEW_REAR_WINDOWS=33
// --------------------------------------------------------------------
VIEW_REAR_LEFT_ZOOM=0.5
VIEW_REAR_LEFT_WINDOWS=34
VIEW_REAR_LEFT_DIR=05.0, 0.0, 225.0
// --------------------------------------------------------------------
VIEW_LEFT_ZOOM=1.0
VIEW_LEFT_WINDOWS=35
VIEW_LEFT_DIR=-1.0, 0.0, 270.0
// --------------------------------------------------------------------
VIEW_FORWARD_LEFT_ZOOM=0.90
VIEW_FORWARD_LEFT_WINDOWS=36
VIEW_FORWARD_LEFT_DIR=1.0, 0.0, 320.0
// --------------------------------------------------------------------
VIEW_UP_ZOOM=0.90
VIEW_UP_WINDOWS=37
VIEW_UP_DIR=08.0, 0.0, 0.0
// --------------------------------------------------------------------

[Window00]
// Main Panel for the Classic 747-200
file=Main.bmp
size_mm=1024
position=1
visible=1
ident=Main_Panel

gauge00=../RFP_V2/RT742_Analog_Night_F, 0,0,1024
gauge01=../RFP_V2/RT742_Tapes!FFRATS_Glare, 99, 368, 81
gauge02=../RFP_V2/RT742_Tapes!VSI, 305, 570, 087
gauge03=../RFP_V2/RT742_Tapes!GPWS, 572, 369, 378
gauge04=../RFP_V2/RT742_Tapes!ADI, 164, 429, 139
gauge05=../RFP_V2/RT742_Tapes!HSI, 160, 566, 143
gauge06=../RFP_V2/RT742_Tapes!Altimeter, 305, 476, 092
gauge07=../RFP_V2/RT742_Tapes!ASI, 061, 451, 102
gauge08=../RFP_V2/RT742_Tapes!RMI, 053, 598, 108
gauge09=../RFP_V2/RT742_Tapes!Clock, 398, 571, 086
gauge10=../RFP_V2/RT742_Tapes!RADIOalt, 405, 444, 060
gauge11=../RFP_V2/RT742_Tapes!Radio_Glare, 301, 290, 215
gauge12=../RFP_V2/RT742_Tapes!Controls, 655, 710, 215
gauge13=../RFP_V2/RT742_Tapes!Analog_Gear, 932, 422, 080
gauge14=../RFP_V2/RT742_Tapes!AP, 517, 260, 499
gauge15=../RFP_V2/RT742_Tapes!Analog_Warnings, 509, 577, 104
gauge16=../RFP_V2/RT742_Tapes!GearWarn, 840, 743, 025
gauge17=../RFP_V2/RT742_Tapes!AltHorn, 331, 450, 039
gauge18=../RFP_V2/RT742_Tapes!FMA, 309, 374, 153
gauge19=../RFP_V2/RT742_Tapes!ResBrake, 348, 710, 117
gauge20=../RFP_V2/RT742_Tapes!Analog_Stby_ADI, 518,490,74
gauge21=../RFP_V2/RT742_Tapes!Analog_Engine1, 620,463,57
gauge22=../RFP_V2/RT742_Tapes!Analog_Engine2, 681,463,57
gauge23=../RFP_V2/RT742_Tapes!Analog_Engine3, 742,463,57
gauge24=../RFP_V2/RT742_Tapes!Analog_Engine4, 803,463,57
gauge25=../RFP_V2/RT742_Tapes!Analog_Limit_Indicator, 861,451,61
gauge26=../RFP_V2/RT742_Tapes!Analog_Flaps, 868,517,50
gauge27=../RFP_V2/RT742_Tapes!Analog_Flaps, 868,578,50
gauge28=../RFP_V2/RT742_Tapes!Flaps_Lights, 869,635,51
gauge29=../RFP_V2/RT742_Tapes!GA_Button, 653, 730, 030
gauge30=../RFP_V2/RT742_Tapes!Analog_TAS, 871,649,50
gauge31=../RFP_V2/RT742_Tapes!DME, 065, 558, 085
gauge32=../RFP_V2/RT742_Tapes!Set_Bugs, 0, 395, 102
gauge33=../RFP_V2/RT742_Tapes!Toggles, 019, 310, 197
gauge34=../RFP_V2/RT742_Tapes!FireWarn, 267, 294, 027
gauge35=../RFP_V2/RT742_Tapes!Compass, 793, 052, 047
gauge36=../RFP_V2/RT742_Tapes!OMI_Lights, 463, 393, 022
gauge37=../RFP_V2/RT742_Tapes!REV1, 622,447,52
gauge38=../RFP_V2/RT742_Tapes!REV2, 684,447,52
gauge39=../RFP_V2/RT742_Tapes!REV3, 746,447,52
gauge40=../RFP_V2/RT742_Tapes!REV4, 805,447,52
gauge41=../RFP_V2/RT742_Tapes!Rating_Select, 921, 457, 11
gauge42=../RFP_V2/RT742_Tapes!Analog_Gearlights, 946,441,53
gauge43=../RFP_V2/RT742_Tapes!Inst_Warn, 253,397,55
gauge44=../RFP_V2/RT742_Tapes!FDComp, 134,715,191

//---------------------------------------------------------------------

// -- HGHB INS Stuff goes here --
//gauge45=../RFP_V2/rt_INS_D, 497, 715, 143
//gauge46=../RFP_V2/rt_INS_D, 866, 714, 143

// -- CIVA INS Stuff goes here --
gauge45=../civa/INS!Config, 0, 0, 0, 0, Vmax742
gauge46=../civa/INS!NavModeTriple, 402, 662, 77
gauge47=../civa/INS!UpdateFlags, 314, 669, 76
gauge48=../civa/INS!Cdu11, 497, 715, 143
gauge49=../civa/INS!Cdu21, 866, 714, 143

// --------------------------------------------------------------------

[Window01]
// Flight Engineer Electrical Panel
file=FE-Elect-256.bmp
size_mm=922, 732
position=1
visible=0
ident=Cruise_Panel

gauge00=../RFP_V2/RT742_tapes!Electrics, 0, 0, 922

// --------------------------------------------------------------------

[Window02]
// Radio Stack - Includes Radios, and Limit Panel
file=Radios1.bmp
size_mm=603,434
position=8
visible=0
ident=Radio_Stack_Panel

gauge00=737-400!Comm 1, 2, 07, 202
gauge01=737-400!Nav 1, 2, 255, 202
gauge02=737-400!Nav 2, 402, 255, 202
gauge03=737-400!Comm 2, 402, 05, 202
gauge04=737-400!Transponder, 202, 341, 202
gauge05=737-400!Audio, 03, 90, 202
gauge06=../RFP_V2/RT742_Tapes!FFRATS, 0, 341, 203
gauge07=737-400!Audio, 402, 89, 202
gauge08=737-400!ADF, 201, 255, 202
gauge09=../RFP_V2/RT742_Tapes!PushBack, 0, 132, 201
gauge10=../RFP_V2/RT742_Tapes!RadiosNight, 0, 0, 603

// -- HGHB INS Stuff goes here --
//gauge11=../RFP_V2/RT_INS_STACK, 203,100,202

// -- CIVA INS stuff goes here --
gauge11=../civa/INS!Cdu31, 203, 92, 202 ,164
gauge12=../CIVA/INS!batparallel, 430, 344, 065, 083
gauge12=../CIVA/INS!batparallel, 430, 344, 065, 083
gauge13=../Civa/Ins!Adeu1, 421,134, 164, 60
gauge14=../Civa/Ins!Adeu2, 421,195, 164, 60

// --------------------------------------------------------------------

[Window03]

size_mm=456,378
window_size=0.5
position=8
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident=GPS_PANEL

gauge00=fs9gps!gps_500,0,0

//---------------------------------------------------------------------

[Window04]
// Overhead Panel
file=overhead-256.bmp
size_mm=1015, 750
position=1
visible=0
ident=Collective_Panel

gauge00=../RFP_V2/RT742_Tapes!Overhead, 0, 0, 1015

// -- CIVA INS stuff goes here --
gauge01=../civa/INS!Msu1, 204, 134, 198, 58
gauge02=../civa/INS!Msu2, 607, 134, 204, 58
gauge03=../civa/INS!Msu3, 204, 354, 201, 58

// --------------------------------------------------------------------

[Window05]
file=Console-Top-1.bmp
size_mm= 509
position= 8
visible=0
ident=Throttle_Panel

gauge00=../RFP_V2/RT742_Tapes!Console, 0, 0, 509

// --------------------------------------------------------------------

[Window06]
// Main INS Display

// -- CIVA INS stuff goes here --
size_mm=750,200
position=8
BACKGROUND_COLOR=16,16,16
VISIBLE=0
gauge00=../civa/ins!Cdu1, 0,02,250
gauge01=../civa/ins!Cdu2, 250,02,250
gauge02=../civa/ins!Cdu3, 500,02,250

// -- HGHB INS stuff goes here --
file=Delco-Atlas-2.BMP
size_mm=402, 318
position=8
visible=0
ident=INS_Panel

//gauge00=../RFP_V2/rt_ins, 0, 2, 400, 316

// --------------------------------------------------------------------

[Window07]
// Flight Engineer's Main Panel
file=FE-Fuel.BMP
size_mm=1024
position=1
visible=0
ident=Fuel_Panel

gauge00=../RFP_V2/RT742_Tapes!Fuel, 0, 0, 1024
gauge01=../RFP_V2/RT742_Tapes!Jettison, 744, 440, 280
gauge02=../RFP_V2/RT742_Tapes!Fuel_Loader, 153, 440, 590

// --------------------------------------------------------------------

[Window08]
// Flight Engineer's Hydraulic's Panel
file=FE-Hydr-256.BMP
size_mm=940, 772
position=8
visible=0
ident=Secondary_FE_Panel

gauge00=../RFP_V2/RT742_Tapes!Hydraulics, 0, 0, 940

// --------------------------------------------------------------------

[Window09]
// Used to hold gauges that must be active at all times
file=Blank.bmp
size_mm=15
position=8
visible=1
ident=Hidden_Panel

// CIVA CDU
gauge00=../RFP_V2/RT742_Tapes!SndCtrl, 1, 1, 0
gauge01=../civa/ins!Cdu1, 1, 1, 0
gauge02=../civa/ins!Cdu11, 1, 1, 0
gauge03=../civa/ins!Cdu12, 1, 1, 0

// -- HGHB INS stuff goes here --
//gauge01=../RFP_V2/rt_ins_mst, 03, 03, 01

//-----------------------------------------------------------------

[Vcockpit01]
file_1024=$Main-2.bmp
Background_color= 0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Main-2

gauge00=../RFP_V2/RT742_Tapes!VC_Analog_Warnings, 509, 770, 104, 165
gauge01=../RFP_V2/RT742_Tapes!Analog_Flaps, 865,690,56, 62
gauge02=../RFP_V2/RT742_Tapes!Analog_Flaps, 865,775,56, 62
gauge03=../RFP_V2/RT742_Tapes!VC_AP, 518, 345, 497, 145
gauge04=../RFP_V2/RT742_Tapes!VC_VSI, 305, 761, 88, 117
gauge05=../RFP_V2/RT742_Tapes!VC_ADI, 158, 574, 145, 180
gauge06=../RFP_V2/RT742_Tapes!VC_HSI, 160, 756, 143, 188
gauge07=../RFP_V2/RT742_Tapes!VC_Analog_Engine1, 620, 617, 057, 315
gauge08=../RFP_V2/RT742_Tapes!VC_Analog_Engine2, 681, 617, 057, 315
gauge09=../RFP_V2/RT742_Tapes!VC_Analog_Engine3, 742, 617, 057, 315
gauge10=../RFP_V2/RT742_Tapes!VC_Analog_Engine4, 803, 617, 057, 315
gauge11=../RFP_V2/RT742_Tapes!VC_ResBrake, 345, 940, 117, 80
gauge12=../RFP_V2/RT742_Tapes!VC_FMA, 309, 498, 153, 92
gauge13=../RFP_V2/RT742_Tapes!VC_ASI, 58, 600, 103, 140
gauge14=../RFP_V2/RT742_Tapes!VC_RadioAlt, 400, 592, 062, 164
gauge15=../RFP_V2/RT742_Tapes!VC_Altimeter, 305, 638, 089, 117
gauge16=../RFP_V2/RT742_Tapes!VC_Clock, 398, 761, 088, 114
gauge17=../RFP_V2/RT742_Tapes!VC_RMI, 053, 801, 108, 147
gauge18=../RFP_V2/RT742_Tapes!VC_DME, 65, 745, 085, 52
gauge19=../RFP_V2/RT742_Tapes!VC_Radio_Glare, 306, 375, 205, 147
gauge20=../RFP_V2/RT742_Tapes!Analog_Limit_Indicator, 860,599,65, 80
gauge21=../RFP_V2/RT742_Tapes!Analog_TAS, 871,866,52, 65
gauge22=../RFP_V2/RT742_Tapes!VC_AltHorn, 211, 540, 038, 028
gauge23=../RFP_V2/RT742_Tapes!VC_FireWarn, 269, 393, 024, 030
gauge24=../RFP_V2/RT742_Tapes!VC_OMI_Lights, 464, 533, 022, 078
gauge25=../RFP_V2/RT742_Tapes!VC_GPWS, 572, 493, 377, 061
gauge26=../RFP_V2/RT742_Tapes!VC_Compass, 791, 69, 046, 031
gauge27=../RFP_V2/RT742_Tapes!VC_FFRATS_Glare, 100, 490, 80, 66
gauge28=../RFP_V2/RT742_Tapes!VC_Analog_Stby_ADI, 518,660,76, 86
gauge29=../RFP_V2/RT742_Tapes!FDComp, 134,955,191,80
gauge30=../RFP_V2\RT742_Tapes!REV1, 622,597,52,15
gauge31=../RFP_V2\RT742_Tapes!REV2, 684,597,52,15
gauge32=../RFP_V2\RT742_Tapes!REV3, 746,597,52,15
gauge33=../RFP_V2\RT742_Tapes!REV4, 805,597,52,15

// --------------------------------------------------------------------

[Vcockpit02]
//file=$FE-TOP.BMP
file_1024=$FE-TOP.BMP
Background_color=0,0,0
size_mm=1024,1024
visible=0
ident=
pixel_size=1024,1024
texture=$FE-TOP

gauge00=../RFP_V2/RT742_Tapes!VC_Fuel_Loader,344, 010, 233, 1024

// --------------------------------------------------------------------

[Vcockpit03]
[Vcockpit03]
//file=$FE-CENTER.BMP
file_1024=$FE-CENTER.BMP
Background_color=0,0,0
size_mm=1024,1024
visible=0
ident=
pixel_size=940,772
texture=$FE-CENTER

gauge00=../RFP_V2/rt742_tapes!VC_Electrics, 03, 016, 473, 1007
gauge01=../RFP_V2/rt742_Tapes!VC_Hydraulics, 474, 015, 455, 1007

// --------------------------------------------------------------------

[Vcockpit04]
//file=$FE-1.BMP
file_1024=$FE-LOWER.BMP
Background_color=0,0,0
size_mm=1024,1024
visible=0
ident=
pixel_size=1024,1024
texture=$FE-LOWER

gauge00=../RFP_V2/rt742_Tapes!VC_Fuel, 238, 4, 567, 1023

// --------------------------------------------------------------------

[Vcockpit05]
//file=$overhead-256.bmp
file_1024=$overhead-256.bmp
Background_color=0,0,0
size_mm=1015,750
visible=0
ident=
pixel_size=1015,750
texture=$overhead-256

gauge00=../RFP_V2/RT742_Tapes!VC_Overhead, 0,0,1015

// --------------------------------------------------------------------

[Vcockpit06]
//file=$Console-Top-1.bmp
file_1024=$Console-Top-1.bmp
Background_color=0,0,0
size_mm=509,509
visible=0
ident=
pixel_size=509,509
texture=$Console-Top-1

gauge00=../RFP_V2/rt_INS_D, 1, 10, 143
gauge01=../RFP_V2/rt_INS_D, 66, 14, 143

// --------------------------------------------------------------------

[Vcockpit07]
//file=$radios1.bmp
file_1024=$radios1.bmp
Background_color=0,0,0
size_mm=603,434
visible=0
ident=
pixel_size=603,434
texture=$radios1

gauge00=737-400!Comm 1, 2,7,202
gauge01=737-400!Nav 1, 2,255,202
gauge02=737-400!Nav 2, 402,255,202
gauge03=737-400!Comm 2, 402,5,202
gauge04=737-400!Transponder, 202,341,202
gauge05=737-400!Audio, 3,90,202
gauge06=../RFP_V2/RT742_Tapes!VC_FFRATS, 0,341,203
gauge07=../RFP_V2/RT_INS_stack, 203,100,202
gauge08=737-400!Audio, 402,89,202
gauge09=737-400!ADF, 201,255,202
gauge10=../RFP_V2/RT742_Tapes!VC_PushBack, 0, 132, 201

// --------------------------------------------------------------------

[Vcockpit08]
file_1024=$rt_ins-a.bmp
Background_color=0,0,0
size_mm=402,319
visible=0
ident=
pixel_size=402,319
texture=$rt_ins-a
gauge00=../RFP_V2/RT_INS_stack, 0,0,402,319

// --------------------------------------------------------------------

[Vcockpit09]
file_1024=$MCP.bmp
Background_color= 0,0,0
size_mm=1015,110
visible=0
pixel_size=1015,110
texture=$MCP

//gauge00=../RFP_V2/RT742_Tapes!VC_AP, 518, 345, 497, 145

//----------------------------------------------------------------

[Fixed Window37]
// Approach Screen View Activates with Ctrl-NumPad 5
file=Approach.bmp
size_mm=1024
visible=0
nomenu=0
render_3d_window=1
window_pos=0.0,0.0
window_size=1.000,1.000
ident=37

gauge00=../RFP_V2/RT742_Analog_Appr, 0,0,1024
gauge01=../RFP_V2/RT742_Tapes!AP, 872, 444, 550
gauge02=../RFP_V2/RT742_Tapes!FMA, 557, 577, 153
gauge03=../RFP_V2/RT742_Tapes!Radio_Glare, 635, 478, 236
gauge04=../RFP_V2/RT742_Tapes!ASI, 308, 667, 102
gauge05=../RFP_V2/RT742_Tapes!Analog_Engine1, 916,684,75
gauge06=../RFP_V2/RT742_Tapes!Analog_Engine2, 991,684,75
gauge07=../RFP_V2/RT742_Tapes!Altimeter, 632, 680, 092
gauge08=../RFP_V2/RT742_Tapes!Analog_Stby_ADI, 780, 718, 095, 095
gauge09=../RFP_V2/RT742_Tapes!GA_Button, 755, 607, 025
gauge10=../RFP_V2/RT742_Tapes!GPWS, 932, 576, 416
gauge11=../RFP_V2/RT742_Tapes!AltHorn, 463, 611, 039
gauge12=../RFP_V2/RT742_Tapes!OMI_Lights, 711, 596, 022
gauge13=../RFP_V2/RT742_Tapes!FireWarn, 598, 482, 030
gauge14=../RFP_V2/RT742_Tapes!Set_Bugs, 247, 611, 102
gauge15=../RFP_V2/RT742_Tapes!FFRATS_Glare, 378, 567, 81
gauge16=../RFP_V2/RT742_Tapes!RadioAlt, 564, 644, 060
gauge17=../RFP_V2/RT742_Tapes!ADI, 412, 632, 139
gauge18=../RFP_V2/RT742_Tapes!REV1, 918,665,66
gauge19=../RFP_V2/RT742_Tapes!REV2, 993,665,66

// --------------------------------------------------------------------

[Color]
Day=255,255,255
Night=177,165,197
Luminous=200,200,90

[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=2800

//---------------------------------------------------------------------

What have I done wrong that the CIVA INS does not work ?

Please sent me your solution and/or the complete and good working RFP panel.cfg with a fine installed intregrated CIVA INS (1.51) for the Analogue Version and Tape-Version and related (#name).cfg if nessesary to get CIVA INS working.

Sincerely Yours,

Title: Re: The INS Mode selector in the RFP does not work
Post by vololiberista on Oct 24^th, 2011, 3:19pm

Try selecting "Align" immediately. That's also normal procedure. Enter your POS coordinates, click on the secret scews for fast align. Enter your wypts. Then when alignment is complete "green ready lights" select NAV and check your wypt distances.
vololiberista

Title: Re: The INS Mode selector in the RFP does not work
Post by Gianfranco Corrias on Oct 24^th, 2011, 5:04pm

[window00]

// -- CIVA INS Stuff goes here --
gauge47=../civa/INS!Config, 0, 0, 0, 0, Vmax742
gauge48=../civa/INS!NavModeTriple, 402, 662, 77
gauge49=../civa/INS!UpdateFlags, 314, 669, 76
gauge50=../civa/INS!Cdu11, 497, 715, 143
gauge51=../civa/INS!Cdu21, 866, 714, 143

In your [window00] the civa gauge number sequence is wrong.
Try to edit it as I put down in my replay.
Gianfranco

Title: Re: The INS Mode selector in the RFP does not work
Post by Marco Ravanello on Oct 25^th, 2011, 9:36am

I think the problem could be related to the fact that gauge Cdu1 is included TWICE.

In Window06 you have Cdu1, 2 and 3

In Windows09 you have Cdu1 (again), Cdu11 and Cdu12
SO I think Windows09 definition is wrong.

Please see CIVA/Docs/PanelIntegrationManual.pdf for a complete gauge names reference.

Hope this helps
Marco

Title: Re: The INS Mode selector in the RFP does not work
Post by R.C. de Visser - Netherlands on Oct 25^th, 2011, 2:37pm

Hio Vololiberista,

I will test this so I presume that waypoint Zero is the actual point where the AC is parked in "Death-Mode" After APU start then clicking the "screw" as input for startlocation. This should be Wpt 0 int the INS
Am I correct?

Hi Gianfranco

I change these lines right away

Hi Marco,

So as I red it well then I have to double slash the lines in windows 09 concerning the CIVA lines or removing these lines that they only will apear in the Windows06 screen.

Something else:
Does the CIVA INS have any influence at the IVAO Network and IVAP Radio ?

Sincerely,

Ronald

Title: Re: The INS Mode selector in the RFP does not work
Post by R.C. de Visser - Netherlands on Oct 25^th, 2011, 6:17pm

Hi,

I changed the Lines but now the AC doesn't respond at all I

Title: Re: The INS Mode selector in the RFP does not work
Post by Marco Ravanello on Oct 25^th, 2011, 6:50pm

Hi Ronald,

> I changed the Lines but now the AC doesn't respond at all

Then revert back to original ;)

> So as I red it well then I have to double slash the lines in windows 09
> concerning the CIVA lines or removing these lines that they only will apear
> in the Windows06 screen.

I'm not sure of this. There is a comment, in Window09 saying:
// Used to hold gauges that must be active at all times
Since I'm not an RFP expert I don't understand what that means but again,
what I'm sure of is that Cdu1 gauge shouldn't be used twice.

> Does the CIVA INS have any influence at the IVAO Network and IVAP Radio ?

No problems reported so far, AFAIK

Gianfranco: Can you please check your installation of RFP, and see what Window09 contains? (panel.cfg of course)

Thanks
Regards
Marco

Title: Re: The INS Mode selector in the RFP does not work
Post by Marco Ravanello on Oct 25^th, 2011, 6:55pm

> I presume that waypoint Zero is the actual point where the AC is parked in
> "Death-Mode" After APU start then clicking the "screw" as input for
> startlocation. This should be Wpt 0 int the INS Am I correct?

WP zero can't be "edited", it is defined as "current position" (sometimes not but that is a different story).

You must use Waypoint #1 to enter your present position, not by copying WP zero, but entering parking position lat/long as specified on the airport chart.

This is to check that the system, is correctly programmed, should show a 0-1 distance equal to ZERO NMs.

Hope this helps,
Marco

Title: Re: The INS Mode selector in the RFP does not work
Post by Gianfranco Corrias on Oct 26^th, 2011, 9:34am

I'm a RFP sim since the RFP was delivered for first time.
When we delivered civa INS,being their HGBH INS very poor the RFP team inserted immediately the civa data strings but with the gauge number sequence wrong. You have two choises:or you cancel the HGBH string or you have to edit as I shown you the civa gauge numbers.
The window09 cannot contain the civa strings and must be as you can see below:
[Window09]
// Used to hold gauges that must be active at all times
file=Blank.bmp
size_mm=15
position=8
visible=1
ident=Hidden_Panel

gauge00=../RFP_V2/RT742_Tapes!SndCtrl, 1, 1, 0

// -- HGHB INS stuff goes here --
//gauge01=../RFP_V2/rt_ins_mst, 03, 03, 01

You can switch on the civa INS selecting as you like, on MSU panel STBY,ALIGN or NAV directly.Before the alignment progress is API 06 you have to insert the ramp position otherwise the Alignment stops at API 06.If you perform the alignment selecting directly NAV the READY NAV light will flash momentarely when the alignment reaches API 05.
Waypoint 0 is always the present position so as Marco said to check the waypoint distances after the waypoint insertion you have to reinsert in the position 1 the ramp position and the distance 0-1 must be zero.
Have a look at Operation manual at civa/Doc.
Gianfranco

Title: Re: The INS Mode selector in the RFP does not work
Post by R.C. de Visser - Netherlands on Oct 26^th, 2011, 1:25pm

Marco_Ravanello wrote:

Normally I though that Wpt 1 should be the SID in the flightplan maybe there is the issue which probaly causes the original INS malfunction at that time. I don´t have problems with IVAO and INS till so far, but I thought that this could be a reason that INS might not work.

At this time I changed the panel.cfg for the original one

Tnx

Ronald

Title: Re: The INS Mode selector in the RFP does not work
Post by Marco Ravanello on Oct 26^th, 2011, 6:53pm

Hi Ronald,

> I though that Wpt 1 should be the SID in the flightplan maybe there is the
> issue which probaly causes the original INS malfunction at that time

No, it's not mandatory to enter parking position as WP #1, it's only to follow real life procedures.

In fact, if you want, you can program WP #1 with the LAT/LON of the destination (!!) airport and simply fly a 0-1 leg :)

Also please note that, AFAIK, (PLEASE Gianfranco correct me if I'm wrong, you're the real pilot, I'm not) the SID and STAR related part of a flight is NOT part of the INS flight plan. So SIDs and STARs are not flown "by INS", but I guess using ground radio aids and radar vectoring.

AFAIK, WP #2 is actually the point where you leave the SID. Such "point" has a name but I can't remember it. And I think the last WP is the one bringing you into the STAR (named IAF, Initial Approach Fix)

Again Gianfranco please confirm if this is true!

Marco

Title: Re: The INS Mode selector in the RFP does not work
Post by vololiberista on Oct 26^th, 2011, 7:17pm

Yes, the SID usually doesn't contain WYPTS. For example at London Heathrow the MID3J SID is turn right onto HDG 173 at 2 DME from LON. At 3.5 DME turn onto MID(Midhurst) radial 027. Once on the radial select 0-1 on the CDU and engage the navigation mode. Now your a/c will perform it's first route turn under INS guidance. Which also confirms that you haven't forgotten to engage the INS as did Korean Air some years ago which was subsequently shot down having been way off course!!!
In other words the end of the SID is your first INS governed navigation point.
vololiberista

Title: Re: The INS Mode selector in the RFP does not work
Post by Marco Ravanello on Oct 26^th, 2011, 8:30pm

> as did Korean Air some years ago which was subsequently shot down having been way off course

Poor them...RIP :'( :'(

Title: Re: The INS Mode selector in the RFP does not work
Post by Marco Ravanello on Oct 26^th, 2011, 8:37pm

Anyway Ronald,

I'd do this:

Leave Window06 as it is

[Window06]
// Main INS Display
// -- CIVA INS stuff goes here --
size_mm=750,200
position=8
BACKGROUND_COLOR=16,16,16
VISIBLE=0
gauge00=../civa/ins!Cdu1, 0,02,250
gauge01=../civa/ins!Cdu2, 250,02,250
gauge02=../civa/ins!Cdu3, 500,02,250

Then, I'd modify Window09 in this way (just copy&paste if you wish):

[Window09]
// Used to hold gauges that must be active at all times
file=Blank.bmp
size_mm=15
position=8
visible=1
ident=Hidden_Panel

// CIVA CDU
gauge00=../RFP_V2/RT742_Tapes!SndCtrl, 1, 1, 0
// -- HGHB INS stuff goes here --
//gauge01=../RFP_V2/rt_ins_mst, 03, 03, 01

Please try and report back.
Obviously, ALWAYS save a copy of panel.cfg before modifying it for experimental purposes :)

Title: Re: The INS Mode selector in the RFP does not work
Post by R.C. de Visser - Netherlands on Oct 26^th, 2011, 9:45pm

Hi,

I always make a backup before I start editing a .cfg file

Anyhow I will change the Windows06.
I have tried to modify again,
but the INS NAV MODE still doesn't work

The buttons remains in the same position I can't switch them on.

I will copy and paste the Windows06 and 09 into the .cfg File

Tnx,

Ronald

Title: Re: The INS Mode selector in the RFP does not work
Post by Marco Ravanello on Oct 27^th, 2011, 9:44am

> but the INS NAV MODE still doesn't work
> The buttons remains in the same position I can't switch them on.

Beware those switches will start to work only if the corresponding INS unit is alighed and "ready for NAV".

Marco

Title: Re: The INS Mode selector in the RFP does not work
Post by R.C. de Visser - Netherlands on Oct 27^th, 2011, 8:19pm

Quote:

Beware those switches will start to work only if the corresponding INS unit is alighed and "ready for NAV".

This is a major point I didn´t know.

Allthough I printed the whole set of manuals, but I can't get the meaning of the numbers. I also printed out the referals of the .cfg from Microsoft 69 pages but it remains a little "magic" to me.

Perhaps you can explain the four numbers x, y, dx, dy, mentioned in the manual. Somehow I can't get the idea behind these syntaxes and I can't find the answeres in the Microsoft manual concerning the .cfg files

Title: Re: The INS Mode selector in the RFP does not work
Post by Gianfranco Corrias on Oct 27^th, 2011, 9:17pm

If I well undertstood Marco asked me to explain the differences of SIDs made in the realty and FS9.
First FS9 is an USA simulator and for this reason flights wherever you are flying are managed by ATC in the USA way.
For instance some KJFK SIDs in the realty:
Bette three departure
Greki three departure
Hapie three departure
Merit three departure
are:RWY HDG or HDG assigned by ATC to 5000ft and via radar vectors to the final SID FIX(Bette,Greki,Hapie or Merit).
Within FS9 are:
Rwy HDG to assigned altitude then radar vectors to be positioned on track.
I repeat this is the clearence within FS9 wherever you are flying in the world.
In the realty the SID isn't part of FLT plan because SID is changing everytime due to weather,traffic etc.The first waypoint(loaded in the INS as position 2) should be the final SID FIX.
So in the realty after T.O. the assigned SID must be flown by pilots manually,but within FS9 after T.O. there are always RWY HDG and radar vectoring.For this reason you have to follow ATC vectors and when the ATC instruct you to resume normal navigation you have to steer the plane to the next waypoint and connect the INS with the A/P to go there.
How to make it?
for short distance to the next waypoint you can use the WPT CHG 0-X INSERT.For remarkable distance in order do not to be off track for long time you can select on CDU XTR/TKE and steer the plane by the HDG selector in order to reduce the TKE quite to zero.At this point being on track you can connect the INS to A/P.
Gianfranco

Title: Re: The INS Mode selector in the RFP does not work
Post by Marco Ravanello on Oct 28^th, 2011, 11:14am

> Perhaps you can explain the four numbers x, y, dx, dy, mentioned in
> the manual. Somehow I can't get the idea behind these syntaxes and I
> can't find the answeres in the Microsoft manual concerning the .cfg
> files

Very simple!
When you define a gauge, in the cfg file, you have obviously to set where it gets displayed on the screen. To do that you have to define the coordinates of the gauge TOP LEFT corner (which are the first x, y two numbers) but you also have to specify gauge WIDTH (dx value) and HEIGHT (dy).

Hope this helps
Marco

Title: Re: The INS Mode selector in the RFP does not work
Post by R.C. de Visser - Netherlands on Oct 29^th, 2011, 7:54pm

Gianfranco wrote:

If I well undertstood Marco asked me to explain the differences of SIDs made in the realty and FS9.
First FS9 is an USA simulator and for this reason flights wherever you are flying are managed by ATC in the USA way.
For instance some KJFK SIDs in the realty:
Bette three departure
Greki three departure
Hapie three departure
Merit three departure
are:RWY HDG to 5000ft and via radar vectors to the final SID FIX(Bette,Greki,Hapie or Merit).
Within FS9 are:
Rwy HDG to assigned altitude then radar vectors to be positioned on track.
I repeat this is the clearence within FS9 wherever you are flying in the world.
In the realty the SID isn't part of FLT plan because SID is changing everytime due to weather,traffic etc.The first waypoint(loaded in the INS as position 2) should be the final SID FIX.
So in the realty after T.O. the assigned SID must be flown by pilots manually,but within FS9 after T.O. there are always RWY HDG and radar vectoring.For this reason you have to follow ATC vectors and when the ATC instruct you to resume normal navigation you have to steer the plane to the next waypoint and connect the INS with the A/P to go there.
How to make it?
for short distance to the next waypoint you can use the WPT CHG 0-X INSERT.For remarkable distance in order to not be off track for long time you can select on CDU XTR/TKE and steer the plane by the HDG selector in order to reduce the TKE quite to zero.At this point being on track you can connect the INS to A/P.
Gianfranco

I am going to try this :o

Title: Re: The INS Mode selector in the RFP does not work
Post by R.C. de Visser - Netherlands on Oct 29^th, 2011, 8:02pm

Marco_Ravanello wrote:

Thank you. This is helpfull Information. It is realy that simple.

Title: Re: The INS Mode selector in the RFP does not work
Post by Marco Ravanello on Oct 30^th, 2011, 2:22pm

And if you don't specify DY (the fourth number, which is NOT mandatory) the gauge bitmap height will be calculated based on given width, maintaining a correct aspect ratio of the main gauge bitmap.