Remote Debugging On Matrox 4Sight Using; Microsoft Visual Basic; Working With Mil - Matrox 4Sight User Manual

Using the 1394 ports
Using the auxiliary I/Os
Displaying grabbed
images
Remote debugging on Matrox 4Sight using Microsoft Visual Basic

Remote debugging on Matrox 4Sight using

Microsoft Visual Basic

Remote debugging is not supported under Windows NT
Embedded for Visual Basic applications.

Working with MIL

When developing a MIL application for Matrox 4Sight, there
are several things to note.
It is important to note that MIL can automatically perform
YUV to RGB transformations and vice versa. MIL performs
these transformations automatically when copying or grabbing
into an image buffer of the required type.
When using the IEEE 1394 ports, you can only use cameras
that are compliant with the IEEE 1394 Digital Camera
Specifications. In addition, once the MIL Matrox Meteor-II
1394 driver is installed, you can only use these cameras through
MIL. Furthermore, MIL does not support the hot-plugging
capabilities inherent in the IEEE 1394 standard.
To use the auxiliary I/Os on Matrox 4Sight from MIL, you must
first assign an interrupt line to the group of I/Os in the BIOS.
These I/Os can then be controlled from within MIL. Refer to the
MIL/MIL-Lite Board-Specific Notes for more information.
When displaying grabbed images, the pre-installed Matrox
Meteor-II driver can take advantage of the National
Semiconductor
capabilities and use MIL's DirectDraw underlay-surface
display capabilities. In this mode, Matrox Meteor-II does not
need any CPU intervention to maintain a live image display,
with or without overlay. By default, the Matrox Meteor-II driver
uses this mode.
® ™
Geode GXLV graphics controller's overlay
61