In-Depth Immersive Hardware and Software


Hardware | General Software

Hardware

Standard Setup

The main VR setup supports the VR4 helmet, two fastraks and the Divison 3D Mouse. This section describes how to connect and make preliminary tests on the equipment.

Helmet

The front of the helmet control box is shown in Figure 1.


Figure 1: Helmet Control Box (front view).

The on/off switch is labelled A. The led below should come on when the unit is on. The video connection to the helmet is labelled C. Connection B is not necessary - it is composite video out that can be connected to a TV. This can be plugged into the front of the TV on the PV200, into the socket labelled AV4. Note the colour signal is corrupt or not present since only B&W pictures will be seen. Also the helmet has no power switch of its own so turn the box off whenever the helmet is not in use.

The back of the helmet control box is shown in Figure 2.


Figure 2: Helmet Control Box (back view).

The main connectors on the back are the two video sources (label A). The cables for these are labelled "left" and "right" so that it is easy to identify the cable to plug into the Onyx (see below). Please make sure that the cables are reconnected properly if you disconnect them in order to make a video. There are a pair of dip switches on the back of the control box (label C). The left of these controls switches between mono and stereo display. In mono mode the left eye video signal is sent to both eyes. The cable B is the power cable to the transformer.

Video Source

The video is connected to the twin video out connectors on the Onyx, see Figure 3, label A.


Figure 3: Connectors on the Onyx.

The video connectors have been removed in this picture, but the lower port named channel 1 should be permanently connected to the left eye on the helmet control box. If running in mono mode, channel 0 should be connected to the monitor, in stereo mode, channel 0 should be connected to the right eye.

Tracking

Figure 4 shows the front of the PV100VTX (red flash on front cover).


Figure 4: PV100VTX front view.

The power switch is the obvious red-button on the front. The button labelled A is the tracker reset. It should be pressed before every attempt to run immersive software. The reset cycle takes 9 seconds, so pause before running the software. The tracker cables can be seen emerging front the left of the front panel. Figure 5 shows the front of the PV100VTX with the front panel removed.


Figure 5: PV100VTX, front panel removed.

It is important to remember that the fastrak devices must not be detached when the power is on. The two receivers are plugged into the left hand sockets (A) (head to the top-left, hand to the bottom-left as indicated by labels next to the sockets). The transmitter is plugged into the rightmost socket (B). The fastrak has several configuration options, see the manual. Note that the fastrak in the PV100VTX has been customised by Division, the "Receiver selector" switch, has been resoldered inside the case of the PV100, so the machine must be dismantled to change the number of trackers supported (the new internal dip-switches are labelled back to front and upside down).

Figure 6 shows the back of the PV100VTX (the VPX is similar).


Figure 6: PV100VTX, back view.

Indicated are the serial connection to the Onyx (A), and the communication configuration dip switches (B). The switches are set up to report at 38400 baud, and this should not be changed.

The tracker is connected to the Onyx via the connector labelled C in Figure 3. This is named /dev/ttyd2 on the Onyx itself.

Button Device

The button control box is shown in Figure 7.


Figure 7: Button Control Box.

The connector to the 3D Mouse is indicated by label C. For the moment this is a bare connector, which can be joined in two orientations. Power comes from a transformer to A. The light B should come on when the power is connected. The light will go off after the configuration has been set in software (see below). Every time a data packet is sent, the light will then flash. The button device is connected to the port labell /dev/ttyd3 labelled B in Figure 3.

Options

The PV100VPX fastrak differs from the VTX only in that the receiver configuration switch has been left on the outside of the box. See Figure 8, label A.


Figure 8: PV100VPX with front panel removed..

This means it is more simple to connect 4 trackers to this box than that on the PV100 VTX. Label B shows the extra two receiver connections.


General Software

Video Configuration

The video card must be reconfigured in order to drive the helmet. On the Onyx video formats are created using the tool /usr/gfx/ircombine. You must run this as root in order to create new video combinations. Video formats can then be set with the command /usr/gfx/setmon video-format-file. You must be in the directory with the video format file (/usr/gfx/ucode/KONA/dg4/cmb) for this to work? You do not need to be root in order to set monitor configurations, only to create them.

The two important combinations are:

Video to the VR4 consists of 640x486 interleaved composite at 30Hz. For the mono format, the monitor is still visible at 1280x1024, but the bottom left (640x486) of the screen is also sent to the channel 1 output (the left eye of the VR4 - i.e. the one that is presented to both eyes if the VR4 control box is set to mono mode - see above). For simplicity I have created three scripts that set useful video formats, all are installed in /cs/research/vr/starship/common/irix/bin/setmonitor : Note that these can only be run on the local machine display (:0), so setting your display will have no effect (and is overridden in these scripts anyway).

Input Testing

I have provided simple scripts with which you can test a device. Remember that the fastrak will need reseting before you attempt and immersive session. These are all installed in /cs/research/vr/starship/common/irix/bin/.

Note that each of these processes tries to read the device on the default port for our own setup (/dev/ttyd2 for readfastrak, /dev/ttyd3 for readbutton). This can be changed on the command line.

Original code and source for all these scripts can be found as part of the Dive support for the immersive system. See Dive Immersive page.

Cabling

Figure 9 shows the complete wiring diagram for the HMD (no audio in/out) and inidcations of socket names when they exist.


Figure 9: Cabling for the immersive system.

At the moment, the 3D mouse to button box cable needs re-shielding and a proper connector. Both the serial cables on the Onyx need replacing - in particular the one on the button box since we needa break out box to make it work. We need a video splitter on the monitor/right eye output.



Anthony STEED
Last modified: Mon Mar 23 19:56:18 GMT 1998