CAPTAIN SIM FORUM
707 Captain >> 707 Captain >> CIVA INS - THE ONLY THREAD PLEASE
https://www.captainsim.org/forum/csf.pl?num=1285100008

Message started by Barb. on Sep 21st, 2010 at 8:13pm

Title: CIVA INS - THE ONLY THREAD PLEASE
Post by Barb. on Sep 21st, 2010 at 8:13pm
Heya all

I've been trying to use the INS with the 707 but I can't seem to be able to turn it on. When I switch MSU to 'STBY' nothing happens, as if the gauge was not powered. I've looked in the CIVA manuals but apparently the INS will automatically detect aircraft generators power when engines are running, which was the case. What am-I doing wrong here ?

Cheers

Nico

Title: Re: CIVA INS trouble
Post by PeterL on Sep 23rd, 2010 at 3:41pm
Hi Nico,
Well, I've the same problem, can't understand why. After switching the MSU to STBY no red digits appear on the CDU. I checked with FS9/Legendary 707 on which I've installed CIVA as well and there it works as it should. As I also have the out of memory problem I give up for the moment.

Peter


Title: Re: CIVA INS trouble
Post by Martin Martinov on Oct 1st, 2010 at 12:00pm
Same here with the SP1...The VC INS shows the current position. The actual integrated system doesn't light up at all. No matter if it is in STBY, ALIGN or NAV. The ADEU doesn't respond either...  Any ideas?

Title: Re: CIVA INS trouble
Post by Markoz on Oct 1st, 2010 at 1:00pm

Captain Sim 2 wrote on Sep 27th, 2010 at 4:36pm:
3D CIVA has been added to the 1.1 VC, but to provide full compatibility we need some tech info from the CIVA INS developer. Unfortunately there is no response so far, so the CIVA will be INOP in 1.1 VC .

Here is the answer you seek. It comes from the 707 Captain - It'd be nice forum.

Mark

Title: Re: CIVA INS trouble
Post by CoolP on Oct 1st, 2010 at 3:13pm
Haven't tried the standard Civa panel.cfg coming with the product. I just jumped in and modded it to show the double INS and they are both working, numbers lit, aligned, flight plan loaded.

Here's a shot I took while editing the panel.cfg
http://img245.imageshack.us/img245/767/civa.th.jpg

The only downside so far are the missing DME readings on all instruments. I already wrote a ticket.
The pressurization isn't working too it seems  :(

Shame on me, DME is working!
Just switch the little DME button on the pedestal to "DME". Sorry, Captain Sim, disregard this part of the ticket.

Haven't flown her a while it seems.

Title: Re: CIVA INS trouble
Post by Martin Martinov on Oct 1st, 2010 at 6:05pm
MarkoZ thanks for the imput however the question here is with a bit different orientation.

In VC the CIVA is not working, except is very nicely modelled and I hope one day I will be able to control from there.

I am talking about the 2D pop up windows which should contain the actual working system. I have used the panel_CIVA.cfg file in the v.1.1 package (as instructed in the manual). The popup windows are showing up, but the screens are dark, no matter what position the selector key is (OFF-SDBY-ALLIGN-NAV-ATT). The route loader doesnt seem to react too.. The power is coming from all generators, every other system on the aircraft is working.

What am I missing??...

Title: Re: CIVA INS trouble
Post by CoolP on Oct 1st, 2010 at 6:30pm
Ok, as written in your other thread, the panel.cfg from Captain Sim including the Civa is working, so no error by design here.
See:
http://img841.imageshack.us/img841/6404/workingh.th.jpg


If power is on the plane (batteries are sufficient for the INS), the avionics are on (radios, DME and instruments are working) and the Civa MSU switch set from off to standby, the unit should light up, even at lowest dimmed settings.
Don't forget the INS/Doppler switch.

If not, I think the .isd file might be corrupt. This is sort of a config file for the INS.

Exit FSX, go to the Civa subfolder and find csx701.isd. Delete or move it, reboot and try again.
Maybe this helps here.
Feel free to report back, Martin.

Title: Re: CIVA INS trouble
Post by Barb. on Oct 1st, 2010 at 10:40pm
OK, this might be a dumb question but it might also just be the answer to my earlier question... How much time does it take for the INS to warm up after you switch it on ? I know it will take some time to align, but how long before the unit is powered up and functional and ready to be aligned ?

Cheers

Nico

Title: Re: CIVA INS trouble
Post by Trailboss on Oct 1st, 2010 at 10:54pm
CoolP,

Can you give me the specifics of the modifications you made to files to install the double INS?

Thanks in advance

Title: Civa Double INS Integration
Post by CoolP on Oct 1st, 2010 at 10:56pm
General Civa items:

- The Civa INS on the 707 needs a manual installation of the current (1.51) Civa INS gauge. Get it here http://www.simufly.com/ins/

- To convert a normal FS9/FSX flight plan to one which the Civa ADEU reader can read, you need this tool
PlanConverter http://darkc.no-ip.org/trac/planconverter

- You need to activate the other panel.cfg file in SimObjects\Airplanes\variant's name\panel. Just rename "CIVA_panel.cfg" to "panel.cfg" to activate it. Backup first!

You won't receive any official support on this because this is a user made modification.



Civa Double INS Integration

(updated to 1.3 and all variants of the 707 because some values changed)

http://img709.imageshack.us/img709/4226/allpanels.th.jpg
http://img819.imageshack.us/img819/4223/allpanelsnight.th.jpg

(don't worry, this only shows the panels, not an active navigation in progress)

Captain Sim did some remarkable job on this nice plane and on the VC integration of one unit too (although function here is an item to come in a future service pack, so currently, this is a VC dummy).
I felt free to mod the given panel.cfg for the Civa integration to enable the second unit (as 2D only) and some additional bells and whistles.

In detail:
- modification on the simicon panel (only two buttons now, because I've combined MSU and ADEU in one window instead of two)
- backlit buttons all the way (can easily be changed, if you like)
- quick Civa access on the default Autopilot popup
- two CDUs, two MSUs, one ADEU reader (if you need two, tell me and I will change the setup), twin Nav switch, double update flags for visual verification of a DME update in progress
- quick open/close buttons on all panels


I hope you like it and I appreciate any comments about this small text work.

Here's how it's done

[edit]For the guys who don't want to go through the manual steps here, you can download a complete set of the necessary panel.cfg files. They include all current 707 variants and work with 1.3. http://www.mediafire.com/?449zzlmmy9dpmpl[/edit]

1. First, as we are going to use the panel.cfg with the default Civa integration (named "CIVA_panel.cfg"), make a backup of it and open with notepad or another text editor.

We are talking about the 707 Version 1.3, please make sure to install the update first.


2. You should have the Civa INS installed. Version 1.51 was used here. It's free and all docs come with it. Enjoy!


3. Working in the panel.cfg, [Window Titles] section

Delete all entries after #05 and replace them with these two

Code (]
Window06=INS Control Display Units
Window07=INS MSU+ADEU[/code):


This will give us only two windows for the INS were MSU+ADEU are combined in one and the CDUs with the flags and switches in the other


4. Look at the [Window00] section and delete everything (in that section) after ;CIVA

Replace it with
[code]gauge04=../civa/INS!CduPanelIconB,   0,  652, 24, 24, 11041
gauge05=../civa/INS!AdeuPanelIconB,  0,  676, 24, 24, 11042

This sets up the new buttons for the following windows.
Caution: You will have to alter the gauge numbers (04 and 05 in this example) if you are using the Freighter, since he already has a gauge04 there, so Civa must go to 05 and 06.

On the VC-137, the icons look "stretched" (which doesn't come from my mod though). You can change this back to normal with replacing 144

Code (]gauge02=Captain_Sim.x703.tools!icons, 0,508,24,144[/code):
with 96 on the final number.
To make the Civa buttons fit then, change 652->604 and 676->628 in their lines then.


5. Delete the [Window04] section completely (this is the 2D AP popup) and replace it with this one

[code][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=..\..\CS_B707-300\panel\Captain_Sim.x707.P11!P11_ap,0,0,384,100
gauge01=../civa/INS!CduPanelIconB,    385, 0, 20, 20, 11041
gauge02=../civa/INS!AdeuPanelIconB,    385, 20, 20, 20, 11042


This gives you another placement of the AP popup and two backlit buttons on its right side for quick access to CDU and MSU+ADEU.


6. Delete [Window06], [Window07] and [Window08] completely and replace those old three windows with our new two ones


Code (];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


This defines the new combined windows as described above.


7. Go to the [VCockpit01] section and add
[code]gauge27=../civa/INS!Config,         0,    0,  0, 0, CS707 // this gauge will initialize the Civa units, "CS707.Isd" is the file name of the config file in the Civa folder[/code]
after the last gauge (26)


8. Last step, save the panel.cfg as "panel.cfg" (you might want to backup the default one first) to make sure it's active and fire up FSX together with the 707.
It should look like the screenshot above and it works like the Civa integration before with the additional units and flags.

[edit]The INS/Doppler switch has to be in the "INS" position, battery and avionics must be turned on, the DME switches on the radios should be on and the AP will follow the INS commands when in NAV mode only.
How to warm up and align the Civa INS is described in the extensive documentation that comes with this free gauge. Just look into the "Civa" folder.
[/edit]

Sadly, I won't take any responsibility for harming your system or installation with these text changes, neither does Captain Sim of course.

Do this at your own risk and hopefully enjoy the now enhanced INS experience.



Feel free to comment here.
I'm no programmer, I'm just a guy that has read the Civa manuals and started working on the modification after getting the idea from Cthulhus.

Title: Re: CIVA INS trouble
Post by Martin Martinov on Oct 2nd, 2010 at 6:32am
Finally after some testing and comparing with the working INS on my Captain 727 I figured out what was the problem.

A simple missing line from the panel.cfg (which was provided with the package)

Here goes:

[Window06]
size_mm=250,196
background_color=16,16,16
window_pos=0.300, 0.070
position=0
visible=0
ident=11041
no_luminous=1
gauge00=../civa/INS!Config,         0,    0,  0, 0, csx701
gauge01=../civa/INS!Cdu1, 0, 0, 250, 196

The file csx701.Isd is not created in the CIVA folder when this line is missing, and this is preventing the gauge from initializing....

Title: Re: CIVA INS trouble
Post by Barb. on Oct 2nd, 2010 at 7:42am

Quote:
look for the Civa manuals, they are free and present if you have installed the gauge (which is free too).
You'll have to use them anyway because a fresh approach on the INS navigation takes some time to understand.


Couldn't find anything about warmup time in the manual. As I read it, switch it on and it lights up, it's the align phase that takes a while.

Might need to have a closer look at that manual though because the INs I'm used to using (SimCheck) doesn't have a MSU and has been simplified in some regards.

Cheers

Nico

Title: Re: CIVA INS trouble
Post by CoolP on Oct 2nd, 2010 at 12:28pm
Martin, that line IS provided in the panel.cfg coming with the plane. I've just checked it.
Otherwise my installation would not have been operational.

Here's the excerpt from the original Captain Sim file

Code (][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
;CIVA
gauge03=../civa/INS!Config,         0,    0,  0, 0, csx701


So whatever mixed up your default panel.cfg, kill it!  ;D

Barb., maybe we're talking about different things. You asked me about the warm up time and I responded with the align time.
So maybe my fault here not to have answered correctly.

Read the "QuickReferenceGuideCompact", warm up is mentioned there.

You are right, the Simcheck Airbus has a easy INS compared to the Civa and I'm looking forward to the SP2 of it, because then Civa might work in that plane too.
The Simcheck version isn't bad at all but I'd like to use Civa on all planes, seeing it drift, having a need for DME update and so on.
Optics are much nicer on the easy INS but functions are what makes the Civa special.

Title: Re: CIVA INS trouble
Post by Martin Martinov on Oct 2nd, 2010 at 4:40pm
Well alright, but in my cfg file the line was missing and I don't know why. A couple of users here are having similar problem like mine (INS 2D popup panel showing up but not working) so I hope they read this post to find the answer...

Title: Re: CIVA INS trouble
Post by CoolP on Oct 2nd, 2010 at 6:10pm
It's not I don't trust you, but did you look at your window00 entry in that config file?
Just asking because you've posted your window06 entry.

I find it hard to believe that our installers of the CS 707 1.1 differ much and therefor I assume we are having the same config files delivered.

But this question isn't so important of course. Glad to read your INS ins working then.

Title: Double Civa INS - a short how to
Post by CoolP on Oct 2nd, 2010 at 1:09pm
You can find the how to for the Civa Double INS Integration on page 1 of this thread.
I'm sorry for inconvenience, the mods moved the separate thread into this one.

Title: SimFly INS Navigation Sistems problem
Post by Alberto on Oct 4th, 2010 at 2:53pm
Hi Forum,


I have succesfull installed the INS by SimFly.

It works, but When I try to push the NAV button by the panel, (to activate the navigation as HDG) it don't works!

Please Help!

Title: Re: SimFly INS Navigation Sistems problem
Post by Markoz on Oct 4th, 2010 at 3:01pm
Two things Alberto.

FIRST.....DO NOT TURN THE DOPPLER NAVIGATION KNOB ON THE OVERHEAD TO REC ONLY/ON/TEST. It appears to be causing CTD's. Even more so IF you are using the INS as well.

Ok. I gave you the warning and that's now out of the way.

Secondly. On the lower front panel, in front of the Captains seat, is a switch that needs to be switched to INS. Open the cover and you will see it is set to DNS. As for the rest of the procedure with the CIVA-INS, you need to read the documentation that came with it. I'm still coming to grips with this too. It's a bit of hard work, but fun.

Mark

Title: Re: SimFly INS Navigation Sistems problem
Post by Alberto on Oct 4th, 2010 at 3:19pm
You are absolutly the best Mark!

Now it works correctly!  :-* ;D

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Jesse on Oct 4th, 2010 at 7:09pm
I need help getting the Civa INS to work. Kind of got bits and pieces around the forum, this is what I have done so far. I changed the name of the files as per. Marko's suggestion and that helped. Inserted the missing line in the cfg file as suggested by coolp? and that also helped. Auto-pilot doesn't work and I can't insert west co-ordinates. If someone has complete info on how to fix it all starting from the beginning I will so much appreciate it. I will be forever indebted to you.   :-/

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Oct 4th, 2010 at 9:48pm
Finally I made my first flight with Civa INS. It was flawless. Worked perfect. It was  a 6 waypoints flight. First leg I helped Civa intercept the course, then over 400 miles  crossed over 5 waypoints, CIVA INS  was on target. :) :)

A/P also worked well. :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Oct 5th, 2010 at 12:35am
Hi Jesse.

A big part of using the CIVA INS is that you need to read the manuals/documents that come with it. I'm still going back to go over exactly what to do because I hav not fully got a hold of it. I'm close, but not quite there.

Out of curiosity. What is "Inserted the missing line in the cfg file as suggested by coolp?"? I don't think I'm using it.

At the moment I am using a slightly modified civa_panel.cfg (renamed panel.cfg, of course). I press Shift+7 (instead of shift+7, shift+8 and shift+9) and all three parts of the INS show up together. It's my preference. ;)

Mark


Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Jesse on Oct 5th, 2010 at 1:37pm
Thanks, patience is not my greatest virtue, about the inserted line it was Martin who wrote,"Finally after some testing and comparing with the working INS on my Captain 727 I figured out what was the problem.

A simple missing line from the panel.cfg (which was provided with the package)

Here goes:

[Window06]
size_mm=250,196
background_color=16,16,16
window_pos=0.300, 0.070
position=0
visible=0
ident=11041
no_luminous=1
gauge00=../civa/INS!Config,         0,    0,  0, 0, csx701
gauge01=../civa/INS!Cdu1, 0, 0, 250, 196

The file csx701.Isd is not created in the CIVA folder when this line is missing, and this is preventing the gauge from initializing....

Title: Re: SimFly INS Navigation Sistems problem
Post by ToddL on Oct 5th, 2010 at 2:21pm

Markoz wrote on Oct 4th, 2010 at 3:01pm:
I'm still coming to grips with this too. It's a bit of hard work, but fun.

Mark


I have been watching some tutorial on you tube that have helped me alot.  The link is below to the first one - if I copied it correctly.  If I didn't just search CIVA INS tutorial and the 4 of them should pop up.

http://www.youtube.com/watch?v=nF0-ZbvjrEw&feature=related


Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Oct 5th, 2010 at 3:31pm

Jesse wrote on Oct 5th, 2010 at 1:37pm:
Thanks, patience is not my greatest virtue, about the inserted line it was Martin who wrote,"Finally after some testing and comparing with the working INS on my Captain 727 I figured out what was the problem.

A simple missing line from the panel.cfg (which was provided with the package)

Here goes:

[Window06]
size_mm=250,196
background_color=16,16,16
window_pos=0.300, 0.070
position=0
visible=0
ident=11041
no_luminous=1
gauge00=../civa/INS!Config,         0,    0,  0, 0, csx701
gauge01=../civa/INS!Cdu1, 0, 0, 250, 196

The file csx701.Isd is not created in the CIVA folder when this line is missing, and this is preventing the gauge from initializing....
Hi Jesse.

Here is a copy of [Window00] from my civa_panel.cfg (the one installed when by csx701_1100.exe):

[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
;CIVA
gauge03=../civa/INS!Config,         0,    0,  0, 0, csx701
gauge04=../civa/INS!NavModeSingle,  0,  652,  1, 1
gauge05=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041
gauge06=../civa/INS!MsuPanelIcon,   0,  676, 24, 24, 11040
gauge07=../civa/INS!AdeuPanelIcon,  0,  700, 24, 24, 11042

As you can see, the missing line isn't missing at all in mine. It has always been there. You might want to check and see if it is in your [Window00].

@Toddl. I have watched, but not studied them. Yet. ;)

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Emi on Oct 5th, 2010 at 4:34pm
Hello,
on my 707 the whole 2D INS is missing! I'm sure i have installed it and i'm also sure that it works correctly on other planes (like the well known Concorde). But on the 707 it just doesn't appear!
By the way, the panels (those opened with Shift+1) don't show the Icons for the INS either...

Does someone know what i can do to get my INS?

I have already tried to reinstall the whole thing (Aircraft AND INS) but it doesn't help!  :'(
My installed version is V1.1 (bought yesterday)

Please anybodys help is welcome...
Regards
Emi

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by rickjake on Oct 5th, 2010 at 5:09pm
Hello Emi

It sounds like you have not made the panel.cfg change. In order to get the CIVA ins to show up you have to make a small change to you panel.cfg file. CS has included a modified panel config file that will allow you to use the CIVA Ins with the minipanel.
You need to go into your FSX\Simopjects\Airplanes\CS707 folder. You should see a civa_panel.cfg file. Im not at home right now, so I am going by memory, You need to make a copy of your original panel.cfg file first or rename it something like panel_orginal.cfg. Then rename the civa_panel.cfg to panel.cfg (after you make a copy first). You should now see the mini icons for the CIVA Ins and the 2D gauges should be availabe now in fSX.

Hope this helps

Rick

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Emi on Oct 6th, 2010 at 6:21am
Thanks Rick,
now the INS works (or at least it is now inside the Boeing^^)

but what i don't understand is how to load a flightsimulator flightplan in the INS... my flightplan shows up in the ADEU Unit, but it isn't imported when i click the button for that. But also the Red Error Button doesn't illuminate, so does anyone know where the mistake now is?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Barb. on Oct 6th, 2010 at 9:12am
Emi, the flightplans you see on the ADEU are not MSFS flightplans, they are pre-saved INS flighplans that were installed with the gauge and are meant to be used as example. I believe one corresponds to the 'Tutorial' document found under 'FSX root folder/Civa/Docs' which I highly recommend you read, along with the other manuals in that folder. the videotutorials in the link above are also very useful.

Unfortunately, MSFS flighplans cannot be imported directly into the CIVA INS. You will have to enter them manually in the unit, waypoint by waypoint.

What I do when creating a flightplan is select 'direct GPS', then pick my waypoints myself along the way, noting down their coordinates on a piece of paper, because they won't appear on the MSFS 'Kneeboard - flight plan' screen. Be sure to use some VORs in your route, which you can use to update your position and re-calibrate your INS during flight.

Hope this helps

Cheers

Nico

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Emi on Oct 6th, 2010 at 1:06pm
Thanks for your help, but that's not really my problem. let me make a little summary of what i do when i want to import the flightplan:
1) i create the flightplan using Vroute (freeware)
2) i use a tool which has been delivered togeather with the concorde add-on i have, which makes the fsx flightplans into the format needed for the CIVA INS. (with the concorde this works and i can load the flightplans in the INS)
3) I select my flightplan on the ADEU unit and click the import button on it, and then the green light glows. but nothing else happens! so what do i need to do that the flightplan get's imported? (i know that it isn't imported because i look at the waypoints section on the INS)

where is my/the programms mistaked?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Alberto on Oct 6th, 2010 at 3:48pm
Hi,

I have now installed new versons of 07, and now I have INS in VC

But I have problems:

When I try to turn on STBY mode the selector of functions of the INS (from Overhed panel) it do not respond, and it not turn ON.

I have connected EXT PWR, and acrtivate it.

In previuws versons, I had CIVA panel in 2D mode, but only 2D (myself installed)

Have I to reinstall it?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Oct 6th, 2010 at 4:34pm
Alberto, unfortunately the current VC integration of Civa INS is a dummy one. So you can't turn any knobs on the overhead.

You can only go with the 2D panels if you have activated the other panel.cfg file coming with the 1.1 version.

I think that this thread already includes some tips to get it done, just read on  ;)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Tim Capps on Oct 9th, 2010 at 2:15pm
First try with the INS after studying it at 2 a.m. this morning (no, I have no life, in case you haven't guessed by now) and it worked perfectly!

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Oct 9th, 2010 at 10:03pm
Tim, hard work at unsuitable times is what a Captain's live is made off. Never mind the clock, always mind the safety of your passengers (I hope you had some).  8-)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Tim Capps on Oct 10th, 2010 at 12:43am
Now I remember the great frustration with the CIVA INS from my Ready for Pushback days.  Why do I get stuck at 6 -- alignment never counts down to 5, but stays at 6 forever?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Oct 10th, 2010 at 2:22am
Does it give you an error code then? Check all digits.

It talks to you but only uses numbers (which are described in the very good docs coming with it in the Civa\Docs folder).
My major faults when using the INS are
- wrong coordinates at "position", it therefor stops alignment
- no fresh entry of those coordinates (even when the right ones are already shown) on both units. It tends to stop there too.

I also recommend everyone to use the small hidden button on the units to get a full alignment in less time. Just hover over the srews of the units and discover this big help.

The "DisplayedStatus" pdf in Civa\Docs might help if alignment just stops and you want to find out the reason for this behavior.

The 6 to 5 phase is the critical one on the INS. If no green "nav" lights come up, user mistakes are the most possibly source of errors.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by bloodclot on Oct 10th, 2010 at 10:40am
Hello
I'm having trouble with starting the INS, the first time i loaded the airplane with the new panel (i renamed the civa to panel and vice versa)
the INS worked perfectly. But now the second time I try to make an INS flight icant start the INS, nothing happens when i put it into STBY mode, the vc dummy illuminates but not the 2d one.

I've read in another or this topic about deleting an file in the civa folder called csx701. i've deleted this file and after doing so the INS worked, but after another atempt flying the 707 there's the same issue, not being able to turn on the INS.

any ideas

regards
mikael

Title: Re: CIVA INS trouble
Post by TheFinn on Oct 10th, 2010 at 3:36pm

Martin Martinov wrote on Oct 2nd, 2010 at 6:32am:
Finally after some testing and comparing with the working INS on my Captain 727 I figured out what was the problem.

A simple missing line from the panel.cfg (which was provided with the package)

Here goes:

[Window06]
size_mm=250,196
background_color=16,16,16
window_pos=0.300, 0.070
position=0
visible=0
ident=11041
no_luminous=1
gauge00=../civa/INS!Config,         0,    0,  0, 0, csx701
gauge01=../civa/INS!Cdu1, 0, 0, 250, 196

The file csx701.Isd is not created in the CIVA folder when this line is missing, and this is preventing the gauge from initializing....


Same for me, after one flight the INS wouldnt start anymore. I added this line mentioned above and now it seems to work again.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Tim Capps on Oct 10th, 2010 at 11:16pm

CoolP wrote on Oct 10th, 2010 at 2:22am:
Does it give you an error code then? Check all digits.

It talks to you but only uses numbers (which are described in the very good docs coming with it in the Civa\Docs folder).
My major faults when using the INS are
- wrong coordinates at "position", it therefor stops alignment
- no fresh entry of those coordinates (even when the right ones are already shown) on both units. It tends to stop there too.

I also recommend everyone to use the small hidden button on the units to get a full alignment in less time. Just hover over the srews of the units and discover this big help.

The "DisplayedStatus" pdf in Civa\Docs might help if alignment just stops and you want to find out the reason for this behavior.

The 6 to 5 phase is the critical one on the INS. If no green "nav" lights come up, user mistakes are the most possibly source of errors.



No, no lights or error codes, it just sits there maddeningly on "65."  Forever.  Forever and ever.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Oct 11th, 2010 at 2:30am

Tim Capps wrote on Oct 10th, 2010 at 11:16pm:
No, no lights or error codes, it just sits there maddeningly on "65."  Forever.  Forever and ever.

I don't recall ever seeing any numbers. I just turn it on to standby for a couple of minutes, then to align. I wait until the green READY light comes on and away I go (after entering my waypoints of course).

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by rickjake on Oct 11th, 2010 at 3:00am
[color=#00ff00]Now I remember the great frustration with the CIVA INS from my Ready for Pushback days. Why do I get stuck at 6 -- alignment never counts down to 5, but stays at 6 forever? [/color]

Don't know if this may help or not, but I remember reading on another forum, that FSX has a bad habit of creaping your plane forward very slowly when parked at a gate. This can cause the INS alignment to stop because the aircraft has moved from its original positon when you started the alignment. As you know, the aircraft must remain still with engines off for the alignment to complete. Is your parking brake on when you start your alignment?
I have never experienced this myself, but I have heard of others who have. Anyway It a thought.

Rick

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by TheFinn on Oct 11th, 2010 at 5:52am
I had this behavior too that it got stuck at 6. But my plane "jumped" on the ground, so I think this was the cause. Now at another airport, where I havnt got a low-riding 707, it counts below 6 very nicely!

Dont know what my FSX did, maybe reloaded the scenery and afterward my plane startet to jump. Or it might be a problem with the add-on scenery itself due to a higher ground-level than the original FSX-standard-airport...

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by felks on Oct 11th, 2010 at 6:02am
Hi TheFinn
I too have had my 707 jump on occasions.Last noticed when taxiing @ ORBX Avalon scenery -at threshold to rwy 34 and outside northern terminal whilst taxiing past.It jumps a couple of feet ???
Maybe over sensitive to any minor elevation changes.No other products appear to do this at these locations ??
Regards
Glenn

Title: Civa INS Problem with 707 1.1 and 1.0
Post by asanal on Oct 9th, 2010 at 5:31pm
Before I installed CIVA.INS to 707 1.1 I was having  perfect flights. Now, I am having difficulties with flashing graphics as soon as I click the "Space Bar" on my keyboard. I am hoping Captain Sim will solve this problem soon.

So, I put the 707 1.1 in the hangar and pulled out 707 1.0. Here I go again. Like I didn't learn my lesson from CIVA.INS problem in 707 1.1, I installed CIVA,INS to 707.1.0. Good news is there are no flashing graphics, but there is a catch 22 in 707 1.0.

I shot engines to load CIVA INS. All went accordingly; in 7 minutes I received the "Green Light" and switched to NAV mode.
Now I am in engine starting mode. Whatever I try,  engine doesn't start. I shut down CIVA.INS and reloaded the 707 through select aircraft bar and tried to start engine.  In one attempt all engines started.  I have to shut down engines again to start CIVA.INS. Waited another 10 minutes; tried to start engines; no luck. That is the Catch 22:  in order to load CIVA, I have to shut down;  once I shut down, engines don't start.  

I already generated K# for CS. Am I the only one having this problem?
I will appreciate your input.

Sanal

Title: Re: Civa INS Problem with 707 1.1 and 1.0
Post by Markoz on Oct 10th, 2010 at 1:43am
Hi Sanal.

A lot of people had that issue of the flashing graphics/textures in v1.1, just having the VC only and NOT the VC+Passenger Cabin, which is the default after installing, got rid of the flashing graphics. See THIS TOPIC. I have done some tweaking since then, and now I don't get the flashing graphics/textures and I have the passenger cabin too.

To get your engines started, try my method HERE AND see if that helps.

Mark

Title: Re: Civa INS Problem with 707 1.1 and 1.0
Post by asanal on Oct 10th, 2010 at 4:37am
Mark,
I installed 1,1 again. and selected with out cabin. I made a test flight and there were NO  flashing.

You wrote "I don't get the flashing graphics/textures and I have the passenger cabin too."

Can you share your tweaks I can also test them.
Engines are starting.
Thanks for your advise.
Sanal


Title: Re: Civa INS Problem with 707 1.1 and 1.0
Post by Markoz on Oct 10th, 2010 at 10:01am
Hi Sanal.

Here are the ones I changed in the fsx.cfg :

[GRAPHICS]
HIGHMEMFIX=1

[BUFFERPOOLS]
Poolsize=250000000

With the bufferpools, you need to try different numbers to see what suits your graphics card. I have an Nvidia 1280MB (1.280GB GDDR5) GTX470 and have found that it is very happy with the 250000000 (250MB) setting. You might need to try different number a bit to find the number that suits your graphics card the best.

My previous graphics card, an Nvidia 1GB (GDDR3) 9800GTX+ was happy with 200000000 (200MB). Because I saw a forum topic (one of the Avsim forums) about this, and within it,  a post that said a lot of people were finding that 200000000 was the number that seemed to suit their graphics card (it worked great for me).

You will have a [GRAPHICS] segment. But you will probably need to add the [BUFFERPOOLS], just add it at the bottom of the fsx.cfg

Back up your fsx.cfg before making changes! ;)

Mark

Title: Re: Civa INS Problem with 707 1.1 and 1.0
Post by asanal on Oct 10th, 2010 at 4:29pm
Hi Mark,

I made adjustment based on my pc configuration, Now I will load Cabin+, FsPassenger, LiveATC and FsCaptain dispatcher programs and will make flight from KBWI to BGSF ( 6 Hours /Greenland) .
Lets see the result. I will inform you. :)
Sanal

Title: Re: Civa INS Problem with 707 1.1 and 1.0
Post by asanal on Oct 10th, 2010 at 4:56pm
I just loaded 707 with Cabin+ from ACE., started FSX . immediately graphic flashing started,

That is definitly same problem like JS4100 VC Cabin with High resolution. When they lowered to madium settings flashing disappeared.

Now  Captain SIM knows what  is causing the problem, they can fix it.

Title: Re: Civa INS Problem with 707 1.1 and 1.0
Post by Markoz on Oct 11th, 2010 at 2:33am
I still get the JS4100 graphics flashing occasionally. All I do is reload the plane and it goes away.

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Oct 11th, 2010 at 8:23am
To further add to my previous post above (HERE). I switched the MODE SELECTOR Knob to standby, entered my location into the INS and then turned MODE SELECTOR Knob to ALIGN. Then I turned the DATA SELECTOR Knob to DSRTK/STS and waited for the ALIGN process to finish. This time I saw the numbers descend all the way down to 05 (the green READY light came on before it got that low though). While the ALIGN process is going on, I am entering waypoints and so I never really got to see that until now.

Mark

EDIT: I added a link to the post that I was adding to.

Title: Re: Civa INS Problem with 707 1.1 and 1.0
Post by DAL 191 on Oct 11th, 2010 at 2:40pm

