Contents
21
Intersekt, problem loading RCU’s!
PROBLEM
When using the Intersekt RER16 there can be a problem loading the second interface. For example if the
RCU at position 1:7 on interface 1 fails to load then you will not be able to load room interface 2 or any
after that. The later RCU’s can of course be loaded using UPLOAD from DOS .
OVERVIEW OF SOLUTION
When a compilation is done in Linstall the program creates a set of files that are meant to be loaded into
the various interfaces on the Intersekt. These have, for instance, which of the sockets on the back of the
Intersekt have a room connected to them and which RCU’s are grouped together.
These files need to be loaded into their respective interfaces unaltered. Otherwise you could find that the
groups you have set up do not work as planned.
The aim of this work around is to “fool” the Linstall program into thinking it is loading the first interface
every time.
This is what we want:
Intersekt RER16
Interface 2 definition file (ROOMIF02.DAT)
Interface 1 definition file (ROOMIF01.DAT)
To achieve this we do the following:
Intersekt RER16
Interface 2 definition file renamed (ROOMIF01.DAT)
Interface 1 definition file (ROOMIF01.DAT)
SOLUTION
1.
Back up your customers definition files.
2.
Compile the customers definition file as usual.
3.
Load the multi-room system as normal.
4.
Whichever RCU’s fail to load, load using UPLOAD.
5.
In File Manager/Explorer rename ROOMIF01.DAT as TEMPIF01.DAT .
6.
Rename ROOMIF02.DAT as ROOMIF01.DAT .
7.
Connect the PC serial lead to the second PC socket on the Intersekt.
8.
In Linstall load the system.
9.
It will ask if you want to “Overwrite Room Interface 2 with Interface 1”, click on “Yes” .
10.
Room Interface 2 will now be loaded, the room after this will NOT load. Do NOT worry, this is what
should happen.
11.
Exit Linstall.
12.
In File Manager/Explorer rename ROOMIF01.DAT as ROOMIF02.DAT .
13.
Rename TEMPIF01.DAT as ROOMIF01.DAT
Interface2
Interface2
Interface1
Interface1
