IS-1500 User Guide
Thales Visionix, Inc.
MNL- 0024 (D)
Page 38 of 59
A
DVANCED
S
ETTINGS AND
C
ONFIGURATION
F
ILES
5.1
Introduction
This section explains the advanced settings found in some of the key software configuration files. The configuration files covered in
this section include:
sfHub.info
sfAccess.ini
sfStudio.ini
SVM.ini
There are a few important warnings that should be noted before proceeding:
If at any time the configuration files need to be reverted to their defaults, copies of the default files can be found in the
Configuration Files folder of the software directory. These files should never be overwritten.
These settings are for advanced users only. Changing configuration files improperly can have severe impacts on the
performance and operation of the system.
Generally, unless directed here by the guide or by a Thales Visionix technical support engineer, these files should not need to
be changed from their original state.
Any settings in the configuration files not covered in this section should be changed only by Thales Visionix engineers.
It is recommended that a backup file of the current configurations be created in a folder outside of the main installation
directory before making any changes.
If the changes made to the file are intended to be permanent, further backups of the working edited files should be created.
Updates to the software may change the content of the configuration files.
o
Any backups of configuration files saved in the installation directory may by overwritten or deleted by a software
update.
o
After updating the software, rather than rolling back to an older configuration file, manually edit the newly installed
configuration files to match the system to ensure updates do not get overwritten.
If there is any confusion on how to change a configuration file, do not make any changes and instead contact Thales Visionix
Technical Support using the contact information on Page 2.
5.2
Editing Configuration Files
Each of the files discussed in this section can be viewed and edited using a standard plain text editor, such as Notepad in Windows.
After changes to the file have been made, it must be saved and the software restarted for the changes to take effect.
When reading configuration files, any text following a semicolon (;) is considered a comment and is not actually read by the system.
Comments are used as notes on what the values represent or can be used for organization. In the sample files and example text
presented here, comments will have
green
text. Comments can be edited or added without affecting the system in any way, but they
must always be preceded by a semicolon. When changes from the default configuration are made, it is even recommended that they
by commented by the user for future reference
Each setting has a variable followed by a value. Only the values should ever be changed – editing variables will render them
unrecognizable by the software and could compromise the system. In example text, when a value should be changed (or has been
changed) it will be marked in
red
.
When editing configuration files, only text marked
green
or
red
in the examples here can be changed without invalidating the
configuration.