Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Civa INS won't capture

Featured Replies

I have version 1.51 Civa INS installed within FS2004 along with my Tinmouse 737-200 aircraft.When I set the INS system up ready for operation prior to moving the aircraft all seems well, (Aligning, setting to Nav, entering waypoints, etc.), I have waypoints ready to follow which have been entered and checked, after take off, when I click on the "Nav" button (Rad/Nav") on the main panel to couple the INS system to the auto pilot, with the auto pilot B "on" and with heading mode selected, and while on a heading providing a very low cross track error "XTR/TKE" (0.9 or less), the INS waypoint is not captured and I continue to stay in heading mode. Any suggestions what might be wrong, or what I need to do?Thanks for any help with this question.

I have version 1.51 Civa INS installed within FS2004 along with my Tinmouse 737-200 aircraft.When I set the INS system up ready for operation prior to moving the aircraft all seems well, (Aligning, setting to Nav, entering waypoints, etc.), I have waypoints ready to follow which have been entered and checked, after take off, when I click on the "Nav" button (Rad/Nav") on the main panel to couple the INS system to the auto pilot, with the auto pilot B "on" and with heading mode selected, and while on a heading providing a very low cross track error "XTR/TKE" (0.9 or less), the INS waypoint is not captured and I continue to stay in heading mode. Any suggestions what might be wrong, or what I need to do?Thanks for any help with this question.
The Sperry 77 will stay in heading mode...the INS makes its inputs to the AFCS by slewing the heading bug.Make sure that after entering NAV mode you have entered an active leg, normally "WYPT CHG" then "1" then "2" then "INSERT" to activate a leg from waypoint 1 to waypoint 2. If the INS is in "AUTO" the active legs will switch automatically at waypoint passage.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE
Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@60Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090
Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus,
TM TCA Officer Pack
, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case

  • Author

Thank you for your reply to this topic, I did make sure your directions where followed, sadly the same problem persists.When I set the selection from "Rad" to "Nav" with the auto pilot on and in heading mode etc. the heading bug remains in its previously selected position, and I am still able to alter the heading bug as in "Rad" mode and the aircraft follows any alteration to my heading as if still in "Rad" mode. It seems that the INS system is not connecting to drive the heading bug.Maybe if you are able to send be the parts of the aircraft.cfg and/or panel.cfg that effect this aspect of the simulation, I could copy and paste it into my panel.cfg and/or aircraft.cfg and give that a try. My tinmouse has the reality xp weather radar and the "ilh_tcas_v4" installed and working fine.Thank you for your continued help in this regard.

Make sure that you have v1.24 of the panel gauge...the earlier versions will not work with the new (v1.50 and later) versions of the CIVA INS unit.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE
Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@60Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090
Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus,
TM TCA Officer Pack
, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case

  • 2 weeks later...
  • Author

Thank you for your advice, can I ask how do I check which version of the panel gauge I have? The reason I ask is of interest for another reason aswell as the one you mention, with regard to the "performance data Calcuation system". When I validate the "pdcs" (page 3) system and then enter a figure in to the temperature field and activate the take off thrust calculation I always get the default epr of 1.52 which can be activated and the bugs on the epf fauge do move to indicate this selection.The epf remains the same (1.52) when I select climb thrust. It seems that the calculation is not being made.This part of the panel I know should provide variable epr settings, maybe it is a problem with my panel gauge.All other aspects of the panel seem to be working well. any ideas?Thank you for your continued help with my Tinmouse 737-200 panel issues.

  • Author

Found a more recent gauge (from "version2 panel" download from flightsim.com), after adding this all seems well with tinmouse panel.Thanks for the help.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.