User manual MAXTOR MULTMET2

[. . . ] Topics covered below are: ü installation of the boards; ü grabbing from genlocked or non-sync cameras; ü the number of cameras per board; ü system bandwidth requirements; ü along with a software example and software support. MULTIPLE BOARD INSTALLATION Installation of multiple boards will require an empty PCI (32-bit) slot for each board to be installed, and in some instances, the removal of a PCI card from the system to make room for the additional board. When installing an additional card, it is important to observe the steps followed when installing the first Matrox Meteor board and pay close attention to the existence of a large black-ridged heat sink found in some computers. The Matrox Meteor boards must never come in contact with this heat sink and it is important to use a slot that will allow the boards to completely avoid the heat sink. [. . . ] With MIL driver version 3. 1x, any overlap of windows on the display device will result in one live and one pseudo live image at 15 frames per second (see figure 4). With the upcoming MIL driver 4. 0, performance will be improved to 27 frames per second. An improved detection of window overlap will also exist; for a simple overlap there will be live grab capability for both windows (see figure 5). pseudo-live grab (approx. 15 fps or less) live grab (active window) live grab (active window) pseudo-live grab (non-active window) non-simple overlap (without interference) pseudo-live grab (non-active window) live grab (active window) simple overlap (without interference) Figure 4: Using MIL driver version 3. 1x May 8, 1998 3 Using the Multiple Matrox Meteor in a System pseudo-live grab (up to 27 fps) live grab (active window) live grab (active window) live grab (non-active window) non-simple overlap (without interference) live grab (non-active window) live grab (active window) simple overlap (without interference) Figure 5: Using MIL driver version 4. 0 SOFTWARE SUPPORT Software support for the multiple boards is available through recent versions of the libraries, i. e. MIL-16/MIL16 Lite 2. 2 and MIL-32/MIL-32 Lite 3. 1 or higher; and the recent versions of the drivers, i. e. MIL-16 Driver for Meteor 2. 21 and MIL-32 driver for Meteor 3. 11 or higher. SOFTWARE EXAMPLE Since there are now two boards being used in this example, there are two application identifiers. For each additional board introduced into the system, the addition of an identifier and allocation will be necessary. In this example, allocation of the first MIL system, digitizer, display, 2D data buffer is followed by the allocation of the second. The function MdispSelect() outputs the specified image buffer contents to the specified display controller, while the function MdigGrabContinuous grabs continuously from the input device (the camera) until MdigHalt(. . . ) is issued. Again there are two function calls for the two boards installed in the system. The function MdispDeselect stops displaying the specified image buffer, leaving the display blank. Deallocation of the buffer, display controller, digitizer, and system (MbufFree, MdigFree, MdispFree, MsysFree respectively) is done for each of the boards individually. May 8, 1998 4 Using the Multiple Matrox Meteor in a System CODE EXAMPLE The program following is an example that (using the defaults) displays live and pseudo-live images from multiple Matrox Meteor boards. #include <stdlib. h> #include <stdio. h> #include <mil. h> void main() { MIL_ID MilApplication, /* Application identifier. */ MilSystem0, MilImage0, MilDisplay0, MilDigitizer0, /* System identifier. */ MappAlloc(M_DEFAULT, &MilApplication); /* Allocate first system objects. [. . . ] */ MdispDeselect(MilDisplay0, MilImage0); MbufFree(MilImage0); MdigFree(MilDigitizer0); MdispFree(MilDisplay0); MsysFree(MilSystem0); /* Free appplication . */ MappFree(MilApplication); } Corporate Headquarters: Canada and U. S. A. Dorval, Quebec, Canada H9P 2T4 Tel: (514) 685-7230 Fax: (514) 822-6273 Sales Offices: U. K. [. . . ]