On Sunday 12 December 2004 09:05, Chris Metzler wrote:
> Hi. From the CVS logs, it looks like a whole lot of
> radios/instrumentation changes went through last week to finish the
> transition (and thus fix the NAV radio problems). I just went through
> and manually checked all the a/c which have relevant gauges, and found
> that the c172 and 737 and so on all work; but three planes still have
> broken NAV radios: the c310 (and its children),
There is no electrical output to power the nav radio. Apply this patch to fix
it:
Index: c310-electrical.xml
===================================================================
RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/c310/c310-electrical.xml,v
retrieving revision 1.8
diff -p -u -r1.8 c310-electrical.xml
--- c310-electrical.xml 22 Apr 2004 14:54:34 -0000 1.8
+++ c310-electrical.xml 12 Dec 2004 10:53:03 -0000
@@ -144,6 +144,11 @@
<prop>/systems/electrical/outputs/gps</prop>
</output>
+ <output>
+ <name>Nav Radio Power</name>
+ <prop>/systems/electrical/outputs/nav</prop>
+ </output>
+
<!-- connect in power sources -->
<connector>
@@ -317,4 +322,12 @@
</switch>
</connector>
+ <connector>
+ <input>Bus Bar</input>
+ <output>Nav Radio Power</output>
+ <switch>
+ <prop>/controls/circuit-breakers/nav</prop>
+ </switch>
+ </connector>
+
</PropertyList>
What puzzles me is that there was never a "navcom" output in the c310
electrical config, so how did it work before??
> the pa28-161,
I tried the pa28-161 and it seemed to work fine.
> and the
> beech99.
The same problem as for the c310. The same patch can be applied to the
beech99-electrical.xml file.
> Lots of things don't work about the latter, including various
> gauges, so the problem may be something other than this transition.
Hmmm... I just tried it, and all gauges seemed to work fine (alt, vs, turn,
airspeed, ai)
--
Roy Vegard Ovesen
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