Markoz wrote on Oct 10th, 2010 at 10:01am:
Hi Sanal.

Here are the ones I changed in the fsx.cfg :

[GRAPHICS]
HIGHMEMFIX=1

[BUFFERPOOLS]
Poolsize=250000000

With the bufferpools, you need to try different numbers to see what suits your graphics card. I have an Nvidia 1280MB (1.280GB GDDR5) GTX470 and have found that it is very happy with the 250000000 (250MB) setting. You might need to try different number a bit to find the number that suits your graphics card the best.

My previous graphics card, an Nvidia 1GB (GDDR3) 9800GTX+ was happy with 200000000 (200MB). Because I saw a forum topic (one of the Avsim forums) about this, and within it,  a post that said a lot of people were finding that 200000000 was the number that seemed to suit their graphics card (it worked great for me).

You will have a [GRAPHICS] segment. But you will probably need to add the [BUFFERPOOLS], just add it at the bottom of the fsx.cfg

Back up your fsx.cfg before making changes! ;)

Mark


Mark
This is the entire content of my fsx.CFG graphics segment. There is no HIGHMEMFLEX anyplace in the fsx.CFG file.

[GRAPHICS]
SHADER_CACHE_PRIMED=1693458432
TEXTURE_MAX_LOAD=2048
NUM_LIGHTS=8
AIRCRAFT_SHADOWS=1
AIRCRAFT_REFLECTIONS=1
COCKPIT_HIGH_LOD=1
LANDING_LIGHTS=1
AC_SELF_SHADOW=0
EFFECTS_QUALITY=1
GROUND_SHADOWS=0
TEXTURE_QUALITY=3
IMAGE_QUALITY=0
See_Self=1
Text_Scroll=1
SHADER_CACHE_PRIMED_10=1693458432
D3D10=0

Any ideas on this issue?

Thanks
Michael Cubine

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Tim Capps on Oct 11th, 2010 at 4:36pm
Okay, better success now.  I don't think I was clearing the error messages before.  One thing I don't get is how the ADEU thing is supposed to make things easier.  Looks to me like it is at least as complicated to create the "cards."  But if someone has done some routes, maybe they could be made available for the rest of us.

Title: Re: Civa INS Problem with 707 1.1 and 1.0
Post by Markoz on Oct 11th, 2010 at 10:22pm

DAL191 wrote on Oct 11th, 2010 at 2:40pm:
Mark
This is the entire content of my fsx.CFG graphics segment. There is no HIGHMEMFLEX anyplace in the fsx.CFG file.

[GRAPHICS]
SHADER_CACHE_PRIMED=1693458432
TEXTURE_MAX_LOAD=2048
NUM_LIGHTS=8
AIRCRAFT_SHADOWS=1
AIRCRAFT_REFLECTIONS=1
COCKPIT_HIGH_LOD=1
LANDING_LIGHTS=1
AC_SELF_SHADOW=0
EFFECTS_QUALITY=1
GROUND_SHADOWS=0
TEXTURE_QUALITY=3
IMAGE_QUALITY=0
See_Self=1
Text_Scroll=1
SHADER_CACHE_PRIMED_10=1693458432
D3D10=0

Any ideas on this issue?

Thanks
Michael Cubine

Hi Michael.

Here is mine:

[GRAPHICS]
HIGHMEMFIX=1
SHADER_CACHE_PRIMED=1693500672
TEXTURE_MAX_LOAD=2048
NUM_LIGHTS=8
AIRCRAFT_SHADOWS=1
AIRCRAFT_REFLECTIONS=1
COCKPIT_HIGH_LOD=1
LANDING_LIGHTS=1
AC_SELF_SHADOW=0
EFFECTS_QUALITY=2
GROUND_SHADOWS=0
TEXTURE_QUALITY=3
IMAGE_QUALITY=0
See_Self=1
Text_Scroll=1
SHADER_CACHE_PRIMED_10=1693500672
D3D10=0


I added the HIGHMEMFIX=1 myself, it is/was not created by FSX. There are quite a few things you can add to fsx.cfg. It comes down to trial and error to find out which ones help, and how they help.

Some of this I got from the Avsim forum from Jesus Altuve (specifically for the "shattered" graphics). The rest I got from NickN's FSX tweaks (for Nvidia graphics cards) at SimForums.

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by DAL 191 on Oct 12th, 2010 at 2:58am
Mark

Thanks for the info. I am trying different things to correct a situation where the screen temporarly goes black for several seconds and then returns to normal. After quittting FSX when the flight is finished I receive a message that "The Display Driver has stopped responding but is operating normaly now". I'll keep on trying different things.

Thank you
Michael Cubine

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Oct 12th, 2010 at 11:25am
Hi Michael.

Although I haven't seen that message in quite a while, I have had it before. Maybe your settings need to lowered just a bit.

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by JayG on Oct 12th, 2010 at 3:12pm
I had it with this plane as well. As soon as I selected 'flight deck only' I havent seen it again.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Oct 21st, 2010 at 8:39pm
I've updated the Civa Double INS Integration to 1.2 of the 707 as the values in [Window00] changed slightly.

Fell free to test and comment on it again.

http://www.captainsim.org/yabb2/YaBB.pl?num=1285100008
Reply #9

Title: Clarification on installing CIVA INS Please.
Post by Jesse on Oct 22nd, 2010 at 2:07am
How about a clarification on how to install the CIVA INS in the  707. My programming knowledge is limited and I have gotten bits and pieces from all around the forum and still no results. I have tried to use the manuals that come with CIVA but I think there is a problem in translation. Can't make heads or tails out of it. Is there supposed to be three files in the 707 file for panels and what should they be called? And should they be in any specific order? What changes should we do to them and what should they be called? I have tried to modify some and it won't let me save them. Would really like to use the INS for navigation because even after reading the manuals I can't find a thing on how to use the Doppler. Is there anybody else out there with me on this?  :(

Title: Re: Clarification on installing CIVA INS Please.
Post by CoolP on Oct 22nd, 2010 at 3:58am
Don't worry, Jesse, it will surely be easier than you might currently think.

First, use this thread for questions
CIVA INS - THE ONLY THREAD PLEASE : http://www.captainsim.org/yabb2/YaBB.pl?num=1285100008
You can also look up answers there, the ones concerning the installation are very common and therefor already present.

For the Doppler, this thread will be it
Doppler Navigation SPOT ON!: http://www.captainsim.org/yabb2/YaBB.pl?num=1285938402

I recommend a forum search or just a short view in the thread list on the next support item.  ;)

Title: INS integration question.
Post by Barb. on Oct 24th, 2010 at 2:31am
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 :D

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Fahrenheit on Oct 29th, 2010 at 4:59pm
Hey Guys I have a little Problem with my INS. I entered the current position (N 40*51.8 E 017*25.6) and started alignment. But after it ran down to 6 the warn light is turning on and the errorcode 04-45 is show wich means the following reffering to the manual


Quote:

04-45 Loaded Present Position Latitude is not correct or not within operating limits (80 00.0 N or S)


But i entert 40 Degrees something so it is within the limits.  :P

Hope you have an idea whats going wrong

Thanks in advance, Kai

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Oct 30th, 2010 at 3:30am
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
http://img831.imageshack.us/img831/1193/wheree.th.jpg

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.
http://img220.imageshack.us/img220/6533/where2z.jpg
(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.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Fahrenheit on Oct 31st, 2010 at 10:22am
Found my mistake. I entered the coordinates of the first waypoint by mistake :D

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Nov 3rd, 2010 at 4:38pm
Glad to hear. Have some nice guided flights now and don't forget updating via DME tuning. Also a good practice for entering coordinates.  :P

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 7th, 2010 at 2:05pm
Guys any help appricated,

I programmed the INS, but the autopilot and display doesnt show or fly anything INS related. i thought there was an [amber] i think, pointer with a distance etc.. i cannot see it

(made sure it is in INS mode not doppler, but the two switches to nav]

P.S in the ins it self, i cannot select INS Nav 1, only NAV 2 is switchable

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Nov 7th, 2010 at 2:55pm
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

Doppler-INS.png (Attachment deleted)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 7th, 2010 at 4:25pm

I have made sure it is in the down position,

what i am interested in is the progress and buttons you have to press after takeoff to get it working

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Nov 7th, 2010 at 10:02pm
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

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 8th, 2010 at 2:19pm
Hi MArkoz,

I ment in terms of ins .

I doubt i am putting in the aircraft position and waypoints wrong, becuase i x check it with dis/time, and they are all correct,

the 707 always follows the heading and its roughly 180 degrees, no matter what my f/p is :(

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Nov 8th, 2010 at 3:07pm
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

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Nov 8th, 2010 at 7:46pm
aceridgey maybe you can post a picture where we can see the HDG bug, the AP popup and the INS popup together.

Would be easy to see if some status or switch is wrong then.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 12th, 2010 at 7:59pm
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

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Nov 12th, 2010 at 10:34pm
Hi Alex.

I can see one that could be a BIG problem. The bold line is where it is, the underlined is the problem:

[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
;CIVA
gauge03=../civa/INS!Config,         0,    0,  0, 0, CS707      <--- This should be csx701 instead
gauge04=../civa/INS!NavModeSingle,  0,  652,  1, 1
gauge05=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041
gauge06=../civa/INS!MsuPanelIcon,   0,  676, 24, 24, 11040
gauge07=../civa/INS!AdeuPanelIcon,  0,  700, 24, 24, 11042

As far as I can tell the rest is/should be fine. I'm using the single CIVA-INS unit as per the civa_panel in that comes with the 707.

Hope this helps

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 13th, 2010 at 12:01am
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

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Nov 13th, 2010 at 1:25am
You have no power to the CIVA INS? I can't figure that one out. My INS works fine as long as the power is on.

Which leads me to think this -> Are you starting from a flight that has the Avionics Master Switch OFF? Just asking to be sure I cover everything I can think of.

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 13th, 2010 at 9:43am


Mark,

By avionics you mean turning the ground power to on? setting the rotating knobs to ESS ,
Ext power
Ext power?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Nov 13th, 2010 at 1:09pm

aceridgey wrote on Nov 13th, 2010 at 9:43am:


Mark,

By avionics you mean turning the ground power to on? setting the rotating knobs to ESS ,
Ext power
Ext power?

No. My default flight for FSX is the C172, cold-n-dark except for the Master Avionics Switch. With a few of my add-on aircraft, if that switch is off, I can't get the avionics turned on without using my keyboard shortcut (CTRL+SHIFT+A). This includes what you are referring to with External Power, ESS, etc...

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 13th, 2010 at 5:47pm
still not working mark,
i will submit a ticket, but it would be nice if Captain sim would actually help out for a change.

Erm, i am now lost, i do not know what to do at all,
the VC ins lights up when i turn it to stanby, but not the 2d panels

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Nov 13th, 2010 at 10:59pm

Quote:
gauge03=../civa/INS!Config,         0,    0,  0, 0, CS707      <--- This should be csx701 instead

The marked value is just a name for the .Isd file in the civa folder. See this as some sort of saved configuration file.
You can name it anything you want and I've chosen a different name for "my" Civa installation to enable all users to go back to the default Captain Sim one without loosing any files there.

From the Civa manual

Quote:
Configuration Files (.ISD)
The ISD files, to be found in the /Civa subfolder, is where the INS system stores all its own
saved information.
By default the INS system (see "Config" gauge reference below) uses default.isd. The
system also supports custom ISD file names in order to associate each panel (where the
INS is installed) with a specific ISD file, so keeping saved data separated on a per-panel
basis.
If specified .ISD file does not exist it will be automatically created by the INS system as soon
as "Config" gauge is executed.
;)


Your installation looks ok to me.
Please go to the Civa folder, find the 707 related .Isd files and move or delete them. Restart your PC, load the 707 and try again to establish power on the Civa.

Something seems to corrupt the .Isd file from time to time, not only on my installation but on the default one too. I haven't found the trigger for this so far but starting on a fresh Isd helps here.

Don't worry, you won't lose any data by doing this. The last coordinates will always show "0" as there are no last ones available. Not a problem, you have to enter new ones anyway every time you start aligning the INS.


Please don't think that the VC INS gauge has anything to do with the real Civa INS (which is 2D only). This one is just a dummy and shows the FSX coordinates when powered.
The only linkage between this gauge and the Civa one seems to be the power switch. But it only causes the VC one to light up and this doesn't reflect any status concerning the Civa gauge.


You can't write tickets on this because this is a modification of your original installation.
Please revert back to the Captain Sim INS solution (this is the one with the single CDU) and then test again if you want to have official support on this.

My double Civa installation is not supported by Captain Sim. It can't be and it shouldn't be and nobody said that it is.
A known fact on all user made modifications.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by simbiosi on Nov 13th, 2010 at 11:13pm

aceridgey wrote on Nov 13th, 2010 at 5:47pm:
but not the 2d panels

Maybe i am wrong and maybe is nothing related but I have a strange sitution, all the INS CDU are always blank after turn knob to STBY even with APU power.
Everything light up by opening the CS AP 2d panel and all INS CDU works correctly.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Nov 13th, 2010 at 11:36pm

Quote:
Everything light up by opening the CS AP 2d panel and all INS CDU works correctly.

simbiosi, that's a good input here which might lead to a source of non working INS units.
I'll investigate on this. Thanks in the meantime.

Investigated: No source of problems here but a small advisory on the INS usage.

This line here

Quote:
gauge04=../civa/INS!Config,         0,    0,  0, 0, CS707

defines the "initial" gauge of the whole Civa installation. Regardless if you use my modification or the original one from Captain sim.

This line is located in the [Window00] entry (of panel.cfg) on both INS approaches. This means that [Window00] is the only window which can initialize the Civa INS and therefor make it work.

[Window00] is the simicons popup. You have to open this little popup once to initialize the Civa INS, otherwise it will stay black and powerless all the time.

So if you don't use the simicons at all and try to open the Civa with the Shift key combination, it won't initialize and therefor will stay black and powerless.

Captain Sim integrated the "INS!Config" entry in [Window00] and I did too, so the behavior will stay the same, regardless if you use my installation or the CS one.


For more details on this, see the text from the Civa manual

Quote:
Syntax: gaugeXX=../Civa/Ins!Config, x, y, dx, dy, NameOfTheConfigFile
Usage: MANDATORY
Window00: The gauge  MUST be placed in the main  [Window00]  section of
panel.cfg. The order is not important, it can be "appended" as the last gauge but, if
there are other INS gauges within [Window00], then this gauge MUST be the first INS
gauge to be defined.

This "must be in [Window00]" seems to come from the old 2D panel times. [Window00] was your 2D cockpit there.
As we don't have a 2D cockpit now, the initial panel is the [VCockpit01] and following ones. So if you want to enable the Civa config gauge, you have to open up a popup panel (or integrate the gauge in the VCockpit section).
But, to make complicated looking things short, initialization can easily be achieved by opening the one panel (or "window") that contains the Ins!Config gauge.

Conclusion:
The usage of the Civa INS has to be started by opening the simicons panel ([Window00], shift-1) once to enable the initialization of the INS related gauges. After this, the simicons panel isn't needed any more (for this).

If further problems arise, delete the mentioned .Isd file to allow a clean start of the gauges.

I hope this helps to understand some things.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Nov 14th, 2010 at 12:19pm

Quote:
This line is located in the [Window00] entry (of panel.cfg) on both INS approaches. This means that [Window00] is the only window which can initialize the Civa INS and therefor make it work.

I don't have to open the SimIcon Panel to get mine to work. Here is what I do once the 707 using the CIVA INS is loaded into FSX:

1) Battery.....ON
2) External Power ON (Animations Panel opened using Shift+2)
3) External Air ON.External Power.....ON (Animations Panel opened using Shift+2)
4) DC Meters Selector.....TR ESS
5) Essential Power Source Selector.....EXT PWR
6) AC Paralleling Selector.....EXTERNAL POWER
7) Engine Bleed Air Switches.....ON
8) Wing Valves.....OPEN
9) Left & Right Air-Conditioning Unit Pack Switches.....ON
10) Open INS Unit (Shift+7) and Turn MODE SELECTOR Knob to STBY

The lights come up straight away. My CIVA INS unit is ready for me to enter the coordinates and then turn the MODE SELECTOR Knob to ALIGN. I only ever press Shift+1 to bring up the SimIcons panel once in a blue moon. I can't remember the last time I did this. As you can see, pressing SHIFT+1 is not a part of my powering up the plane.

So you understand how I have my INS setup in the civa_panel that I modified to suit me. Here it is:

;CIVA
[Window06]
size_mm=250,368
background_color=16,16,16
window_pos=0.000, 0.070
position=0
visible=0
ident=11041
no_luminous=1
gauge00=../civa/INS!Config, 0, 0,   0,   0, csx701
gauge01=../civa/INS!Cdu1,   0, 0, 250, 196
gauge02=../civa/INS!Msu1, 0, 196, 250, 71
gauge03=../civa/INS!Adeu1, 0, 267, 250, 101

Oh. And here is my [Window00] from that same panel.cfg file:

[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=..\panel\Captain_Sim.x707.sys!main, 0,0, 2,2
gauge01=..\panel\Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
gauge02=..\panel\Captain_Sim.x707.tools!icons, 0,532,24,120
;CIVA
gauge03=../civa/INS!Config,         0,    0,  0, 0, csx701
gauge04=../civa/INS!NavModeSingle,  0,  652,  1, 1
gauge05=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Nov 14th, 2010 at 10:59pm
Mark, you've doubled

Quote:
../civa/INS!Config, 0, 0,   0,   0, csx701

and now you have it in Window06 and Window00.

Doesn't seem to cause a problem though. But your opening of Window06 causes the gauges to initialize (because the "INS!Config" gauge comes alive) and they therefor work, that's all.

This doubling isn't recommended by the Civa manuals but it's not forbidden too of course.

As you already have an Engineers Award on the 707, you now have a INS Navigator one too.  :) Congratulations!


You could, just for testing purposes, delete the entry in the window06 and then go with your mentioned checklist again.
If you don't open window00 (simicons panel) at all, your INS units should stay black and powerless then because the one initialization gauge ("INS!Config") doesn't get triggered to active.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Nov 15th, 2010 at 8:50am

CoolP wrote on Nov 14th, 2010 at 10:59pm:
Mark, you've doubled

Quote:
../civa/INS!Config, 0, 0,   0,   0, csx701

and now you have it in Window06 and Window00.

Doesn't seem to cause a problem though. But your opening of Window06 causes the gauges to initialize (because the "INS!Config" gauge comes alive) and they therefor work, that's all.

This doubling isn't recommended by the Civa manuals but it's not forbidden too of course.

As you already have an Engineers Award on the 707, you now have a INS Navigator one too.  :) Congratulations!


You could, just for testing purposes, delete the entry in the window06 and then go with your mentioned checklist again.
If you don't open window00 (simicons panel) at all, your INS units should stay black and powerless then because the one initialization gauge ("INS!Config") doesn't get triggered to active.

Well I'll be a monkeys uncle!

How I came to put that in Window06, I don't honestly know. My modified Window06 was just supposed to be the gauges from windows 06, 07 and 08 combined so that when I open the INS I have everything there that I want to access, without having to open window 07 or 08. OK. For some unknown reason I copied that line from Window00, seeing all those lines were below ;Civa, and knowing that Window00 was the SimIcons gauge, I shouldn't have copied anything from there.

Now. If I comment out //gauge00=../civa/INS!Config, 0, 0,   0,   0, csx701 then you are right. I have to open Window00 (Shift+1) to get the INS to come alive. My next test was to remove that line from Window00 and leave it in window06. It works that way.

THEN. To further the experiment. I removed the line from both Window00 and Window06 and placed it in the VCockpit01. It works there, although I haven't done a flight with it being in the VCockpit01, the fact that it comes alive leads me believe it will work fine.

So for me. I will keep it in Window06 and not have it in Window00 (because it isn't recommended). I have done quite a few flights using INS with the setting that way (not that it was intentional) and it worked perfectly. Although I will do a few test flights with it in the VCockpit00 and see if all goes well.

And finally. That, I believe, will explain why Alex couldn't get the INS to come alive. :D ;D

Thanks CoolP. You have been a great help in getting to the bottom of this. I'm sure Alex will appreciate it even more!

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Nov 15th, 2010 at 10:24am
I hope it helps, that's what it's for.

VCockpit entries would be the most logical solution here. The VC is the thing that you see when loading the plane, so all gauges would get initialized without a click or the need to open a popup.

I'd have to test this too and maybe we can advance the Civa mod with this new and easy setup which eliminates at least one big source of errors.

Putting it into the CDU or MSU popup window would be another easy method to get rid of this error source.
I've just placed it in window00 because the CS original panel.cfg had it there.
If you look into my 727 modification, you'll see that I didn't follow the Civa manual and placed it on the AP 2D popup, which is Window03.

Now, with me and you knowing more than before, we can maybe advance those two mods with another place for the initialization gauge of the Civa.
I'll test this soon and then maybe edit my tutorial posts here.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Nov 15th, 2010 at 4:11pm
Hi CoolP.

Why not put it with the MSU gauge? That is the gauge that you first need to open. You use it to put the INS into STBY mode, which is when the INS needs to "come alive" for the first time. Or maybe even in the INS CDU unit which is nice to have open at the time you put it into STBY. They just seem to be the obvious places to put it. Although, for me, putting it in the VCockpit00 is the best place. Definitely THE best place for those of us who start in the VC and not the 2D Cockpit. If it works fine in my tests, that's where I may leave it.

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 15th, 2010 at 4:29pm

CoolP and Mark, you are true gents!

I am not home at all for a while, so cannot test your theory out at all,

as far as i understand this is what i need to do?

1) I need to go to fsx/civa and see if there is a 707 file in there? and delete it [i cant remember a 707 file being there but i have to check again]


2) Follow CoolP set up on page one of this thread [coolp could you check its updated to 1.2 and anything else you have learnt since].

3) when i load the plane, the first thing i need to do, is press shift+1, then load up the power and the 2d ins should work fine?

I think thats all?

Alex


Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Nov 16th, 2010 at 12:54am

Quote:
3) when i load the plane, the first thing i need to do, is press shift+1, then load up the power and the 2d ins should work fine?

Exactly, that's the current way to go. Shift-1 opens the simicons panel (the small quick access buttons). Do this once and the Civa gets initialized and will start up fine.

Mark, I'll put the changes in in the next days, so that everybody gets initialized gauges right from the start.
Seems like a good finding to me, thanks for the help there guys.


I've just edited the 707 and 727 tutorial. The config entry now is in the Vcockpit section so no special user made initialization is needed anymore.
Both planes are VC only, so the initialization will start when entering the cockpit.

If one wants to go for this new version I suggest starting from the scratch (with the backup panel.cfg) to avoid any possible error sources.
See page 1 in this thread for the details.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Nov 16th, 2010 at 7:29am

aceridgey wrote on Nov 15th, 2010 at 4:29pm:
3) when i load the plane, the first thing i need to do, is press shift+1, then load up the power and the 2d ins should work fine?


Yes. That is all you need to do. For now! But only until CoolP updates the instructions on how to do the dual INS. ;)

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Nov 18th, 2010 at 7:26am
I already did, Mark.

The one gauge went into the VCockpit section, so the shift-1 usage remains to be valid for the original Captain Sim solution only while mine now initializes when loading the plane.

Thanks for your help on this, guys.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 19th, 2010 at 4:24pm
***cooolp,

I think with your latest edit, the landing gear is now not visible in external view, if you start on the ground.,

reverting back to original panel file solves the issue..

could you perhaps test this, and also copy and past the full section of your config under the gauge 27 bit,

==edit,

still no power in the +CIVA INS 2D panel

==EDIT,

ok so i think it is to do with window 06.

Like Mark on the previous page he was window 00 and window06 with the

gauge03=../civa/INS!Config,         0,    0,  0, 0, csx701



I just put that in so my config looks like this . pressed shift and 1, and it works!!
[coolp check the first post,
gauge03=../civa/INS!Config,         0,    0,  0, 0, csx701
is not under your window00, it is only 04 and 05]


[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
gauge03=../civa/INS!Config,         0,    0,  0, 0, csx701
gauge04=../civa/INS!CduPanelIconB,   0,  652, 24, 24, 11041
gauge05=../civa/INS!AdeuPanelIconB,  0,  676, 24, 24, 11042

;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!Config,         0,    0,  0, 0, csx701
gauge01=../civa/ins!Cdu1,   0,  0, 200, 158
gauge02=../civa/ins!Cdu2, 200,  0, 200, 158
gauge03=../civa/INS!UpdateFlags, 150, 160, 115, 63
gauge04=../civa/INS!CduPanelIconB,      400, 0, 20, 20, 11041
gauge05=../civa/INS!NavModeDual,      270, 160, 50, 45
gauge06=../civa/INS!AdeuPanelIconB,      400, 138, 20, 20, 11042

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 19th, 2010 at 8:58pm
sorry guys, i am giving up on this one,.

even with the lights working on ins, the 707 didnt follow the routing.

Also,

The CIVA INS software currupts my FSX, with IVAO [IVAP]
So when i start IVAP in any aircraft now i get a 30% reduction in fps.
I thought it was the FSL concorde a couple of windows installations ago, but i am 95% sure, that it is the ins panel,

Mark, CoolP i greatly appricate your help, but i have uninstalled the 707 for good,
I wish there wasnt so much strinchent rules on refunds, becuase for me i have completely wasted £45 which i cannot replace.

thanks again

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Nov 20th, 2010 at 1:45pm
The fps thing might happen because overlay panels and undocked 2D ones might interfere with the antialiasing setting of your graphic card. This is a general issue, not a special Civa INS one.
If you use a Nvidia card, try "override" instead of "enhance" in the AA policy. This can be done via the great Nvidia Inspector. Just google the phrase and you will find the downloads and guides. It's freeware.
ATI cards surely have AA triggers too and I have to state clearly that the Civa won't affect fps by design in any way so there surely is something else causing this.


As for the guidance stuff, you should make sure to have all switches set up correctly. INS aligned, Nav mode active, Nav mode switch (if using my modification) and the INS/Doppler switch on the 707 should be mentioned there.
The next thing will be the AP and FD setting. So there are some sources for "no guidance" of course.


I wouldn't blame Captain Sim for INS problems at all. This is an addon module and it works fine. We can't really rule out some more or less big error on your system or setup causing this, so the refund wish lacks a bit of an objective viewpoint in my eyes.
They mainly deliver a complete aircraft with the Doppler system. The INS is an addition (which works) but isn't necessary to drive the thing.
If I could read more complains about it, we might come to a point where CS would be to blame, but if the setup is done correctly, this additional gauge drives your AP, adds some useful data and doesn't affect the performance at all.
I know it can be unsatisfying to read this but, as I pointed out above, there are quite some settings to get mixed up. Maybe you're a victim of at least one of them and as long as the input stays diffuse, help will be somehow catchy.


I also wonder about your reports which can't be reproduced here. My modification can not for example cause any problem with the landing gear showing or not. I can't, because the gauges there aren't connected to such things in any way.
I hope you don't feel offended if I use the example of someone telling my that he pulled the plug of his monitor and now his fridge isn't working anymore. But that's pretty much my impression about some things there.

Let me assure you that I have tested my small Civa integration and I think some other guys did too (as they are using it or used it as a start point).
As we are all humans, problems and mistakes surely can arise but I can't see any of this in the tutorial and the only non-working reports so far were caused by faulty editing the stuff, which is a human factor too, no problem with that of course.

So maybe a short break from all 707 stuff will lead to a fresh minded approach after some days or so. 1.2 is working, with and without Civa INS.
One has to make sure that no other software with e. g. guidance control interferes it and as we all use our sim with loads of addons, this can sometimes be hard to oversee.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 20th, 2010 at 8:25pm

Hi coolp,

i use inspector, so AA is not done through any FSX setting..

Also,

Everytime i fly in the uk, and say, do a flight plan west,

the ins engages, and the heading selector will ALWAYS fix on north..

every time i reproduce it

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Nov 20th, 2010 at 8:43pm
i use inspector, so AA is not done through any FSX setting..
Perfect. So try the "override" instead of the "enhance" flag at the antialiasing options there and test again.
As said before, the Civa INS doesn't affect the fps at all but the handling of the antialiasing of popup windows (which is a global one for FSX) surely does.

Everytime i fly in the uk, and say, do a flight plan west,

the ins engages, and the heading selector will ALWAYS fix on north..

every time i reproduce it
I have no doubt that you can reproduce this behavior, but no one else can so far. That's an indicator of a system based or user caused error and therefor not a general fault (so far).
I'm sure we can help you here, on a user basis, but we need some information about how you get the INS ready for navigation and how you operate the AP and FD on the 707.

I also suggest to use and test the Doppler system first as this is the intended way of operating the 707. Captain Sim planned and programed her to use this while the INS is an optional thing.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by aceridgey on Nov 20th, 2010 at 8:59pm

it has been on override,
i am almost certain its the ins civa,

when i go back to it, i will learn how to fly with doppler

Title: CIVA/INS and Autopilit
Post by TurbofanDude on Jan 13th, 2011 at 12:06pm
Alright, maybe I'm stupid,
 I can't get autopilot to work. I installed the CIVA and changed the panel.cfg over, but I can't get it to work. It just turns on and that's it. As well, how does autopilot work on this thing? I put in a VOR the other day and set it to vor and it flew my the wrong direction all together. So, can somebody please explain this to me in a way a little easier to understand than the manual? (I swear I don't even see the things the CIVA tutorial is talking about)

Thanks

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Jan 13th, 2011 at 2:16pm
There is a switch on the panel in front of the pilot (with a cover over it), by default it is set to DNS, it needs to be switched to INS or the CIVA-INS wont work.

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Viethson on Jan 22nd, 2011 at 2:18pm
Hi folks,

don´t you think that the INS drifts a little bit too fast? It´s great to have an INS that realisticaly drifts but without DME update this INS is more or less useless after 10-15 minutes. That seems to be a little too fast. I mean if you cross the pond it has to work for hours until you get a chance for a DME update.
Or maybe the INS does actually not drift so much but the index is over five within 10 minutes  :o
The same INS in Concorde X works much more stable.
Is there a way to adjust the drift/index  rate?

Cheers,
Marc

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Jan 23rd, 2011 at 12:54am
Hi Marc.

I don't think that the INS drifts that much or that quickly for me. I found on a flight from SEA to HNL, in being over the Pacific for about four hours, I was about 1 mile off the track when I came within sight of the Hawaiian coast. You can align the INS once you get in range of VOR with DME in the usual way for the CIVA INS (or at least I believe you can with a single unit).

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jan 23rd, 2011 at 1:28am
Welcome back, Mark.  :)

I have to join in to Viethson's post but I wouldn't say that it drifts too fast but faster than on the Concorde for example. I usually start my DME update at the gate (if I get reception from a DME of course), so that I don't have to care much on the initial climb until level off.

Maybe they've tweak the behavior on the Conc as she really needs the accuracy there and travels a lot fast while developing a higher need for fast updates.

I'm not so much into the actual gauges and I also haven't really measured the loss if alignment, but my subjective feeling is the same as Viethson's, the gauges in our birds are more sensible.

Maybe some rw flyer can explain what actually leads to faster loss of alignment. I could image that a straight and level flight will hold the INS in shape while all turns and climbs lead to fast misalignment.
As you turn and climb out your SID, you may therefore have the highest need for an updated INS.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Viethson on Jan 23rd, 2011 at 6:38pm
Hello again,

you´re right. Maybe the INS actually doesn´t drift so much.
A normal rate would be about 2 miles per hour of operation.
I am a rw flyer, but todays INSs are linked to a FMS and so there is an INS position which is a mix of all individual INS positions a GPS position (if thus equipped) and a FMS position which is also updated by radio beacons (if no GPS avail) so there also is a radio position  :D
The radios don´t update the INS itself but the FMS position which is then presented on the nav display.
What you would check after a flight is the offset of all individual INS positions from the mixed INS position and also the ground speed after parking brakes set. After some hours it is usually showing some knots (btw 0-5). If above 5 we usually realign the INSs.
I do the GS check after the flight in FSX too and it usually shows speeds around 3-5 knots so that seems OK to me.

