User`s guide

Figure 15: Infrared Monitor control panel showing no devices in range
However, IRServer and IRClient have been tested successfully with null modem connections and
some other serial devices. In fact, it works with any serial device that initiates its own protocol (and
can withstand some latency). A MIDI keyboard is such a device, and can be used with IRServer and
IRClient, although this hasn’t been tested with two MIDI keyboards. The infra-red transceivers,
and the protocol used by the QuickBeam virtual port, on the other hand, require handshaking to
be initiated by the application.
5.3 Using the Servers and Clients
The IRServer and VidServer application are intended to be launched and left to run in the back-
ground, and not interfered with unless some error occurs requiring manual intervention. This “no
hands” approach is important because we are trying to create a virtual room where technology is
not obvious, and people can use the system without having to use any equipment directly.
When the applications are first installed, they must be configured by editing their preferences files.
The TCP/IP port number shouldn’t require changing, but the COM port names (and possibly baud
rates) will probably need to be changed. The preference files shouldn’t require further modification,
unless particular hardware modifications are later made to the system.
The VidServer and IRServer applications only need to be installed on one VAN (probably at
Clayton), while VidClient and IRClient need to installed on each VAN. Each server application
must be run before the clients are, otherwise the clients will be unable to contact the server. The
order in which the disconnections occur (client first or server first) doesn’t matter.
If required, use of the system can be monitored by analysing the timestamped log windows pro-
vided in each of the client and server applications. As mentioned in sections 5.1 and 5.2, these show
when connections were made, when disconnections occurred, what data was sent and received, and
in the case of VidClient and VidServer, the current state of the system (up or down).
As mentioned in Section 5.2, the IRServer and IRClient applications, in their current form, cannot
be used for transmitting IrDA data from the Actisys transceivers. However, if other transceivers
become available in the future which send data without handshaking, then the IR applications will
automatically work with them.
25