Utility Diagnostic Tool

A Sierra Monitor Company
Utility Manual
FST_Diag
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Utility Version 1.03p

Document revision Rev 3
FS-XXXX-YY Driver Name Driver Manual
TABLE OF CONTENTS
1. FST_DIAG UTILITY DESCRIPTION ..................................................................................2
2. INSTALLATION..................................................................................................................3
3. BEFORE USING THE FST_DIAG......................................................................................4
4. USING THE FST_DIAG......................................................................................................4
5. TERMINATING THE UTILITY ............................................................................................8
6. HOW THE UTILITY WORKS..............................................................................................9
7. OPTIONS ............................................................................................................................9
8. CONFIGURE THE “LOG TYPE” LIST.............................................................................10
9. TROUBLESHOOTING TIPS.............................................................................................11
9.1. GET FS IP ADDRESS BUTTON DOES NOT SEEM TO DO ANY THING ...................................11
9.2. I GET THIS ERROR MESSAGE "TAKELOG:#1 ERR. CANT EXECUTE UTILITY (RUINET)"........11
9.3. I GET THIS ERROR MESSAGE "TAKELOG:#11 ERR. CANT EXECUTE UTILITY (RUIDEBUG) " 11
9.4. I GET THIS ERROR MESSAGE " 7. TAKELOG:#12 ERR. CANT EXECUTE UTILITY (ZIP) ".......11
9.5. I GET THIS ERROR MESSAGE " TAKELOG:#13 ERR. CANT EXECUTE UTILITY (FST_PING)" 11
9.6. I GET THIS ERROR DIALOG WHEN TRYING TO SEND MY E-MAIL TO SUPPORT .....................11
10. CONTENTS OF UPLOAD.ZIP..........................................................................................12
11. REVISION HISTORY ........................................................................................................13

11.1. MANUAL REVISIONS......................................................................................................13
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

Tel: (408) 262-2299 Fax: (408) 262-9042
Visit our website: www.FieldServer.com E-mail: support@fieldserver.com
Index
1. FST_Diag Utility Description
The FST_Diag Utility connects to a Field Server, collects information about the Field Server
setup and current communications activities and then reports back to Field Server support

Tel: (408) 262-2299 Fax: (408) 262-9042
Page 2
2. Installation
The utility is provided in the form of a self-executing installer. Double click on the installer and
the utility will be installed in a folder of your choice, added to the list of programs you see when
you push the start button. An option added the start menu program group would allow you to
uninstall the utility.
The name of the installer is
The version number of the utility may be included in the installer name.

Tel: (408) 262-2299 Fax: (408) 262-9042
Page 3
3. Before using the FST_DIAG
Before using this utility, please make sure of the followings.
1) Your computer is on the same subnet as the FieldServer.

2) You are connected directly to the network the FieldServer is on, you are not connecting
through a VPN or other remote networking software.
3) You do not have multiple Ethernet cards active on your computer. For laptops
especially, check your Ethernet settings and if you have a separate wireless Ethernet
card, make sure it is not active.
4) Antivirus software that prevents your NIC card from operating properly. E.g. Norton
Antivirus*.
*You may be able to connect to FieldServer, but utility may work improperly.
Are any of the protocols running on your FieldServer, Ethernet protocols such as
BACnet_IP / Modbus_TCP or Ethernet_IP ? If the answer is yes then we strongly recommend
that you capture an Ethernet Log too. That process is not automated but start the Ethernet log
before you push the button to ‘Take Log’ and end the Ethernet log after you have been told to
‘Now Send Log’. A written procedure for taking an Ethernet Log can be found on our Web Site
(under Support). The procedure is named ‘Enote0063’.
4. Using the FST_Diag
Step 1: Select a Field Server IP address.

You can do this one of two ways. You can do this by entering the IP address of the field server
manually or you may use our utility.

Tel: (408) 262-2299 Fax: (408) 262-9042
Page 4
Manually typing in your Field

server IP address
To use are our utility click the button located near the bottom of the dialog.
After you click the button a dialog will appear and shortly disappear, after
about 5 seconds. Once the dialog disappears you will be able to select a Field Server IP
address from the drop down menu near the top of the program

Tel: (408) 262-2299 Fax: (408) 262-9042
Page 5
You can select a

Field Server IP
address from the drop
down menu