But what about the accuracy index? When we start with 0 after alignment can it be 5 or worse after 20min of flight?
Or is that normal? Haven´t seen a real CIVA INS working yet...

Thanks for your replys  :)
Marc

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jan 25th, 2011 at 3:23am
Maybe Lou drove some of the former INS navigated birds then.

Otherwise a former real Concorde pilot would be welcome too as this one was INS only.  :D

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Gambler on Jan 29th, 2011 at 12:36am
As I understand at present CIVA system in VC is only a pure visual joy. Yet I am curious how many CIVA systems are present in VC after panel.cfg file modification? I suppose both Bendix doppler navigation systems should be replaced by two CIVAs.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jan 29th, 2011 at 1:19pm
As I understand at present CIVA system in VC is only a pure visual joy.
That's the way it is, yes. You can show some coordinates (not the Civa processed ones, but the ones from FSX itself) and the alert signs there though. So it's partially operative if you'd like to say so.

Yet I am curious how many CIVA systems are present in VC after panel.cfg file modification? I suppose both Bendix doppler navigation systems should be replaced by two CIVAs.
That's where the tricky part comes in.

Without tweaking the Civa gauges itself (which would require knowledge and approval of course), you can place them in the VC but they will be flat and the 3D model of the airplane (which most likely isn't flat at all) then makes them look "strange" (can't describe it any better, one has to see this for himself).

The other and much more important limitation then would be that every unit can only be shown once at a time.
So while you could place some Civa CDUs in the VC, they can't be present as 2D popups too.
CDU 1 can only be shown once, so does CDU 2. Placing them both in the VC and opening up a 2D popup (for the ease of operating them) will fail and most likely make the VC ones look odd and useless.
There's some plane on the market using the Civas in the VC and on a 2D popup at the same time, but this one plane has unique Civa gauges, tweaked and protected, so we can't compare them to our freeware source here.

I've covered these limitations in another thread before, so see this as the brief version.  :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Gambler on Jan 29th, 2011 at 3:42pm
OK, let me describe what I would like to see after CIVA installation on-board CS 707:

- Virtual Cockpit: two CIVA systems replacing both Bendix doppler systems but those CIVAs would be only eye-candy mock-ups

- 2D panels: two working CIVA systems which I could use for navigation and DME course corrections

So I have one simple question: Is it possible at all after some panel.cfg tweaking?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Jan 30th, 2011 at 1:45am
Virtual Cockpit: two CIVA systems replacing both Bendix doppler systems but those CIVAs would be only eye-candy mock-ups
Captain Sim will need to model this in the VC. We can only hope they do it in a future update.

2D panels: two working CIVA systems which I could use for navigation and DME course corrections
CoolP shows how to do this in great detail HERE. It is reply #9 of this very Topic. ;)

Hope this helps.

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jan 31st, 2011 at 4:40pm
Is it possible at all after some panel.cfg tweaking?
To give a short answer with my limited knowledge: No.  :(

The VC and 2D usage (at the same time) is not available in the Civa gauges, so one has to rework them like another dev did on his bird (and his only, being protected stuff).
I remember CS stating that they've tried to write to the Civa guys (remember, this is some "older" freeware, so I actually don't know if there is a real team to write to for example).
The last information was that they didn't get an answer there. So the will from the CS side is there.
So far, I'm really pleased by the optics of that 707 VC dummy (e. g. if the lights come up, looks very nice), but sadly, it stays a dummy and the only mid-term solution to drive Civa INS in that bird is to stay 2D only.

We could do a VC only thing (no easy to operate 2D panel then) as this would be well within the Civa freeware limits, but I haven't tried this very much so far as the 3D model of the VC interferes with the actual optics of the gauges. This 3D alignment is well beyond my knowledge too.
But this 3D VC thing would also mean that you have to switch your viewpoint to "close to INS" to actually operate the units as no 2D popup would work then.
So the 2D version stays the best one to use so far and I'm ok with it.

I've four birds (three from CS) in my hangar now (one was added today hint, hint), using this setup, while another one is the thing from that other dev and with the tweaked gauges.
So I have five Civa driven aircrafts around, all of them nice and fun to fly.  :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Gambler on Jan 31st, 2011 at 8:03pm
So it looks like the best choice for CS oldies is to add two or three CIVAs in 2D panels and leave their VC untouched. Not very realistic but acceptable. Possibly CS 707 has some switch in VC to choose between INS/DNS/NAV autopilot mode.  

BTW - Could you tell me how good Doppler navigation system on 707 is?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Feb 2nd, 2011 at 1:25pm

wrote on Jan 31st, 2011 at 8:03pm:
BTW - Could you tell me how good Doppler navigation system on 707 is?

It works very well. :)

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Feb 2nd, 2011 at 5:34pm

Quote:
Possibly CS 707 has some switch in VC to choose between INS/DNS/NAV autopilot mode.

You can follow INS or Doppler (that's one switch), or just let it follow some radial or the Localizer (that's an AP mode), so all modes are operational.
Check out the 707 page at the CS shop, the manuals are free to download and you can check out details there.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Mric29 on Feb 17th, 2011 at 1:59am
How could i do to remove CIVA system in virtual cockpit?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Feb 17th, 2011 at 2:35am

Mric29 wrote on Feb 17th, 2011 at 1:59am:
How could i do to remove CIVA system in virtual cockpit?

Why would you want to do that?

But to answer your question: Yes, you could remove the texture showing up there but the 3D model (the elevation of the knobs for example) will stay as it's in the model of the plane. So you would have some black hole with a 3D structure then, if I'm assuming right.

Does the nice looking VC unit annoy or distract you? I still like it although it's a dummy unit with just some lights on.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Mric29 on Feb 17th, 2011 at 6:32pm

CoolP wrote on Feb 17th, 2011 at 2:35am:

Why would you want to do that?

But to answer your question: Yes, you could remove the texture showing up there but the 3D model (the elevation of the knobs for example) will stay as it's in the model of the plane. So you would have some black hole with a 3D structure then, if I'm assuming right.

Does the nice looking VC unit annoy or distract you? I still like it although it's a dummy unit with just some lights on.


I kept the old 3D model in 'csx701_1000' so I'm going to put it back. I don't know how to use correctly CIVA INS, so it's useless and ugly.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Feb 18th, 2011 at 7:15am

Quote:
CIVA INS, so it's useless and ugly.

Ouch, that did hurt as I'm a Civa fan.  :(
Just kidding, I'm ok with your opinion but I can tell you that when you have gotten on that tricky thing, you wanna ride it all the time.  :D
I even like watching the numbers "go by". Seems like I'm an addict, huh?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Feb 18th, 2011 at 7:47am

CoolP wrote on Feb 18th, 2011 at 7:15am:
Seems like I'm an addict, huh?

Sure does sound that way to me! ;D

If you were NOT, then we wouldn't have that great Dual INS mod for our 707. ;)

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Feb 18th, 2011 at 9:11am
And we even have to fear that it's happening again on the upcoming 737.  8-)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by gflyer on Feb 19th, 2011 at 3:14am
Cool IP.. your instructions say if I want a dual ADEU to ask for it.. I thought it was there, but when working with eyefinity I messed up my files and had to redo ur install, now I only have 1 ADEU.. Can you tell me how to get the second ADEU back?

Thanks,
Gflyer

Never mind, figured it out.. Problem I am having is get CS simicons to load with eyefinity going, doesnt display and cause corrupt mouse.. has to be a resolution problem.. any ideas?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Mar 3rd, 2011 at 8:37pm
Hi CoolIP.

I am experiencing problems with CIVA INS in 707.
Every time I open the INS, position already filled with coordinates.
I tried to fill right coordinates from Shift+z, but  INS overrides the Shift+Z  coordinates,Therefore I cant go further then  stage 6.5. :(

How can I prevent INS filling the position coordinates?
Thanks
Sanal


Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 3rd, 2011 at 9:22pm
Don't worry, those last coordinates shown are normal. These are saved in that .isd file inside the "Civa" folder, like all previous states of the device.
The "autofill" seems to arise if you enter the coordinates in the wrong format, because FSX often doesn't show a "0" (zero) where you have to enter one in the CDU.
So please check your inputs again or give me screenshot with the FSX coordinates and your input on the Civa and I might tell you what was entered wrong in that special case.  :)
Maybe this helps too. http://forum.avsim.net/topic/326447-civa-ins-issue/page__view__findpost__p__1925566

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Mar 3rd, 2011 at 11:24pm
Thanks for your reply.

1-You are right I did not entered correctly: :o
Here is the coordinates:

N25.47.09 W80.16.73

Correct entry should be:

N25479   W080167

2- During the long flight with correct coordinate entry, INS  lost signals and alignment from 0.4  went to back 9.5.

3- Here is the interesting 707 good joke on me. INS lost direction, but 707 did not.
Continue to follow flight plan next 1950 nm with out any error.

4-IF 707  internal nav system can followup the FP independently, why I am keep spending 30-45 minutes at Airport to prepare the INS navigation system? >:(

5- New 707 Extension, Will Captain Sim  remove on-realistic  Flight Plan followup and put real INS navigation system into 707 ?  :)

6- Over ocean, how can I lower 9.5 to 0.5. There is no DME/VOR available? :-?

THX :)


Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 4th, 2011 at 7:59pm
Glad to hear it works now.

I haven't really tried the deviation when losing the alignment yet, but in another thread we came to the conclusion that, from the numbers, you really lose it fast.
So I would recommend setting up the first DME update process just before starting the engines, so you will get a DME update on the first few miles of the flight where your workload is higher. Later, you can tune in the next station while already being in cruise or closer to it.
Over the ocean, you can't align and so you will lose the accuracy until getting in range of a high alt DME station. Should be around 200nm out from every coast, so enough time to be accurate over land then.

Maybe Lou can tell in more detail how they coped with the lost alignment. I don't think that they flew back to the departure airport then.  ;D
I would shout at the Flight Engineer or so, "that's why you are second officer only!, now I have to fix this".

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Mar 4th, 2011 at 9:45pm
After completion of  alignment to 5.5 and NAV is Green, Do you turn A/P selector to HDG or NAV mode for INS ?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 5th, 2011 at 7:04pm
I'm quoting myself (from p.1, in the Civa integration tutorial).  :P

Quote:
The INS/Doppler switch has to be in the "INS" position, battery and avionics must be turned on, the DME switches on the radios should be on and the AP will follow the INS commands when in NAV mode only.

That Doppler/INS switch is an important one. Saying this because I often forgot it.  :-/

Hey, guys, 1.3 is there, so I'll have to check if the tutorial is still valid and I'll also add instructions for the expansion models. I will mark it as "1.3 ready" later.

[edit]Ok, the changes are made, the mod is ready for 1.3 and all variants. Just surf to page 1 of this very thread and see for yourself.

The guys who had the 1.2 description should redo the whole stuff in 1.3, I've changed the AP window for safety reasons and a fresh start only takes you two minutes while you don't run into trouble with old values.[/edit]

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 6th, 2011 at 12:52am

CoolP wrote on Mar 5th, 2011 at 7:04pm:
Hey, guys, 1.3 is there, so I'll have to check if the tutorial is still valid and I'll also add instructions for the expansion models. I will mark it as "1.3 ready" later.

[edit]Ok, the changes are made, the mod is ready for 1.3 and all variants. Just surf to page 1 of this very thread and see for yourself.

The guys who had the 1.2 description should redo the whole stuff in 1.3, I've changed the AP window for safety reasons and a fresh start only takes you two minutes while you don't run into trouble with old values.[/edit]

Thank's for getting onto that so quickly CoolP. It will help make the transition from 1.2 to 1.3 a LOT easier! ;D I have already made the changes to to the CIVA_panel (single unit) for all the 707's (707-300, 300C, VC-137 & E-3).

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by AaronMyers on Mar 6th, 2011 at 2:38am
I used the 1.2 values on a 1.3 install and despite my flub up with the external power things seem to work fine. Are there changes in your civa config that I should update then?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Mar 6th, 2011 at 3:32am
Mark,

Is it possible if you can give Civa INS cfg file with your new updates?
Thx
Sanal

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 6th, 2011 at 8:29am

asanal wrote on Mar 6th, 2011 at 3:32am:
Mark,

Is it possible if you can give Civa INS cfg file with your new updates?
Thx
Sanal

I would love to Sanal.

BUT......I messed up bad. My weather radar, and some other gauges in the VC went missing. I have just run a repair on the 707-300 Base Pack. I'm not sure what I did, but I had a bunch of modified panel.cfg's from v1.2 in the panel folder and I obviously got confused and deleted a newer file and continued editing an older file. I don't stuff up like that very often, but I sure messed this one up good and proper. I have no real idea how or what I really did to set the mistake in motion. All I can say is that you are lucky you never heard my response (the army taught me some very nasty words)! It had my boys looking rather surprised at the commotion I was making. :-[

I had actually posted it in here, but had to delete it because it was really a crazy mess (I hope no one saw and tried to copy it). I can redo it in a while and I'll get it up here soon. Hopefully.

Mark

[edit]It's worse! It's affected the 300C, E-3 and VC-137. There all missing gauges. I must have gotten more drunk last night than I thought I had (my niece got married yesterday and I obviously drank quite a bit).[/edit]

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 6th, 2011 at 10:55am
OK. I fixed up the mess. For a while there I was making it worse with each attempt at fixing it up.

So here is what I did with the CIVA_panel:

I changed the Window Titles to this
[Window Titles]
Window00=Simicons
Window01=Animations Control
Window02=CS Weather Radar
Window03=Map
Window04=Autopilot
Window05=Crew Messenger
Window06=INS Control Display Unit
I removed the Window07 and Window08 entries because I don't need them (see the changes to Window06).

Windows00 now looks like this
[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!NavModeSingle,  0,  652,  1, 1
gauge05=../civa/INS!MsuPanelIcon,   0,  652, 24, 24, 11040
Because of the changes in Window06, I only need the one SimIcon for the CIVA-INS.

I changed Window06 to look like this:
;CIVA
[Window06]
size_mm=250,368
background_color=16,16,16
window_pos=0.0, 0.050
position=0
visible=0
ident=11040
no_luminous=1
gauge00=../civa/INS!Cdu1, 0, 0, 250, 196
gauge01=../civa/INS!Msu1, 0, 197, 250, 71
gauge02=../civa/INS!Adeu1, 0, 268, 250, 101

The 3 INS panels (CDU, MSU and ADEU) are now grouped together because I like it that way.

And finally. I placed the INS!Config into the VCockpit01 like this:
[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$FPSP
background_color=0,0,0
gauge00=Captain_Sim.x707.R01!R01_001_light, 625, 824, 56,55
gauge01=Captain_Sim.x707.R02!R02_clock, 50, 300, 155,151
gauge02=Captain_Sim.x707.R03!R03_aplight, 625, 750, 55,55
gauge03=Captain_Sim.x707.R05!R05_rmi, 275, 775, 200,200
.....
gauge26=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
gauge27=../civa/INS!Config,         0,    0,  0, 0, csx701
Placing the INS!config in the VCockpit, gets the INS initialized as soon as the 707 loads into FSX.

And it works great. :)

Mark
707-13-INS.JPG (Attachment deleted)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 6th, 2011 at 3:19pm
I'm sorry, guys, I don't get the point here.
Is there something wrong with my tutorial (which was updated to 1.3 and the expansions lately) or are you describing something else?  :-/

For the guys who had the 1.2 version of the tutorial before, there aren't big changes, only the AP popup window (which is [Window04]) had been given a "save" gauge entry to make it work for all variants.
If you just use the 707 passenger model, you don't need to change it and therefore can leave out the 1.3 update.
If you are using the variants like Cargo, E-3 or Air Force One, you have to use the new 1.3-aware entry of course.


Mark, to avoid confusion, I suggest to "mark"  ;D your Civa integration more clearly as e. g. "Single Unit integration" or so.
Otherwise a new customer or visitor stumbles upon this thread and gets all kinds of config entries, mixing them up and also (and most of all) asking questions about it, while we don't know to which edit he's referring to.

So I might accidentally answer some question the wrong way since I don't know what thing the guy is using.

[edit]So "Civa Double INS Integration" is CoolP's solution
and "Single Unit Integration" is Markoz's solution
for example.
The "default Civa Integration" (from CS itself) offers a third variant here and it really makes a difference which one is used when some questions are asked. That's my point here.  :)[/edit]


I have another suggestion, but this needs some approval from CS of course.
We could offer the complete panel.cfg file for each model. To download and to just drop into the corresponding folder.
I've avoided this for copyright reasons, but if it get's approved, I could attach all four (=all variants covered) panel.cfg files for the guys.
They would just have to backup their original stuff first while avoiding any error source there is. I would just have to make sure that those files are always updated to the current 707 build.
So currently, you would find a "1.3 panel.cfg package for Civa Double INS Integration" there.
What do you think?

So under Mark's solution there would be such a download, under mine, and so on. Just drop and forget those files, no need to read, observe or understand anything. So the workload on both sides (customer and "support") would be reduced and the integration would be made very simple.

I've just asked CS for approval, results to come.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 6th, 2011 at 4:59pm
Sorry CoolP. There is nothing wrong with you dual INS tutorial. It was just that Sanal asked if I could share mine setup and I did.

I appreciate the tutorial for the dual INS and I will use it soon. ;D

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Mar 6th, 2011 at 6:56pm
Mark,

Thank you. It is working now. ;D I was having lot of problems.

Sanal :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 6th, 2011 at 8:44pm
Ok, thanks for the confirmation though.  :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 6th, 2011 at 11:18pm
Sorry, my mistake I pushed wrong key and posted.
Any reply you have made, has a button that you can press to delete it. You only see it on YOUR replies, no-one elses . ;)

2- I cannot find Civa INS Manual
The CIVA INS manuals should be in the FSX\Civa\Docs\ folder

Mark
delete_reply.jpg (Attachment deleted)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Mar 6th, 2011 at 11:31pm
Thank you.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Mar 7th, 2011 at 2:59pm
Question for DME UPDATING:

Every flight during first 150 nm of Flight Plan, INS gradually starts to loose signals.It goes to 9 from 0. I establish  "DME Position Updating".
Signals slowly goes back to "0". Then during the next 150nm, it starts all over again, signal slowly goes back to 9.

Is this a normal INS procedure ? (I dont think so.Otherwise just fly VOR to VOR)
Do I need to do DME Updating always? >:(

Thx


Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 7th, 2011 at 10:29pm
You can't fly VOR to VOR if you are doing Trans Atlantic flight or, like me, doing Trans Pacific flights. SEA - HNL is a 3.5 - 4.5 hour stretch over the ocean and there are no navaids within cooee of you. It's just you and your trusty old INS.
My INS flight wasn't too bad, I was only 2 miles off the track when I got back into range of the VORs.

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 7th, 2011 at 11:34pm
Hey, guys, I've just received the approval for attaching those mentioned panel.cfg files to my tutorial post.
So if you don't want to go through all the manual steps for installation, just load that small package and pick the right cfg file. Just surf to page 1 of this thread and look for the "edited" box there.  :)
The all work for the corresponding variants if version 1.3 of the 707 is installed.

Sanal, seems like you are getting really interested in the Civa INS.  :)
First of all, you are right with your assumption, you will always have to update the INS because it's always losing its accuracy when the plane moves or shakes (which happens all the time after getting off the Gates).
So every time you don't update, accuracy slowly goes down (seems to depend on the actual shaking or course corrections made), while the opposite happens when you tune and set up a DME station for the update. So, in theory, you could tune one VOR when 200nm out, leave it there, overfly it and leave for another 200nm, getting 400nm of range and low workload.
So the best time to start updating is at the Gates. Choose the nearest DME VOR station, tune it, enter the coordinates and start updating just before engine start or taxi, so you are free for the next 100+nm if you like, and the units stay aligned.

For the update itself, you need some DME VOR in range, not necessarily one which is on your route, but in reception range which gives you around 200nm of possible radius. With two CDUs, you should chose one VOR which is on your route (you will overfly it) and one with an offset. You will see that the accuracy index then stays well within limits.
The green "Nav" light shows you that an accurate navigation is possible, which leads to an index of "5" as worst one, while "0" is best. Value 6 (which is too high) corresponds to 0.5 NM of error for example.
When you are using the Civa gauges together with the Update Flags, you will see if an update is in progress or not. You can see it on the CDUs too, but these flags are easier to read. If not, one has to check the error source there as this means that his units are losing accuracy now, instead of gaining it.
http://img847.imageshack.us/img847/7494/updateinprogress.jpg

Here's what the OperationsManual states about updating.

Quote:
3 DME  POSITION  UPDATING
The INS positions may be updated by a single or dual DME (Distance Measuring Equipment). Optimum single updating may be obtained selecting a DME station “off track”, at least 15 NM off the intended track, and within 200NM of range. Optimum dual DME updating is obtained tuning a second DME along track. INS 3 does not require DME data insertion, since the INS 3 receives DME updating from INS1 and/or INS2. Tuning both VHF NAV on the same frequency will not improve the single DME updating both in efficiency and velocity.


So, as you see, there's no need to plan your flights from VOR to VOR. I'm using my Civa equipped planes on all standard routes in US and European Airspace for example. So they mainly consist of Intersections, like they would do on the FMC aircraft. DME Updates take place when the workload allows it, so the final descent or the initial climb are not distracted by this procedure.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Mar 8th, 2011 at 12:54am
Mark and CoolIP

Thank you both of you. Now I clearly understood, how to handle INS.
I think both of your dedication to INS, MAKE FEEL BAD, I decided to learn to operate  INS navigation system.

Now one more question I have:

When green light appears ,INS mode selector should be turn to NAV mode.

To connect INS to A/P:
1-Do you turn just HDG selector of A/P and also push down the INS NAV switch on cockpit pane.

Or,

2-Do you just turn A/P mode selector to NAV?

Sanal

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 8th, 2011 at 2:03am
2-Do you just turn A/P mode selector to NAV?
That should do it in the 707. Make sure to switch to INS on the Doppler/INS switch too, and everything will be set. The INS then drives the HDG bug.
The FD should go to HDG then, showing you the way to the INS driven heading value.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by yallu on Mar 11th, 2011 at 6:51am
I just installed simufly's CIVA INS and CS's panel.cfg for it. Following the YouTube tutorial... I'm propably just doing something wrong but... Just in case - Is there a known problem with setting initial fix on INS? I can set latitude (key 2/N) just fine but not longitude (key 6/E). It just won't activate the data entry mode.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 11th, 2011 at 10:27am
To set the initial location on the INS, press 2/N the number then INSERT to enter the North co-ordinate, then 6/W the number then INSERT again to enter the West co-ordinate. e.g. To enter these co-ordinates, N33o 56.33' W118o 24.2'9 press 2/N, 33563, INSERT, 6/W 118242, INSERT. ;)

Hope this helps.

Masrk

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 11th, 2011 at 3:22pm

Markoz wrote on Mar 11th, 2011 at 10:27am:

Hope this helps.

Masrk

I think Mark's account has been hacked, he now calls himself "Masrk", very suspicious.  :o
At least, the tips are still good though.  :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 11th, 2011 at 4:07pm

CoolP wrote on Mar 11th, 2011 at 3:22pm:

Markoz wrote on Mar 11th, 2011 at 10:27am:

Hope this helps.

Masrk

I think Mark's account has been hacked, he now calls himself "Masrk", very suspicious.  :o
At least, the tips are still good though.  :)
Rats! And I thought I wrote Marsk. :(

:P

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by yallu on Mar 11th, 2011 at 8:14pm
Thank you Markoz, seems to work now. My mistake was pressing INSERT twice after entering 8/N. I thought I have to get the INSERT light off before I can start inserting W/E fix. Or, in other words:

My incorrect procedure:

1. 8/N
2. lat
3. INSERT
4. INSERT
5. 6/E

-> Won't work

1. 8/N
2. lat
3. INSERT
4. 6/E
5. lon
6. INSERT

-> Works.

Anyways, thanks for the help, very kind or you. :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 12th, 2011 at 1:56am
You're welcome yallu.

Now for something I'm curious about:
Say I have a waypoint with these co-ordinates: S37o 14.49' E144o 29.24' - Would you enter them into the INS as S37144 E144292 or S37145 E144292? Because S37145 E144292 would put the INS location closer to the actual waypoint, rather than using 4, which is slightly further away. We can really do as we please, it's just that I put it as close to the waypoint as I can, so I would enter it as S37145 E144292.

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by yallu on Mar 12th, 2011 at 7:58am
That's what I did too...

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 12th, 2011 at 4:04pm
I'm working like you too, Mark. The initial fix should be as accurate as it could be while the rest is done with the DME updates. We should operate as accurate as we can to allow the system to do it the same way.
If the accuracy at the end of the flight really reflects this whole investment? I don't know, but I hope so.  :)
You won't land at the wrong airport when picking the 4 instead of the 5 there though.  ;D

By the way, did some of you ever land at the wrong one? I did once, but this wasn't a Civa flight. I laughed about this "incident" for quite some time when thinking about a real pilot acting like this.
"Oops, either they've rebuild the place since last week or I'm at the wrong place. However, lets act as if nothing happened".

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 12th, 2011 at 4:18pm
I still have problems updating the INS.

I was unsuccessful again using a single INS unit. I was within range of two VORs (Hawaii) and I selected the one that was not on the flight plan route. I couldn't find the one I wanted in the list (#1-#9). The ones that showed up, I had no information on them and to top it off, they were a long way from me.

I will do some short flights and practice updating the INS. I must be doing something wrong, although I was following the instructions in the manual. :(

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 12th, 2011 at 4:34pm
I couldn't find the one I wanted in the list (#1-#9)
At which list are you referring to, Mark (famous driver of the M-RKOZ 707)?
That flight plan converter tool gives you a list, but these items are just nice to have, not mandatory. I think that it only offers the enroute ones (you overfly them), no stations with an offset to your route.
You can use and enter every DME you can tune. It only takes the coordinates there, so maybe that's the point where you are currently struggling.
It would need some charts or flight planning tools to see them. I'm using payware but maybe some freeware or even the map in FSX (haven't tried it) shows you those coordinates.

See an example here of a neat payware tool from Aivlasoft.
http://img849.imageshack.us/img849/9913/phnl.th.jpg
So you would enter the DME update mode, enter the coordinates of the corresponding DME (after tuning it) and use its position and readings to update. 4 (DME) stations around PHNL there.

My last flight in the 727 (twin Civa INS setup), where I used one offset and one enroute DME, even gave me a "0" on the accuracy, leaving me surprised since this is the highest rank possible there. As said, one overfly and one offset DME was used and I've changed the stations when getting more than 100nm away, so no extremely high workload there when in cruise.
But the trip was only 600nm long, so maybe that has to be considered too.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by nosex on Mar 14th, 2011 at 2:30pm
Oh yes ^^"
__________________________________
หากจะมองเกมพนันใน บาคาร่าออนไลน์ ว่าเป็นศาสตร์อย่างหนึ่ง ก็จะต้องบอกว่า บาคาร่าออนไลน์ คือศาสตร์แห่งการเอาชนะอันเข้มข้น

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 14th, 2011 at 5:15pm
Am I the only one wondering to which statement he's referring to with "oh yes"?  :-?
You have a somehow sad forum name, Sir.  :P

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 15th, 2011 at 2:04am
Hi CoolP.

On my flight plan from Seattle to Honolulu, I use Jetway A331 (SEDAR to ZIGIE), V7 (ZIGIE to JOELE) and V13 (JOELE to CHK). So I don't use VOR CHK to align my INS because it is on the flight plan (remember that I am using a single INS). I try to use either the MKK or NGF VOR as neither of these are used as waypoints on the flight plan. Once I come into range of NGF a few minutes before MKK (followed by CHK a few minutes later), I start the alignment process, making sure not to initiate it until CHK has come into range (I'm not sure if that helps or not with it being part of the flight plan). It is this part, from Operations Manual, page 15, that gets me confused:

CDU Keyboard Push DME ID Number

Check that DME ID number appears on TO indicator.


as I'm not 100% sure what that means. When I get to the ID's, I go through them looking for either of the VORs I have selected to do the alignment with, and look for one with the same co-ordinates. None match. I saw one that its Longitude was close but the Latitude was in the Southern Hemisphere and not Northern Hemisphere. This left me with no VOR to use for the alignment process. I eventually tried one that was listed that had Degrees N and W, but it didn't align.

I use the FS Map (ALT > WORLD > MAP), before I leave, and obtained the Latitude and Longitude and height above sea level for both of them. Here is an image to show the area I'm using to get the VOR info from:



Am I the only one wondering to which statement he's referring to with "oh yes"? :-?
It had me wondering too. ;D

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 15th, 2011 at 4:44pm
Mark, I have a few questions towards some expressions used as I don't fully understand them.

Once I come into range of NGF a few minutes before MKK (followed by CHK a few minutes later), I start the alignment process, making sure not to initiate it until CHK has come into range (I'm not sure if that helps or not with it being part of the flight plan).
So do you start alignment there or not?
If the thing you have tuned shows a DME value and you're aware of the coordinates, just start it. There's no other dependency which has to be considered then.

That ID number being displayed corresponds to the available "presets" inside the CDU. The are available from 1-9 and can be loaded via that ADC file the plan converter creates.
In the creating process, you can mark "ADC" on some waypoints and those waypoints will appear in the ADC file then.
If you load that ADC file into the Civa (via the ADEU reader, just like you would load a flight plan, which is AWC), the coordinates from those selected waypoints are written into the preset storage.
So you just have to check their coordinates later, instead of having to enter each one manually.

You can also add waypoints to this preset list which are not part of the flight plan (all offset waypoints=stations would be handled like this).

The thinking behind this is to reduce workload and enable some planning in the question of when and where to update the CDU's position.
So these ADC files contain all your planned update stations and their coordinates with being selectable by this very ID you spoke of.

Here's an example plan from Melbourne to Brisbane.
http://img836.imageshack.us/img836/1272/planview.jpg
It gave me two AWC files (the actual plan to follow, including all the waypoints which actually get overflown by our plane), YMML to YBBN.1AWC and 2AWC. The contents of these files can be seen on the left side.

On the right side, all waypoints are shown and also their type is described. As we can only update on some VORs (DMEs to be precise), all those "Intersection" waypoints aren't of any use here.
As you see, the VORs are already marked with "ADC" but two of them are unchecked by "In plan", so they don't appear in the left side view and therefore won't be overflown by us.
What's their use?
Note: You have to manually get them out of the plan (=uncheck "In plan"), otherwise the Civa will try to overfly them.

Look at the view in the flight planner, to catch their location.
http://img859.imageshack.us/img859/1307/planinflightplanner.jpg
See them, namely DU and LAV? Those are the "spikes" on our plan. We don't want to fly that spiky, do we?
As they don't get overflown, those will be some VORs with an offset to our route. They are only included in the ADC file, not in the AWC (left side view, which defines the actual flight plan).
Lets look into this ADC file now and see.

Quote:
; ADC card for: YMML to YBBN
; Departure: YMML
; Destination: YBBN
1 S 32*33.6 E 149*35.6 00 ; MDG
2 S 32*13.2 E 148*34.6 00 ; DU
3 S 31*04.0 E 150*49.8 00 ; TW
4 S 28*05.4 E 152*55.5 00 ; LAV
;
; End Of File
;

Four VORs are named there and each of them has an ID now. This is the preset which can be used later.
So if you want to update on one of those four, make sure to load the ADC into the Civa (don't worry, it won't harm your flight plan there, it just writes into the preset memory) and later look up the corresponding ID of the "update station" to use. That's the point where CDU Keyboard Push DME ID Number enters the game.

As said, this setup requires some planning first and enables some comfortable way of updating later.
I must admit, I rarely use it, if ever. I just watch my charts, look up some DME, tune it and enter its coordinates by hand, so I get rid of this planning phase and just feed the Civa with my flight plan ADEU cards, not the ADC ones.


Your way of using the FSX map for planning is clever, Mark. Although not as comfortable and effective as some payware around, it comes for free and is already there.
So you are, once again, showing that you are a clever user of resources.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 16th, 2011 at 11:56am
So do you start alignment there or not?
Yes. I start getting the INS ready for alignment then. And no, because by the time I get it all set up and ready to start doing the actual alignment, I have moved quite a distance, which, seeing as I'm flying at 500 knots ground speed, is not surprising.

For now, you have given me another way to give updating a try. I hope I can succeed. I will keep trying until I get there. I really think that I am missing something in the manual that would allow me to do it correctly and easily. I'm patiently awaiting for the "AHA!" moment to arrive!

Your way of using the FSX map for planning is clever, Mark. Although not as comfortable and effective as some payware around, it comes for free and is already there.
So you are, once again, showing that you are a clever user of resources.
Thank you, but I'm really only using the FS Map to get the Altitude of the VOR in question (and to get a clearer image of what I'm trying to do). For flight planing I usually use Flight Sim Commander 9 which I think is a great payware program for that. Plus I get updated AIRACs every month from Navigraph.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 16th, 2011 at 5:49pm
So, what holds you back on starting the DME update then?

