Cessna 337 Nav needle not working

[SurferTim]

It's a interpolation challenge.
Localizer full scale deflection value -2.2 to 2.2
VOR full scale deflection value -10.0 to 10.0
I have it working (I think). I'll test fly it a few times to make sure.

[polly]

@SurferTim
Could you explain 'localiser' please ? The Nav dials on the c337 are identical, KI206 according to their titles in Models/Instruments/VOR, both have GS indicators and so I was thinking either can handle either VOR or ILS.

With the Nav2 settings shown in OP's 'real' screenshot, 108.50 is Inverness' 08/23 ILS and Nav2 display clearly shows ILS and GS false lobes on departure from EGPE, so Nav2 does both VOR and ILS, as is.

The OP is pretty clear there's no movement at all in the dial when at Iverness, about 60nm from Wick. OP has not follwed the advice to locate at Wick to see the effect of a strong signal but their screenshot clearly shows No Signal from Wick, whose range is 130nm from the Nav database, in the properties tree: in-range is false and the ID is empty. I think we can all see a small deviation on Wick VOR when on the ground at inverness and the sensitivity increases as soon as in the air. OP can see no deviation at all.

I think the issue still is, OP's Nav1 is not receiving Wick VOR from Inverness. If they would follow advice and try again from Wick we could learn something.

[D-ECHO]

@SurferTim: You can use the -norm properties, then there is no interpolation needed

[SurferTim]

The name of the localizer needle is Needle_LOC. It serves as the bearing offset indicator for VOR, and localizer when ILS.
This is the change in C337/Models/Instruments/VOR/KI-206-nav1.xml. It's 2 animations now. These replace the original single animation.
Note the condition parameters.

Code: Select all

<animation>
   <type>translate</type>
   <object-name>Needle_LOC</object-name>
   <property>instrumentation/nav[0]/heading-needle-deflection</property>
   <condition>
      <property>instrumentation/nav[0]/nav-loc</property>
   </condition>
   <interpolation>
      <entry><ind>-12.0</ind><dep>-0.0161</dep></entry>
      <entry><ind>0.0</ind><dep>0.0</dep></entry>
      <entry><ind>12.0</ind><dep>0.0161</dep></entry>
   </interpolation>
   <axis>
      <x>0.0</x>
      <y>1.0</y>
      <z>0.0</z>
   </axis>
</animation>

<animation>
   <type>translate</type>
   <object-name>Needle_LOC</object-name>
   <property>instrumentation/nav[0]/heading-needle-deflection</property>
   <condition>
      <not>
         <property>instrumentation/nav[0]/nav-loc</property>
      </not>
   </condition>
   <interpolation>
      <entry><ind>-2.2</ind><dep>-0.0161</dep></entry>
      <entry><ind>0.0</ind><dep>0.0000</dep></entry>
      <entry><ind>2.2</ind><dep>0.0161</dep></entry>
   </interpolation>
   <axis>
      <x>0.0</x>
      <y>1.0</y>
      <z>0.0</z>
   </axis>
</animation>


@D-ECHO what do you mean by "-norm"?

I'm sittinng on the ramp at Inverness airport in the C337, and I am getting a valid signal and display on 109.20

[D-ECHO]

instrumentation/nav/heading-needle-deflection-norm

[SurferTim]

I'll take a look. Thanks. That would save a bit of coding.

Edit: The -norm has the same scaling problem. VOR range is 0.22 to -0.22. Localizer range is 1 to -1.

[cookf]

Console slightly trickier as I am unwisely not running it on Linux. I hope I copied the correct output from the console. Not sure if it is relevant:I took off from inverness with nav1 tuned to local VOR at 109.20MHz.

props.dump(props.globals.getNode("/instrumentation/nav[0]"));

