IM_BASD,TABLE_HELP,IM-BAS Protocol Driver
IM-BAS Dataset definition

Wizard InfoSys IM-BAS Protocol Driver which commu-
nicates with BAS Control Subsystems and a transla-
tor which supports the IMX Mailbox Communication 
Interface.

The Dataset Definition panel must be used to defi-
ne datasets which remain in the subsystem. This
dataset will be referred in the translator and 
specific communication will be done on these data-
sets such as reading, writing or unsolicited recei-
ves.

$
IM_BASD,SNDMBX,IO-Translator Mailbox Tag
Tag name of a translator mailbox element, to be 
referenced by the IM-BAS protocol driver task (N.B.
IMX must be supported by the translator task). The 
I/O translator task uses this mailbox to receive data 
from the IM-BAS protocol driver.

$
IM_BASD,DATASET,Dataset Tag
Tag name representing a (unique) logical name for a 
dataset. The tag is used internally in the I/O trans-
lator and protocol driver for activating a dataset 
read from the external device. The I/O translator 
and the protocol driver internally reference a data-
set by the tag name defined in this field. As a con-
sequence the tag specified must be unique. The same 
tag should be used in configuration of the I/O trans-
lator to select the conversions for the dataset.

$
IM_BASD,MSGTYPE,Message
This field defines the type of the data area in the 
logical device (subsystem). 

$
IM_BASD,DATATYPE,Message
This field defines the data type of the data in the 
message defined in the previous field. The combination
of message and data type uniquely defines a data area
in the subsystem. Every data area in the subsystem has
the following limits for addressing: minimum address is
zero and maximum address is 9999.

$
IM_BASD,START,Start Address
Start address number of the dataset.

$
IM_BASD,LENGTH,Length of Data
Length of the dataset in bytes, words or longs, depen-
ding on the type of the dataset, see the table for 
the field `Message'. The minimum length allowed is 
`1'.

$
IM_BASP,TABLE_HELP,IM-BAS Protocol Driver
IM-BAS Device Definition

Wizard InfoSys IM-BAS Protocol Driver which commu-
nicates with BAS Control Subsystems and a transla-
tor which supports the IMX Mailbox Communication 
Interface.

The IM-BAS Device Definition table must be used to 
specify logical devices. These logical devices consist 
of a logical device name and physical parameters. It 
is possible to assign more than one logical devices to 
the same physical device (or subsystem).

$
IM_BASP,DEVNAME,Device Name
Logical name assigned by the user to represent a par-
ticular communication device. This field is used as 
a selection criterion for the next panel: IM-BAS Da-
taset Definition.

$
IM_BASP,SUBTYPE,Subsystem ID (Remote)
The subsystem id is used to uniquely identify the 
subsystem on the network, just like the local system 
ID of the driver. Only after accepting the TCP/IP 
connection and reception of the first life-sign, the 
relation between connection and device is known, and 
is internally in the driver the connection linked to 
the device.      

$
IM_BASP,ALIVETIME,Alive Time [sec]
The alive time specifies the maximum number of seconds 
admitted between the reception of two life sign mes-
sages. If the time between two successive life signs 
exceeds the entered value, the connection is assumed 
to be lost and is closed by the driver.

$
IM_BASP,CONNECTION,Connection Tag
The connection status for every device can be made 
available throughout the application, the only thing 
to do is specify a tag in this field. The value of 
the tag will represent the connection state of the 
device. Please remember that a life sign is needed 
before the subsystem id is known of the device to 
which a driver has a TCP/IP connection. Due to this 
definition, a device has still the disconnected state 
after acceptation of a TCP/IP connection request, but 
before a life sign message is received. Before recei-
ving the life sign, there is no relation between a 
device (or actually the subsystem id) and the TCP/IP 
connection.

$
IM_BASP,STATUS,Status Tag
The IM-BAS protocol driver writes to this real-time 
database element, the value of the tag indicates the 
status of communication commands. The status element 
can be referenced by any task to handle communication 
error situations. A value of zero indicates no error 
(success), any other value represents an error, see 
the next chapter how to solve or prevent errors. A 
detailed list of all possible error codes also can 
be found in the next chapter. 
If a digital tag is used to evaluate errors, only 
the error situation is indicated, the value of the 
digital is `ON' to indicate an error. A digital tag 
only has two values (`ON' and `OFF'), and can not 
have the error value.