Tel: (408) 262-2299 Fax: (408) 262-9042
Page 6
Step 2: take a log
Are any of the protocols running on your FieldServer, Ethernet protocols such as
BACnet_IP / Modbus_TCP or Ethernet_IP ? Read chapter ‘3 Before using the FST_DIAG’
Press the button near the bottom of the dialog. As the utility runs a few DOS
prompts will appear and disappear. Don't click or type any thing in to these DOS prompts. This
step may take a few min depending on what Log Type you chose and your computer speed.
When the utility is finished you will be presented with a log of events that have occurred
Log of events that

occurred

Tel: (408) 262-2299 Fax: (408) 262-9042
Page 7
Step 3: Send Log

Now you can send the log file to field servers support buy clicking the button
located near the bottom of the dialog. Once clicked a new dialog should appear.
Now you know where the uploaded files are stored. Push the ‘Locate Folder’ button to launch
explorer and have it point directly at the correct folder. It is this file – upload.zip – that must be
sent to Tech Support.
Step 4: Close the program

to close the program press the exit button
5. Terminating the Utility
Press the exit button on the bottom right of the utility

If the utility is in the progress of taking a log you must wait until it has complete before you may
exit

Tel: (408) 262-2299 Fax: (408) 262-9042
Page 8
6. How the Utility Works
The FST_Diag Utility connect to a Field Server and collects information about the Field Server
setup and current processes then downloads the configuration, zip all the file in to one big file,
then tries to reports back to Field Server support with the information
7. Options
From the Menu selection ‘Options’. You are presented with the following dialog.
This is a list of files found in

upload_list.ini which is used to
configure the utility.
The utility tries to upload these

files.
You cannot edit the list within the

FST_Diag application but you can
edit it externally. Each time you re-
install FST_Diag your changes will
be lost.
Return IP address. Leave the checkbox and edit field blank unless directed by FST Tech
Support personnel.
When a valid IP is specified and the ‘Use..” checkbox is checked then the utility adds the
following to the command line of Ruidebug: “-mReturn_IP_Address”

Tel: (408) 262-2299 Fax: (408) 262-9042
Page 9
8. Configure the “Log Type” List
In the install folder a file named config.ini controls the contents of the list named ‘Log Types’
This is an ASCII file. Its default contents are :
// This line is ignored because it begins with //

//
// File Format
// Description, Time_In_Seconds, Command_Line
//
// Where Description Is a text field which will be shown when the list of 'Log Types' is displayed
// Time_In_Seconds Is the log duration specified by the -qn command for ruidebug
// Command_Line Is normally left empty.
// When you specify a cmd line it overwrites
// part of the command line used by default for the program
// The app still specified -i -q -a and if
// required -m. The command line specified here is added.
5 Minute Log (Short Log),300,
10 Minute Log ,600,
15 Minute Log ,900,
20 Minute Log (Long Log) ,1200,
30 Minute Log ,1800,
2 Hour Log ,7200,
6 Hour Log ,21600,
12 Hour Log ,43200,
24 Hour Log ,86400,
Custom: si1003 ,300,-zP1[at]
You can add or edit these lines by using a text editor.

Tel: (408) 262-2299 Fax: (408) 262-9042
Page 10
9. Troubleshooting tips
9.1. Get FS IP address button does not seem to do any thing
Check the install directory of FST_Diag (default is c:\temp\fst_diag) for FST_Ping.exe

If it is not there please reinstall this utility.
If it is there, then it is not working so please manually type in your FS IP address
9.2. I get this error message "TakeLog:#1 Err. Cant execute utility (Ruinet)"
Check the install directory of FST_Diag (default is c:\temp\fst_log\) for Ruinet.exe

if it is not there please reinstall this utility.
9.3. I get this error message "TakeLog:#11 Err. Cant execute utility
(Ruidebug) "
Check the install directory of FST_Diag (default is c:\temp\fst_log\) for Ruidebug.exe

9.4. I get this error message " 7. TakeLog:#12 Err. Cant execute utility (Zip) "
Check the install directory of FST_Diag (default is c:\temp\fst_log\) for Zip.exe

9.5. I get this error message " TakeLog:#13 Err. Cant execute utility
(FST_ping)"
Check the install directory of FST_Diag (default is c:\temp\fst_log\) for FST_ping.exe

9.6. I get this error dialog when trying to send my e-mail to support
Check the install directory of FST_Diag (default is c:\temp\fst_log\) for blat.exe


