On Thursday 27 Oct 2005 20:20, Vassilii Khachaturov wrote: > In the recent 737 autopilot change, > we see that the only improvement is the change of the target > speet. > > diff -u -2 -r1.15 -r1.16 > --- 737-set.xml 18 Oct 2005 16:32:23 -0000 1.15 > +++ 737-set.xml 27 Oct 2005 08:34:40 -0000 1.16 > @@ -110,5 +110,5 @@ > <target-altitude-ft > type="double">4000.0</target-altitude-ft> <heading-bug-deg > type="double">283.0</heading-bug-deg> - <target-speed-kt > type="double">200.0</target-speed-kt> + <target-speed-kt > type="double">165.0</target-speed-kt> </settings> > </autopilot> > > However, I am surprised to see that the target speed is > hardwired here. AFAIK, the heavies use different target speeds > dependant on the density altitude and aircraft landing weight. > I don't know how big the difference can be within the possible > range of the allowed landing weights. Can a 737 specialist > sched some more light, please? > > V.
Hello Vassilii, these aren't 'hardwired' values but defaults. The values declared here, in the aircraft 'set' file create the corresponding nodes in the property tree and their values can be changed using panel instruments, GUIs, the property browser, nasal scripts and the telnet and http interfaces. The file that defines the characteristics of the autopilot is Aircraft/737/Systems/737-autopilot.xml If you have a look at this you'll see that the relevant autopilot PID controllers read their reference values from the property tree nodes holding the values declared in the aircraft 'set' file. LeeE _______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