$
IM_BASP,RDISABLE,Read Disable Tag
Real-time digital database element used to enable/
disable read-commands for the logical device. Read-
commands are enabled in case there is no tag defined, 
or the status of the digital tag is `OFF'. Read-com-
mands are disabled if a tag is defined and the status 
of the tag is `ON'.

$
IM_BASP,WDISABLE,Write Disable Tag
Real-time digital database element used to enable/
disable write-commands for the logical device. Write-
commands are enabled in case there is no tag defined, 
or the status of the digital tag is `OFF'. Write-com-
mands are disabled if a tag is defined and the status 
of the tag is `ON'.

$
IM_BASP,RCVDISABLE,Receive Disable Tag
Real-time digital database element used to enable/
disable receive-commands for the logical device. Re-
ceive-commands are enabled in case there is no tag 
defined, or the status of the digital tag is `OFF'. 
Receive-commands are disabled if a tag is defined 
and the status of the tag is `ON'.

$
IM_BASM,TABLE_HELP,IM-BAS Protocol Driver
IM-BAS Driver Definition

Wizard InfoSys IM-BAS Protocol Driver which commu-
nicates with BAS Control Subsystems and a transla-
tor which supports the IMX Mailbox Communication 
Interface.

The `IM-BAS Driver Definition' panel is used to defi-
ne global settings for the driver. For these global 
settings only one record or row is needed, if you 
define more then one row, the driver will ignore the 
second and following rows. The first row however is 
required, an empty table will generate a task error 
and cause the driver to stop.

$
IM_BASM,RCVMBX,Protocol Driver Mailbox Tag
The I/O-translator will send read and write requests 
to IM-BAS driver using IMX, only one mailbox is used 
to send requests to the protocol driver. For the dri-
ver this the `receive' mailbox, every translator will 
wirte requests for the driver in this mailbox. To 
make sure IMX is working properly the mailbox tagname 
entered should only be used for sending requests to 
the IM-BAS driver!

$
IM_BASM,LIPADDR,Local TCP/IP Address
This entry is optional, only if there is more then 
one Ethernet card present in your computer system the 
field may require an address. If this field is left 
blank, the driver will locate every Ethernet card in 
your system, and start listening to connect requests 
from BAS Control subsystems.
If a DNS name or (dotted) IP address is filled in 
only connection request from subsystems using the 
Ethernet card with that address or name are accepted. 
All other cards are ignored, connection requests arri-
ving on these cards will also be ignored.

$
IM_BASM,SUBID,Subsystem ID (Local)
The local subsystem id is send to every device when 
writing or fetching data from that device, the id is 
part of the IM-BAS protocol. The id's for every sys-
tem in the network are defined and distributed by the 
network administrator (Schiphol). The id is a two-
byte code, and is entered in the configuration panel 
as a string of two characters.

$
IM_BASM,LPORT,Local Port
The connection between the driver and a device is de-
fined with the IP-addresses of both systems and the 
port number on both sides. The IM-BAS protocol driver 
acts as a server, and will listen to connection re-
quests from subsystems, therefore only the local port 
number is defined. The driver will listen for connec-
tion requests on this port for every Ip-address.

$
IM_BASM,STANDBY,Driver Standby Tag
In a redundant FactoryLink system are two applications 
active, one of them can be in (hot) standby mode. 
For the IM-BAS protocol is defined that a susbsystem 
only communicates with one server, so the driver in 
the standby system will NOT communicate with susbsys-
tems.
To direct the driver in in standby or normal mode, 
you need to define a digital tag in this field, the 
value of the tag forces the driver to switch to one 
of the two modes. A value of zero `OFF' instructs 
the driver to switch (or maintain) the normal mode, 
the switches to standby whenever the tag value goes 
from `OFF' to `ON'.

$
IM_BASM,DISCONNECT,Driver Disconnect Tag
In a redundant FactoryLink system are two applications 
active, one of them can be in (hot) standby mode. 
The subsystems connects default to the system with the
'lowest' IP-address, however if this server is off-line
connections are build up with the second server. As a 
result the subsystems will be divided over the two sys-
tems, to force the subsystems to (re)connect to the ser-
ver with the 'lowest' IP-address a disconnect of all the 
subsystems can be given.
To force the driver to disconnect all the subsystems, 
you need to define a digital tag in this field, the 
value of the tag instructs the driver to disconnect or 
accept incoming connections (and process them normally). 
A value of zero `OFF' instructs the driver to accept (and 
process) incoming connection requests, changing the tag 
value from `OFF' to `ON' forces a disconnect for every 
subsystem. As long as the tag value is 'ON' incoming 
connections are not accepted, they are rejected.
$