Tel: (408) 262-2299 Fax: (408) 262-9042
Page 11
10. Contents of Upload.zip
Upload.zip contains the following files.
Upload.bat This is bridge.bat as found on the FS

Upload.f If bridge.bat calls cb8menu with a forth file
then this is that file
Upload0.csv If bridge.bat calls cb8menu with a config file
then this is that config file.
If bridge.bat calls cb8menu with a forth file

then this is the 1st config file loaded by the
forth file. Ie. It is the 1st file found in the .f file
preceded by a “read_csv” command.
Upload1/2/3…..csv If bridge.bat calls cb8menu with a forth file
then this is the 2nd and subsequent config
file(s) loaded by the forth file. Ie. It is the
2nd/3rd… file found in the .f file preceded by a
“read_csv” command.
Snap.log This is produced by Ruidebug. It is a simple
snapshot.
Upload.log This is the log file created when Ruidebug
starts logging the ports. It contains the
snapshot before and fater the port log too.
Com_*.log These are the serial port log files.
*.sys Device Drivers
*.ini Various initialization files
*.xif, Lon*.cfg Lonworks files
*.mib SNMP files
*.gse, *.ss1 Profibus files
*.bat Various bridge script files

Tel: (408) 262-2299 Fax: (408) 262-9042
Page 12
11. Revision History
11.1. Manual Revisions
Document
Date Resp Comment
Revision
01/28/03 SWS 0 Created.
Corresponds to 1.03cA of the utility
Updated after name change from FST_Log to

31Jul03 PMC 0 FST_Diag
Added section on Options

Added section on Log Type Configuration
Updated installer name from install_Fst_log.exe to
15 Jun04 SSS 1
Install_Fst_diag.exe
28 Jun04 SSS 2 Added section 3 (Before using FST_DIAG)
Updated section on contents of upload.zip
29 Mar06 PMC 3 Updated send log dialog
Added notes about Ethernet protocols

Tel: (408) 262-2299 Fax: (408) 262-9042
Page 13

Utility Diagnostic Tool

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Utility Diagnostic Tool

Uploaded by

Copyright:

Available Formats

A Sierra Monitor Company

APPLICABILITY & EFFECTIVITY

Effective for all systems manufactured after May 1, 2001

Utility Version 1.03p

1. FST_DIAG UTILITY DESCRIPTION ..................................................................................2

3. BEFORE USING THE FST_DIAG......................................................................................4

4. USING THE FST_DIAG......................................................................................................4

5. TERMINATING THE UTILITY ............................................................................................8

6. HOW THE UTILITY WORKS..............................................................................................9

8. CONFIGURE THE “LOG TYPE” LIST.............................................................................10

11. REVISION HISTORY ........................................................................................................13

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

1. FST_Diag Utility Description

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

The name of the installer is

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

3. Before using the FST_DIAG

Before using this utility, please make sure of the followings.

1) Your computer is on the same subnet as the FieldServer.

4. Using the FST_Diag

Step 1: Select a Field Server IP address.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

Manually typing in your Field

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

You can select a

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

Step 2: take a log

Log of events that

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

Step 3: Send Log

Step 4: Close the program

5. Terminating the Utility

Press the exit button on the bottom right of the utility

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

6. How the Utility Works

This is a list of files found in

The utility tries to upload these

You cannot edit the list within the

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

8. Configure the “Log Type” List

This is an ASCII file. Its default contents are :

// This line is ignored because it begins with //

You can add or edit these lines by using a text editor.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

9.1. Get FS IP address button does not seem to do any thing

Check the install directory of FST_Diag (default is c:\temp\fst_diag) for FST_Ping.exe

Check the install directory of FST_Diag (default is c:\temp\fst_log\) for Ruinet.exe

Check the install directory of FST_Diag (default is c:\temp\fst_log\) for Ruidebug.exe

Check the install directory of FST_Diag (default is c:\temp\fst_log\) for Zip.exe

Check the install directory of FST_Diag (default is c:\temp\fst_log\) for FST_ping.exe

Check the install directory of FST_Diag (default is c:\temp\fst_log\) for blat.exe

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

10. Contents of Upload.zip

Upload.zip contains the following files.

Upload.bat This is bridge.bat as found on the FS

If bridge.bat calls cb8menu with a forth file

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

11. Revision History

11.1. Manual Revisions

Updated after name change from FST_Log to

Added section on Options

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035

You might also like