| Customize Help

Using Matrox Concord PoE with MIL

To use Matrox Concord PoE with MIL for acquisition, you must allocate a MIL GigE Vision system (M_SYSTEM_GIGE_VISION), using MsysAlloc(). This allocation opens communication with GigE Vision compliant cameras (through one or more Gigabit Ethernet network adapters in your computer). You can then access and grab from multiple connected GigE Vision cameras by allocating a digitizer for each connected camera (using MdigAlloc() with M_DEVn). Each process (executable) can allocate only one MIL GigE Vision system. Each camera can be used by one process (executable) at a time. For additional information, refer to the Matrox GigE Vision driver chapter in the MIL Hardware-specific Notes.

To use other functionality available on Matrox Concord PoE with ToE or inquire about the status (for example, BoardType) of either model of the board, you must allocate a MIL Concord PoE system, using MsysAlloc() with M_SYSTEM_CONCORD_POE.

Be aware that to access the MIL license that is included on the Matrox Concord PoE board, you must install the Matrox Concord PoE driver.

Refer to the Matrox Concord PoE release notes for any additions/modifications to the MIL Hardware-specific Notes in this chapter or in the MIL Reference.

Using the Advanced I/O Engine of Matrox Concord PoE with ToE

Matrox Concord PoE with ToE has an Advanced I/O Engine that controls the auxiliary I/O interface. The engine includes 16 timers, 2 rotary decoders, 2 I/O command lists, a user-output register, 2 auxiliary output signals, 6 auxiliary input signals and a Trigger-over-Ethernet (ToE) module. To route I/O signals, configure interrupts, and set the mode of an auxiliary signal, use MsysControl(). To inquire this information, use MsysInquire() For more information on some of these features, refer to Chapter 41: I/O signals and communicating with external devices. For information on how to use the ToE module to send a Trigger-over-Ethernet packet (as an action command or GigE Vision software trigger) to the camera, refer to the Sending a Trigger-over-Ethernet packet without Host intervention section later in this chapter.