User manual

03/03 15 - 16 DS 2.501A
Logged Data Files – Satchnet V6.2 and later
Logs are stored in the following files:-
LG_MM_YY.DAT
LG_MM_YY.REC
Where MM = Current Month
YY = Current Year
All logs are stored in the same file. Files from previous months may be
back up and/or deleted.
Configuration Library Files
The configuration library option causes files to be saved - or rather
copied within the LOG directory. The filenames used are - for
example:-
DDC1$001.LIB
DDC1$001.BUB
The names of these files are constructed as followed:-
XXXX$NNN.LIB and XXXX$NNN.BUB
where
XXXX is the controller type I.D.
and
NNN is generated as a number from 001 to 999 but can be
any three characters.
The numbers are generated automatically whenever a library file is
saved. If you wish to copy a file to a new system - or `lock a file' within
a system, the files may be renamed such that the last three characters
are not numbers. When transferring a library file pair, it is always wise
to rename the last characters to ensure that the file will not overwrite
an existing configuration. The user-defined label, which can be viewed
from within Satchnet, is held inside the file.
Satchnet systems are supplied with a set of library files named:
XXXX$.PRN.LIB
which contain the controllers pre-sets (N being the pre-set number).
The file with the extension .LIB is identical in format to the .DAT file.
The file with the extension .BUB is identical to the normal
controller.BUB files and will only be present if the controller is an IAC
type.
Although the .LIB files may be copied from one system to another,
great care is needed to ensure that compatibility is maintained. In
Satchnet version 6.11, the file MUST be used with the same .CNF file
as was in use when it was created. This restriction does not continue
to .LIB files created with version Satchnet Plus (6.20) although files
created with version Satchnet Plus (6.20) cannot be read by version
6.11.
If there is any doubt as to the compatibility of .LIB files, the following
upgrade procedure should be used:
Use this procedure if a .LIB and .BUB of uncertain compatibility is
to be transferred to a new system.
1. If a controller is present on the system, already programmed from
the .LIB and .BUB files on the old system, skip straight to 3). This
is a much easier procedure and should be followed wherever
possible.
2. Using the old system, go into bubbleland and note down all
significant values of the parameters within the modules.
3. From configuration library, select ‘Load Configuration from Disk’.
4. Pick out the configuration you require and answer ‘No’ to ‘Transmit
data’.
5. If the controller is already programmed with the configuration (by
the old system), you may skip to section 7).
6. Go into bubbleland and then, in each module, program the correct
parameters - as noted in section 2).
7. Select ‘Get Controller Data’ and wait for all data to be read.
8. Save the new format files in the configuration library. Delete the old
files as soon as possible to remove possible confusion.
IMAGES AND BACKGROUNDS
Satchnet Pro is supplied with a set of bit-map graphics (.CUT format)
which may be used to build up the screens. Backgrounds are held in
the BACKGRD directory while smaller images are placed in the IMG
directory. In some systems, these will be extended and any extra files
must be kept as part of the system configuration. It is also possible for
a system to have additional images added to the SYM directory in
order to provide extra active symbols.
THE SATCHNET ROOT DIRECTORY
Some significant files are present in the main Satchnet directory.
These are:
All other files in the Satchnet main directory are supplied.
The .CNF Directory
The .CNF directory will be almost empty in production software under
normal circumstances. The only file present will be a file called `0'
which is there simply to ensure that the directory is created. All .CNF
files used by the system are included in the file CNF.PAK which is
present in the main directory. If you have a system which has some
.CNF files in the .CNF directory, they should not be necessary with a
new system. Satchnet will always use a .CNF file from the .CNF
directory in preference to the CNF.PAK file.
ALMCNF.DAT
Holds the setup of the various alarm
types.
ALARMS.DAT The alarm history list.
PASSE.FIC The current users and passwords.
POLL.SCH Polling time schedules.
LOGON.DAT The user logon list.
PARAM.DAT
Various setup items including mouse
speed, COM ports, time-outs etc. This
file is created by SETUP.EXE.