Curt wrote:

> The nasal script is specific code to impliment a specific aircraft's
> electrical system, but the overall structure could be copied and adapted
> to new aircraft.  But each aircraft will need it's own aircraft specific
> script.

I'll add that there are probably several ways to do various 
mechanical/electrical system
models. You may recall from Summer 2005 JSBSim newsletter an article about the 
L410
aircraft model done by Jiri Javurek. They use the JSBSim flight control 
components to
model various systems in ways I had not considered before. For example (and 
this is "old
format" - the current format in FlightGear CVS - JSBSim specification):

 <FLIGHT_CONTROL NAME="l410">

  <!--Stav baterii-->

  <COMPONENT NAME="battery-all-ok" TYPE="SWITCH">
    <TEST LOGIC="DEFAULT" VALUE="0">
    </TEST>
    <TEST LOGIC="AND" VALUE="1">
        /systems/l410/battery1-ok == 1
        /systems/l410/battery2-ok == 1
    </TEST>
  </COMPONENT>

  <COMPONENT NAME="battery-one-ok" TYPE="SWITCH">
    <TEST LOGIC="DEFAULT" VALUE="0">
    </TEST>
    <TEST LOGIC="OR" VALUE="1">
        /systems/l410/battery1-ok == 1
        /systems/l410/battery2-ok == 1
    </TEST>
  </COMPONENT>

  <COMPONENT NAME="battery-all-ok2" TYPE="PURE_GAIN">
     INPUT   fcs/battery-all-ok
     GAIN 1
     OUTPUT  /systems/l410/battery-all-ok
  </COMPONENT>

  <COMPONENT NAME="battery-one-ok2" TYPE="PURE_GAIN">
     INPUT   fcs/battery-one-ok
     GAIN 1
     OUTPUT  /systems/l410/battery-one-ok
  </COMPONENT>

  <!-- specialni nasobne sbernice -->

  <COMPONENT NAME="spec-turn" TYPE="SWITCH">
    <TEST LOGIC="DEFAULT" VALUE="0">
    </TEST>
    <TEST LOGIC="AND" VALUE="1">
        /systems/electrical/outputs/bus28v > 10
        /systems/electrical/outputs/bus36v > 10
        /systems/electrical/outputs/bus115v > 10
    </TEST>
  </COMPONENT>
  <COMPONENT NAME="spec-turn2" TYPE="PURE_GAIN">
     INPUT   fcs/spec-turn
     GAIN 1
     OUTPUT  /controls/switches/specbus_28v_115v_36v
  </COMPONENT>

  etc.

It's quite an impressive use of the components.

Jon


_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to