Chapter 4 _____________________________________________________ TTY Nonvolatile Setups
VAISALA______________________________________________________________________ 133
IFDR as a serial stream to be received by an outboard DAFC module
(which supports arbitrary remapping of its output pins).
To summarize, the internal AFC feedback level is first mapped into an
arbitrary numeric span, then encoded using a choice of formats, and finally
mapped into an arbitrary set of pins for digital output. We are hopeful that
this degree of flexibility allows easy hookup to virtually any STALO
synthesizer that one might encounter.
These questions only appear when the "PinMap" uplink protocol has been
selected. The table assigns a bit from the encoded numeric word to each of
the 25 pins of the RVP900/DAFC module. For example, the default table
shown above assigns the low 25 bits of the encoded bit pattern to pins 1–
25 in that order. You may also pull a pin high or low by assigning it to +5
or GND. Such assignments produce a logic–high or logic–low signal level,
not an actual power or ground connection. The latter must be done with
actual physical wires.
One of the RVP900/DAFC pins can optionally be selected as a Fault Status
indicator. You may choose which pin to use for this purpose, as well as the
polarity of the incoming signal level. The standard RVP900/DAFC
module only supports the selection of pins 1, 3, 4, 13, 14, and 25 as inputs.
This setup question allows you to choose any pin, however, because it does
not know what kind of hardware may be listening on the uplink and what
its constraints might be.
Burst frequency increases with increasing AFC voltage: NO
If the frequency of the transmit burst increases when the AFC control
voltage increases, then answer this question "Yes"; otherwise answer
"No". When this question is answered correctly, a numerical increase in the
AFC drive (D–Units) will result in an increase in the estimated burst
frequency. If the AFC loop is completely unstable, try reversing this
parameter.
Enable Burst Pulse Tracking: YES
This question enables the Burst Pulse Tracking algorithm that is described
in Section 6.1.4 Burst Pulse Tracking on page 188. For such an intricate
PinMap Table (Type ’31’ for GND, ’30’ for +5)
Pin01:00 Pin02:01 Pin03:02 Pin04:03 Pin05:04
Pin06:05 Pin07:06 Pin08:07 Pin09:08 Pin10:09
Pin11:10 Pin12:11 Pin13:12 Pin14:13 Pin15:14
Pin16:15 Pin17:16 Pin18:17 Pin19:18 Pin20:19
Pin21:20 Pin22:21 Pin23:22 Pin24:23 Pin25:24
FAULT status pin (0:None): 0, ActLow: NO