82.30 [INFO]:nasal
82.30 [INFO]:nasal MODEL INFO: Cessna 337G Skymaster
82.30 [INFO]:nasal ---------------------------------
82.30 [INFO]:nasal Type: Two-engine aircraft (civilian version)
82.30 [INFO]:nasal Powerplant: 2 Continental IO-360-C piston engines in a push-pull line configuration, 210HP each one
82.30 [INFO]:nasal Capacity: 1 pilot and 5 passengers
82.30 [INFO]:nasal ---
82.30 [INFO]:nasal Tipo: Avioneta bimotor (version civil)
82.30 [INFO]:nasal Planta motriz: 2 motores a piston Continental IO-360-C de 210HP cada uno, de configuracion tira-empuje en linea
82.30 [INFO]:nasal Capacidad: 1 piloto y 5 pasajeros
82.30 [INFO]:nasal
82.30 [INFO]:nasal Authors/Autores: Fernando Espinosa y Pavel Cueto
82.30 [INFO]:nasal February/Febrero 2012
82.31 [INFO]:nasal KMA24 AudioPanel loaded
82.31 [INFO]:nasal Emergency Locator Transmitter (ELT) loaded
82.31 [INFO]:nasal Navomatic 400A Autopilot Loaded
82.31 [INFO]:nasal KN62A DME #0 loaded
82.35 [INFO]:nasal KT76A Transponder #0 loaded
82.35 [INFO]:nasal Hobbs Meter #0 loaded
96.23 [ALRT]:flight Failed to save initial FDM property state
248.04 [ALRT]:flight Failed to save initial FDM property state
273.93 [INFO]:terrasync Starting automatic scenery download/synchronization to 'C:/Users/cookf/FlightGear/Downloads/TerraSync'.
280.50 [INFO]:nasal
280.50 [INFO]:nasal MODEL INFO: Cessna 337G Skymaster
280.50 [INFO]:nasal ---------------------------------
280.50 [INFO]:nasal Type: Two-engine aircraft (civilian version)
280.50 [INFO]:nasal Powerplant: 2 Continental IO-360-C piston engines in a push-pull line configuration, 210HP each one
280.51 [INFO]:nasal Capacity: 1 pilot and 5 passengers
280.51 [INFO]:nasal ---
280.51 [INFO]:nasal Tipo: Avioneta bimotor (version civil)
280.51 [INFO]:nasal Planta motriz: 2 motores a piston Continental IO-360-C de 210HP cada uno, de configuracion tira-empuje en linea
280.51 [INFO]:nasal Capacidad: 1 piloto y 5 pasajeros
280.51 [INFO]:nasal
280.51 [INFO]:nasal Authors/Autores: Fernando Espinosa y Pavel Cueto
280.51 [INFO]:nasal February/Febrero 2012
280.52 [INFO]:nasal KMA24 AudioPanel loaded
280.52 [INFO]:nasal Emergency Locator Transmitter (ELT) loaded
280.52 [INFO]:nasal Navomatic 400A Autopilot Loaded
280.52 [INFO]:nasal KN62A DME #0 loaded
280.53 [INFO]:nasal KT76A Transponder #0 loaded
280.53 [INFO]:nasal Hobbs Meter #0 loaded
301.39 [ALRT]:flight Failed to save initial FDM property state
742.34 [INFO]:nasal nav {NONE} = nil
742.34 [INFO]:nasal nav/frequencies {NONE} = nil
742.34 [INFO]:nasal nav/frequencies/selected-mhz {DOUBLE} = 109.2
742.34 [INFO]:nasal nav/frequencies/standby-mhz {DOUBLE} = 112
742.34 [INFO]:nasal nav/frequencies/selected-mhz-fmt {STRING} = 109.20
742.35 [INFO]:nasal nav/frequencies/standby-mhz-fmt {STRING} = 112.00
742.35 [INFO]:nasal nav/frequencies/is-localizer-frequency {BOOL} = 0
742.35 [INFO]:nasal nav/radials {NONE} = nil
742.35 [INFO]:nasal nav/radials/selected-deg {DOUBLE} = 284
742.35 [INFO]:nasal nav/radials/actual-deg {NONE} = nil
742.35 [INFO]:nasal nav/radials/reciprocal-radial-deg {NONE} = nil
742.35 [INFO]:nasal nav/radials/target-radial-deg {NONE} = nil
742.35 [INFO]:nasal nav/radials/target-auto-hdg-deg {NONE} = nil
742.35 [INFO]:nasal nav/serviceable {BOOL} = 1
742.35 [INFO]:nasal nav/cdi {NONE} = nil
742.35 [INFO]:nasal nav/cdi/serviceable {BOOL} = 1
742.35 [INFO]:nasal nav/gs {NONE} = nil
742.35 [INFO]:nasal nav/gs/serviceable {BOOL} = 1
742.35 [INFO]:nasal nav/to-from {NONE} = nil
742.35 [INFO]:nasal nav/to-from/serviceable {BOOL} = 1
742.35 [INFO]:nasal nav/slaved-to-gps {BOOL} = 0
742.35 [INFO]:nasal nav/power-btn {BOOL} = 0
742.35 [INFO]:nasal nav/volume {DOUBLE} = 0.5
742.35 [INFO]:nasal nav/ident {BOOL} = 1
742.35 [INFO]:nasal nav/frq-swap-btn {UNSPECIFIED} = 0
742.35 [INFO]:nasal nav/operable {BOOL} = 0
742.36 [INFO]:nasal nav/data-is-valid {BOOL} = 0
742.36 [INFO]:nasal nav/audio-btn {BOOL} = 0
742.36 [INFO]:nasal nav/back-course-btn {BOOL} = 0
742.36 [INFO]:nasal nav/heading-deg {DOUBLE} = 0
742.36 [INFO]:nasal nav/time-to-intercept-sec {DOUBLE} = 0
742.36 [INFO]:nasal nav/to-flag {BOOL} = 0
742.36 [INFO]:nasal nav/from-flag {BOOL} = 0
742.36 [INFO]:nasal nav/in-range {BOOL} = 0
742.36 [INFO]:nasal nav/signal-quality-norm {DOUBLE} = 0
742.36 [INFO]:nasal nav/heading-needle-deflection {DOUBLE} = 0
742.36 [INFO]:nasal nav/heading-needle-deflection-norm {DOUBLE} = 0
742.36 [INFO]:nasal nav/crosstrack-error-m {DOUBLE} = 0
742.36 [INFO]:nasal nav/crosstrack-heading-error-deg {DOUBLE} = 0
742.36 [INFO]:nasal nav/has-gs {BOOL} = 0
742.36 [INFO]:nasal nav/nav-loc {BOOL} = 0
742.36 [INFO]:nasal nav/nav-distance {NONE} = nil
742.36 [INFO]:nasal nav/gs-needle-deflection {DOUBLE} = 0
742.36 [INFO]:nasal nav/gs-needle-deflection-deg {DOUBLE} = 0
742.36 [INFO]:nasal nav/gs-needle-deflection-norm {DOUBLE} = 0
742.36 [INFO]:nasal nav/gs-direct-deg {DOUBLE} = 0
742.36 [INFO]:nasal nav/gs-rate-of-climb {NONE} = nil
742.37 [INFO]:nasal nav/gs-rate-of-climb-fpm {NONE} = nil
742.37 [INFO]:nasal nav/gs-distance {NONE} = nil
742.37 [INFO]:nasal nav/gs-in-range {BOOL} = 0
742.37 [INFO]:nasal nav/nav-id {STRING} =
742.37 [INFO]:nasal nav/nav-id_asc1 {NONE} = nil
742.37 [INFO]:nasal nav/nav-id_asc2 {NONE} = nil
742.37 [INFO]:nasal nav/nav-id_asc3 {NONE} = nil
742.37 [INFO]:nasal nav/nav-id_asc4 {NONE} = nil
742.37 [INFO]:nasal nav/dme-in-range {BOOL} = 1
749.91 [INFO]:nasal --------------------------------------------------------------------------------

