User manual

DS 2.501A 14 - 16 03/03
ADDRESSING CONVENTIONS
Where IAC600 Touch-screens are used on a LAN the following
addressing convention should be adopted.
MIUs used in ‘modem mode’ to be address 0.
Controllers on Slave LANs to be addressed 1-31.
Controllers on the Master LAN to be addressed 32-63.
IAC600 Touch-screens to be address 65-95.
BUBBLELAND
Saving Configurations
Before saving a controller configuration to disk it is recommended that
the data is first uploaded from the controller. Satchnet Pro will
automatically prompt for this. Failure to do this may result in
uninitialized data being saved as part of the configuration which will
cause IAC controllers to reset when this data is subsequently sent to
them.
SECTION 7 – UPGRADING IAC FIRMWARE
(EPROM)
STATIC PRECAUTIONS
The components within this product can be damaged by static
electricity. In view of this anti-static precautions should be taken when
changing jumper, firmware (EPROM) or handling the PCB.
When upgrading controller firmware from versions 1.XX to 2.XX the
following procedure should be followed if a software preset is used.
With version 1.XX.
1. Enter the configuration library, select load a configuration from disk
and note the file name of the application you wish to upgrade.
2. Enter Bubbleland and for each module used make a note if it's
instantiation number (top left of the parameter box) and the
value/state of all the associated parameters.
3. Exit from Satchnet. The file noted in step 1 has a name that
consists of the following fields:
PPPV$NNN where;
PPP = Product identifier (DDC, VAV or VAS etc)
V = Version number (i.e. 1 for 113, 2 for 206, 207 etc)
NNN = Configuration number
Enter the SATCHNET/LOG directory and copy PPP1$NNN.* to
PPP2$NNN.*
4. Upgrade the Controller firmware.
5. Perform a cold start, setting the same address as used before.
6. Run Satchnet.
7. Enter Bubbleland and select the system module. Put the controller
into ‘NULL OUTPUT’ (‘GO SAFE’).
8. Exit Bubbleland, select ‘configuration library’ and load the
appropriate configuration from disk. When prompted with ‘Send
configuration to controller?’ select NO. This will set up the
bubbleland configuration screen but will not send any parameter
values.
9. Enter Bubbleland. Using the notes made in (2) re-enter the
modules parameter data.
10. Take the controller out of ‘NULL OUTPUT’ (‘GO SAFE’).
11. Select the configuration library option from the controller main
menu and perform a "get data from controller".
12. Save the new configuration to disk.
CONFIGURATION BACK-UP
Check the configuration is operating correctly by resetting controller.
All parameters are checked on power up. If the Null Outputs button on
the System Module is ON the controller contains corrupt data. The
controller will need to be cold started and the corrupt parameter must
be re-entered.
Always ‘get data’ from controller before saving configuration to disk.
Put parameter values under the modules in bubbleland so that in the
unlikely event of losing the data they may be reprogrammed easily.
SECTION 8 – SATCHNET DATA FILES
INTRODUCTION
This section provides information about the files which Satchnet
creates when in use and which may be needed to back up a system or
transfer a system from one machine to another.
When graphics or controllers are created in Satchnet, information
about them is stored in disk files. These files are divided amongst
several directories but all of the files together specify the current state
of the system.
THE SCN DIRECTORY
The SCN directory holds several different files but these must be
considered as a set. NEVER mix files from different Satchnet systems
or the results will be highly unpredictable.
An example of the SCN directory would be:-
The SCN directory holds all the information needed to build up the
presentation graphics of your system along with alarm limits and the
last-read values of all active symbols.
THE LOG DIRECTORY
The LOG directory is used to hold data which is associated with
specific controllers and may be used to configure them. There may be
a very large number of files in this directory, falling into three main
categories:-
Controller Files
For every controller on the system, there are one or two files held in the
LOG directory.
These files are named using the site number and controller address to
ensure that the filenames are unique.
In the following, SS is the site number, i.e. the item number in the site
list of the site which the controller is designated as being on. AA is the
controller address, specified on the controller bit switch or by other
means as appropriate.
Controller .Dat Files
SS_AA.DAT e.g. 1_21.DAT
There is one of these files for each controller on your system. They hold
a copy of all the data in the controller from when it was last accessed.
Controller Bubble Files
SS_AA.BUB e.g. 1_21.BUB
There is one of these files for each IAC type controller on your system.
They hold the graphic information to form "Bubbleland" and are vital if
the bubbleland of a controller is to be accessed. .BUB files are stored
in addition to .DAT files.
Touch-screen Files
HNDAA.DAT
SS_AA.TCH (Satchnet V6.2 and later)
There is one of these files for each touch-screen configured by the
system. This file holds all the menus and view parameters for the
touch-screen. This file is additional to the .DAT file.
Logged Data Files – Prior to Satchnet V6.2
These files store logged data, either from Satchnet based logging, or
from controller based logging such as that carried out by the CSMC.
e.g. GRA16.LOG
One of these files is present for each logging parameter on your
system and additional files if CSMC logging is used. The number is
referred to an item in the .SCN directory and so these files cannot be
accessed unless kept along with the .SCN directory they were created
with.
Always wear your
wrist strap
0.SCN the graphics of the root screen
1.SCN the first subscreen
2.SCN another subscreen
VALS.DAT .
SCRN.DAT .
PRDCTS.DAT . Various system data files
TYPS.DAT .
LIMS.DAT .
SITES.DAT .
LABELS.DAT
Controller files - Store information specific to each
controller in the system, and referenced
by address
Log Files - Store logged data
Config library files - Hold controller data for the config library