From: gerard r. <gh...@gm...> - 2010-04-22 12:47:12
|
On jeudi 22 avril 2010, Jon S. Berndt wrote: > > Modified Files: > > FGTurbine.cpp > > Log Message: > > Make the turbine engien start running again at startup when requested > > > > Index: FGTurbine.cpp > > =================================================================== > > RCS file: /cvsroot/jsbsim/JSBSim/src/models/propulsion/FGTurbine.cpp,v > > retrieving revision 1.25 > > retrieving revision 1.26 > > diff -C2 -r1.25 -r1.26 > > *** FGTurbine.cpp 25 Feb 2010 05:21:36 -0000 1.25 > > --- FGTurbine.cpp 22 Apr 2010 08:15:27 -0000 1.26 > > *************** > > *** 155,159 **** > > > > if (Cutoff && (phase != tpSpinUp)) phase = tpOff; > > ! if (dt == 0 && !Cutoff) phase = tpTrim; > > if (Starved) phase = tpOff; > > if (Stalled) phase = tpStall; > > --- 155,159 ---- > > > > if (Cutoff && (phase != tpSpinUp)) phase = tpOff; > > ! if (dt == 0) phase = tpTrim; > > if (Starved) phase = tpOff; > > if (Stalled) phase = tpStall; > > Guys, > > I don't have time to review this now, but I believe I added the "!Cutoff" > conditional check to address another problem. We will probably need to > understand this better in how the turbine engine works in standalone and > when integrated with FlightGear. > > Jon > Jon, Tested, working in both condition, => running when requested "running" => not running when requested not running, the start process (with the .xml process shown before) is longer working. About the cutoff , we do have, longer, that strange "propulsion/cutoff_cmd" property value which is exposed EVER remaining to zero in any case. Though when giving it the value "0" with a switch, it does transmit it to FG (which makes the start process working). And probably getting the 1 value (internally ????, not expsed) , when we ask /controls/engines/engine/cutoff "true". Thanks Cheers -- Gérard J'ai décidé d'être heureux parce que c'est bon pour la santé. Voltaire |