Operation Manual

53
Modied le:
2
2 9 7
A8 /CWA______@ 65 1
A9 /CWS_____KT 66 1
1 4 1
A1 /MASTFOOT 111 2
As can be seen, in addition to adding the extra transmit group we have also modied the rst line of the le to
read ‘2’, which identies the number of transmit groups that follow.
The nal thing to do would be to create new calibration and damping les (mastfoot.cal and mastfoot.l) in the
relevant folders with appropriate values, and, if required, add the new variable into damping.d and/or svcals.d
to allow damping and calibration from Deckman (see Chapter 5: Parameters for more information on these).
If calibration or ltering of the variable is not required it is normal to use null.cal and null.l respectively as the
calibration and damping lenames.
User variables
You are able to create your own data variables, using several methods.
• Taking data from existing variables and applying calibrations and ltering as desired
• 2D variable lookup table
• JavaScript
User Variables are available for distributing to system displays or Deckman in the same manner as a normal
variable.
Dening User variables
Whichever method is being used, any new user variables must be dened by adding them to the variable list
(bg_vars.d).
In bg_vars.d we add a line to dene each new variable, in the example below the next available variable number
was 111 so we have added new lines dening variables 111-113 which we will use in the following examples. See
bg_vars.d section for further information.
108 gps2sva sv2 0 0 0
109 gps2utc ut2 0 0 0
110 Variation Var 2 0 1
111 MA_TWD MWD 0 0 2
112 TargRudder TRd 1 0 1
113 TargDagger TDg 1 0 0
The content of the new user variable is then dened via sample.d, the methodology varies depending on how
the user variable is being created (standard, lookup or javascript), the following section describes the options.