Appendix

STI Manual Input

STI Manual Input Driver

To Index

STI Manual Input Overview ....................................................................... 2

Operation ................................................................................................ 2
<Name>.REC File......................................................................................... 3
[Compatibility] Section................................................................... 3
[Global Settings] Section................................................................. 3
[DB Field List] Section .................................................................... 3
ManIn_exmpl.REC................................................................................. 4
Value Entry Dialog Box ............................................................................... 5
Technical Support......................................................................................... 6

STI Manual Input Appendix 1

STI Manual Input Overview
The Manual Input program allows for user input and recording of
numeric values associated with a position location. Up to two groups
of up to 5 numeric user inputs can be accommodated. Computations
can be performed on each group of inputs and the results logged
along with the user inputs.
There are many applications for the STI Manual input driver.
1. Sets of up to 5 users can judge audio signal quality and input
their individual Quality Of Signal values.
2. Users can manually enter signal parameters such as RSSI, BER
and SINAD values from a separate radio or instrument.
The logged data will be associated with either GPS or Indoor
waypoint location data in the measurement database. Contour plots
can be created after an adequate number of measurements are logged.

Operation
The Manual Input program is a driver that behaves like other Field
Test 4 drivers. The difference is that it waits for user input to log each
“measurement”. As soon as the Save to Database key is selected the
entered value(s) are saved in the measurement database together with
optional values computed from the entered values.
Computations based on each group of user inputs can be added to the
measurement database. These computations include:
1. Average of the user group input.
2. Average less min value less max value of the user group
input.
3. Maximum value from the user group inputs.
4. Minimum value from the user group inputs.
5. Standard Deviation of the user group inputs.

2 February 2003
 <Name>.REC File
The number of inputs and names associated with each numeric entry
are controlled by settings in a <name>.REC file associated with the
[Link] driver. The <name>.REC file contains five sections.

[Compatibility] Section
The [Compatibility] section contains the following entries and should
not be changed.
[Compatibility]
File Version=5
File Version 6=True
driver=[Link]

[Global Settings] Section

There are no settings in the [Global Settings] section.

[DB Field List] Section

The [DB Field List] section controls the number of inputs in each of
two user groups and any calculations on those inputs. The format of
each line in the [DB Field List] section is:
<Line Number>=<Parameter Name>,<[Group][Operation]>
Where
<Line Number> is the number of the line in the [DB Field List]
section. Line numbers must be in ascending order starting at 1.
<Parameter Name> is user defined text that is the name associated
with this input. It will also be the name of the field in the
measurement database and will be used to create file names. Use
names that will satisfy Windows file naming conventions. Examples
are:
Morrison_Site for the name of the transmitter site.
VHF1_153.0125 for the name and frequency of the site.
T2_Bill for the input from an individual who is a member of
Team 2.
<[Group][Operation]> is the third field in the lines in [DB Field List]
section. This field is text that is either a Group name or the name of a
calculated Operation. When this line represents a user input this field
should be the name of either the first or second group of inputs. For
example:
A for an input from a member of the A Group.
RSSI for a manual input of a group of RSSI inputs.
QOS for a manual input of a group of QOS values.

STI Manual Input Appendix 3

 When this line represents a computed value from the previous group
of inputs, this field should represent the desired computation. For
example:
‘Avg’ for the average of the preceding group of inputs.
‘Mid’ for the average-less-min-less-max of the preceding
group of inputs.
‘Max’ for the maximum value from the preceding group of
inputs.
‘Min’ for the minimum value from the preceding group of
inputs.
‘Std’ for the standard deviation of the preceding group of
inputs.

Note: In the [DB Field List] section, inputs from the first group must
be listed first followed by any calculation fields based upon
the first group. The second group of inputs are listed next
followed by any calculation fields based upon the second
group.

ManIn_exmpl.REC
Following is an example of a <Name>.REC file for the [Link]
driver. Note the relationship between the parameters in this file and
the Value Entry dialog box in the next section.
For each entry in the [DB Field List] section there is a corresponding
field in the measurement database for the project.

[Compatibility]
File Version=5
File Version 6=True
driver=[Link]

[Global Settings]

[DB Field List]

1=350.125,RSSI
2=725.138,RSSI
3=825.375,RSSI
4=RSSI_MAX,Max
5=QOS_Bill,QOS
6=QOS_Carl,QOS
7=QOS_Joe,QOS
8=QOS_Avg,Avg

4 February 2003
 Value Entry Dialog Box
The value entry dialog box is the method for entering data into the
measurement database. Values for a data point are entered into the
text boxes then select the Save Data control to save the values into the
measurement database.

Note the frame labels are the Group names in the ManIn_exmpl.REC
file shown in the previous section. Also, text box labels are the
Parameter names in the .REC file.
Note: Empty fields for any of the named input values in any
measurement will be ignored by Field Test 6 as if they did not exist.
Notes when using the [Link] driver for Indoor Tests:
1. In the Test Mode box choose the Single option.
2. Select the Start Receiver control then the Save Data control on
the Value Entry dialog box once to initialize the Indoor Test
process.
3. Be sure waypoint 1 is green and you are at that location.
4. Select Start Acq the Value Entry dialog will appear.
5. Enter the data into the Value Entry dialog box. Then select its
Save Data control.
6. Select the Save Buffer control to save the data to the database.
7. Move to the next, green waypoint location and select Start Acq
for the next data entry.
8. Repeat steps 4, 5 and 6 for all of the waypoint locations.
9. Select Stop Receiver to stop the measurement process.

STI Manual Input Appendix 5

Technical Support
Survey Technologies is available for consultation regarding system
operation during the one year warranty period. Often questions can
be resolved by a phone call or email. When questions about system
operation are more complex, we will need access to several setup and
diagnostic files in the STI-9400 that give us important information on
how the system is operating.
These files can be easily packaged into a zip file for emailing to us.
You can use the export support function found from the main menu
by selecting Proj Setup then General then the Support tab. In the
Create Support File box first select the location you want the support
file placed. My Desktop is recommended for convenience. A list of
projects in the computer is on the right. Select the project that you
were working with when the problem occurred then select Apply.
A zip type file of the form <Project Name>-[Link] will be placed in
the selected location. This file can be emailed to us at:
support@[Link]
Include in the cover message, a complete description of the problem
that you are having including the details of any error messages that
you observe.
In the unlikely event that Field Test 6 will not start you can complete
the identical steps using the Project Copy utility program located in
the Survey Technologies program group.
We will respond to your request for support as soon as possible.

6 February 2003