A common situation would be that you see some nice DME coming into range. You may also see that your CDU could need some update.

Steps are
1) tuning that station
2) switching the CDU to DME update mode
3) entering the coordinates of the tuned station
4) checking, if the rough distance (shown on the CDU display) matches the DME measured one
5) starting the update

Takes some seconds, so even 500 kts GS (I sometimes go 1100 there  :P) can't hold you back there since the measurements (CDU value and DME display) are updated in realtime.
If you use that list feature I've described, you even get faster because you don't have to enter the coordinates as they are already pre-set.
I'd like to help you with that "aha" moment, Mark, but, currently, I can't see why it's not happening.  :-/

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Mar 16th, 2011 at 6:57pm
CoolIP,
I  need to DME update in first 150 nm of my flight. Some updates either I missed or just let it go. Numbers increases to 9.4, BUT no warnings or alerts appears, INS continue to work with out any problems. FD controls the HDG and INS controls the position/legs and coordinate checks/navigation. In my last flight , when first 150 nm update required and I didn't update.   CYYR (Goose Bay) to THXF (Bermuda) INS and FD worked perfect and reached the destination with out any navigational errors. :o
How INS continue function with out DME update? :-?

Sanal

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 16th, 2011 at 7:16pm
I think that on the real thing, you would get quite some offset then. You can't measure this offset (since you haven't any reference there), that's why you would want to avoid it.  :D

Now, in our Sim, the thing loses its navigational accuracy when going above "5" on the index. So your "9" is the max offset it can show (meaning your are "unlimitedly" inaccurate) and well beyond any limits for using it as navigational source.
Now, as said before somewhere, I don't know how FSX models this wrong nav source then. It could well be that, in the Sim, your ac stays on Course even if the INS doesn't really know where you are.
We just have to be aware that this isn't the way the thing should be operated and, also from my viewpoint, not of any fun to let it just go down the drain.  :P

So far, I only ran into trouble with the updating when over the Atlantic. My index went above "5" there and I was glad to see the first land based Nav sources coming into range. So I could bring the index down to below "5" within some minutes and was well aligned when reaching the landmass.
I think that the real planes don't lose accuracy that fast when just flying some "straight" line over the Ocean, that's the only explanation I have for them since they needed to be fairly accurately placed on this NAT track system, to avoid separation issues there.
The "needed" comes from the fact that most planes (if not all) on those tracks nowadays use their GPS which offers far more better readings and also maintains itself when compared to the old INS.

But my main question still remains. What's preventing you guys from updating the INS when some DME actually IS in range?
Something unclear on the procedure?
I can only recommend an installation with those green nav flags showing. Easy to see if you failed on entering the data there, no more questioning "will it update now?". The CDU shows some indicators too, but they are far more subtle than those green flags.
Since my first Civa operations often ended in the thinking that I am updating but in the fact that I did not, this looks like a big help.

Flying above some landmass will always give you enough stations to perform an update. The only places I remember for having only a sparse placement of stations (to perform an DME update on) would be eastern Russia or something. I had tons of NDBs there but only few VOR DMEs.
Being at high altitudes, the DMEs often radiate across quite some range though, so you should be ok in cruise while on the descent, the local nav sources (and not the INS) come into play.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Mar 16th, 2011 at 8:40pm
CoolP,

"But my main question still remains. What's preventing you guys from updating the INS when some DME actually IS in range?"

I am trying so hard managing  DME update. In ten updates, I succeed  only one. :D
It looks like DME update instructions are not clear to followup. Here are some items missing  from Steps:

Steps are
1) tuning that  (VOR/DME) station
2) switching the CDU to DME update mode (Right click on 7+9 Key)
3) entering the coordinates of the tuned station

VOR Altitude insert, 3+9  then 2 key

4) checking, if the rough distance (shown on the CDU display) matches the DME measured one

Turn knob to Way point then  Press Way point change +Press 1 and insert

5) starting the update (Green light should be ON)

Sanal

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 16th, 2011 at 9:25pm
From reading your steps, I can't see any item which should prevent the update. So I'm puzzled.  :-?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 16th, 2011 at 10:41pm

CoolP wrote on Mar 16th, 2011 at 9:25pm:
From reading your steps, I can't see any item which should prevent the update. So I'm puzzled.  :-?

And now you are seeing the fun and games we are having.

I'm doing it like it says to do it (I think), but because I'm not as familiar with this as you are, I can't do it that quick (I'm reading the manual as I do it) so it can take up to 15 minutes to get everything sorted. Sometimes things don't happen like they should, as I think it should and so I have to start again. Most times I use VOR mode to finish my flight because I'm quite a long way off track.

Last time, it might have updated, but I was did something wrong, and the INS caused me change direction AWAY from the track. That really messed up my arrival plans as I wound up on the opposite side of the island to where the flight plan was. :D

I WILL get this, once I figure out what I'm doing wrong.

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 16th, 2011 at 11:28pm
At least, Mark, reading from your experience was fun.  :D

I'd really like to help you there, but I don't have a clue where to start. That turning away motion could arise when you were too late on changing the ADEU cards.
Civa then reads the next waypoint (which is one that's already been used) and tries to turn to it, so the backward direction will become active, I think.

Before this happens (running out of current waypoints), those ALERT signs will start to blink (not only light up, as they do when getting close to a new waypoint) though.
I've had this on stages where you should change the ADEU card when going from 6 to 7 on the list and the distance there was like 2nm or so.
Or I forgot to watch my Civa and only wondered why the plane takes such a strange direction. Luckily, when you realize this thing happening, the HDG mode can be used, the Civas get a new ADEU card and you then can look up the next waypoint on the Civa's list.
In the meantime, you can correct the heading roughly via the bug or, when you were to late on realizing, fly a circle and continue like nothing has happened.
Maybe say something like "oh, dear passengers, did you see that small house on the left side? So cute!".

Always have that small text file open which is compiled by the flight plan converter. It shows you all distances (so you can prepare for such short ADEU interchange times) and also lets you plan ahead.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 17th, 2011 at 3:26am
That turning away motion could arise when you were too late on changing the ADEU cards.
Civa then reads the next waypoint (which is one that's already been used) and tries to turn to it, so the backward direction will become active, I think.
It would be nice if it had been that simple, but it wasn't. I checked on that because I have had that happen before. :(

I'm planning on doing some short flights over the next few days, so I can practice the alignment process.

Mark.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 17th, 2011 at 8:19pm
The last part in assuming your position always is to listen closely to the ATC's accent.  :D
This even works when only flying online. Those NZ guys just sound different.  :P

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Mar 19th, 2011 at 4:42am
I found my two errors were causing to fail INS DME update.

After completion of VOR?DME elevation entry (3+9) you have  turn knob to  Way point Distance and verify  loaded distance=DME distance. Then press Waypoint Distance on,then press waypoint number where yo insert the coordinates, THEN Press INSERT to Light OFF. (Some reason I wasn't pressing insert off, therefore DME update was falling, then some times I was  selecting WAYP and DIS/TIME . This is another way failing the DME update.)
Now I am careful about these two mistakes, DME update working well.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 19th, 2011 at 5:54am

asanal wrote on Mar 19th, 2011 at 4:42am:
I found my two errors were causing to fail INS DME update.

After completion of VOR?DME elevation entry (3+9) you have  turn knob to  Way point Distance and verify  loaded distance=DME distance. Then press Waypoint Distance on,then press waypoint number where yo insert the coordinates, THEN Press INSERT to Light OFF. (Some reason I wasn't pressing insert off, therefore DME update was falling, then some times I was  selecting WAYP and DIS/TIME . This is another way failing the DME update.)
Now I am careful about these two mistakes, DME update working well.
I'm sure I'm not doing that, but who knows, maybe I am.
I'll let you all know how I go.

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Mar 19th, 2011 at 6:45am
Just to let you know. Although I might seem to be able to operate that Civa INS, I can't really say that its handling is somehow intuitive. In fact, it's not even close.
Which guy in the world would take three number-only display lines, a multi labelled switch and some blinking (or not blinking) signs to advertise an intuitive navigation source for aircraft? Back then, it was high-tech though.

But, I admit, it's fun later, when you get that thing running (somehow) and can experience the awkwardness of operating an oldschool airliner like our beloved 707, 727 and even the B-52.
So good luck, buddy, it's like reading the Matrix for the very first time.  8-)


Quote:
Now I am careful about these two mistakes, DME update working well.

Glad to read this. Happy and accurate flights then.  :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by kiniu on Apr 21st, 2011 at 2:53pm
Hello all simmer

Finally I install successfully civa nav panel on my 707 1.3 v
I follow the tutorial from youtube how to setup align ,add way point ....
I wait till green light goes off , take off switch to AP on nav1 setup to 1st way point freq and course as well switch NAV on autopilot and airplane always fly to hdg 300 deg. newer follow the route which is setup on civa.
I program 4 way points I also check distance between each one and is ok.
Why airplane don't want to follow the route?
Please if somebody can do any video tutorial which show how to successfully setup civa nav system I will be very grateful.
Thank you in advance and sorry for my poor English .
Kind regards
Chris

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Apr 21st, 2011 at 4:13pm
Is your DOPPLER/INS switch in the INS position then? Otherwise the AP won't listen to the Civa but waits for the Doppler system to drive him.
Does the Civa show any error code in the display?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by kiniu on Apr 21st, 2011 at 4:44pm

CoolP wrote on Apr 21st, 2011 at 4:13pm:
Is your DOPPLER/INS switch in the INS position then? Otherwise the AP won't listen to the Civa but waits for the Doppler system to drive him.
Does the Civa show any error code in the display?


Switch doppler/ins is on INS position / I read this post from 1st page and I will not ask for help if I can do something by my self .
Civa not showing any error and I align my position with engine off and park brake on.

No idea what's wrong .
Please do short video tutorial I think this will help many of us.
Regards
Chris

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Apr 21st, 2011 at 6:18pm
I'm not so much into videos, but there should already be more than a few out there.

Can you describe your current steps one by one? So we can correct or comment on them. Seems like you are missing something.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by kiniu on Apr 21st, 2011 at 7:16pm
Ok I will describe my current steps one by one on photos .
I will show everything I'm doing from cold and dark and hopefully you can find what i'm doing wrong.
Thanks for help
Chris

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by kiniu on Apr 21st, 2011 at 9:30pm
Hello all
Here it is my step by step civa programing tutorial not working as it should please find what I may do wrong

Flight plan EGSS:EDDF   CLN->TULIP->TEBRO->COL
ENGINE OFF my current position



Align my position I wait till no 95 change to 5 or less


I wait 45 min for green light to goes off but no luck so I turn nob for nav when both show (05) and light go off



I start adding way points to my route








So I have all 4 way point now let's check distance between them













After take off AP ON crs for CLN set freq SEt Switch to Nav and airplane not going direct to waypoint CLN it's look like NAV not working correctly on this time





After few min of flight HDG selector bar move to HDg 360 and plane follow this HDG And NAV is selected




I have no idea what is wrong with this system or my knowledge but I really want to use this system so if anyone can help me with this I will be very  grateful

Regards
CHris



Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Apr 22nd, 2011 at 1:11pm
Impressive work there, catching all the stuff in the screens, kiniu.
So lets see if I can help you then.

First of all, try to make use of the ADEU flight plan reader to avoid entering the waypoints manually. This manual approach may be cool on shorter routes, but as longer ones come in, you will be very tired from the typing alone and you are running the risk of entering stuff wrongly while the ADEU reader would just read your given flight plan and programs the INS for you.
You would only check the data entries then, like a good pilot would do. So much workload saved and safety gained then.
See the link to some neat flight plan converted on p.1 of this thread.

Second tip, always set up your current position in the INS. Even if it already shows the right coordinates, type them in again after bringing the units alive. See this as some sort of forced reset for the things.

Concerning your problem. When you look at the screens where the units are in the DSRTK mode, you will see that the INS actually commands the headings you are flying. So it seems like the INS to AP links works, but the commands from the INS doesn't seem to match your expectations.

For instance, this picture shows that the INS is on the leg from waypoint 0 to waypoint 1. 0 would describe your current position and 1 is the first waypoint of the plan. Now, since the unit is in the DSRTK mode, it will show you the desired track in the left side of the display. In this case, it's a heading of 96 degrees. So the unit tells you that it's now trying to track those 96 degrees which will result of a aircraft heading of around 96 since the INS does some corrections for the winds.
Your CDI shows you to be on 96 degrees, so the command chain INS to AP works. Conclusion, the technical side of your setup is ok.

http://img152.imageshack.us/img152/7095/dsrtk.th.jpg

Now, what could be the problem in your setup?
As said, the technical side is ok, the logical one seems to struggle.

You can always force the INS to reset the desired track by using the direct-to operation. If you want to go from your current position (which then will be 0) to the first waypoint of your plan, you have to press WYPT CHG, 0 (=current pos) and the number of the waypoint you'd like to go to, in this case 1. Last step, press INSERT.
The desired track then gets recalculated, showing the exact value which is necessary to turn the aircraft directly to the waypoint which was desired.
Try to perform this direct-to action when entering the runway or just before switching the AP over to the INS navigation, to ensure that the desired track calculated takes your current position into account. You have to force this recalculation to update the leg between 0 and 1.
If you, after taking off, are commanded directly to waypoint 3 of your flight plan, you therefore will press WYP CHG, 0, 3 and INSERT. Check the desired track in the INS display and then connect the INS to the AP if not already connected.

The other possible error source are wrong coordinates. If you for example mix up some numbers for the first waypoint, the INS will think of "I have to go South" while you are expecting it to go North.
So check those numbers to make sure that everything is fine. I sometimes mixed up numbers or even West and East (or North and South) coordinates, leading to a useless INS then since it takes you around the globe then.  ;D

So the pre-activation check of the INS (=before you connect it to the AP) will always mean that you look at that desired track when in the DSRTK mode. Does it match your roughly assumed flight plan route? If so, enable the AP link. If not, stay on manual headings and check the data in the units.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by kiniu on Apr 22nd, 2011 at 2:38pm
Thank You CoolP for your help I will try one more time this evening right now I'm on the middle of flying KJFK ->LSZH with MD11 much easier is fly when you have FMC :)

Thanks
Chris

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Apr 22nd, 2011 at 3:49pm

kiniu wrote on Apr 22nd, 2011 at 2:38pm:
I'm on the middle of flying KJFK ->LSZH with MD11 much easier is fly when you have FMC :)

That one is too easy! I put in all the different altitudes for the step climbs, and when the time comes, up she goes. It's a great long haul aircraft (overnight) because I can go to bed and finish in the morning, knowing that it has climbed higher to consume less fuel while I slept. :P

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by asanal on Apr 22nd, 2011 at 9:33pm
Current position, try to load LON:E0, 13,22 to INS as follows:

E not West (W) in POS ;)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by kiniu on Apr 22nd, 2011 at 10:20pm

asanal wrote on Apr 22nd, 2011 at 9:33pm:
Current position, try to load LON:E0, 13,22 to INS as follows:

E not West (W) in POS ;)

Thank you I will try and let you know .I have to get this thing working !

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Apr 23rd, 2011 at 12:29am
I can feel that you're getting closer.  :)

I hope you don't feel offended, but when I see that my problem has some logical nature, I stop the thing and approach it on the next day or so, after sleeping some time. There are days where you don't see or get a thing although it's clearly there. Next day, fresh eyes and mind, easy to catch.

If the problem is on the technical side though, I blame the devs.  :D

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Apr 23rd, 2011 at 3:21am

CoolP wrote on Apr 23rd, 2011 at 12:29am:
but when I see that my problem has some logical nature, I stop the thing and approach it on the next day or so, after sleeping some time. There are days where you don't see or get a thing although it's clearly there. Next day, fresh eyes and mind, easy to catch.

Spot on CoolP! If you get bogged down chasing a problem, you get flustered. Once you get flustered, you are bound to fail because you are no longer thinking clearly/rationally. Walk away, calm down, THEN come back and try again. Better yet, waiting until the next day (after a sleep) is a great idea. Like CoolP says. :)

Title: CIVA INS and HDG mode
Post by SoulFlight on May 20th, 2011 at 4:18pm
I recently try to learn how to use the CIVA INS and followed a youtube tutorial on how to get it steer my 707. Aligning and entering waypoints works fine so far but I have problems actually making it control my aircraft.

-when i switch one unit on and the AP to HDG mode, the AP continues to follow the manually entered heading, as if the cmd switches of my INS did not have an effect.

-in-flight position updates with VORs are not working, the green update light does not light up.

my thoughts are that I have overlooked a setup step for making the INS work correctly on the 707.

anyone got an idea what this could be?

Title: Re: CIVA INS and HDG mode
Post by CoolP on May 20th, 2011 at 4:57pm
SoulFlight, there's a dedicated Civa INS thread in this forum. Find it here, just one page away. http://www.captainsim.org/yabb2/YaBB.pl?num=1285100008  8-)
The 707 has a INS/Doppler switch and is driven by the Civa in AP "Nav" mode only, when that switch is set to INS.
You will find that being explained in the mentioned thread, so apologies for my short answer with the big, big recommendation to dive into that thread and find out about e. g. DME updates and procedures.  

Feel free to post any new Civa related question there, but please take the time to search for already given answers.  :)

Title: Re: CIVA INS and HDG mode
Post by Pinatubo on May 20th, 2011 at 5:15pm
Hi,

1) There is a switch to toggle between [DOPPLER] and [INS] navigation system. It is located at Left Forward Panel below the clock (see Flight Manual Part II – Aircraft and Systems pages 8, 22, 40 and 50..

By default, it is [DOPPLER]. Did you toggle it to [INS] before go to [AP] > [NAV]?

[DOPPLER]
- Autopilot in NAV mode tracks Doppler Navigation System
- Heading Bug on Captain's HSI controlled by HSI Heading Selector

[INS]
- Autopilot in NAV mode tracks CIVA INS
- Heading Bug on Captain's HSI controlled by CIVA INS

2) Check if [CIVA-INS Control Panel] at Overhead Panel is turned to [NAV] and the Ready Nav Green Light is ON.

Hope this help,

Pinatubo.

Title: Re: CIVA INS and HDG mode
Post by SoulFlight on May 20th, 2011 at 9:52pm
Well it seems to work after I pressed the key assigned to "NAV/GPS change"....but only for a few hours then it stopped updating as well.

Also I don't know what the sense of an INS is when I have to use a VOR to recalibrate it every 20 minutes. Then I can as well stick to VOR navigation.

Title: Re: CIVA INS and HDG mode
Post by CoolP on May 20th, 2011 at 11:05pm
The FMC birds use DME too to check and calibrate their data. Watch the autotuned stations there. They are not only used for rough estimates.
It's a difference if you can monitor external nav sources and relative positions to them or if you have an internal nav source which tells you where you are, just by calculating and watching some gyros.
Well, those sources and systems are coupled today, so a GPS works together with an IRS, getting checked with DME to achieve a high level of accuracy and also failsafe operation.
VOR broken or in maintenance? The INS will still be fine with any other DME it can receive while showing your position on a digital display instead of using a fluctuating needle on an analogue gauge.

With a VOR you can fly radial 212 until 12nm out and then turn left 30 degrees. With an INS (calibrated through any DME in 200nm range), you can fly spot on any given coordinate you enter.
It also shows you the current wind, your offset, your GS and can calculate times, speeds and headings between waypoints.
Enter any fictional waypoint of a fancy RNAV procedure and it will show and guide you to it while the VOR guy has to set up his radials to get to N 44 47.2 W 063 18.1 and may miss it when speaking about accuracy.

The INS also guides you when there's no VOR in range. It runs down on accuracy slowly, but you always have your very own nav source on board. With three units, they also crosscheck and enhance each other.

Man, I could sell those things.  ;D
But agree, you have to like these old 7 digit boxes when you operate them in the sim, where all VORs are working, where needles rarely fluctuate and where nobody gets harmed if you miss a spot.
But after a while, they will show more use than just entertaining you with their need to get an update, that's for sure.  :D

Title: Re: CIVA INS and HDG mode
Post by SoulFlight on May 20th, 2011 at 11:34pm
Ok, I'm doing something wrong then, I recalibrate, fly a leg of 300 miles, after 150 miles the new VOR is not in range but accuracy is down to 6 or something, which brings me off course good.

Also I noticed on the 707 you have to turn the autopilot mode select knob once and back to HDG, otherwise an INS programmed course change will not happen.


DAMMIT.....I used HDG mode like the tutorial told me, but in the 707 its the darn NAV MODE i need..... :D

Title: Re: CIVA INS and HDG mode
Post by CoolP on May 21st, 2011 at 9:29pm
Also I noticed on the 707 you have to turn the autopilot mode select knob once and back to HDG, otherwise an INS programmed course change will not happen.
That indeed sounds something strange since the 707 does fine on "Nav" with the Civa. No back and forth with the "HDG" mode necessary.

I used HDG mode like the tutorial told me, but in the 707 its the darn NAV MODE i need
Are you speaking of the general Civa tutorial there? Well, some planes use the Nav mode, others stay on the heading one.
But the 707 manual states the need for "Nav" I think.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by SoulFlight on May 26th, 2011 at 11:42am
Well maybe it does, I read the manual of the 707 5 months ago and installed the CIVA INS a week ago....

Anyways: is there a way to reset the entire INS unit so that all entered data is deleted? because mine seems to store slightly off coordinated all the time an thats a bit confusing.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on May 26th, 2011 at 1:14pm
That thing stores the last state in some .isd file in the Civa folder. You can delete or move it to force a fresh unit on next startup.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Mric29 on May 29th, 2011 at 11:51am

Mric29 wrote on Feb 17th, 2011 at 6:32pm:

CoolP wrote on Feb 17th, 2011 at 2:35am:

Why would you want to do that?

But to answer your question: Yes, you could remove the texture showing up there but the 3D model (the elevation of the knobs for example) will stay as it's in the model of the plane. So you would have some black hole with a 3D structure then, if I'm assuming right.

Does the nice looking VC unit annoy or distract you? I still like it although it's a dummy unit with just some lights on.


I kept the old 3D model in 'csx701_1000' so I'm going to put it back. I don't know how to use correctly CIVA INS, so it's useless and ugly.


Sorry for that, CIVA is amazing it works fine with Planconverter !  :D

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on May 29th, 2011 at 5:19pm
Yes, that's a nice freeware which really helps us sim guys to enjoy the ADEU reader.
Glad you like it.  :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Richard Portier on Jun 17th, 2011 at 2:15pm
Hello,

Where may I find a panel.cfg with all gauges installed for the B727 please.
By now I have just CIVA-CS_B727-100.zip but there are just CDU and MSU into the panel.cfg, not ADEU, Battery Parallel switch. etc...etc

I searched everywhere in the forum  :D but no way except the CIVA-CS_B727-100.zip file. I'm not experimented with panel.cfg.

Thank you in advance.

Regards,

Richard

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jun 18th, 2011 at 3:02am
I've done a tutorial for the 727 here. http://www.captainsim.org/yabb2/YaBB.pl?num=1286031420/0#0

Does that help?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Richard Portier on Jun 21st, 2011 at 12:11am
Hi CoolP,

Thank you very much for your tutorial. All is fine with the 100 model. For the 200 model I'll do it later. By now, I learn to manage the beast   ;)...

Regards,

Richard

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by tebsu on Jun 30th, 2011 at 8:02pm
Hi,

today i purchased the B707 and its really a nice bird. Especially that i can click like every switch or button.. However i have problems with the INS. Here is the way i proceeded.

1. Installed B707
2. Installed E-3A
3. Installed CIVA INS
4. removed original panel.cfg and renamed panel_CIVA (or something) to panel.cfg

Now, i start the sim, go to the MSU and put it to STBY (engines are on, elec is configured correctly and so on) but the display stays blank.. No number on it. However, the INS in the VC is going to light up.

So the problem is:

2D CIVA INS does not work
VC INS lights up but i cant do anything with it

also i noticed, that i do not have that civa ins config file which should be something like "csx701" in my FSX/CIVA folder.. someone knows why?


/edit: and in the next second, i had a solution. I switched to 2D panel and then, the 2D civa ins started.. now i switched back to VC and it still works.. weird..

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jun 30th, 2011 at 8:47pm
Glad it works now.  :)

But your experience isn't weird at all. The gauge which initializes the Civa INS in the panel.cfg coming with the plane is this one.
gauge04=../civa/INS!Config,         0,    0,  0, 0, csx701

It's located in the simicon panel (that small popup with the buttons for the other popups), which is a 2D thing. So as long as this small panel isn't used, the whole Civa gauges won't initialize and therefore stay dark.
So wherever this gauge is placed, it has to be opened at least once to allow the INS operation. Place it in the Vcockpit section for example and it works right out of the box, because the VC is the first thing you see when loading the 707.
Otherwise, just remember to always open the simicons panel once, which triggers the same.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by tebsu on Jul 1st, 2011 at 7:40am
everything works fine :) like i expect (thats so awesome because usually, there are some problems).. this aircraft makes so much fun, it is the best i have now and i do have a huge amount of aircrafts.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by buedi on Jul 14th, 2011 at 4:32pm
First, thanks to CoolP for his Tutorial of how to get a 2 INS systems working in the 707. It works very well so far. Today, while tinkering with AWC and ADC cards, I found a problem. Probably I´m doing something wrong, but I think it´s a bug in the CIVA INS Panel which can´t be fixed by us, so the only workaround would be to have a 2nd ADEU Unit. But let´s see. Here´s what I do:

- Apart from the AWC (Waypoint Cards) I also created a ADC for my DME stations I want to have while in flight.
- Before inserting the ADC card into the ADEU, I press the Remote Button on both MSUs, like I did before when reading the AWC card.
- I select the ADC card
- I read it
- The contents of the Card are only read into the MSU #1. MSU #2 does not have any DME stations in its memory.

Does this work for someone else or do we need a 2nd ADEU reader here maybe? The CIVA manual says, that the ADEU is fully aware of the Remote Switches... but, maybe it´s not?  :-/

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jul 14th, 2011 at 4:50pm
Good question, I've only used the DME data cards on the Concorde so far, but I'm typing the DME coordinates manually most of the time, on all birds. So I actually never tried the DME data input trough the ADEU on the 707 so far.
Adding the second ADEU reader isn't tricky though. The window will get a bit wider and the second gauge has to be defined and placed.

The Civa manual helps you there and if you struggle, please give me a sign and I'll look into it.  :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by buedi on Jul 14th, 2011 at 7:48pm
Thanks for your quick reply CoolP, I appreciate that very much!

I enjoy it much more when entering the coordinates by hand also. Since I was reading the Docs and tinkering with the system to find out how it works in detail, I stumbled upon the ADC (cards). Indeed it works when I add a 2nd ADEU. But I don´t know if this is intended to be like this or if this is a Bug. It doesn´t bother me really, since I enter them by hand also. I was just curious if I am doing something wrong. But maybe the Remote buttons do not work with ADC (cards) in reality too. Who knows.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by BrianG on Jul 15th, 2011 at 3:32am
Hi CoolP,
I'm just a little confused on your tutorial instructions.

Delete all entries after #05 and replace them with these two
Code:
Window06=INS Control Display Units
window07=INS MSU+ADEU

This will give us only two windows for the INS were MSU+ADEU are combined in one and the CDUs with the flags and switches in the other

Do your instruction  mean one should keep everything in Window 5, then add "Window06=INS Control Display Units
window07=INS MSU+ADEU" just below the content of window 5, then delete all of window, 6.7 and 8, leaving all the Vcockpit's in tact? I was just uncertain when it said "delete all entries after #5. Can you show me what this finished and corrected section should look like.
Thanks so much for all your time and effort in helping us with this. Much appreciated



Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jul 15th, 2011 at 3:37am
No problem, Brian.
You can download a fully edited panel.cfg from the link given in the tutorial to compare your results.
[edit]For the guys who don't want to go through the manual steps here, you can download a complete set of the necessary panel.cfg files. They include all current 707 variants and work with 1.3. http://www.mediafire.com/?449zzlmmy9dpmpl[/edit]


Quote:
Delete all entries after #05 and replace them with these two

indeed means that all entries after 05 should get replaced with the new ones posted.


buedi, I still have to test how my other Civa planes handle the remote filling of the DME coordinates with only one ADEU reader.
From the theory, this should work like on a normal flight plan card.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by giorgio nicola on Jul 26th, 2011 at 12:44pm
maybe (very probably) I'm stupid, but I don't know how to perform a DME allignment...
:-?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jul 26th, 2011 at 4:55pm
Hi, giorgio.
That process was discussed on some length in this thread, which is why the search for DME update (not alignment) gave me quite some returns.
Maybe you just jump into the linked posts and then explain which step is the most unknown/unclear one, ok?
Be aware that the docs in the Civa folder also include a tutorial which explains the single and the dual DME update in its chapters 6 and 7.
I hope this all doesn't sound too rude, but it's difficult to go through already discussed items again and again, so I just point to the 'it's already there' fact.  :)

And here are the search results. Mainly start reading at page 10 of this thread to see how Sanal and Mark went through the updating process if you like.
And you are definitely not stupid to struggle there, the thing is a somehow cryptic and tricky one, no doubts.  :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by giorgio nicola on Jul 26th, 2011 at 5:33pm
ok, I'll check at page 10...

I tried to read all thte posts untill page 5, then a great headache took me... CIVA INS is a really challenging (and interesting)app!!


Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by buedi on Jul 27th, 2011 at 7:00pm
Giorgio, you could also watch the Multipart Tutorial on Youtube:
http://www.youtube.com/watch?v=nF0-ZbvjrEw

It gives a nice introduction into the CIVA INS and allowed me to use it without reading much of the manuals. Afterwards however I read all the manuals and was tempted to create additional Tutorials because there are a lot of things not described or slightly wrong described in the Youtoube Video Tutorials. But to get started (also with the DME update), they are fantastic.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by giorgio nicola on Jul 28th, 2011 at 8:55am
thankyou guys, with this thread and the video tutorial all is getting clear!

thanks so much

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Jul 28th, 2011 at 9:54am
Once you get a good understanding of the CIVA INS I'm sure you'll enjoy using it. I know I do, and I am still learning about it. ;)

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jul 28th, 2011 at 6:02pm

Quote:
and I am still learning about it.

