Sensoray 512 DOS - Manual (Page 9)

9
X12TSR.EXE. An API (application program interface) is provided to facilitate 512 application
development. The API provides commands to start/stop the MPEG encoder and decoder, commands to
retrieve or send MPEG data to and from the 512, commands to obtain 512 encoder/decoder status, and
commands to control the digital I/O signals. The parameter data which is maintained by VSETUP.EXE is
read by X12TSR.EXE when acquisition and compression (i.e. encoding) are initiated by the application.
The video system parameter is also read by X12TSR.EXE when X12TSR.exe is initially loaded. A typical
system might first set the path to the system files (see section 5.1), then run VSETUP.EXE to set the
required parameters, load X12TSR.EXE, run the application, etc.
5.1 X12TSR.EXE
X12TSR provides the interface to the 512 hardware and must be loaded before an application can use
the 512. The x86 software interrupt mechanism is used by an application to communicate with the driver
and allows the application to be language independent. In addition to providing the driver functions, it also
initializes the video encoder and decoder and loops the incoming video to the video output.
Before loading X12TSR.EXE the driver must know the location of all the parameter files (*.hex, *.bin, etc.)
If the files are in the current directory nothing needs to be done. If the files are not in the current directory
an environment variable X12PATH must be set to inform the driver about the location of the various
parameter files.
APPLICATION
COMMUNICATES WITH
512 THROUGH X12TSR
X12TSR READS
PARAMETER DATA
X12TSR CONTROLS 512
512 API
PARAMETERS
VSETUP.EXE
X12TSR.EXE
USER
APPLICATION
512
HARDWARE
VSETUP MODIFIES THE
PARAMETERS
Figure 2