Input devices usually transmit data to other Syzygy programs through the program DeviceServer, which loads device driver libraries (see Input Devices).
This chapter lists loadable device drivers included in Syzygy. Of course, you can write your own drivers too.
Some devices are configured with extra database parameters. These parameters have a service name corresponding to a parameter group (e.g., SZG_JOYSTICK for joystick devices). They are associated with the computer running DeviceServer.
The following device drivers interface with a single hardware device. For examples with parameters, replace <computer> with the name of the computer running DeviceServer.
Sorry, no longer supported
<computer> SZG_TRACKER IPhost XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX is the IP address of the Motionstar base station.
<computer> SZG_TRACKER transmitter_offset 0.97/0.20/0.12/0/-0.05/0.7/-0.72/0/-0.22/0.69/0.69/0/0.09/6.71/-2.72/1
Matrix (16 floats in OpenGL order) by which we post-multiply the device's matrix. Corrects for angled transmitter antenna.
<computer> SZG_TRACKER sensor1_rot 0/0/1/-90
A rotation by which we pre-multiply the device's matrix. Corrects for sensors mounted at an angle. Here, sensor 1 (wand) has been rolled 90 degrees to the left about the vector (0,0,1), i.e., the z-axis.
<computer> SZG_FOB config 0/3/0/0A list of codes, one per Flock unit, that configures each unit. Codes are listed in order of their internal Flock IDs. This example shows four units where the first, third, and four units have only a bird, while the second unit has an ERT.
2: Transmitter and bird
4: ERT and bird
<computer> SZG_FOB com_port 4
Serial port to which the Flock-of-Birds is attached. The number is 1-based on all platforms, which means that e.g. on Linux you need to add one (/dev/xxxxx0 is Syzygy port 1).
<computer> SZG_FOB baud_rate 38400
Baud rate of the Flock, one of 2400, 4800, 9600, 19200, 38400, 57600, 115200.
<computer> SZG_FOB hemisphere lower
Hemisphere of the transmitter in which the birds fly, one of front, rear, upper, lower, left, right.
<computer> SZG_FOB transmitter_offset 1/0/0/0/0/1/0/0/0/0/1/0/0/0/0/1
Matrix by which we post-multiply the device's matrix. Corrects for angled transmitter, just like SpacePad.
<computer> SZG_TRACKER sensor1_rot 0/0/1/90
A rotation by which we pre-multiply the device's matrix, to correct for angled birds. Same as SpacePad.
<computer> SZG_EVART IPhost XXX.XXX.XXX.XXXSpecifies the dotted-quad IP address of the EVaRT system.
<computer> SZG_INTERSENSE sleep 10/0Sleep for 10 msec after polling the tracker.
<computer> SZG_INTERSENSE station0_1 0/0/0The 0th tracker's 1st sensor has 0 buttons and 0 axes. It's probably a head tracker.
<computer> SZG_INTERSENSE station0_2 4/2/0The 0th tracker's 2nd sensor has 4 buttons and 2 axes. It's probably a wand. The SZG_INTERSENSE/convert# parameters for re-mapping the coordinates are no longer used. Use a PForth filter to do the coordinate transformation. See the Tracker Coordinate Conversion section for more information.
<computer> SZG_VRPN nameName of the VRPN device to connect to.
<computer> SZG_SERIALSWITCH com_port: Which port to use. The number is 1-based on all platforms, which means that e.g. on Linux you need to add one (/dev/xxxxx0 is Syzygy port 1). <computer> SZG_SERIALSWITCH baud_rate: Baud rate of the port, one of 2400, 4800, 9600, 19200, 38400, 57600, 115200. <computer> SZG_SERIALSWITCH signal_byte: Character to write, defaults to 0x53. <computer> SZG_SERIALSWITCH event_type: What types of switch events to measure, must be one of 'open', 'closed','both' (default='both'). In all cases the absolute value of the transmitted axis event is the time in seconds since the last event of the type specified.
dumpon. Stop recording with
dumpoff. The event stream will be saved in a file
inputdump.xmlin SZG_DATA/path. This is convenient for elaborate event streams such as full-body motion capture.
For a HowTo about getting your tracker data mapped in to Syzygy coordinates, see Tracker Coordinate Conversion