749.91 [INFO]:nasal props.dump(props.globals.getNode("/instrumentation/nav[0]"));
749.91 [INFO]:nasal --------------------------------------------------------------------------------

[wlbragg]

so Nav2 does both VOR and ILS, as is

Yes, absolutely!

I'm really not understanding why we are looking at changing or coding anything. The interpolations should have nothing to do with any of this. They are already synchronized to match the signal to the graphics displayed.

The instrument is working in all but the OP's aircraft. I think the OP still needs to do as suggested and test some frequencies and locations as polly suggested before we need to look at code or anything else.

[TheEagle]

@cookf
From your output:

Code: Select all

742.35 [INFO]:nasal nav/power-btn {BOOL} = 0


Your NAV radio has no power - you must be missing to turn it on somehow !

[SurferTim]

Autostart will turn everything on. Doesn't start the engines.

I shot a few ILS approaches and a couple VOR radial tracking tests, and it worked fine with my patch above.

[cookf]

Something doesn't add up. If my Nav has not power, how did I tune it to the correct frequency. My posted screenshots show LEDs being on. i don't use auto start (I assume "auto start" from the menu). I switch everything on manually via the simulated buttons on the virtual dashboard. I'll try autostart tomorrow.

[SurferTim]

Your pic shows the radios on. It shows the wrong frequency.

[cookf]

From memory, Wick is on 113.60 and Inverness is on 109.20. If tried both, flying over the VOR at WICK or airport at Inverness in various planes. I've verified the frequencies from FGFS map (data) and using SkyVector and other apps.
When I fly the Cessna 337, the NAV needle does not move while the radio show with full bright red LEDs which I believe indicate it is on. Any other plane (that has NAV, like the D400 or DH6) I can use the full VOR/DME/NAV functionality.
And yet other people report it as fully working, so it must be something in the procedure that I follow. I have not used Autostart from the menu, so will try that tonight.

[Alant]

According to https://wiki.flightgear.org/System_dependent_instruments the nav radio requires property /systems/electrical/outputs/nav[]to be set to 1 or greater to provide power. Please check the value of this property to see if it is set.

Be aware that there were changes to the instrument power code earlier this year, so this may have affected some aircraft.

Alan

[polly]

Yep yep.
OP has not confirmed it's recently downloaded from fgaddon.