Just I wanted to taxi to my takeoff-position I noticed, that the Civa brings a failure 03 followed by 22 and 23 but when I push the throttle...If I pull back to idle the failure can be canceled by pushing "test", if I fire it up again -> failure until I decelerate the throttle...What's wrong here?Does anybody have a hint for me?

Just I wanted to taxi to my takeoff-position I noticed, that the Civa brings a failure 03 followed by 22 and 23 but when I push the throttle...If I pull back to idle the failure can be canceled by pushing "test", if I fire it up again -> failure until I decelerate the throttle...What's wrong here?Does anybody have a hint for me?

If you look at your INS manuel you will see:-Action code 03 may be due to either power loss (Bat mode in progress) or connection failure between INS and AP & FD03-22 The TK or TKE+DA output from the INS has failed a comparison check (output value and feedback differ by more than 2

Thx for your comment...I'm strict following the tutorial to set the aircraft up, ok, not from Boston to Miami, but it should be the same...Position is set correctly via the values of Shift+Z and I get the "ready" in green also, after that set to NAV...Distances between the waypoints are different by 1nm to the flightplan-distances, but it should be correct...I don't know, what I'm doing wrong. All seems to be fine until I give throttle to taxi.

Ok, today I tried it again step by step as described in the tutorial.It's not the first time as I'm using the CIVA, I made several flights in the B727 with success.BUTI'm not using the 1.25, because of several custom settings I made for me, but the 1.26 gauge update. Could be the mistake on this side?So again, all went fine until I want to taxi, then comes the mistake with throttle open, if I pull back the throttle the failure is away again.Throttle open -> failureThrottle idle -> no failure

Ok, today I tried it again step by step as described in the tutorial.It's not the first time as I'm using the CIVA, I made several flights in the B727 with success.BUTI'm not using the 1.25, because of several custom settings I made for me, but the 1.26 gauge update. Could be the mistake on this side?So again, all went fine until I want to taxi, then comes the mistake with throttle open, if I pull back the throttle the failure is away again.Throttle open -> failureThrottle idle -> no failure

a. You should be using the 1.5 Civa gauge.b. You also clearly have a problem with your throttle identification. Make sure you are using the correct CIVA gauge and then examine carefully your control settings to ensure there is no conflict. Some 737 panel versions have a form of INS already embedded which conflicts with the add-on CIVA gauge.vololiberista

Thx vololiberista,My Civa is version 1.51Panel should be the Tinmouse-Panel, don't know who created it. (with 1.26 gauge-update, but don't know the version of the panel itself, maybe there's the failure)and I'm using a panel.cfg which I've found in the fsconv-folder called panel.CIVA or so.Does anybody have a working panel.cfg, which I could try. Maybe there's anything wrong?I think, I'll reinstall the Tinmouse...

I just only changed panel.cfg for working suitable with CIVA INS and TCASII in fsfsconv. INS does work as well.As advise above also additional;when start your FS,open default C172 (or any default plane) first, check BAT ON , AVIONICS ON, then select TMII 737200. It does work for referesh the codes.While setup INS be sure you get supporting by BATTERY, don't startup engines. Some of personal setups causing; throttle did not fully iddle position thatswhy, plane moves very very slowly when engines run. Setup your INS while engines stops.When illuminate BAT switch on INS, it should be turns OFF in few seconds. If doesn't turns off, press TEST button on INS panel. INS is very sensitive during setup session.

Did it as you described... but without loading the C172 before...APU on, engines off, then I went through the initialisation, step by step, all seemed to be fine until I move the throttle forward.I don't know, where my mistake is...Will try that to load the default c172 before...EDIT:It seems to work now...!So, what I've done:updated the panel-folder in fsconv to version 1.25 and gauge-update to 1.26changed the panel.cfgloaded the default c172 beforewas careful at the entries in the CIVA INSAnd yes, she's following her route now.I think the problem is solved, but I can't figure it out, if it was my mistake or any wrong config or anything. Of course in every case it was my fault, because the stupid sits in front of the screen... :( I'll enjoy my flight to the Caymans in my Bahamas 732 now.Phil

Phil, have a nice flight. I was looking for Bahamasair 7372 for making an online flight (vatsim) from Nassau to Miami yesterday night :)I've sensitive/excessive nose up action and elevator autopilot problem. hen I engaged A/P ELEV plane starts to pitching .Do you have any problem about this issue?

Noticed this as well, in levelflight she has her nose a little bit up and hang down at the tail. In flight on flightlevel she would be very nervous if you wouldn't fly with AP on.Didn't find the solution and don't know where I could start for search.But for the moment try AP on and if it starts whipping try to get against with the trim until it calm down.

Just I wanted to taxi to my takeoff-position I noticed, that the Civa brings a failure 03 followed by 22 and 23 but when I push the throttle...If I pull back to idle the failure can be canceled by pushing "test", if I fire it up again -> failure until I decelerate the throttle...What's wrong here?Does anybody have a hint for me?

I'm thinking that your original problem was due to not having the parking brakes set during the INU alignment. The CIVA INS gauges simulate a power source to the INU when on the ground with the parking brakes set. If the parking brakes are not set before the engine generators are powered up, the INU thinks it's on batt power only. I believe this is explained in the CIVA docs.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Noticed this as well, in levelflight she has her nose a little bit up and hang down at the tail. In flight on flightlevel she would be very nervous if you wouldn't fly with AP on.Didn't find the solution and don't know where I could start for search.But for the moment try AP on and if it starts whipping try to get against with the trim until it calm down.

You should be flying straight and level with about 102 deg nose up at altitude. That's a normal configuration.vololiberista