Update of /cvsroot/jsbsim/JSBSim/src/models/flight_control
In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv25969/src/models/flight_control
Modified Files:
FGKinemat.h
Log Message:
Added a description of the <noscale/> option to the kinematic component documentation
Index: FGKinemat.h
===================================================================
RCS file: /cvsroot/jsbsim/JSBSim/src/models/flight_control/FGKinemat.h,v
retrieving revision 1.12
retrieving revision 1.13
diff -C2 -r1.12 -r1.13
*** FGKinemat.h 12 Jun 2016 14:47:46 -0000 1.12
--- FGKinemat.h 9 Jul 2016 11:35:39 -0000 1.13
***************
*** 57,68 ****
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%*/
! /** Encapsulates a kinematic (mechanical) component for the flight control system.
! This component models the action of a moving effector, such as an aerosurface or
! other mechanized entity such as a landing gear strut for the purpose of effecting
! vehicle control or configuration. The form of the component specification is:
@code
<kinematic name="Gear Control">
<input> [-]property </input>
<traverse>
<setting>
--- 57,70 ----
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%*/
! /** Encapsulates a kinematic (mechanical) component for the flight control
! system. This component models the action of a moving effector, such as an
! aerosurface or other mechanized entity such as a landing gear strut for the
! purpose of effecting vehicle control or configuration. The form of the component
! specification is:
@code
<kinematic name="Gear Control">
<input> [-]property </input>
+ [<noscale/>]
<traverse>
<setting>
***************
*** 103,106 ****
--- 105,115 ----
In this case, it takes 5 seconds to get to a 1 setting. As this is a software
mechanization of a servo-actuator, there should be an output specified.
+
+ Positions must be given in ascending order.
+
+ By default, the input is assumed to be in the range [-1;1] and is scaled to the
+ value specified in the last <position> tag. This behavior can be modified by
+ adding a <noscale/> tag to the component definition: in that case, the input
+ value is directly used to determine the current position of the component.
*/
|