Me too. I e. g. learned that one should really watch the buttons pressed regarding the coordinates. I, more than once, entered E instead of W and wondered about the big offset then.
Strange thing, I never failed on N and S so far.  :o

Title: Extremely Pissed Off
Post by grant9771 on Dec 24th, 2011 at 12:37am
I cannot get the darn CIVA ins to work. I installed the ins 1st then the 707. The I make sure the ins panel cfg is right. I then go into the 707 turn on the batt and grd power and then turn the ins to standby. The thing does not turn on.

I have tried this install and reinstall 5 times today. In the sequence I mentioned above. I even reversed it on the last attempt. I have spent the last 2.5 hours messing with the Fing thing. Pleas sombody help before I break the thing.

Title: Re: Extremely Pissed Off
Post by Barnes on Dec 24th, 2011 at 12:55am
Have you already seen this thread? You may need to add a line to your panel.cfg file. If you're in a hurry and just want to set up for a single INS, see Martin's post number 10 for details. If you want to get fancy, see CoolP's post number 9.

http://www.captainsim.org/yabb2/YaBB.pl?num=1285100008

Title: Re: Extremely Pissed Off
Post by Markoz on Dec 24th, 2011 at 1:48am
The first thing to do to get the CIVA-INS to work is to rename the panel.cfg (something like panel-BAK.cfg), then rename the CIVA_panel.cfg to panel.cfg. Once FSX is started with the CS707, if you are in the VC, press F10 to go to the 2D cockpit (it is just a window with the SimIcons 2D panel) to initialize the INS in the 707. There are instructions on how to move this from [Window00] to [Vcockpit01] in the panel.cfg in the Topic that Barnes pointed out to you.

Mark

Title: Re: Extremely Pissed Off
Post by grant9771 on Dec 24th, 2011 at 1:58am
Bless you guys for the help. I was never pissed at capt. Sim. Just generally annoy
ed

Title: Re: Extremely Pissed Off
Post by grant9771 on Dec 24th, 2011 at 2:00am
I will try these ideas when I get home again thank you.

Title: Re: Extremely Pissed Off
Post by Markoz on Dec 24th, 2011 at 4:45am
We will help you as much as we can. ;)

Title: Re: Extremely Pissed Off
Post by CoolP on Dec 26th, 2011 at 4:38pm

Markoz wrote on Dec 24th, 2011 at 4:45am:
We will help you as much as we can. ;)

which isn't easy reading some strong language on the rather small sim problems. Thumbs up on the supporter's attitude.  :) And I hope grant has the INS running by now. If not, you know where to ask.

Title: Re: SimFly INS Navigation Sistems problem
Post by lucatrader on Jan 3rd, 2012 at 6:28am

Alberto wrote on Oct 4th, 2010 at 3:19pm:
You are absolutly the best Mark!

Now it works correctly!  :-* ;D


darn....i was wondering the same thing! where was the switch

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Al77994 on Jan 4th, 2012 at 7:15am
not sure if this problem was mentioned before but i'm unable to enter my longitude. has anyone scene this before?, how do you fix it?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Al77994 on Jan 4th, 2012 at 9:21am
just fixed it, i was inputting my initial position wrong.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jan 4th, 2012 at 8:59pm

Al77994 wrote on Jan 4th, 2012 at 9:21am:
just fixed it, i was inputting my initial position wrong.

Don't worry. I think the thing with the initial position is the #1 mistake for the folks being new to the INS.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by mk182 on Jan 9th, 2012 at 8:18am
I think I read somewhere that if you install the CIVA INS then the default doppler navigation becomes non operational. I've tried researching this but haven't found any answers. Is this true? If so, to fix it, do I just switch panel.cfg's when I want to use  DN or INS?

I tried using Doppler Nav for the first time in Months after only INS / VOR navigation, but I couldn't get it to work... So my guess is I'm either really dumb (which is possible  ;D ;D :D) or that I read correctly, and it doesn't work with INS installed.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Jan 9th, 2012 at 11:29am

Quote:
I think I read somewhere that if you install the CIVA INS then the default doppler navigation becomes non operational. I've tried researching this but haven't found any answers. Is this true? If so, to fix it, do I just switch panel.cfg's when I want to use  DN or INS?

Sorry, but that's not true at all.

I have the CIVA INS installed, I use the civa_panel.cfg renamed as panel.cfg (with minor modifications) and I can use Doppler Navigation, INS Navigation or follow an FS Flight Plan.

Here is how my minor modification looks:
[Window Titles]
Window00=Simicons
Window01=Animations Control
Window02=CS Weather Radar
Window03=Map
Window04=Autopilot
Window05=Crew Messenger
Window06=GPS
Window07=INS Control Display Unit

;CIVA
[Window07]
size_mm=250,368
background_color=0,0,0
window_pos=0.0, 0.050
position=0
visible=0
ident=11041
no_luminous=1

gauge00=../civa/INS!Cdu1,           0,   0, 250, 196
gauge01=../civa/INS!Msu1,           0, 197, 250,  71
gauge02=../civa/INS!Adeu1,          0, 268, 250, 101


As you can see, SHIFT+7 brings up all three parts of the CIVA-INS units. And I have added a default FS GPS 500 (SHIFT+8)as well.


Quote:
I tried using Doppler Nav for the first time in Months after only INS / VOR navigation, but I couldn't get it to work... So my guess is I'm either really dumb (which is possible  ;D ;D :D) or that I read correctly, and it doesn't work with INS installed.

‘707 Captain’ FLIGHT MANUAL Part II – Aircraft and Systems (cs707_manual2.pdf) page 22 - L17. DOPPLER-INS SWITCH
My guess is you did not switch the DOPPLER-INS SWITCH from DOPPLER to INS. ;)

Mark

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by mk182 on Jan 9th, 2012 at 5:23pm

Quote:

‘707 Captain’ FLIGHT MANUAL Part II – Aircraft and Systems (cs707_manual2.pdf) page 22 - L17. DOPPLER-INS SWITCH
My guess is you did not switch the DOPPLER-INS SWITCH from DOPPLER to INS. ;)

Mark


I figured it out. I forgot to engage it on the overhead panel.

This plane using doppler navigation combined with CINA INS is amazing! I've been flying it non-stop for about a month.

Thanks for the great answer!!

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by sieggie on Jan 11th, 2012 at 12:43am
If you add the Update indicator to the CDU you get better feedback when you use VOR updating.

[Window06]
size_mm=337,196
background_color=0,0,0
window_pos=0.300, 0.070
position=0
visible=0
ident=11041
no_luminous=1
gauge00=../civa/INS!Cdu1,       87,   0, 250, 196
gauge02=../civa/INS!UpdateFlags, 0,   0,  87,  52

As Markoz mentioned, back up the panel.cfg in case you don't like it.

This puts the Indicator at the top left of the CDU. I usually drag all the gauges to the top right so they are out of the way. I have left them separate as the bottom two gauges are only used on start up and the CDU/Update gauge is used constantly and takes up less screen space by itself.

Dave

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by mk182 on Jan 11th, 2012 at 9:26am

sieggie wrote on Jan 11th, 2012 at 12:43am:
If you add the Update indicator to the CDU you get better feedback when you use VOR updating.

[Window06]
size_mm=337,196
background_color=0,0,0
window_pos=0.300, 0.070
position=0
visible=0
ident=11041
no_luminous=1
gauge00=../civa/INS!Cdu1,       87,   0, 250, 196
gauge02=../civa/INS!UpdateFlags, 0,   0,  87,  52

As Markoz mentioned, back up the panel.cfg in case you don't like it.

This puts the Indicator at the top left of the CDU. I usually drag all the gauges to the top right so they are out of the way. I have left them separate as the bottom two gauges are only used on start up and the CDU/Update gauge is used constantly and takes up less screen space by itself.

Dave


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!!

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by mk182 on Jan 16th, 2012 at 8:10am
So, I've started having another problem.

I had programmed five way points at the beginning of my flight with the intention of programming the beginning of a STAR on my TOD in order to get set up for a visual approach to the active runway.

Now, I know how to update the INS while airborne and program way points and I thought that I had this pretty much figured out. Except that when I went to program in the next waypoint my number 1 INS would just keep flashing 0 in the to/from box.  I even tried to tell switch to main #2 INS, but it wouldn't work.

I know from experience that this usually happens when you do something wrong, and most recently I saw it when I was trying to update the INS with a VOR after entering the wrong coordinates for that VOR.

Now I simply wanted to add another way point, and I double checked (even triple checked) everything that I normally do and it still would not fly me to that way point, nor program a new one. It just kept flashing 0. Any idea on what I was doing wrong?

** In the picture I uploaded, nothing is visible in the to/from box, but its just because I happened to press print screen when it was flashing off**

GDWP.jpg (Attachment deleted)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jan 16th, 2012 at 11:46am
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.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by mk182 on Jan 16th, 2012 at 10:29pm

CoolP wrote on Jan 16th, 2012 at 11:46am:
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.


Yea, I was in update mode, but I was updating the #2 INS. I was also able to add the waypoint in the #2 INS, its just the #1 that was unresponsive.


Quote:
Can you perform a direct-to to your waypoint #6?
That would be
WY PT CHG
0-6
INSERT


I tried it a few times, and not only in the #6 spot, but in a few others, and it would always just go back to a flashing zero.

I'll see if it happens again when I'm in update mode, and if so I'll stop updating and give it a try.

Thanks for your quick reply!

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jan 18th, 2012 at 8:20pm
Hi, vans.

Quote:
however the height indicator on MHPDI when on ILS doesn't move up or down

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

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jan 18th, 2012 at 11:49pm
I think that's where the CS devs needed the input from the Civa ones. You currently only see the FSX coordinates on the VC unit.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by sieggie on Jan 19th, 2012 at 4:17pm

vans wrote on Jan 19th, 2012 at 12:54am:
Ah OK. It was a line provided on the first page of this thread - a virtual cockpit entry for the cfg -  gauge 27; I just wondered about that,  but it isn't what I thought it to be. No problem. I'm happy with the 2D panel - I just noticed earlier  when the warning light illuminated on the 2D it also illuminated on my VC unit and wondered if the digit display should be 'mimiking' the 2D.
Thanks again anyway for your help.

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.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Morten on Mar 30th, 2012 at 4:17am
I'm following the manual on alignment exactly - but getting a "Warning" and the CDU wont count down, from 9 to 0.
What is happening?  >:(

(I'm using CoolP's double Civa setup)  

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Jettrader on Mar 30th, 2012 at 8:27am

Morten wrote on Mar 30th, 2012 at 4:17am:
I'm following the manual on alignment exactly - but getting a "Warning" and the CDU wont count down, from 9 to 0.
What is happening?  >:(

(I'm using CoolP's double Civa setup)  


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

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by sieggie on Mar 30th, 2012 at 12:45pm
Does it count down at all or does it stay at 9 forever?

Dave

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Morten on Mar 31st, 2012 at 6:13am
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?  :-[  
 

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Jettrader on Mar 31st, 2012 at 8:59am
You got to be patient - alignment can take up to 15 minutes and sometimes it seems that it gets stuck at t, but just wait and it eventually will move down further.

The red light after entering the position indicates that your last aircraft position differs from your current position by more than two miles. To "reset" the memory of the INS, delete the corresponding .isd file in the civa folder (csx701.isd).

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) - the amount of alignment time will reduce significantly, yet it will still take a longer pause at a PI of 6 before going down to 5

And last but not least: Make sure you have external power connected to the aircraft, otherwise your batteries might drain which might influence the alignment process

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Apr 2nd, 2012 at 11:14am
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.



Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Morten on Apr 2nd, 2012 at 11:05pm
I read the Civas Manual forward and backward and already did all what you guys proposed, from day one! - except for deleting the isd. files which I then did today - half a six pack/1 hour later, staring into the blue.., absolutely NOTHING happens - still stuck by "65" instead of 5..!!

So I guess it must have something to do with some sort of syntax error regarding to the insertion of coordinates into this middle age contraption - or whatever...bullocks!!






 

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Jettrader on Apr 3rd, 2012 at 9:11am
how long did you wait during the alignment?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Apr 3rd, 2012 at 10:38am
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.

http://img839.imageshack.us/img839/1152/posnnl.th.jpghttp://img851.imageshack.us/img851/1078/statey.th.jpg

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.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by sieggie on Apr 3rd, 2012 at 1:27pm
Not sure if this will cause a problem but your starting location is off by .1 on both the Lat and Long. You should round the Lat up to .7 and the Long up to .3

Its a long shot but I do not see anything else you are doing wrong.

Dave

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Morten on Apr 3rd, 2012 at 2:07pm
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..!




Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Apr 3rd, 2012 at 8:40pm
Glad it's working now. Good catch on the manual. I don't know if it really makes a difference, but if you now receive a working gauge while the one before was stuck at '6', things obviously have changed.

Haha, same preference on the airport. I also have the one with the working jetways.  :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Morten on Apr 3rd, 2012 at 11:26pm

CoolP wrote on Apr 3rd, 2012 at 8:40pm:
...I don't know if it really makes a difference, but if you now receive a working gauge while the one before was stuck at '6', things obviously have changed.


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...!  :o        

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Morten on Apr 4th, 2012 at 8:25pm
Those Civa manuals, including the tutorial, are indeed impressing, however not particular educational in their context - almost as inaccessible as the FSUIPC manual, with miles of subordinate clauses making it hard to catch the point! :-)

I wonder if someone experienced with the Civa kindly would simplify the dual INS DME Update procedure by making a straight forward "to do" list?

1. a
2. b
3. c
.....etc, etc.  

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Apr 5th, 2012 at 1:51am

Morten wrote on Apr 4th, 2012 at 8:25pm:
I wonder if someone experienced with the Civa kindly would simplify the dual INS DME Update procedure by making a straight forward "to do" list?

1. a
2. b
3. c
.....etc, etc.  

I would be interested in seeing that too!

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Trailboss on Apr 5th, 2012 at 2:41am
Hi Morten,

There is a step-by-step update process in the manual that, as I remember, is included in the zipped CIVA file.  Tomorrow if I can find the pdf file I'll try to post those steps.

Jim C

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Apr 5th, 2012 at 5:28pm
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.  ;D

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by boeing247 on Jul 11th, 2012 at 1:02am
Could somebody provide instructions on how to set up the INS for the current version? I've seen the one for v1.1, but it looks like it now works in the VC. I have all the required gauges--I have installed them in a different aircraft, but how much has CS already done for the 707, and how much do I need to do?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Jul 11th, 2012 at 3:56am
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.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jul 11th, 2012 at 6:09am

boeing247 wrote on Jul 11th, 2012 at 1:02am:
Could somebody provide instructions on how to set up the INS for the current version?

First thread page, post #9. http://www.captainsim.org/yabb2/YaBB.pl?num=1285100008/9#9  :P

There's a full set of panel.cfg files if you don't like the manual steps and 've updated the tutorial every time a new 707 version came out. Means that 1.3 is in the box and verified for compatibility.  :)

For the version with the single INS and no additional gauges, the CS installer offers a pre-set panel.cfg one just has to rename. In either case, the installation of the INS gauge itself (into FSX) is mandatory.

And Mark is right, the VC INS just lights up and displays the FSX coordinates (not the one the INS computes). They were waiting for some reply from the Civa devs which never arrived as it seems. So that unfortunately still is the current state.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Jul 11th, 2012 at 12:00pm

CoolP wrote on Jul 11th, 2012 at 6:09am:
They were waiting for some reply from the Civa devs which never arrived as it seems. So that unfortunately still is the current state.
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). ::)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by DanW on Jul 11th, 2012 at 1:44pm
Thanks for that tutorial, it appears to be working quite easily and all the pretty lights come on  :D

Now if I can only find the time to sit down and learn the CIVA INS... soon.. later more like lol.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jul 11th, 2012 at 4:38pm

Markoz wrote on Jul 11th, 2012 at 12:00pm:
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). ::)

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 11th, 2012 at 1:44pm:

Now if I can only find the time to sit down and learn the CIVA INS... soon.. later more like lol.

Glad to hear it's working, Dan.  :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by boeing247 on Jul 11th, 2012 at 8:29pm
Okay, thanks, Mark and CoolP. By the way, I don't know if this was resolved earlier, but the INS won't turn on. I set it to Standby and nothing happens.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jul 11th, 2012 at 9:12pm
This should only happen when using the single INS installation. The solution is to open the simicons panel (those shortcut icons) once as this panel contains an invisible gauge which initializes the INS. After that, turn the INS on via the MSU and it should light up.

On the twin INS installation, we've worked around the issue by adding the invisible gauge to the VC itself. So when loading the plane, which always means that the VC shows up, the INS will work right out of the box.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by boeing247 on Jul 11th, 2012 at 11:58pm
Yeah, the double INS worked.

By the way, in order to save the INS state, you need to decouple it from the autopilot, but it won't let me--the switch just pops back into position. What's causing this?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jul 12th, 2012 at 8:38am
I've never tried that one. But perhaps switch the AP to HDG select and then try again. Just make sure that NAV isn't active.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Jul 12th, 2012 at 10:49am

CoolP wrote on Jul 11th, 2012 at 9:12pm:
On the twin INS installation, we've worked around the issue by adding the invisible gauge to the VC itself. So when loading the plane, which always means that the VC shows up, the INS will work right out of the box.
I dded it to the single INS as a workaround too, and it work's fine.

@boeing247

In the single INS panel.cfg (the one that was originally named CIVA-panel.cfg), change this:

[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, csx701
gauge05=../civa/INS!NavModeSingle,  0,  652,  1, 1
gauge06=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041
gauge07=../civa/INS!MsuPanelIcon,   0,  676, 24, 24, 11040
gauge08=../civa/INS!AdeuPanelIcon,  0,  700, 24, 24, 11042


to this:

[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!NavModeSingle,  0,  652,  1, 1
gauge05=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041
gauge06=../civa/INS!MsuPanelIcon,   0,  676, 24, 24, 11040
gauge07=../civa/INS!AdeuPanelIcon,  0,  700, 24, 24, 11042


And add the gauge00=Captain_Sim.x707.sys!main, 0,0, 2,2 to the bottom of [VCockpit01] like this:

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$FPSP
background_color=0,0,0
gauge00=Captain_Sim.x707.R01!R01_001_light, 625, 824, 56,55
gauge01=Captain_Sim.x707.R02!R02_clock, 50, 300, 155,151
gauge02=Captain_Sim.x707.R03!R03_aplight, 625, 750, 55,55
gauge03=Captain_Sim.x707.R05!R05_rmi, 275, 775, 200,200
gauge04=Captain_Sim.x707.R06!R06_001_light, 500,450, 58,57
gauge05=Captain_Sim.x707.R06!R06_002_light, 498,526, 58,57
gauge06=Captain_Sim.x707.R06!R06_003_light, 502,854, 58,57
gauge07=Captain_Sim.x707.R06!R06_004_light, 502,925, 60,57
gauge08=Captain_Sim.x707.R08!R08_hsi, 602, 275, 375, 374      
gauge09=Captain_Sim.x707.R09!R09_001_light, 402,126, 57,57
gauge10=Captain_Sim.x707.R09!R09_002_light, 402,202, 57,57
gauge11=Captain_Sim.x707.R10!R10_altimeter, 280,280, 190,214
gauge12=Captain_Sim.x707.R11!R11_vsi, 725,700, 289,289
gauge13=Captain_Sim.x707.R13!R13_ra, 252,499, 254,254
gauge14=Captain_Sim.x707.R13!R13_001_light, 500,675, 50,50
gauge15=Captain_Sim.x707.R14!R14_001_light, 300,0, 76,75
gauge16=Captain_Sim.x707.R17!R17_008_ndl, 500,125, 130,130
gauge17=Captain_Sim.x707.R17!R17_001_light, 0,0,   75,75
gauge18=Captain_Sim.x707.R17!R17_002_light, 75,0,  75,75
gauge19=Captain_Sim.x707.R17!R17_003_light, 150,0, 75,75
gauge20=Captain_Sim.x707.R17!R17_004_light, 225,0, 75,75
gauge21=Captain_Sim.x707.R18!R18_001_light, 925,25, 75,75
gauge22=Captain_Sim.x707.R18!R18_002_light, 925,100, 75,75
gauge23=Captain_Sim.x707.R18!R18_003_light, 925,175, 75,75
gauge24=Captain_Sim.x707.R16!R16_3D, 25,525,230,74
gauge25=Captain_Sim.x707.menu!main, 0, 0, 1, 1
gauge26=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
gauge27=../civa/INS!Config,         0,    0,  0, 0, csx701

It should initialize as soon as the 707 loads into FSX (when your Default cockpit view is set to 3-D virtual cockpit in FSX). ;)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by jetman40 on Jul 19th, 2012 at 5:34pm
Hi All

I had been trying to get my INS to work also.  I am not going to read all the post in here (it would take too long) but if someone can give me the short version on how I can get it up to run.  I have no display on it. :-[

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by jetman40 on Jul 19th, 2012 at 6:08pm
Mark

When you say to add the last line to the bottom of Vcockpit1 it does not make sense.  It says gauge 00 and the last line in Vcockpit1 is highlighted in bold.  Am I suppose to replace that line and add to it?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jul 19th, 2012 at 10:05pm

Quote:
I am not going to read all the post in here (it would take too long)

They've invented the search feature for those cases, shortly after the Internet.  ;D  :P

I guess the problem is the same as some posts before, the gauge doesn't initialize. So you could
  • open the simicons panel once before starting to work with the INS
  • move the gauge to the VCockpit section (that's what Mark shows)
  • use the twin INS mod, which already comes with the gauge at the right spot

gaugexx=../civa/INS!Config is that vital one. You just grab it from the one window and move it to Vcockpit, editing the gauge number to allow for free spot. Mark's edits show that step. See? He picked gauge27=. That text editing stuff always looks a bit cryptic at first, don't worry about that.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Jul 20th, 2012 at 2:35am

jetman40 wrote on Jul 19th, 2012 at 6:08pm:
Mark

When you say to add the last line to the bottom of Vcockpit1 it does not make sense.  It says gauge 00 and the last line in Vcockpit1 is highlighted in bold.  Am I suppose to replace that line and add to it?

Sorry. My bad. I should have written:

And add the gauge27=Captain_Sim.x707.sys!main, 0,0, 2,2 to the bottom of [VCockpit01] like this:

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$FPSP
background_color=0,0,0
gauge00=Captain_Sim.x707.R01!R01_001_light, 625, 824, 56,55
gauge01=Captain_Sim.x707.R02!R02_clock, 50, 300, 155,151
gauge02=Captain_Sim.x707.R03!R03_aplight, 625, 750, 55,55
gauge03=Captain_Sim.x707.R05!R05_rmi, 275, 775, 200,200
gauge04=Captain_Sim.x707.R06!R06_001_light, 500,450, 58,57
gauge05=Captain_Sim.x707.R06!R06_002_light, 498,526, 58,57
gauge06=Captain_Sim.x707.R06!R06_003_light, 502,854, 58,57
gauge07=Captain_Sim.x707.R06!R06_004_light, 502,925, 60,57
gauge08=Captain_Sim.x707.R08!R08_hsi, 602, 275, 375, 374      
gauge09=Captain_Sim.x707.R09!R09_001_light, 402,126, 57,57
gauge10=Captain_Sim.x707.R09!R09_002_light, 402,202, 57,57
gauge11=Captain_Sim.x707.R10!R10_altimeter, 280,280, 190,214
gauge12=Captain_Sim.x707.R11!R11_vsi, 725,700, 289,289
gauge13=Captain_Sim.x707.R13!R13_ra, 252,499, 254,254
gauge14=Captain_Sim.x707.R13!R13_001_light, 500,675, 50,50
gauge15=Captain_Sim.x707.R14!R14_001_light, 300,0, 76,75
gauge16=Captain_Sim.x707.R17!R17_008_ndl, 500,125, 130,130
gauge17=Captain_Sim.x707.R17!R17_001_light, 0,0,   75,75
gauge18=Captain_Sim.x707.R17!R17_002_light, 75,0,  75,75
gauge19=Captain_Sim.x707.R17!R17_003_light, 150,0, 75,75
gauge20=Captain_Sim.x707.R17!R17_004_light, 225,0, 75,75
gauge21=Captain_Sim.x707.R18!R18_001_light, 925,25, 75,75
gauge22=Captain_Sim.x707.R18!R18_002_light, 925,100, 75,75
gauge23=Captain_Sim.x707.R18!R18_003_light, 925,175, 75,75
gauge24=Captain_Sim.x707.R16!R16_3D, 25,525,230,74
gauge25=Captain_Sim.x707.menu!main, 0, 0, 1, 1
gauge26=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
gauge27=../civa/INS!Config,         0,    0,  0, 0, csx701

The gauges must be consecutive numbers (gauge00, gauge01, gauge02 etc. up to gauge27). By adding another gauge00 it would prevent both gauges from working.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by jetman40 on Jul 21st, 2012 at 4:59pm
Hi Mark

It did not work.  I am still getting a blank screen on the INS.  Is there a way I can get an attachment of the updated file so I can just over write the file?  I can't believe that CS did not address this problem with an update to fix it.  :(

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jul 21st, 2012 at 6:18pm

Quote:
I can't believe that CS did not address this problem with an update to fix it.   :(

The reason might be that the CS INS rendition actually does work, right out of the box.  ;)

I have to ask if you have installed the Civa INS gauge. That's a separate installer, not coming with the 707. People sometimes forget that step and I'm not sure on how to interpret the statements of yours. That's why I'm asking, just in case.

So if you make sure to install the extra Civa gauge and if you are using the separate panel.cfg which was delivered by CS (CIVA_panel.cfg, which has to be renamed to be active), the only remaining special item might be this one. One has to open the 2D simicons panel once.
[url=www.captainsim.org/yabb2/YaBB.pl?num=1285100008/256#256[/url]]www.captainsim.org/yabb2/YaBB.pl?num=1285100008/256#256[/url]

To work around that, you can tweak your cfg like Mark has shown or use the twin INS mod. And that's actually how we got here.  :)


jetman40 wrote on Jul 21st, 2012 at 4:59pm:
I am still getting a blank screen on the INS.

If the problem persists, I suggest posting a screenshot of that situation. It helps helping.  :D

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by jetman40 on Jul 22nd, 2012 at 2:59am
Is this the gauge I need to install?  
http://www.simufly.com/ins/download.html

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Jul 22nd, 2012 at 3:47am
Spot on.  :) Just run it as admin and point it to your FSX folder. Then try again with loading the 707 in FSX, but make sure to enable that special panel.cfg file for the Civa operation.

CIVA_panel.cfg in \SimObjects\Airplanes\CS_B707-300\panel has to be renamed to panel.cfg. Make a backup of the old file, just in case.

For tweaking the installation, refer to Mark's tips on moving the one gauge entry. Or take a look at the twin INS installation. But the first step will surely be to check if the basic stuff is working, so you are right on track with the Civa installer.  :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by rservice on Aug 1st, 2012 at 3:49pm
I'm still getting CTD's with several developer's aircraft,when using the dropdown menus.I don't know if it is caused by a particular situation,but it sure is a pain when you are in the middle of a flight. :'( :'( :'(
Ron

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Aug 1st, 2012 at 10:25pm
I don't know if that has anything to do with the Civa INS, Ron. I doubt it. But are you already using that uiautomationcore.dll fix? Without it, Win7 PCs may run into a CTD with FSX and accessing the menus.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Aug 2nd, 2012 at 4:14am

CoolP wrote on Aug 1st, 2012 at 10:25pm:
I don't know if that has anything to do with the Civa INS, Ron. I doubt it. But are you already using that uiautomationcore.dll fix? Without it, Win7 PCs may run into a CTD with FSX and accessing the menus.

I'm using the uiautomationcore.dll fix, but I still get CTD sometimes when I access the menu. :(

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Aug 2nd, 2012 at 12:00pm

Quote:
but I still get CTD sometimes when I access the menu.

:( Any clues on what could be the problem? Windows event log showing something maybe?

It spoils the thread topic, but there are different ways of applying that uiautomationcore.dll fix. Perhaps there's some cure within trying some of them. I've just mentioned it because it solved the menu crashes for me, back then when I was new to Win7.

I've just added the dll to my FSX folder and that helped. No other edits done. Still wondering why Ron brought it up in the Civa thread though. Maybe I'm misunderstanding his post.  :-/

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by rservice on Aug 2nd, 2012 at 12:33pm
Sorry for posting in this thread,it should be on the general thread,maybe CS can move it there.Anyway,I just did the Windows uiautomation.dll "fix" and will keep an eye on it.I suspect this probelm may have started appearing due to a Windows update,but we may never know for sure.
Ron :-? :-?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Aug 2nd, 2012 at 12:40pm
No problem, Ron. No harm done.  :) I mean you could still post a Civa related question like 'why are there so many keys?' or something, just to keep the peace.  :D  :P

Good luck with the fix. Maybe Jim over at Avsim has some more ideas if it doesn't work. He is the main poster in the CTD section and he's helped a lot of folks. http://forum.avsim.net/forum/262-crash-to-desktop-ctd-forum/ Pick your favourite CTD cause if you like.  :o

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by giorgio nicola on Aug 10th, 2012 at 9:39pm
I don't know why my CIVA ins stops alignment at 6/9...

I also turn off the engines to ensure no-moving

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Aug 10th, 2012 at 10:38pm

giorgio nicola wrote on Aug 10th, 2012 at 9:39pm:
I don't know why my CIVA ins stops alignment at 6/9...

Sounds like you've entered the coordinates in the wrong format and a 0 (zero) is missing. You are right, some movement will also spoil the process, but the error on entering coordinates seems like the most common one so far when being new to the gauge.

So here's a list on what to do in general. http://www.captainsim.org/yabb2/YaBB.pl?num=1285100008/240

And here's something on that format issue.


Quote:
I think that your problem is already covered in that bigger thread and it really looks like you are missing some numbers (often "0") when entering your current position manually. This leads to a stop just before getting the green "nav" light on and also to this experienced change of numbers when pressing "INSERT".

There already had been a guy running in the same trouble (wrong format, wrong coordinates), so maybe this page of the thread can help you. http://www.captainsim.org/yabb2/YaBB.pl?num=1285100008/60

Your "N55.320 / W 115.322" should be entered as 55 03 2 and 115 03 2 for example. The FSX coordinates display drops this zero when displaying the minutes (so "03" minutes get "3") while the Civa doesn't process the seconds in full detail (last digit is left out) but needs the "invisible" zero for the minutes value.



Is entered as.


Mind that one zero in the example after the first two digits.



Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by giorgio nicola on Aug 11th, 2012 at 1:10pm
thankyou coolP, I'll try another time and be aware of the 0 ;-)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by giorgio nicola on Aug 11th, 2012 at 1:30pm
yeah, now it works!

I may did 2 things wrong:
-i didn't set the parking brakes (however the aircraft wasn't moving)
-I didn't pressed the test button, but I did that because no warning lights come-up

thankyou so much!

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Aug 11th, 2012 at 6:16pm
Glad it worked.

Always mind the parking brake. The tug drivers love it!  :D Starts at 00:45.
http://www.youtube.com/watch?v=cMyR8U7xJO0

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Aug 12th, 2012 at 4:06am

CoolP wrote on Aug 11th, 2012 at 6:16pm:
Glad it worked.

Always mind the parking brake. The tug drivers love it!  :D Starts at 00:45.
http://www.youtube.com/watch?v=cMyR8U7xJO0

Ouch!! :o

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Aug 12th, 2012 at 9:13pm
I like how they run away and let the physics work.  ;D Well, more on the thread, I guess the alignment got slightly disturbed.  8-)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Aug 13th, 2012 at 5:25am

CoolP wrote on Aug 12th, 2012 at 9:13pm:
I like how they run away and let the physics work.  ;D

I would have stood there, put my hand on the nose gear, and stopped it!
But that's only because I'm Superman! Da dah!!! :o :P ;D :D

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Aug 13th, 2012 at 9:50pm

Markoz wrote on Aug 13th, 2012 at 5:25am:

I would have stood there, put my hand on the nose gear, and stopped it!

;D Yes, seems like you appreciate aligned gauges very much, same as I do.  :D That's the spirit!

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Rick Winkelman on Oct 20th, 2012 at 11:27am
Hello all,

I'm very sorry to ask thisa question but i cant find it anywhere else.

I'm flying the 1.3 version of the ins install posted here in this forum, the only thing is i have edited it for myself to add a second adeu for the second cdu.

Now i i load a part two of my flightplan into the second cdu it works perfect. The only problem is that i cant select the secons cdu to control the INS.

What i do:

- Switch from NAV to HDG mode
- Disable INS1 to the unit
- Couple the INS2 to the unit
- Switching from HDG to NAV

What the system does when i'm switching back to NAV mode, is disabling the INS2 automatic and enables the INS1.

Is anyone here willing to help me with this strange problem?

Kindly regards,

Rick Winkelman

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Oct 20th, 2012 at 6:45pm
Hi, Rick.

I think the special setup on the 707 (INS/DOPPLER switch and dedicated NAV mode for the AP) binds the CDU#1 steering input to the plane, no matter what. Even regardless of the nav switches on the INS popup. So I guess your plans on using the #2 unit to steer the AP will fail. At least, I wouldn't know how to force a CDU#2 priority on this plane.

For all other purposes like cross-checking or just some second display reference, the #2 unit will do fine.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Rick Winkelman on Oct 20th, 2012 at 7:55pm
CoolP,

Thanks for the answer. That makes sence indeed.

But now one more big problem.

If i change to HDG mode to update the INS1 it doesnt update at all.

I follow the manual and have watched the video tutorial about 10 times now.
But the update light does not light up at all. do you know if there is a special setting in the 707 to do because i think it has something to do with the nav1 / nav2 freq active status.

Kindly regards,

Rick Winkelman

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Oct 21st, 2012 at 7:35am
I'm not sure if I understand you correctly. Are you trying to perform a DME update maybe? These two sentences puzzle me.  :-[quote]If i change to HDG mode to update the INS1 it doesnt update at all.

But the update light does not light up at all.[/quote]
For a DME update, just make sure the proper station is tuned and showing up on the DME display (of the 707). Means that you have a reception. Then perform the steps to start the DME update for the INS.

Here's some more information from this thread.
http://captainsim.org/yabb2/YaBB.pl?num=1285100008/156#156

http://www.captainsim.org/yabb2/YaBB.pl?num=1285100008/138#138


Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Rick Winkelman on Oct 22nd, 2012 at 8:37am
CoolP,

Thanks for your answer, going to try that.
But since we are navigating the 707 on one single INS, is it possible to Update the INS (DME Update) while we are navigating or do we have to couple the ins off first?

Kindly regards and allready thanks for all the help!

Rick Winkelman

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Oct 22nd, 2012 at 9:37am

Quote:
is it possible to Update the INS (DME Update) while we are navigating or do we have to couple the ins off first?

Good question. They recommend to uncouple the autopilot (with e.g. reverting back to HDG select) for the time the unit starts the DME update. Reason is that the update may cause more or less severe heading corrections which would harm passenger comfort.

Now that seems to be a recommendation for the rw units and also for the case of a huge offset already having developed. In the sim, I never saw huge jumps or something, so you are safe to leave the autopilot in NAV and then start the DME update.

The CDU itself can do both things, deliver the signal to the AP and, at the same time, process the DME update correction. So even a single INS installation is stable enough to perform both tasks at a time.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Rick Winkelman on Oct 22nd, 2012 at 10:46am
CoolP,

Again, Thank you!

Now one more question to ask and i know this is not the right place but okay.

This question is about fuel planning.

I've see a lot of posts where is said you must plan your fuel backwards since it is not possible to plan your fuel the normal way with the performance charts.

This because you need a gross weight for the planning. Only is that not possible to know because the gross weight is included the Fuel weight. and that is the thing you need to plan.

Is there a short description availible on how to plan your fuel?

Kindly regards,

Rick

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Oct 22nd, 2012 at 12:57pm
I think one could write an Excel sheet for planning with the fuel. There's a document hosted at Avsim (707perf.zip) which lists some cruise and climb values for a given GW. Our CS 707 needs a bit less than charted, but the values should give a nice overview.

Now, on the data we have. Assuming that the CS plane roughly follows the charts.

The rate of fuel burn at cruise. There's a cruise chart which allows for an overview on how many nm you get out of 1000 lbs of fuel. You can also use a second table to define the fuel flow rate per engine. So, for the cruise portion, we are ok.  [smiley=thumbsup.gif]

The climb part is also covered, but I think we will see a more or less severe discrepancy there. Either way, I'm ok.  [smiley=thumbsup.gif]

The descent stage isn't covered but we may assume that throttling back and pointing the nose down will cause a decreased fuel flow until we come to the point where the approach procedure starts.   :question

On the reserve fuel, I'd say it depends. You could add a percentage of the trip fuel or, on short trips, a fixed addition of fuel weight. With the charts and when knowing your cruise FL, you can look up how much fuel the engines need per hour. So if you wanted to add some hours extra, you can get your values.  :question


On the problem to plan reversed, just jump in with a ZFW or your liking (after using the ACE) and then add 'just some' fuel to have a GW value to start with. Then plan ahead, with that given GW, and see if you would make it when looking at the fuel charts. If you would have too much fuel left, do it again with a lower GW. The other way around when it turns out that you are running too low on fuel.

To give some examples. You would start with a TOGW of some 210.000 lbs. Lets say 40.000 lbs are fuel. The cruise chart recommends FL390 for your flight, which would cause every 1000lbs of fuel to give you approx 46nm of range. For the climb up to that cruise flight level of 390, you can look up that, at a GW of 210.000 lbs, it would take 8900 lbs and 25 minutes on a standard ISA day.

When leaving out any considerations on extra fuel and the winds, you would therefore climb, use those 8900 lbs of fuel, then be at cruise altitude and have 31.100 lbs left, giving you a range of 1430nm (31.1 x 46) if you wanted to run out of fuel and then glide to an airport.  :D

Now if your trip was only 1000nm, you would have consumed the climb fuel and the part of the cruise portion. Lets say your climb took some 150nm, means 850nm are left for cruising, which would need 850 / 46 = 18.5; 18.500 lbs of fuel. You've started with 40.000 so 12.600 lbs are still there and since you would start your descent sooner than just above the destination, the descent will save some fuel while the approach stuff then consumes a bit more.

If your trip was 2000nm, you would need more fuel of course. So you could start again and add some 20.000 lbs, means you have 60.000. The GW now is 230.000 lbs and the cruise charts recommends FL370 with 1000 lbs of fuel resulting in approx 41nm.

To climb up to FL370 on a standard ISA day, you need 9500 lbs and 25 minutes. Estimate some 150nm for the climb, leaves 1850nm for the cruise, which needs 1850 / 41 = 45.1; 45.100 lbs of fuel. You've loaded 60.000 lbs of fuel, 9500 are gone with the climb and 41.500 are needed for a cruise above the airport, so 5400 lbs are left. That's a bit thin, so do it again with some extra fuel.

Well, if you have wind data in place, you can estimate it's effect on the planning distance. I would just check the winds for a general trend. If you receive headwind, add fuel and run the calcs again. The 707perf docs give you some TAS values to play with, means a 'no wind' planning basis. Tailwind would make me (I'm a sim pilot!) leave the initial fuel as it is, unless my no-wind landing weight would be anywhere close to exceeding structural limits. But that's not the case on the examples given. If you want to land on short runways, that's a different ball game of course.

But, from the charts, landing a 247.000 lbs plane on a wet runway with the airport being at 2.000ft gives me just above 7600ft of landing distance. So any major hub larger airport will be just fine and those 247.000 are your limit for the real plane. And the sim plane brakes way better.  :P

To give an example on the winds. Lets cruise at FL370 with standard ISA temps. This gives you 458 KTAS. We have a trip of 1850 ahead, so, with no winds, you are above the airport in slightly over 4 hours (1850 / 458 = 4.04) . If you have a headwind of 70 kts at cruise, you GS will be 388 kts, means the 1850nm are gone in 4 hours and 45 minutes, so you need fuel for roughly one hour extra. Yes, this increases the GW and slightly decreases the nm per 1000 lbs of fuel. So extra fuel means.. extra fuel.  :D

Now I never ran her on those 6 hour or more trips, just on shorter ones. Means that the roughness of those calcs may indeed backfire on you when it comes to either the max landing weight or the danger of running out of fuel. Maybe another 707 fan has set up a Excel sheet or something to help you.

[edit]Just to be clear, that sort of 'planning' isn't really worth to be called like that. No rw pilot would plan that (rough) way, so just take it as a sim special and a very vague concept of rule of thumb. So only look at it as the guesstimated thing it is.[/edit]

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Rick Winkelman on Oct 22nd, 2012 at 8:36pm
CoolP,

Thanks again for your answer.
I've decided to start creating a fuel planner program based on inputs you (as a user) can give it.

Based on those inputs it will make (i hope) a rough fuel planning form.

Will keep you updated!

Rick

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Oct 23rd, 2012 at 9:11am
Good idea, Rick. I can send you a template if you like. It's from another plane, but it shows a nice concept. If I had some leisure time and some more data, I think I would start one myself. I will PM you the example file.

Title: CIVA INS or ISG1 FMC??
Post by RyanJames170 on Nov 22nd, 2012 at 5:35am
how would one go about adding the CIVA INS or the ISG1 Smiths FMC to the 707?

Title: Re: CIVA INS or ISG1 FMC??
Post by Markoz on Nov 22nd, 2012 at 5:55am

RyanJames170 wrote on Nov 22nd, 2012 at 5:35am:
how would one go about adding the CIVA INS or the ISG1 Smiths FMC to the 707?

Almost all you need to know about CIVA-INS and the 707: CIVA INS - THE ONLY THREAD PLEASE. And if you still have problems, feel free to ask questions. ;)

As for the ISG1 Smiths FMC, it has been mentioned several times, but I don't know who has done it, or how they did it. And seeing as I don't have it, I can't help you with it. Sorry.

Title: Re: CIVA INS or ISG1 FMC??
Post by pete197 on Nov 22nd, 2012 at 8:34pm
I have used it, but not in the CS 707. I have on the CLS 747. What do you want specifically?
Pete

Title: Re: CIVA INS or ISG1 FMC??
Post by RyanJames170 on Nov 23rd, 2012 at 1:34am
I would love to have the ISG1 Smiths FMC in the 707 so i can fly flight plans

anyone know how to do that?

Title: Re: CIVA INS or ISG1 FMC??
Post by Markoz on Nov 23rd, 2012 at 5:10am

RyanJames170 wrote on Nov 23rd, 2012 at 1:34am:
I would love to have the ISG1 Smiths FMC in the 707 so i can fly flight plans

anyone know how to do that?

The 707 can fly GPS flight plans made using the FS Flight Planner, or plans made by Third Party addons that can save them in the FS PLN format (like FS Commander v9.2 which I sometime do).

I haven't done an FS Flight Plan (GPS) flight plan in ages. This is how I think I do it (*I'll check later). You load the flight plan from the FS Flight Planner and by putting the Autopilot Mode Selector knob on NAV Mode (make sure that the Doppler/INS switch is set to Doppler, but the Doppler is turned OFF). The only things you need to do is control the 707's speed using the throttles and calculate your own T/D.

I mostly use either the Doppler Navigation or CIVA-INS Navigation (my preference being the INS).

*I'll correct this if I am wrong. ;)

Title: Re: CIVA INS or ISG1 FMC??
Post by G_Sproson on Nov 23rd, 2012 at 4:30pm
Can you actually get the INS into the VC or does it have remain a 2D pop-up?

Title: Re: CIVA INS or ISG1 FMC??
Post by Markoz on Nov 23rd, 2012 at 4:44pm
Captain Sim asked the developers who made CIVA-INS if it would be okay to modify the code so it could work in the VC. They never got a response. Or something like that.

Title: Missing INS?
Post by AndersCN on Mar 15th, 2013 at 7:44pm
Hi,

The INS is not showing up in any 2D panel. Neither are the icons Shift+7-9 available in the Icon Control Panel.

And yes, I have installed Delco Caroussel CIVA version 1.51.

What could be wrong?

BR,
Anders

Title: Re: Missing INS?
Post by Markoz on Mar 15th, 2013 at 11:42pm
Take a look through this forum topic: CIVA INS - THE ONLY THREAD PLEASE
You might find an answer to your problem in there.

Title: Re: Missing INS?
Post by AndersCN on Mar 16th, 2013 at 8:56am
Thank you for the tip.

So, I renamed the CIVA_panel.cfg to panel.cfg, and renamed the original panel.cfg to panel.original.cfg - then it works :)

But am I right, that the one in the VC is for display only (it shows the position coordinates) but other than that is inop?

BR,
Anders

Title: Re: Missing INS?
Post by Markoz on Mar 17th, 2013 at 12:14pm

Quote:
But am I right, that the one in the VC is for display only (it shows the position coordinates) but other than that is inop?

Yes. You are right. Last I heard, Captain Sim hadn't gotten permission from the creators of CIVA-INS to incorporate a working unit in the VC.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by INSSUck on Apr 12th, 2013 at 5:41am
hey guys I got The ins work but when i enable Autopilot noting happens here is my panel cfg
[Window Titles]
Window00=Simicons
Window01=Animations Control
Window02=Radio Stack
Window03=Autopilot
Window04=Crew Messenger
Window05=GPS
window06=INS Control Display Units
window07=INS MSU + ADEU

////<VoxATC
Window08=VoxATC
////>VoxATC
[VIEWS]
VIEW_FORWARD_WINDOWS=MAIN_PANEL,RADIO_STACK_PANEL,60,115
VIEW_FORWARD_ZOOM=0.8
VIEW_FORWARD_DIR=1.0,0.0,0.0
VIEW_DOWN_WINDOWS=30,80,115
VIEW_REAR_RIGHT_WINDOWS=33,85,115
VIEW_DOWN_ZOOM=1.0
VIEW_DOWN_DIR=-30.0,0.0,30.0
VIEW_REAR_RIGHT_ZOOM=0.8
VIEW_REAR_RIGHT_DIR=0.0,0.0,120.0

[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.p721.sys!main, 0,0, 2,2
gauge01=Captain_Sim.p721.tools!icons,  0, 570, 64,198
gauge02=../civa/INS!CduPanelIconB,      0, 538,32, 32, 40
gauge03=../civa/INS!AdeuPanelIconB,    32,  538,  32,  32,  41

[Window01]
Background_color=0,0,0
size_mm=367,469
position=0
visible=0
ident=10002
windowsize_ratio=1.00
gauge00=Captain_Sim.p721.ac200!ac200, 0,0, 367,469

[Window02]
size_mm=349,845
position=8
background_color=25,0,0
visible=0
windowsize_ratio=0.75
ident=RADIO_STACK_PANEL
gauge00=..\..\CS_B727-100\panel\Captain_Sim.p721.P10!P10_001_vhf,  0,  0,349,190
gauge01=..\..\CS_B727-100\panel\Captain_Sim.p721.P11!P11_001_vhf,  0,190,349,190
gauge02=..\..\CS_B727-100\panel\Captain_Sim.p721.P13!P13_001_tcas, 0,380,349,155
gauge03=..\..\CS_B727-100\panel\Captain_Sim.p721.P01!P01_001_adf,  0,535,349,155
gauge04=..\..\CS_B727-100\panel\Captain_Sim.p721.P07!P07_001_adf,  0,690,349,155

[Window03]
size_mm=480,130
window_pos= 0.300, 0.020
position=2
Background_color=0,0,0
visible=0
ident=10005

gauge00=..\..\CS_B727-100\panel\Captain_Sim.p721.P12!P12_001_ap,     0, 0, 427, 106
gauge01=../civa/INS!Config,        0, 0, 0, 0, CS727
gauge02=../civa/INS!CduPanelIconB,    427, 0, 20, 20, 40
gauge03=../civa/INS!AdeuPanelIconB,    427, 20, 20, 20, 41
gauge04=../civa/INS!NavModeDual,    427, 40, 50, 45
//gauge05=Cessna!Nav_GPS_Annunciator,                   447,106,20,19
//gauge06=Cessna!Nav GPS Switch,                          427,106,20,19


[Window04]
background_color=0,0,0
size_mm=349,218
window_size_ratio=0.70  
position=7
visible=0
ident=10007
render_3d_window=0
gauge00=..\..\CS_B727-100\panel\Captain_Sim.p721.P15!P15_bg, 0,0, 349,218

[Window05]
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

[Window06]
size_mm=420,221
background_color=0,0,0
window_pos=0.300, 0.160
position=0
visible=0
ident=40
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, 40


[Window07]
size_mm=420,161
background_color=0,0,0
window_pos=0.300, 0.450
position=0
visible=0
ident=41
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, 41



////<VoxATC
[Window08]
visible=1
position=4
size_mm=400,200
pixel_size = 400, 200
background_color=0,0,0
ident=14077
zorder=5
alpha_blend=0.65
gauge00=VAGauge!VoxATCPrompt,0,0
////>VoxATC

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$FPSP
background_color=0,0,0

gauge00=Captain_Sim.p721.general!L_backlight, 25, 230, 200, 20
gauge01=Captain_Sim.p721.L01!L01_machmeter, 24,26, 200,200
gauge02=Captain_Sim.p721.L02!L02_clock, 50, 300, 155, 151
gauge03=Captain_Sim.p721.L03!L03_aplight, 625,749, 55,55
gauge04=Captain_Sim.p721.L04!L04_airspeed, 275, 30, 177, 169
gauge05=Captain_Sim.p721.L05!L05_rmi, 275, 775, 200,200
gauge06=Captain_Sim.p721.L10!L10_altimeter, 275,270, 210,240
gauge07=Captain_Sim.p721.L11!L11_vsi, 20,524, 217,220
gauge08=Captain_Sim.p721.L13!L13_ra, 260,505, 240,240
gauge09=Captain_Sim.p721.L14!L14_ealtimeter, 25, 779, 200, 220
gauge10=Captain_Sim.p721.general!R_backlight, 25, 749, 200, 20
gauge11=Captain_Sim.p721.general!C_backlight, 25, 500, 200, 20
gauge12=Captain_Sim.p721.L07!L07_adi, 505, 29 , 168, 150
gauge13=Captain_Sim.p721.L07!L07_010_slip, 275,225, 200, 47
gauge14=Captain_Sim.p721.L08!L08_hsi, 599, 399, 199, 239
gauge15=Captain_Sim.p721.L09!L09_002_light, 725,649, 133,64
gauge16=Captain_Sim.p721.L09!L09_003_light, 725,724, 133,64
gauge17=Captain_Sim.p721.L09!L09_004_light, 725,799, 133,64
gauge18=Captain_Sim.p721.L09!L09_005_light, 725,874, 133,64
gauge19=Captain_Sim.p721.L09!L09_006_light, 725,949, 80,64
gauge20=Captain_Sim.p721.L09!L09_007_light, 799,949, 80,64
gauge21=Captain_Sim.p721.L09!L09_008_light, 871,649, 136,64
gauge22=Captain_Sim.p721.L09!L09_009_light, 871,724, 136,64
gauge23=Captain_Sim.p721.L09!L09_010_light, 871,799, 136,64
gauge24=Captain_Sim.p721.L09!L09_011_light, 871,874, 136,64
gauge25=Captain_Sim.p721.L09!L09_012_light, 871,949, 136,64
gauge26=Captain_Sim.p721.L09!L09_001_light, 623,924, 92,90
gauge27=Captain_Sim.p721.L15!L15_001_dme,      499,799, 90,30
gauge28=Captain_Sim.p721.L15!L15_002_light, 625,824, 100,45
gauge29=Captain_Sim.p721.L15!L15_003_light, 625,873, 100,45
gauge30=Captain_Sim.p721.L06!L06_001_light, 624,698, 101,46
gauge31=Captain_Sim.p721.L06!L06_002_light, 498,923, 115,81
gauge32=Captain_Sim.p721.L06!L06_003_light, 499,849, 87,57
gauge33=Captain_Sim.p721.L09!L09_013_light, 626,649, 100,45
gauge34=Captain_Sim.p721.L13!L13_001_light, 500,675, 50,50
gauge35=Captain_Sim.p727.sound!main, 0,0, 10,10, Captain_Sim\727\sound.ini
gauge36=../civa/INS!Config,            0, 0, 0, 0, CS727 // this gauge initializes the Civa INS gauges, "CS727.Isd" is the name of the config file in the Civa folder

[VCockpit02]
size_mm=1024,1024
pixel_size=1024,1024
texture=$BIsp
background_color=0,0,0

gauge00=Captain_Sim.p721.W01!W01_003_fuel, 24, 24, 102,78
gauge01=Captain_Sim.p721.W01!W01_009_fuel, 174,24, 102,78
gauge02=Captain_Sim.p721.W01!W01_015_fuel, 300,24, 102,78
gauge03=Captain_Sim.p721.W09!W09_010_ndl, 0,150, 125,125
gauge04=Captain_Sim.p721.W10!W10_015_ndl, 150,150, 125,125
gauge05=Captain_Sim.p721.W10!W10_017_ndl, 300,150, 125,125
gauge06=Captain_Sim.p721.W10!W10_019_ndl, 0,300, 125,125
gauge07=Captain_Sim.p721.W10!W10_022_ndl, 150,300, 125,125
gauge08=Captain_Sim.p721.W10!W10_021_ndl, 300,300, 125,125
gauge09=Captain_Sim.p721.W02!W02_001_clock, 450,0, 150,150
gauge10=Captain_Sim.p721.W04!W04_001, 625,0, 125,125
gauge11=Captain_Sim.p721.W04!W04_002, 775,0, 125,125
gauge12=Captain_Sim.p721.W04!W04_003, 900,0, 125,125
gauge13=Captain_Sim.p721.W04!W04_004, 625,150, 125,125
gauge14=Captain_Sim.p721.W04!W04_005, 775,150, 125,125
gauge15=Captain_Sim.p721.W04!W04_006, 900,150, 125,125
gauge16=Captain_Sim.p721.W04!W04_007, 625,300, 125,125
gauge17=Captain_Sim.p721.W04!W04_008, 775,300, 125,125
gauge18=Captain_Sim.p721.W04!W04_009, 900,300, 125,125
gauge19=Captain_Sim.p721.U04!U04_004, 450,175, 125,66
gauge20=Captain_Sim.p721.U04!U04_005, 450,325, 125,66
gauge21=Captain_Sim.p721.U01!U01_001_dcv, 375,450, 125,66
gauge22=Captain_Sim.p721.U01!U01_002_dca, 500,450, 125,66
gauge23=Captain_Sim.p721.U03!U03_001, 375,575, 125,66
gauge24=Captain_Sim.p721.U03!U03_010, 500,575, 125,66
gauge25=Captain_Sim.p721.U03!U03_019, 625,575, 125,66
gauge26=Captain_Sim.p721.U03!U03_008, 750,575, 125,66
gauge27=Captain_Sim.p721.U03!U03_017, 0,675, 125,66
gauge28=Captain_Sim.p721.U03!U03_026, 150,675, 125,66
gauge29=Captain_Sim.p721.U05!U05_001_ndl, 625,450, 125,125
gauge30=Captain_Sim.p721.U05!U05_002_ndl, 750,450, 125,125
gauge31=Captain_Sim.p721.U10!U10_005_ndl, 300,700, 94,94
gauge32=Captain_Sim.p721.U10!U10_007_ndl, 400,700, 94,94
gauge33=Captain_Sim.p721.U10!U10_006_ndl, 875,450, 125,125
gauge34=Captain_Sim.p721.U11!U11_004_ndl, 900,750, 125,125
gauge35=Captain_Sim.p721.U11!U11_010_ndl, 0,825, 200,200
gauge36=Captain_Sim.p721.U11!U11_015_ndl, 225,825, 200,200
gauge37=Captain_Sim.p721.U10!U10_004_ndl, 600,725, 71,37
gauge38=Captain_Sim.p721.U10!U10_009_ndl, 525,725, 71,37
gauge39=Captain_Sim.p721.U11!U11_017_ndl, 450,825, 200,200
gauge40=Captain_Sim.p721.U11!U11_012_ndl, 675,825, 200,180
gauge41=Captain_Sim.p721.U11!U11_003_ndl, 675,725, 71,37
gauge42=Captain_Sim.p721.U11!U11_007_ndl, 750,725, 71,37
gauge43=Captain_Sim.p721.U06!U06_002_ndl, 825,725, 71,37
gauge44=Captain_Sim.p721.W07!W07_001_light, 10,458, 96,19
gauge45=Captain_Sim.p721.W07!W07_002_light, 10,492, 96,19
gauge46=Captain_Sim.p721.W07!W07_003_light, 10,524, 96,19
gauge47=Captain_Sim.p721.W07!W07_004_light, 10,557, 96,19
gauge48=Captain_Sim.p721.W07!W07_005_light, 10,594, 96,19
gauge49=Captain_Sim.p721.W07!W07_006_light, 10,626, 96,19
gauge50=Captain_Sim.p721.W07!W07_007_light, 125,458, 96,19
gauge51=Captain_Sim.p721.W07!W07_008_light, 125,492, 96,19
gauge52=Captain_Sim.p721.W07!W07_009_light, 125,524, 96,19
gauge53=Captain_Sim.p721.W07!W07_010_light, 125,557, 96,19
gauge54=Captain_Sim.p721.W07!W07_011_light, 125,594, 96,19
gauge55=Captain_Sim.p721.W07!W07_012_light, 243,458, 96,19
gauge56=Captain_Sim.p721.W07!W07_013_light, 243,492, 96,19
gauge57=Captain_Sim.p721.W07!W07_014_light, 243,524, 96,19
gauge58=Captain_Sim.p721.W07!W07_015_light, 243,557, 96,19
gauge59=Captain_Sim.p721.W07!W07_016_light, 243,594, 96,19
gauge60=Captain_Sim.p721.W07!W07_017_light, 243,626, 96,19
gauge61=Captain_Sim.p721.P603!P603_011_ndl, 750,650, 110,55
gauge62=Captain_Sim.p721.P603!P603_012_ndl, 900,600, 107,106

[VCockpit03]
size_mm=1024,1024
pixel_size=1024,1024
texture=$BIlamp
background_color=0,0,0

gauge00=Captain_Sim.p721.U02!U02_003_light, 950,0, 90,90
gauge01=Captain_Sim.p721.U02!U02_006_light, 950,75, 90,90
gauge02=Captain_Sim.p721.U02!U02_009_light, 950,150, 90,90
gauge03=Captain_Sim.p721.U03!U03_002_light, 950,300, 90,90
gauge04=Captain_Sim.p721.U03!U03_004_light, 950,525, 90,90
gauge05=Captain_Sim.p721.U03!U03_006_light, 950,750, 90,90
gauge06=Captain_Sim.p721.U03!U03_011_light, 950,375, 90,90
gauge07=Captain_Sim.p721.U03!U03_013_light, 950,600, 90,90
gauge08=Captain_Sim.p721.U03!U03_015_light, 950,825, 90,90
gauge09=Captain_Sim.p721.U03!U03_021_light, 950,450, 90,90
gauge10=Captain_Sim.p721.U03!U03_023_light, 950,675, 90,90
gauge11=Captain_Sim.p721.U03!U03_025_light, 950,900, 90,90
gauge12=Captain_Sim.p721.U04!U04_002_light, 950,225, 90,90
gauge13=Captain_Sim.p721.U04!U04_007_light, 650,0, 90,90
gauge14=Captain_Sim.p721.U04!U04_008_light, 725,0, 90,90
gauge15=Captain_Sim.p721.U05!U05_004_light, 875,75, 90,90
gauge16=Captain_Sim.p721.U06!U06_004_light, 875,150, 90,90
gauge17=Captain_Sim.p721.U07!U07_001_light, 875,225, 90,90
gauge18=Captain_Sim.p721.U07!U07_002_light, 875,300, 90,90
gauge19=Captain_Sim.p721.U07!U07_003_light, 875,375, 90,90
gauge20=Captain_Sim.p721.U08!U08_008_light, 875,450, 90,90
gauge21=Captain_Sim.p721.U08!U08_009_light, 875,525, 90,90
gauge22=Captain_Sim.p721.U09!U09_001_light, 875,600, 90,90
gauge23=Captain_Sim.p721.U09!U09_002_light, 875,675, 90,90
gauge24=Captain_Sim.p721.U09!U09_003_light, 875,750, 90,90
gauge25=Captain_Sim.p721.U09!U09_005_light, 875,825, 90,90
gauge26=Captain_Sim.p721.U10!U10_011_light, 800,75, 90,90
gauge27=Captain_Sim.p721.U10!U10_013_light, 800,150, 90,90
gauge28=Captain_Sim.p721.U10!U10_017_light, 800,225, 90,90
gauge29=Captain_Sim.p721.U10!U10_020_light, 800,300, 90,90
gauge30=Captain_Sim.p721.W01!W01_002_light, 800,375, 90,90
gauge31=Captain_Sim.p721.W01!W01_004_light, 800,450, 90,90
gauge32=Captain_Sim.p721.W01!W01_019_light, 800,525, 90,90
gauge33=Captain_Sim.p721.W01!W01_022_light, 800,600, 90,90
gauge34=Captain_Sim.p721.W01!W01_012_light, 800,675, 90,90
gauge35=Captain_Sim.p721.W01!W01_014_light, 800,750, 90,90
gauge36=Captain_Sim.p721.W01!W01_006_light, 800,825, 90,90
gauge37=Captain_Sim.p721.W01!W01_016_light, 800,900, 90,90
gauge38=Captain_Sim.p721.W01!W01_024_light, 725,900, 90,90
gauge39=Captain_Sim.p721.W01!W01_028_light, 875,900, 90,90
gauge40=Captain_Sim.p721.W01!W01_023_light, 725,75, 90,90  
gauge41=Captain_Sim.p721.W01!W01_029_light, 725,150, 90,90
gauge42=Captain_Sim.p721.W01!W01_034_light, 725,225, 90,90
gauge43=Captain_Sim.p721.W01!W01_033_light, 725,300, 90,90
gauge44=Captain_Sim.p721.W03!W03_001_light, 725,375, 90,90
gauge45=Captain_Sim.p721.W09!W09_002_light, 725,450, 90,90
gauge46=Captain_Sim.p721.W09!W09_004_light, 725,525, 90,90
gauge47=Captain_Sim.p721.W09!W09_006_light, 725,600, 90,90
gauge48=Captain_Sim.p721.W09!W09_001_light, 725,675, 90,90
gauge49=Captain_Sim.p721.W09!W09_003_light, 725,750, 90,90
gauge50=Captain_Sim.p721.W09!W09_005_light, 725,825, 90,90
gauge51=Captain_Sim.p721.W10!W10_002_light, 650,75, 90,90
gauge52=Captain_Sim.p721.W10!W10_004_light, 650,150, 90,90
gauge53=Captain_Sim.p721.W10!W10_016_light, 650,225, 90,90
gauge54=Captain_Sim.p721.W10!W10_010_light, 650,300, 90,90
gauge55=Captain_Sim.p721.W10!W10_012_light, 650,375, 90,90
gauge56=Captain_Sim.p721.W10!W10_013_light, 650,450, 90,90
gauge57=Captain_Sim.p721.W10!W10_014_light, 650,525, 90,90
gauge58=Captain_Sim.p721.W10!W10_020_light, 650,600, 90,90
gauge59=Captain_Sim.p721.U02!U02_016_light, 899,  0, 25,25
gauge60=Captain_Sim.p721.P601!P601_001_light, 0,300, 90,90
gauge61=Captain_Sim.p721.P601!P601_002_light, 75,300, 90,90
gauge62=Captain_Sim.p721.P601!P601_003_light, 150,300, 90,90
gauge63=Captain_Sim.p721.P601!P601_004_light, 225,300, 90,90
gauge64=Captain_Sim.p721.P601!P601_010_light, 0,375, 90,90
gauge65=Captain_Sim.p721.P601!P601_011_light, 75,375, 90,90
gauge66=Captain_Sim.p721.P603!P603_002_light, 0,450, 90,90
gauge67=Captain_Sim.p721.P603!P603_003_light, 0,525, 90,90
gauge68=Captain_Sim.p721.U10!U10_014_light, 0,50, 45,45
gauge69=Captain_Sim.p721.U10!U10_021_light, 75,50, 45,45
gauge70=Captain_Sim.p721.U11!U11_001_light, 0,0, 45,45
gauge71=Captain_Sim.p721.U11!U11_009_light, 75,0, 45,45
gauge72=Captain_Sim.p721.U11!U11_018_light, 150,0, 121,45
gauge73=Captain_Sim.p721.W12!W12_002_light, 75,100, 45,45
gauge74=Captain_Sim.p721.W12!W12_003_light, 0,100, 45,45
gauge75=Captain_Sim.p721.W12!W12_004_light, 0,150, 45,45
gauge76=Captain_Sim.p721.O00!O00_002_light, 275,0, 140,116
gauge77=Captain_Sim.p721.O00!O00_001_light, 425,0, 140,116
gauge78=Captain_Sim.p721.P605!P605_001_light, 125,475, 150,35
gauge79=Captain_Sim.p721.P605!P605_002_light, 125,525, 150,35
gauge80=Captain_Sim.p721.P605!P605_003_light, 125,575, 150,35
gauge81=Captain_Sim.p721.P605!P605_004_light, 125,625, 150,35
gauge82=Captain_Sim.p721.P605!P605_005_light, 125,675, 150,35
gauge83=Captain_Sim.p721.P605!P605_006_light, 125,725, 150,35
gauge84=Captain_Sim.p721.P605!P605_007_light, 125,775, 150,35
gauge85=Captain_Sim.p721.P605!P605_008_light, 125,825, 150,35
gauge86=Captain_Sim.p721.P605!P605_009_light, 125,875, 150,35
gauge87=Captain_Sim.p721.P605!P605_010_light, 300,475, 150,35
gauge88=Captain_Sim.p721.P605!P605_011_light, 300,525, 150,35
gauge89=Captain_Sim.p721.P605!P605_012_light, 300,575, 150,35
gauge90=Captain_Sim.p721.P605!P605_013_light, 300,625, 150,35
gauge91=Captain_Sim.p721.P605!P605_014_light, 300,675, 150,35
gauge92=Captain_Sim.p721.P605!P605_015_light, 300,725, 150,35
gauge93=Captain_Sim.p721.P605!P605_016_light, 300,775, 150,35
gauge94=Captain_Sim.p721.P605!P605_017_light, 300,825, 150,35
gauge95=Captain_Sim.p721.P605!P605_018_light, 300,875, 150,35
gauge96=Captain_Sim.p721.P605!P605_019_light, 475,475, 150,35
gauge97=Captain_Sim.p721.P605!P605_020_light, 475,525, 150,35
gauge98=Captain_Sim.p721.P605!P605_021_light, 475,575, 150,35
gauge99=Captain_Sim.p721.P605!P605_022_light, 475,625, 150,35
gauge100=Captain_Sim.p721.P605!P605_023_light, 475,675, 150,35
gauge101=Captain_Sim.p721.P605!P605_024_light, 475,725, 150,35
gauge102=Captain_Sim.p721.P605!P605_025_light, 475,775, 150,35
gauge103=Captain_Sim.p721.P605!P605_026_light, 475,825, 150,35
gauge104=Captain_Sim.p721.P605!P605_027_light, 475,875, 150,35
gauge105=Captain_Sim.p721.P602!P602_002_light, 0,199, 20,20
gauge106=Captain_Sim.p721.P604!P604_001, 0, 624, 125, 85
gauge107=Captain_Sim.p721.P604!P604_002, 0, 724, 125, 85
gauge108=Captain_Sim.p721.P603!P603_004_light, 0,225, 50,50


[VCockpit04]
size_mm=1024,1024
pixel_size=1024,1024
texture=$cpsp
background_color=0,0,0
gauge00=Captain_Sim.p721.C07!C07_016_n1, 0,200, 200,200
gauge01=Captain_Sim.p721.C07!C07_017_n1, 200,200, 200,200
gauge02=Captain_Sim.p721.C07!C07_018_n1, 400,200, 200,200
gauge03=Captain_Sim.p721.C07!C07_022_n2, 0,600, 200,200
gauge04=Captain_Sim.p721.C07!C07_023_n2, 200,600, 200,200
gauge05=Captain_Sim.p721.C07!C07_024_n2, 400,600, 200,200
gauge06=Captain_Sim.p721.C07!C07_019_egt, 0, 400,200,200
gauge07=Captain_Sim.p721.C07!C07_020_egt, 200,400, 200,200
gauge08=Captain_Sim.p721.C07!C07_021_egt, 400,400, 200,200
gauge09=Captain_Sim.p721.C07!C07_025_ff, 0,800, 200,200
gauge10=Captain_Sim.p721.C07!C07_026_ff, 200,800, 200,200
gauge11=Captain_Sim.p721.C07!C07_027_ff, 400,800, 200,200
gauge12=Captain_Sim.p721.C07!C07_004_epr, 0,0, 200,200
gauge13=Captain_Sim.p721.C07!C07_005_epr, 200,0, 200,200
gauge14=Captain_Sim.p721.C07!C07_006_epr, 400,0, 200,200
gauge15=Captain_Sim.p721.C08!C08_005_flap, 600,0, 200,200
gauge16=Captain_Sim.p721.C08!C08_002_flap, 800,0, 200,200
gauge17=Captain_Sim.p721.C04!C04_SAH, 600,202, 250,250
gauge18=Captain_Sim.p721.C06!C06_001_trim, 900,200, 101,101
gauge19=Captain_Sim.p721.C07!C07_001_light, 650,874, 100,45
gauge20=Captain_Sim.p721.C07!C07_002_light, 650,924, 100,45
gauge21=Captain_Sim.p721.C07!C07_003_light, 650,974, 100,45
gauge22=Captain_Sim.p721.C08!C08_003_light, 650,774, 100,45
gauge23=Captain_Sim.p721.C08!C08_004_light, 650,824, 100,45
gauge24=Captain_Sim.p721.C08!C08_001_light, 775,924, 48,89
gauge25=Captain_Sim.p721.C10!C10_001_light, 775,824, 39,89
gauge26=Captain_Sim.p721.C10!C10_002_light, 650,550, 100,50
gauge27=Captain_Sim.p721.C10!C10_003_light, 650,600, 100,50
gauge28=Captain_Sim.p721.C10!C10_004_light, 650,650, 100,50
gauge29=Captain_Sim.p721.C10!C10_005_light, 650,700, 100,50
gauge30=Captain_Sim.p721.C10!C10_006_light, 750,650, 100,50
gauge31=Captain_Sim.p721.C10!C10_007_light, 750,700, 100,50
gauge32=Captain_Sim.p721.C05!C05_001_light, 925,924, 97,95
gauge33=Captain_Sim.p721.C05!C05_002_light, 825,924, 97,95
gauge34=Captain_Sim.p721.C03!C03_001_light, 875,675, 75,75
gauge35=Captain_Sim.p721.C03!C03_002_light, 875,750, 75,75
gauge36=Captain_Sim.p721.C03!C03_003_light, 875,825, 75,75
gauge37=Captain_Sim.p721.C09!C09_001_light, 625,475, 75,75
gauge38=Captain_Sim.p721.C09!C09_002_light, 700,475, 75,75
gauge39=Captain_Sim.p721.C09!C09_003_light, 775,475, 75,75
gauge40=Captain_Sim.p721.C02!C02_001_digit, 772,773, 97, 33

[VCockpit05]
size_mm=1024,1024
pixel_size=1024,1024
texture=$CPDSP
background_color=0,0,0
gauge00=Captain_Sim.p721.P01!P01_003_adf, 0, 0, 79, 35
gauge01=Captain_Sim.p721.P01!P01_004_adf, 0, 300, 55, 29
gauge02=Captain_Sim.p721.P07!P07_003_adf, 0, 50, 79, 35
gauge03=Captain_Sim.p721.P07!P07_004_adf, 0, 350, 55, 29
gauge04=Captain_Sim.p721.P10!P10_001_nav, 0, 100, 79, 50
gauge05=Captain_Sim.p721.P10!P10_002_comm, 0, 200, 79, 50
gauge06=Captain_Sim.p721.P11!P11_001_nav, 0, 150, 79, 50
gauge07=Captain_Sim.p721.P11!P11_002_comm, 0, 250, 79, 50
gauge08=Captain_Sim.p721.P10!P10_006_dme, 0, 400, 17, 17
gauge09=Captain_Sim.p721.P11!P11_006_dme, 20, 400, 17, 17
gauge10=Captain_Sim.p721.P09!P09_013_light, 100, 0, 90, 90
gauge11=Captain_Sim.p721.P09!P09_019_light, 175, 0, 90, 90
gauge12=Captain_Sim.p721.P13!P13_002_light, 99, 175, 20, 20
gauge13=Captain_Sim.p721.P13!P13_003_tcas, 98,  98, 85, 52


[VCockpit06]
size_mm=1024,1024
pixel_size=1024,1024
texture=$OHSP
background_color=0,0,0

gauge00=Captain_Sim.p721.O04!O04_007_light, 0, 0, 25,25
gauge01=Captain_Sim.p721.O04!O04_008_light, 25, 0, 25,25
gauge02=Captain_Sim.p721.O04!O04_002_light, 50, 0, 25,25
gauge03=Captain_Sim.p721.O04!O04_009_light, 75, 0, 25,25
gauge04=Captain_Sim.p721.O04!O04_010_light, 100, 0, 25,25
gauge05=Captain_Sim.p721.O07!O07_002_ndl, 150, 0, 25,25
gauge06=Captain_Sim.p721.O07!O07_001_light, 0, 100, 90,90
gauge07=Captain_Sim.p721.O08!O08_001_light, 0, 175, 90,90
gauge08=Captain_Sim.p721.O11!O11_004_light, 0, 250, 90,90
gauge09=Captain_Sim.p721.O14!O14_004_light, 0, 400, 90,90
gauge10=Captain_Sim.p721.O17!O17_003_light, 75, 100, 90,90
gauge11=Captain_Sim.p721.O17!O17_004_light, 75, 175, 90,90
gauge12=Captain_Sim.p721.O17!O17_007_light, 75, 250, 90,90
gauge13=Captain_Sim.p721.O17!O17_008_light, 75, 325, 90,90
gauge14=Captain_Sim.p721.O18!O18_001_ndl, 200, 0, 100,100
gauge15=Captain_Sim.p721.O18!O18_002_light, 75, 400, 90,90
gauge16=Captain_Sim.p721.O17!O17_005_light, 150, 100, 90,90
gauge17=Captain_Sim.p721.O17!O17_006_light, 150, 175, 90,90
gauge18=Captain_Sim.p721.O17!O17_009_light, 150, 250, 90,90
gauge19=Captain_Sim.p721.O17!O17_010_light, 150, 325, 90,90
gauge20=Captain_Sim.p721.O20!O20_004_light, 150, 400, 90,90
gauge21=Captain_Sim.p721.O19!O19_001_light, 225, 100, 90,90
gauge22=Captain_Sim.p721.O19!O19_004_light, 225, 175, 90,90
gauge23=Captain_Sim.p721.O19!O19_008_light, 225, 250, 90,90
gauge24=Captain_Sim.p721.O19!O19_006_light, 225, 325, 90,90
gauge25=Captain_Sim.p721.O19!O19_011_light, 225, 400, 90,90
gauge26=Captain_Sim.p721.O20!O20_001_ndl, 350, 0, 50,100
gauge27=Captain_Sim.p721.O20!O20_003_ndl, 425, 0, 50,100
gauge28=Captain_Sim.p721.O12!O12_003_light, 14,337, 46,46
gauge29=Captain_Sim.p721.O10!O10_001_light, 525, 0, 84,197
gauge30=Captain_Sim.p721.O10!O10_002_light, 625, 0, 37,149


[VCockpit07]
size_mm=1024,1024
pixel_size=1024,1024
texture=$fprsp
background_color=0,0,0
gauge00=Captain_Sim.p721.R01!R01_machmeter, 24,26, 200,200
gauge01=Captain_Sim.p721.R03!R03_aplight, 625,749, 55,55
gauge02=Captain_Sim.p721.R04!R04_airspeed, 275, 30, 177, 169
gauge03=Captain_Sim.p721.R05!R05_rmi, 275, 775, 200,200
gauge04=Captain_Sim.p721.R10!R10_altimeter, 275,270, 210,240
gauge05=Captain_Sim.p721.R11!R11_vsi, 20,524, 217,220
gauge06=Captain_Sim.p721.R13!R13_ra, 260,505, 240,240
gauge07=Captain_Sim.p721.R07!R07_adi, 500, 30, 175, 152
gauge08=Captain_Sim.p721.R07!R07_010_slip, 275,225, 200, 47
gauge09=Captain_Sim.p721.R08!R08_hsi, 599, 400, 200, 250
gauge10=Captain_Sim.p721.R09!R09_002_light, 723,649, 133,64
gauge11=Captain_Sim.p721.R09!R09_003_light, 723,724, 133,64
gauge12=Captain_Sim.p721.R09!R09_004_light, 723,799, 133,64
gauge13=Captain_Sim.p721.R09!R09_005_light, 723,874, 133,64
gauge14=Captain_Sim.p721.R09!R09_006_light, 723,949, 80,64
gauge15=Captain_Sim.p721.R09!R09_007_light, 799,949, 80,64
gauge16=Captain_Sim.p721.R09!R09_008_light, 871,649, 136,64
gauge17=Captain_Sim.p721.R09!R09_009_light, 871,724, 136,64
gauge18=Captain_Sim.p721.R09!R09_010_light, 871,799, 136,64
gauge19=Captain_Sim.p721.R09!R09_011_light, 871,874, 136,64
gauge20=Captain_Sim.p721.R09!R09_012_light, 871,949, 136,64
gauge21=Captain_Sim.p721.R09!R09_001_light, 623,924, 92,90
gauge22=Captain_Sim.p721.R15!R15_001_dme,      499,799, 90,30
gauge23=Captain_Sim.p721.R15!R15_002_light, 625,824, 100,45
gauge24=Captain_Sim.p721.R15!R15_003_light, 625,873, 100,45
gauge25=Captain_Sim.p721.R06!R06_001_light, 624,698, 101,46
gauge26=Captain_Sim.p721.R06!R06_002_light, 498,923, 115,81
gauge27=Captain_Sim.p721.R06!R06_003_light, 499,849, 87,57
gauge28=Captain_Sim.p721.R09!R09_013_light, 626,649, 100,45
gauge29=Captain_Sim.p721.R12!R12_001_ndl, 650,225,130,130
gauge30=Captain_Sim.p721.R12!R12_002_ndl, 500,225,130,130
gauge31=Captain_Sim.p721.R02!R02_001_light, 700, 25, 100, 45
gauge32=Captain_Sim.p721.R02!R02_002_light, 700, 75, 100, 45
gauge33=Captain_Sim.p721.R02!R02_003_light, 700, 125, 100, 45
gauge34=Captain_Sim.p721.R02!R02_004_light, 825, 25, 100, 45
gauge35=Captain_Sim.p721.R02!R02_005_light, 825, 75, 100, 45
gauge36=Captain_Sim.p721.R02!R02_006_light, 825, 125, 100, 45
gauge37=Captain_Sim.p721.O21!O21_001, 796, 196, 110, 63

[VCockpit08]
size_mm=1024,1024
pixel_size=1024,1024
texture=$cpsp2
background_color=0,0,0

gauge00=Captain_Sim.p721.C06!C06_001_trim, 0, 0, 380, 380

[VCockpit09]
size_mm=1024,1024
pixel_size=1024,1024
texture=$TVSP
background_color=0,0,0

gauge00=Captain_Sim.p721.L02!L02_clock, 50, 300, 155, 151

[VCockpit10]
size_mm=1024,1024
pixel_size=1024,1024
texture=$gssp
background_color=0,0,0

gauge00=Captain_Sim.p721.GS!GS_004_light, 0,250, 57,91
gauge01=Captain_Sim.p721.GS!GS_007_light, 75,250, 58,91
gauge02=Captain_Sim.p721.GS!GS_010_light, 150,250, 58,91
gauge03=Captain_Sim.p721.GS!GS_001_light, 0,0, 100,50
gauge04=Captain_Sim.p721.GS!GS_002_light, 0,75, 124,63
gauge05=Captain_Sim.p721.GS!GS_003_light, 0,150, 124,63
gauge06=Captain_Sim.p721.GS!GS_009_light, 0,200, 124,63

[Color]
Day=255,255,255
Night=4,4,4
Luminous=128,0,0

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

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on Apr 12th, 2013 at 6:37pm
Welcome to the forums.  :) Can you confirm that your INS/DOPPLER switch is set to INS and that you are running the AP in NAV (not HDG)?




If you INS is properly aligned and working in NAV mode plus has at least one waypoint loaded, it should work.

If you still have trouble, please post a screenshot of the INS unit. Maybe it shows an error code or something which could help. To post screenshots, you can use a free hoster like imageshack.com for example.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Leonardo Pierry on Apr 23rd, 2013 at 11:39pm
Good thread, got my INS unit working also now, thanks.

Leo

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by hellmike on May 24th, 2013 at 4:47pm
is possible to place the ins Virtual Cockpit 707 727 and 737?
how do I do that? please help me, I really want to use INS, but do not know where to look in the topic
my english is not very good ;/

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by CoolP on May 25th, 2013 at 8:22am

hellmike wrote on May 24th, 2013 at 4:47pm:
is possible to place the ins Virtual Cockpit 707 727 and 737?

Well the 707 features this dummy when you are using the 'CIVA' panel.cfg. http://captainsim.org/yabb2/YaBB.pl?num=1285100008/302#302 Unfortunately, it's inop when it comes to interacting with the CIVA gauge.

Regarding the 727, there's a replacement texture set here. http://www.captainsim.org/yabb2/YaBB.pl?num=1277200750

And on the 737 I don't know about any VC mods so far. 2D panels for the CIVA INS work on almost every plane, but the VC integration needs a compatible 3D model (which you can't change) and a replacement or at least free space in the cockpit itself. So if you would for example try to replace the 737 PDCS with the INS gauge, the underlying 3D model would interfere. You might not be able to read and operate the new gauge then.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by highflight on Apr 13th, 2014 at 10:41am
Hello all INS simmers.

Re opening this thread.

I recently d/l the Civa Carousel.

Set up as per the first posts in this thread.

Had a series of failures. Main issue being, the Civa install does not work with the "V" gauge add on.  When "V" gauge is opened the INS displays get badly corrupted along with some VC gauges?

However, I used the download panel.cfg for dual installation and had a little more success. (Thanks CoolP)

Took the best part of 6 hours and still having mixed results. Minus the "V" gauge, so far.

The Civa web site has the following interesting features listed:-

Additional features:

- Induced, per-INS, NAV time based, random "drifting" error
- Induced, per-INS, random unit "hardware" failures


I wonder if those "random" hardware failures are influencing my growing disillusion with the Civa INS?  Its failing to command the heading bug to the first ins waypoint.

Also, the "quick align" counts down to 6:9 and halts there.

I have the "INS/Doppler" set to INS and NAV AP set on? Also follow CoolP's instructions...Well still practising!

Will try some more today.

The loss of the "V" gauge is a greater loss then the INS gauge, so I wll revert back to the V install, if I have more failures today!

Like has been said on this forum, the INS Carousel was state of the art back in the day. ART being the operative word! The modern FMC is very easy to use compared to the INS. Perhaps the totally non-intuitive INS system input is the culprit.  Also we are on a simulation platform known for its quirky behaviour with VAS etc. and we are installing gauges by hand, over different FSX installs.... :-/

Aw well, it may be back to VOR/Doppler NAV ::)

Cheers
David

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by highflight on Apr 13th, 2014 at 2:02pm
Final report on the INS, it cause two CTD's when attempting to update the INS, which incidentally, would not function as described and seen in the video.:-

http://youtu.be/BOuClh2CDBA


So in my case I have not succeeded.  :(

Speed Bird 231 Heavy Bye Bye!

Best regards
David

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Ken Boardman on Apr 30th, 2014 at 6:56am
Just installed dual CIVA in CS Captain (FSX) B727-100.
It aligned and worked perfectly for about 3 waypoints
into the flight and then suddenly quit (shut off). The yellow battery
light on the CDUs appeared when I started to taxi and would go out
when power was reduced and or brakes applied.  After takeoff
this light stayed on constantly until about 3 waypoints (30nm)
and then the CDUs' red warning lights came on and very shortly
thereafter the CIVA system shut down. Anyone have any
idea what I may have missed?
 FYI, I use FSUIPC payware with infinite battery enabled. Also double
checked the generator switches and power switch settings.  Even tried
turning the APU back on and giving it the load (with appropriate power
switch settings).  Recycled the main battery switch (on engineers panel).  
Nothing I tried made the yellow CDU battery light even blink ~:)
Thank you,
Ken  

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by highflight on May 1st, 2014 at 2:00pm
Hello Ken,

I have not tried the CIVA gauge in the 727. My 707 install was only a partial success. I thought I had it nailed after experimenting with different configs. Alas, the CIVA never worked properly for more than a couple of waypoints.

As I previously stated the CIVA INS never worked as demonstrated in the linked video.

http://youtu.be/BOuClh2CDBA

I assumed there must be an anomaly with my FSX/CS 707 install. Since the CIVA INS gauge is freeware and installed by the user, obviously its prone to errors by the users install method.

Of greater concern was the CTD's it caused. In my opinion, when software causes CTD's its either incorrectly set up for FSX, or the Aircraft simulated, or both?

Its a pity because we are attempting to recreate a true simulation of these historic aircraft, which were fitted with an INS for long haul overseas routes.

In the 707, the Doppler nav. works very well. But of course the INS would be the long haul navigation option of choice.

The 727 has only the navigation radios and these work well for VOR/NDB navigation and allow us to simulate short/medium haul routes. I have not attempted an install of the CIVA gauge in the 727. My assumption being that since the gauge code is the same, the panel config.  the same,  the errors would be also.



I suppose the bottom line is that the INS needs to be integrated by the CS programmers to be properly functional.

The 707 Doppler System has been perfectly integrated. So the INS requires the same treatment! ;)

Oh, and a nice 3d INS panel with a Dual gauge would be very welcome too ;)



Best Regards
David.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Ken Boardman on May 1st, 2014 at 5:54pm
Thank you for responding David. I haven't given up yet > a few
more things to try when time permits.  I used the CIVA for several
years with the RFP B742 and loved it, so I'm motivated to get it
working. I'll follow up later.
Best regards,
Ken

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on May 2nd, 2014 at 4:38am
In the 707, all I did was:

1. Install the freeware CIVA INS
2. Backed up the original panel.cfg by renaming it panel_bak.cfg
3. Renamed the CIVA_panel.cfg to panel.cfg
4. *CUT this line: gauge04=../civa/INS!Config,         0,    0,  0, 0, csx701 (from [Window00]) and
   pasted it in [VCockpit01] as gauge27=../civa/INS!Config,         0,    0,  0, 0, csx701
5. Saved panel.cfg.

It works fine.

I did do a dual INS panel a long time ago, but I prefer to use a single unit (i.e. the CIVA_panel.cfg).

* Doing this means that the CIVA INS is initialised as soon as you load the 707 into FSX, rather than having to press SHIFT+1 to initialise it.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Ken Boardman on May 2nd, 2014 at 7:04pm
Thank you for sharing this Mark.  I've never used Shift + 1 to
initialize the CIVA.  The doggon system works fantastic for me in the
CS B727 (when it's selfpowered :)  Only problem is that there seems to
be no transfer of power to it after engine start,  so the CIVA system
(CDU) battery light comes on and stays on after I release parking
brake and apply power for taxi.  Then of course after about 15 min
then red warning light and then after about 5 min the CIVA goes
dead.  Just seems like the aircraft power is not transferring to and
taking over the CIVA system when it should.
  For a workaround > do you know of a way to keep the CIVA
indefinitely powered up by it's own power supply (instead of switching to
aircraft elect system power)?
  Seems somewhere I read that we can delete a *.Isd file in the
CIVA folder and let it recreate itself.  I think I'll try that tonight as
well as default Cessna startup.  Also read that toggling the aircraft
elect syst battery switch two times is part of the solution to this
nasty problem so maybe I'll do that too :)
Best regards,
Ken

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on May 3rd, 2014 at 2:54am
Hi Ken.

So the CIVA INS works okay in the CS B707 for you, but not properly in the CS B727?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by highflight on May 3rd, 2014 at 2:36pm
Its very curious that this CIVA INS should work for some and not for others. Working in the 727 and not in the 707?

In the Dual gauge I attempted to install, I did see the dreaded battery light come on, even after all engine driven generators were stabilised and supplying the entire aircraft? I managed to get that to go out after numerous reset "presses".



I may even try a single install again, like you have Mark.  Perhaps that's the answer?



But at the end of the day the CIVA INS did not work as I saw in the video. Its like it was corrupted somehow?  Trying to update it with the VOR method caused CTD!

Frustrating, to say the least.

The 3d INS in the CS 707 worked as a "dummy" when I had the CIVA running. The Lat/Long current position was displayed. That was also frustrating.


Why can't CS just implement the INS as a full gauge?  It cant be too difficult for the programmer guys...? Can it? :o :-? Why model a very nice "Dummy" 3d gauge? :(

Cheers
David

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Ken Boardman on May 3rd, 2014 at 7:24pm
Hi Mark,
 I saw the "CIVA INS - The thread only please" in this forum so I entered my CIVA question here first.  I don't have the CS B707 (yet ~:)
Do you have the CIVA working properly in the 707?  I sure miss
the VMAX RFP B742.  The CIVA (triple redundant) worked
beautifully in it.
 I'm still working on a (CIVA) solution for the CS B727 that works
every time.  Maybe I'll get lucky.  When I do,  I'll post a CIVA
startup checklist in the CS B727 forum.
Best regards,
Ken  

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on May 4th, 2014 at 1:51am

highflight wrote on May 3rd, 2014 at 2:36pm:
Its very curious that this CIVA INS should work for some and not for others. Working in the 727 and not in the 707?

In the Dual gauge I attempted to install, I did see the dreaded battery light come on, even after all engine driven generators were stabilised and supplying the entire aircraft? I managed to get that to go out after numerous reset "presses".



I may even try a single install again, like you have Mark.  Perhaps that's the answer?



But at the end of the day the CIVA INS did not work as I saw in the video. Its like it was corrupted somehow?  Trying to update it with the VOR method caused CTD!

Frustrating, to say the least.

The 3d INS in the CS 707 worked as a "dummy" when I had the CIVA running. The Lat/Long current position was displayed. That was also frustrating.


Why can't CS just implement the INS as a full gauge?  It cant be too difficult for the programmer guys...? Can it? :o :-? Why model a very nice "Dummy" 3d gauge? :(
As far as I know, the reason that there is no 3D CIVA INS in the 707, is because Captain Sim were waiting for a response from the developers of the SimuFly Delco Carousel IV-A INS and never got one. I hope that now that they (Captain Sim) have made their own version for the L-1011, that this will find its way over to the 707.


Ken Boardman wrote on May 3rd, 2014 at 7:24pm:
I saw the "CIVA INS - The thread only please" in this forum so I entered my CIVA question here first.  I don't have the CS B707 (yet ~:)
Do you have the CIVA working properly in the 707?  I sure miss
the VMAX RFP B742.  The CIVA (triple redundant) worked
beautifully in it.
 I'm still working on a (CIVA) solution for the CS B727 that works
every time.  Maybe I'll get lucky.  When I do,  I'll post a CIVA
startup checklist in the CS B727 forum.

I did think it was about the 727 when I first saw the post here, but I wasn't totally sure.

The INS in the 707 works perfectly fine for me. I originally had a few problems that I fixed by moving the line: gauge04=../civa/INS!Config, 0, 0, 0, 0, csx701 (from [Window00]) and pasting it in [VCockpit01] as gauge27=../civa/INS!Config, 0, 0, 0, 0, csx701. I never realised that pressing SHIFT+1 was the key to getting it to initialise, until it was pointed out to me somewhere in this thread. By then it didn't matter, because having in the [VCockpit.xx] section, it activated as soon as I loaded the 707.

I had a go at doing a flight in the 727 with a Dual INS added, but it performed strangely. The 727 wandered across the sky on its way to each waypoint, as if it had never captured the track properly. After about 30 minutes, I had successfully (and I use that term loosely) navigated 5 waypoints, and was heading for the 6th when I aborted the flight. On that final 100nm  leg, it was still wandering across the sky, not flying the track in a direct line. I never fully lost the battery power during the flight, although the BAT light was on for quite some time before I aborted. It made me think that the performance might have been caused by low battery power, but I doubt that is really why. It was erratic right from the start, long before the battery light came on. :-/

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Ken Boardman on May 4th, 2014 at 5:59am
Hi Mark,
Thank you for this info regarding your success wit B707 and CIVA.
It sweetens the pot (no pun intended ~;)
 I had IMO acceptable success with B727 and CIVA tonight using some
considerably unorthodox preparation and startup procedures.  A fun
(INS) fright from Guam (PGUM) to Kwajalein (PKWA). I have prepared
a somewhat detailed checklist,  and if I'm able to duplicate success
on two more frights I will submit it in 727 forum for use by those
eager to "take the plunge".  CDU Battery caution light stayed out,
Auto Pilot worked, with exception of an annoying but manageable
issue with the pitch channel.  INS connected with the Heading
Channel of the AP, and the aircraft followed the flight plan.  Even
was able to load two *.awc files via the trusty dusty ADEU.  
Best regards,
Ken

UPDATE:  I've had enough success with CS B727 and CIVA to
allow uploading my startup procedure.  If interested,  you can
find it in the "B727 Captain" General forum.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by metzy on Sep 1st, 2014 at 12:35pm
Hi all,

any help or ideas would be much appreciated:

I have installed the gauges fine (did the rename the panel cfg trick).

It starts up all right, but i have to wait like an hour for it to get to 65, where it hangs, then eventually i get an error message.

Is there a fast alaign, and should it take one whole real life hour to align??

thanks

metzy

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Sep 1st, 2014 at 3:19pm
Fast align:

If, in the meantime, 15 mins are passed, we should have on the CDUs the accuracy
performance indexes (API) at value 5 or less and all MSUs READY NAV lights on. If they
aren't yet, we can accelerate the alignement progress by the hidden FAST ALIGN button
below any MSU right upper screw (left mouse click on the screw).

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by metzy on Sep 1st, 2014 at 3:34pm
Great thanks for that. I got it to work after making the change to the VC panel cfg (adding the CIVA CFG gauge) and restarting FSX.

For the life of me find was not helping in acrobat!

thanks again, much appreciated. :)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Sep 2nd, 2014 at 5:30am
Yeah. The docs/manuals are not easy to follow/understand (in my opinion), but over the years I have slowly managed to understand what  the important parts to me. :D

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by addman on Feb 15th, 2015 at 2:18pm
Can't for the love of all things sacred get the CIVA to work. I've installed the Carousel Civa 1.51 in the FSX folder. Installed the 707 1.3 and edited the CIVA_panel.cfg file accordingly. It starts up and I enter my current position (all engines off, parking breaks on and battery on, clear weather no wind). After I turn the knob(s) to Align nothing happens, performance index is stuck at 95. Until I click the "fast positioning" screw, then the battery light lights up yellow and the performance index starts ticking down to 65 and the yellow bat light goes out. After that it gets stuck and stays at 65 forever and nothing happens. I used the CIVA_panel.cfg that was already in the 707 panel folder and did your cut and paste trick but it didn't help. What to do? I'm at complete loss here.

Cheers/Andreas

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Feb 16th, 2015 at 3:42am
Have you initialized the INS?

If you haven't moved the gauge04=../civa/INS!Config,         0,    0,  0, 0, csx701 from the [Window00] section to the [VCockpit01] section (gauge27=../civa/INS!Config,         0,    0,  0, 0, csx701), then you will need to press F10 to go to the Cockpit window of the 707 to initialize the INS.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Don-P1126 on Sep 9th, 2016 at 7:49pm
Breaking out the old lady, and was going through this thread for CIVA installation.   Not sure it could be any more confusing.   But in the hope that it can become less confusing can we get a complete panel setup how it should be with everything there instead of piece mill lines.    Holy wow does that make it really confusing.   I've tried going backwards but that wasn't much help either.   

Just for clarification sake:  There is two panel.cfg in my panel folder so I should be updating the CIVA_Panel.cfg.

Then It will replace the panel.cfg as the main cfg in the PANEL folder?  For the CS_707-300, CS_707-300C, CS_E3       RIGHT?

Thanks
Don

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Sep 10th, 2016 at 2:38am

Don-P1126 wrote on Sep 9th, 2016 at 7:49pm:
Just for clarification sake:  There is two panel.cfg in my panel folder so I should be updating the CIVA_Panel.cfg.

Then It will replace the panel.cfg as the main cfg in the PANEL folder?  For the CS_707-300, CS_707-300C, CS_E3       RIGHT?
Yes. That is the one to modify. I suggest you do this first:

1. Rename the panel.cfg (I renamed mine panel-bak.cfg).
2. Highlight the CIVA_panel.cfg file, press CTRL+C (to copy it), then press CTRL+V (to paste a new copy there) - CIVA_panel - Copy.cfg will appear.
3. Rename the CIVA_panel - Copy.cfg to panel.cfg.

That way you will have a backup of the original panel.cfg, AND the CIVA_panel.cfg ;)

Note. You won't see the file extension (.cfg) unless you have unchecked the Folder options > View tab > Hide extensions for known file types

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by IronRain on Sep 29th, 2016 at 5:06pm
Hi all!

I've got a thing and I'm not sure if this is default behavior or something is wrong.

I've installed the Civa INS (1.51) and renamed CIVA_panel to panel.
If I start FSX and switch to 2D view (F10) I can open the pop-up CIVA panels and initialize everything.
However; my shift keys stops working. I can't open any windows with shift-1, shift-2, etc. If I try to press shift-z (to get my current position), the autopilot is activated (default behavior of the Z key).

Also, looking around through the cockpit while holding the spacebar and moving my mouse doesn't work either.

Any ideas?

Thanks,
Derk

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Sep 30th, 2016 at 1:29am
Open the panel.cfg and change the [Window01] entry from this:

[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, csx701
gauge05=../civa/INS!NavModeSingle,  0,  652,  1, 1
gauge06=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041
gauge07=../civa/INS!MsuPanelIcon,   0,  676, 24, 24, 11040
gauge08=../civa/INS!AdeuPanelIcon,  0,  700, 24, 24, 11042


To this:

[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!NavModeSingle,  0,  652,  1, 1
gauge05=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041
gauge06=../civa/INS!MsuPanelIcon,   0,  676, 24, 24, 11040
gauge07=../civa/INS!AdeuPanelIcon,  0,  700, 24, 24, 11042


Then change the [VCockpit01] entry from this:

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$FPSP
background_color=0,0,0
gauge00=Captain_Sim.x707.R01!R01_001_light, 625, 824, 56,55
gauge01=Captain_Sim.x707.R02!R02_clock, 50, 300, 155,151
gauge02=Captain_Sim.x707.R03!R03_aplight, 625, 750, 55,55
gauge03=Captain_Sim.x707.R05!R05_rmi, 275, 775, 200,200
gauge04=Captain_Sim.x707.R06!R06_001_light, 500,450, 58,57
gauge05=Captain_Sim.x707.R06!R06_002_light, 498,526, 58,57
gauge06=Captain_Sim.x707.R06!R06_003_light, 502,854, 58,57
gauge07=Captain_Sim.x707.R06!R06_004_light, 502,925, 60,57
gauge08=Captain_Sim.x707.R08!R08_hsi, 602, 275, 375, 374      
gauge09=Captain_Sim.x707.R09!R09_001_light, 402,126, 57,57
gauge10=Captain_Sim.x707.R09!R09_002_light, 402,202, 57,57
gauge11=Captain_Sim.x707.R10!R10_altimeter, 280,280, 190,214
gauge12=Captain_Sim.x707.R11!R11_vsi, 725,700, 289,289
gauge13=Captain_Sim.x707.R13!R13_ra, 252,499, 254,254
gauge14=Captain_Sim.x707.R13!R13_001_light, 500,675, 50,50
gauge15=Captain_Sim.x707.R14!R14_001_light, 300,0, 76,75
gauge16=Captain_Sim.x707.R17!R17_008_ndl, 500,125, 130,130
gauge17=Captain_Sim.x707.R17!R17_001_light, 0,0,   75,75
gauge18=Captain_Sim.x707.R17!R17_002_light, 75,0,  75,75
gauge19=Captain_Sim.x707.R17!R17_003_light, 150,0, 75,75
gauge20=Captain_Sim.x707.R17!R17_004_light, 225,0, 75,75
gauge21=Captain_Sim.x707.R18!R18_001_light, 925,25, 75,75
gauge22=Captain_Sim.x707.R18!R18_002_light, 925,100, 75,75
gauge23=Captain_Sim.x707.R18!R18_003_light, 925,175, 75,75
gauge24=Captain_Sim.x707.R16!R16_3D, 25,525,230,74
gauge25=Captain_Sim.x707.menu!main, 0, 0, 1, 1
gauge26=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini


To this:

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$FPSP
background_color=0,0,0
gauge00=Captain_Sim.x707.R01!R01_001_light, 625, 824, 56,55
gauge01=Captain_Sim.x707.R02!R02_clock, 50, 300, 155,151
gauge02=Captain_Sim.x707.R03!R03_aplight, 625, 750, 55,55
gauge03=Captain_Sim.x707.R05!R05_rmi, 275, 775, 200,200
gauge04=Captain_Sim.x707.R06!R06_001_light, 500,450, 58,57
gauge05=Captain_Sim.x707.R06!R06_002_light, 498,526, 58,57
gauge06=Captain_Sim.x707.R06!R06_003_light, 502,854, 58,57
gauge07=Captain_Sim.x707.R06!R06_004_light, 502,925, 60,57
gauge08=Captain_Sim.x707.R08!R08_hsi, 602, 275, 375, 374      
gauge09=Captain_Sim.x707.R09!R09_001_light, 402,126, 57,57
gauge10=Captain_Sim.x707.R09!R09_002_light, 402,202, 57,57
gauge11=Captain_Sim.x707.R10!R10_altimeter, 280,280, 190,214
gauge12=Captain_Sim.x707.R11!R11_vsi, 725,700, 289,289
gauge13=Captain_Sim.x707.R13!R13_ra, 252,499, 254,254
gauge14=Captain_Sim.x707.R13!R13_001_light, 500,675, 50,50
gauge15=Captain_Sim.x707.R14!R14_001_light, 300,0, 76,75
gauge16=Captain_Sim.x707.R17!R17_008_ndl, 500,125, 130,130
gauge17=Captain_Sim.x707.R17!R17_001_light, 0,0,   75,75
gauge18=Captain_Sim.x707.R17!R17_002_light, 75,0,  75,75
gauge19=Captain_Sim.x707.R17!R17_003_light, 150,0, 75,75
gauge20=Captain_Sim.x707.R17!R17_004_light, 225,0, 75,75
gauge21=Captain_Sim.x707.R18!R18_001_light, 925,25, 75,75
gauge22=Captain_Sim.x707.R18!R18_002_light, 925,100, 75,75
gauge23=Captain_Sim.x707.R18!R18_003_light, 925,175, 75,75
gauge24=Captain_Sim.x707.R16!R16_3D, 25,525,230,74
gauge25=Captain_Sim.x707.menu!main, 0, 0, 1, 1
gauge26=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
gauge27=../civa/INS!Config,         0,    0,  0, 0, csx701


All you are doing, is placing the initialisation of the CIVA INS to the Virtual Cockpit, rather than having it in the 2D Cockpit, so you don't need to press F10 to initialize it. The INS will initialize the moment you load the CS 707 into FSX.

Note. I'm not sure why your SHIFT keys don't work correctly after initializing the INS, nor if doing the above will fix that, but I sure hope it does.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by spauls121 on Oct 5th, 2016 at 2:36am
Just want to throw my two cents in; I'm having the same problem with the shift key not working. I'm running FSX: Steam on Windows 10.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Oct 6th, 2016 at 1:34am

spauls121 wrote on Oct 5th, 2016 at 2:36am:
Just want to throw my two cents in; I'm having the same problem with the shift key not working. I'm running FSX: Steam on Windows 10.

It sounds to me like it's an issue between the SimuFly Delco CIVA-INS, and Windows 10 and/or FSX Steam Edition.

I will try it in FSX-SE (Win7), and if that works fine, I guess I'll have to install FSX-SE in Win10 and test it there. <sigh> ;)

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Haseen on Oct 29th, 2016 at 8:24pm
Dear:
I purchased CS707 v1.3 recently for my FSX from Simmarket. I also downloaded/installed SimuFly CIVA INS. After Present Position (PPOS)entry, red warning light on the MSU illuminates. Clear button doesn't extinguish the red light. The fault code is 6. I put the selector to STBY and re-entered PPOS which is already correct. But warning lt. remains on and INS PI doesn't go below 95, green ready light doesn't come on. Please help. :(
Haseen Ahmad
Bangladesh.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Mikhail on Oct 31st, 2016 at 3:56pm
Hello. I have CS 727.
I would like to add CIVA in my VC of 727-200F (cargo model)

If possible, could you help me? Please send me panel.cfg.
Mike, Russia.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by L-1011 on Nov 29th, 2016 at 8:15pm

Jesse wrote on Oct 4th, 2010 at 7:09pm:
I need help getting the Civa INS to work. Kind of got bits and pieces around the forum, this is what I have done so far. I changed the name of the files as per. Marko's suggestion and that helped. Inserted the missing line in the cfg file as suggested by coolp? and that also helped. Auto-pilot doesn't work and I can't insert west co-ordinates. If someone has complete info on how to fix it all starting from the beginning I will so much appreciate it. I will be forever indebted to you.   :-/



Markoz wrote on Sep 30th, 2016 at 1:29am:
Open the panel.cfg and change the [Window01] entry from this:

[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, csx701
gauge05=../civa/INS!NavModeSingle,  0,  652,  1, 1
gauge06=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041
gauge07=../civa/INS!MsuPanelIcon,   0,  676, 24, 24, 11040
gauge08=../civa/INS!AdeuPanelIcon,  0,  700, 24, 24, 11042


To this:

[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!NavModeSingle,  0,  652,  1, 1
gauge05=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041
gauge06=../civa/INS!MsuPanelIcon,   0,  676, 24, 24, 11040
gauge07=../civa/INS!AdeuPanelIcon,  0,  700, 24, 24, 11042


Then change the [VCockpit01] entry from this:

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$FPSP
background_color=0,0,0
gauge00=Captain_Sim.x707.R01!R01_001_light, 625, 824, 56,55
gauge01=Captain_Sim.x707.R02!R02_clock, 50, 300, 155,151
gauge02=Captain_Sim.x707.R03!R03_aplight, 625, 750, 55,55
gauge03=Captain_Sim.x707.R05!R05_rmi, 275, 775, 200,200
gauge04=Captain_Sim.x707.R06!R06_001_light, 500,450, 58,57
gauge05=Captain_Sim.x707.R06!R06_002_light, 498,526, 58,57
gauge06=Captain_Sim.x707.R06!R06_003_light, 502,854, 58,57
gauge07=Captain_Sim.x707.R06!R06_004_light, 502,925, 60,57
gauge08=Captain_Sim.x707.R08!R08_hsi, 602, 275, 375, 374      
gauge09=Captain_Sim.x707.R09!R09_001_light, 402,126, 57,57
gauge10=Captain_Sim.x707.R09!R09_002_light, 402,202, 57,57
gauge11=Captain_Sim.x707.R10!R10_altimeter, 280,280, 190,214
gauge12=Captain_Sim.x707.R11!R11_vsi, 725,700, 289,289
gauge13=Captain_Sim.x707.R13!R13_ra, 252,499, 254,254
gauge14=Captain_Sim.x707.R13!R13_001_light, 500,675, 50,50
gauge15=Captain_Sim.x707.R14!R14_001_light, 300,0, 76,75
gauge16=Captain_Sim.x707.R17!R17_008_ndl, 500,125, 130,130
gauge17=Captain_Sim.x707.R17!R17_001_light, 0,0,   75,75
gauge18=Captain_Sim.x707.R17!R17_002_light, 75,0,  75,75
gauge19=Captain_Sim.x707.R17!R17_003_light, 150,0, 75,75
gauge20=Captain_Sim.x707.R17!R17_004_light, 225,0, 75,75
gauge21=Captain_Sim.x707.R18!R18_001_light, 925,25, 75,75
gauge22=Captain_Sim.x707.R18!R18_002_light, 925,100, 75,75
gauge23=Captain_Sim.x707.R18!R18_003_light, 925,175, 75,75
gauge24=Captain_Sim.x707.R16!R16_3D, 25,525,230,74
gauge25=Captain_Sim.x707.menu!main, 0, 0, 1, 1
gauge26=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini


To this:

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$FPSP
background_color=0,0,0
gauge00=Captain_Sim.x707.R01!R01_001_light, 625, 824, 56,55
gauge01=Captain_Sim.x707.R02!R02_clock, 50, 300, 155,151
gauge02=Captain_Sim.x707.R03!R03_aplight, 625, 750, 55,55
gauge03=Captain_Sim.x707.R05!R05_rmi, 275, 775, 200,200
gauge04=Captain_Sim.x707.R06!R06_001_light, 500,450, 58,57
gauge05=Captain_Sim.x707.R06!R06_002_light, 498,526, 58,57
gauge06=Captain_Sim.x707.R06!R06_003_light, 502,854, 58,57
gauge07=Captain_Sim.x707.R06!R06_004_light, 502,925, 60,57
gauge08=Captain_Sim.x707.R08!R08_hsi, 602, 275, 375, 374      
gauge09=Captain_Sim.x707.R09!R09_001_light, 402,126, 57,57
gauge10=Captain_Sim.x707.R09!R09_002_light, 402,202, 57,57
gauge11=Captain_Sim.x707.R10!R10_altimeter, 280,280, 190,214
gauge12=Captain_Sim.x707.R11!R11_vsi, 725,700, 289,289
gauge13=Captain_Sim.x707.R13!R13_ra, 252,499, 254,254
gauge14=Captain_Sim.x707.R13!R13_001_light, 500,675, 50,50
gauge15=Captain_Sim.x707.R14!R14_001_light, 300,0, 76,75
gauge16=Captain_Sim.x707.R17!R17_008_ndl, 500,125, 130,130
gauge17=Captain_Sim.x707.R17!R17_001_light, 0,0,   75,75
gauge18=Captain_Sim.x707.R17!R17_002_light, 75,0,  75,75
gauge19=Captain_Sim.x707.R17!R17_003_light, 150,0, 75,75
gauge20=Captain_Sim.x707.R17!R17_004_light, 225,0, 75,75
gauge21=Captain_Sim.x707.R18!R18_001_light, 925,25, 75,75
gauge22=Captain_Sim.x707.R18!R18_002_light, 925,100, 75,75
gauge23=Captain_Sim.x707.R18!R18_003_light, 925,175, 75,75
gauge24=Captain_Sim.x707.R16!R16_3D, 25,525,230,74
gauge25=Captain_Sim.x707.menu!main, 0, 0, 1, 1
gauge26=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
gauge27=../civa/INS!Config,         0,    0,  0, 0, csx701


All you are doing, is placing the initialisation of the CIVA INS to the Virtual Cockpit, rather than having it in the 2D Cockpit, so you don't need to press F10 to initialize it. The INS will initialize the moment you load the CS 707 into FSX.

Note. I'm not sure why your SHIFT keys don't work correctly after initializing the INS, nor if doing the above will fix that, but I sure hope it does.


I've the same problem on L-1011...the same solution in this post about 707 will be used also in on L-1011 on P3D ???

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Nov 30th, 2016 at 12:50am

L-1011 wrote on Nov 29th, 2016 at 8:15pm:
I've the same problem on L-1011...the same solution in this post about 707 will be used also in on L-1011 on P3D ???

No. The L-1011 uses Captain Sim's own CIVA INS, not the Simufly Delco CIVA INS that is used on the 707, so this solution will not work on the L-1011.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Pat Mussotte on Dec 3rd, 2016 at 5:12pm

Haseen wrote on Oct 29th, 2016 at 8:24pm:
Dear:
I purchased CS707 v1.3 recently for my FSX from Simmarket. I also downloaded/installed SimuFly CIVA INS. After Present Position (PPOS)entry, red warning light on the MSU illuminates. Clear button doesn't extinguish the red light. The fault code is 6. I put the selector to STBY and re-entered PPOS which is already correct. But warning lt. remains on and INS PI doesn't go below 95, green ready light doesn't come on. Please help. :(
Haseen Ahmad
Bangladesh.

Hi!
6 is not a fault code but as far as I remember the action code 06(I'm a former flight engineer and I used these INS on the DC8 and the DC10 I flew)
When you enter the plane position, you can get a warn with an action code 06. The correct procedure then is to place the selector on DSTRK/STS, you press TEST and most of the time you get an error code 41. Press again TEST and you will see the red warning light goes off. The reason is that you have a discrepancy between the last position recorded by the INS and the present position inserted(That can happen if your plane has been moved to another parking spot far from the arrival parking spot of the previous flight ;)
Cheers

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Sentry on Jan 16th, 2017 at 11:15pm

IronRain wrote on Sep 29th, 2016 at 5:06pm:
Hi all!

I've got a thing and I'm not sure if this is default behavior or something is wrong.

I've installed the Civa INS (1.51) and renamed CIVA_panel to panel.
If I start FSX and switch to 2D view (F10) I can open the pop-up CIVA panels and initialize everything.
However; my shift keys stops working. I can't open any windows with shift-1, shift-2, etc. If I try to press shift-z (to get my current position), the autopilot is activated (default behavior of the Z key).

Also, looking around through the cockpit while holding the spacebar and moving my mouse doesn't work either.

Any ideas?

Thanks,
Derk


Did anyone find a soluction to this problem? I just got the 707, and when editing the panel.cfg to fit it with CIVA my Shift+1,2,3 does not work. The spacebar for freelook is not working either. It may be a hotkey missmatch.
I tried to install the INS only to the base version, and it is this version (or any other that I install it into) that get this problem. The other models 300C and E-3 is unaffected as long as I don't add the CIVA into the panel.cfg.

Please, anyone?  :D

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Sentry on Jan 23rd, 2017 at 3:02pm
I've un-installed and installed the airplane several times now, and allways end up with the same problem. I can't understand how the entry to the cfg can change the keymapping?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Jan 24th, 2017 at 5:23am

Sentry wrote on Jan 23rd, 2017 at 3:02pm:
I've un-installed and installed the airplane several times now, and allways end up with the same problem. I can't understand how the entry to the cfg can change the keymapping?

The 707 comes with a panel_CIVA.cfg. Have you tried using that, to see if affects the shift keys, or are you just adding the SimuFly CIVA INS to the 707's default panel.cfg?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Sentry on Jan 24th, 2017 at 8:40pm
I used the panel_civa.cfg file as I see other have had no problems with that. Sadly my sucess was not that great.  :-/

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by FtHays2000 on Mar 18th, 2017 at 8:54pm
I came here to the forum because I too have the issue with the INS not powering on, but am madder now than before I began my search for a resolution.

I have tried the following:

1) Flipped the INS/Doppler switch on the main panel to "INS."

2) Attempted to find and delete the file csx701.isd, but wasn't able to find it. I checked every single place I could in the CIVA directory.

3) Renamed the civa panel config file to just panel config (after making backup copies of both)

I have successfully programmed and used an INS on other payware aircraft, so I have no idea what I'm doing wrong or what I need to change. It's not very practical for me to wade through 23 pages of discussion on the topic. I'm also terrified of screwing up my installation so badly that I have to delete and reinstall.

Would someone with more knowledge about this issue help me out? I just want my INS to work so I can actually fly somewhere.

-Matt

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Mar 19th, 2017 at 1:12am
Did you go to the Cockpit (the default keyboard shortcut is F10) to initialize it? Or did you move the initialisation line to [VCockpit01], which initialises the CIVA INS as soon as the 707 loads into FSX/FSX-SE (see bellow)?

Move the gauge04=../civa/INS!Config,         0,    0,  0, 0, csx701:

[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, csx701
gauge05=../civa/INS!NavModeSingle,  0,  652,  1, 1        (then change this to gauge04= etc.)
gauge06=../civa/INS!CduPanelIcon,   0,  652, 24, 24, 11041        (then change this to gauge05= etc.)
gauge07=../civa/INS!MsuPanelIcon,   0,  676, 24, 24, 11040        (then change this to gauge06= etc.)
gauge08=../civa/INS!AdeuPanelIcon,  0,  700, 24, 24, 11042        (then change this to gauge07= etc.)

To here:

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$FPSP
background_color=0,0,0
gauge00=Captain_Sim.x707.R01!R01_001_light, 625, 824, 56,55
gauge01=Captain_Sim.x707.R02!R02_clock, 50, 300, 155,151
gauge02=Captain_Sim.x707.R03!R03_aplight, 625, 750, 55,55
gauge03=Captain_Sim.x707.R05!R05_rmi, 275, 775, 200,200
gauge04=Captain_Sim.x707.R06!R06_001_light, 500,450, 58,57
gauge05=Captain_Sim.x707.R06!R06_002_light, 498,526, 58,57
gauge06=Captain_Sim.x707.R06!R06_003_light, 502,854, 58,57
gauge07=Captain_Sim.x707.R06!R06_004_light, 502,925, 60,57
gauge08=Captain_Sim.x707.R08!R08_hsi, 602, 275, 375, 374      
gauge09=Captain_Sim.x707.R09!R09_001_light, 402,126, 57,57
gauge10=Captain_Sim.x707.R09!R09_002_light, 402,202, 57,57
gauge11=Captain_Sim.x707.R10!R10_altimeter, 280,280, 190,214
gauge12=Captain_Sim.x707.R11!R11_vsi, 725,700, 289,289
gauge13=Captain_Sim.x707.R13!R13_ra, 252,499, 254,254
gauge14=Captain_Sim.x707.R13!R13_001_light, 500,675, 50,50
gauge15=Captain_Sim.x707.R14!R14_001_light, 300,0, 76,75
gauge16=Captain_Sim.x707.R17!R17_008_ndl, 500,125, 130,130
gauge17=Captain_Sim.x707.R17!R17_001_light, 0,0,   75,75
gauge18=Captain_Sim.x707.R17!R17_002_light, 75,0,  75,75
gauge19=Captain_Sim.x707.R17!R17_003_light, 150,0, 75,75
gauge20=Captain_Sim.x707.R17!R17_004_light, 225,0, 75,75
gauge21=Captain_Sim.x707.R18!R18_001_light, 925,25, 75,75
gauge22=Captain_Sim.x707.R18!R18_002_light, 925,100, 75,75
gauge23=Captain_Sim.x707.R18!R18_003_light, 925,175, 75,75
gauge24=Captain_Sim.x707.R16!R16_3D, 25,525,230,74
gauge25=Captain_Sim.x707.menu!main, 0, 0, 1, 1
gauge26=Captain_Sim.x707.sound!main, 0,0,1,1,Captain_Sim\707\sound.ini
;CIVA
gauge27=../civa/INS!Config,         0,    0,  0, 0, csx701

The csx701.Isd file should be in the FSX\Civa folder. If it isn't there, then the CIVA INS hasn't initialsed the INS for the 707 yet.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Caribflyer on Apr 8th, 2017 at 11:08pm
Does anyone know how to add a second Adeu unit? I have everything setup nicely but for some reason even with the remote button on, DME info is not transfered to the second INS unit.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Apr 10th, 2017 at 1:49am
I would assume that you just add a second Adeu gauge in the [Window08] section. Like this:

[Window08]
size_mm=500,101
background_color=16,16,16
window_pos=0.300, 0.416
position=8
visible=0
ident=11042
no_luminous=1
gauge00=../civa/INS!Adeu1, 0, 0, 250, 101
gauge01=../civa/INS!Adeu2, 250, 0, 250, 101

Note. This is using the CIVA_panel.cfg as the file to make the changes in.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Caribflyer on Apr 11th, 2017 at 3:00pm
Thanks!

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by 1230james on Sep 25th, 2017 at 4:05am

IronRain wrote on Sep 29th, 2016 at 5:06pm:
Hi all!

I've got a thing and I'm not sure if this is default behavior or something is wrong.

I've installed the Civa INS (1.51) and renamed CIVA_panel to panel.
If I start FSX and switch to 2D view (F10) I can open the pop-up CIVA panels and initialize everything.
However; my shift keys stops working. I can't open any windows with shift-1, shift-2, etc. If I try to press shift-z (to get my current position), the autopilot is activated (default behavior of the Z key).

Also, looking around through the cockpit while holding the spacebar and moving my mouse doesn't work either.

Any ideas?

Thanks,
Derk

I'm getting the same issue.
I've already tried moving the Civa INS gauge lines in panel.cfg around to have it initialize right as the plane loads, but it hasn't worked.

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by 1230james on Oct 13th, 2017 at 8:34pm
I just fixed it!

Disabling the in-game Steam Overlay seems to have fixed the issue. It seems that it happens with a few other addons, too, according to other forums.

Hope this helps!

Title: Strange bug using the CIVA panel.cfg
Post by Alessio_Calandrella on Jul 30th, 2017 at 3:32am
Hi captains!
I've recently purchased the 707 captain.
I decided to use the civa ins.
So:
I have already installed the delco carousel civa ins v1.51
Renamed the CIVA INS panel.cfg to panel.cfg as mentioned here:
"1. Backup (rename) original panel.cfg file in ...\SimObjects\Airplanes\CS_B707-300\panel\ folder.
2. Rename civa_panel.cfg file to panel.cfg file."
But doing this i cant move anymore the view using space + mouse movement, i cant use any of 2D panels (if i press Shift + 1, in example, nothing happens).
If i restore the "original" panel.cfg everythings works as intended.
Any clues?
Thanks in advance
Alessio

Title: Re: Strange bug using the CIVA panel.cfg
Post by 1230james on Aug 9th, 2017 at 3:23am
Make sure everything about the CIVA INS panel.cfg is the exact same as the regular one.

The only difference between the two, if I recall correctly, is that one has some lines for the CIVA INS 2D panel "elements" tacked onto the bottom of the list of 2D panel items.

Title: Re: Strange bug using the CIVA panel.cfg
Post by Markoz on Aug 10th, 2017 at 4:25am
Backing up the original panel.cfg, then renaming the CIVA_panel.cfg to panel.cfg, should allow everything to work properly. You will need to go to the 2D Cockpit (the default keyboard shortcut is F10) to initialise the CIVA INS so it works.

Note - I moved the gauge04=../civa/INS!Config, 0, 0, 0, 0, csx701
from [Window00], and added it to [VCockpit01] gauge27=../civa/INS!Config, 0, 0, 0, 0, csx701, so that the CIVA INS initialises as soon as the 707 is loaded into FSX, without the need to press F10 to initialise it.

Title: Re: Strange bug using the CIVA panel.cfg
Post by 1230james on Sep 23rd, 2017 at 11:22pm
Err, I am suddenly having the exact same issue.

Title: Re: Strange bug using the CIVA panel.cfg
Post by 1230james on Oct 13th, 2017 at 2:26am
I tried doing a fresh reinstallation of FSX before reinstalling the 707 and Civa INS. No luck.

Although, I have the sneaking suspicion that having the A2A C172 might be related to it. Stupid move on my part, but I guess I should have installed and tested the 707 before installing the 172.

Title: Re: Strange bug using the CIVA panel.cfg
Post by Alessio_Calandrella on Oct 14th, 2017 at 1:27pm

1230james wrote on Oct 13th, 2017 at 2:26am:
I tried doing a fresh reinstallation of FSX before reinstalling the 707 and Civa INS. No luck.

Although, I have the sneaking suspicion that having the A2A C172 might be related to it. Stupid move on my part, but I guess I should have installed and tested the 707 before installing the 172.

I dont have the A2A 172 but i still have the civa issue. I don't think its related to the 172

Title: Re: Strange bug using the CIVA panel.cfg
Post by 1230james on Oct 16th, 2017 at 12:29am
I fixed it a few days ago. It seems that I went to every thread I knew except this one when I went to go post the solutions, lol

Are you running FSX:SE (or FSX Boxed through Steam)? If so, try disabling the Steam Overlay on FSX.

Title: Re: Strange bug using the CIVA panel.cfg
Post by Markoz on Oct 16th, 2017 at 3:12am

1230james wrote on Oct 16th, 2017 at 12:29am:
I fixed it a few days ago. It seems that I went to every thread I knew except this one when I went to go post the solutions, lol

Are you running FSX:SE (or FSX Boxed through Steam)? If so, try disabling the Steam Overlay on FSX.

Thanks for the fix! At least I now know why I never encountered this problem with FSX-SE - It's because I can't stand the Steam Overlay, and have had it turned off for all games, since soon after installing Steam on my PC! ;D ;D

Title: Re: Strange bug using the CIVA panel.cfg
Post by Alessio_Calandrella on Oct 20th, 2017 at 9:04am

1230james wrote on Oct 16th, 2017 at 12:29am:
I fixed it a few days ago. It seems that I went to every thread I knew except this one when I went to go post the solutions, lol

Are you running FSX:SE (or FSX Boxed through Steam)? If so, try disabling the Steam Overlay on FSX.

Thank you for this!

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by ghostminer on Apr 3rd, 2018 at 11:22pm
i have been trouble with the ins not turning on when i put it to stand by and a graphic glitch in the cockpit of the 707 when i rename the civa_panel and start up fsx and get in it is there a fix for it?

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by Markoz on Apr 4th, 2018 at 12:46am
I'm pretty sure I read somewhere, that the Delco CIV-A INS doesn't work in Windows 10. So if your using Windws 10, then that might explain why it isn't working. :(

It seems that after a long period of nothing happening with it, after 10 years, they now have a 1.60 BETA version, so you might want to try it:

Delco CIV-A INS v1.60 BETA 3

This might just be what you need to use to get it working.  :-/

Title: Re: CIVA INS - THE ONLY THREAD PLEASE
Post by 1230james on Jul 14th, 2018 at 5:43pm

Markoz wrote on Apr 4th, 2018 at 12:46am:
I'm pretty sure I read somewhere, that the Delco CIV-A INS doesn't work in Windows 10. So if your using Windws 10, then that might explain why it isn't working. :(

I have some doubts about that. I'm running Windows 10 and Simufly's CIV-A INS works just fine for me.
Excluding those angry moments I get from random INS battery overheats on single-INS aircraft

CAPTAIN SIM FORUM » Powered by YaBB 2.6.0!
YaBB Forum Software © 2000-2024. All Rights Reserved.