Using a MIL Concord PoE system with the Matrox Concord PoE base model

See also

Reference:

MsysAlloc MsysControl MsysFree MsysInquire

To use Matrox Concord PoE for acquisition, you must allocate and use a MIL GigE Vision system (MsysAlloc() with M_SYSTEM_GIGE_VISION); refer to information denoted for a GigE Vision system. You only need to allocate and use a MIL Concord PoE system (MsysAlloc() with M_SYSTEM_CONCORD_POE) to use the other functionality on the board and to inquire about the board itself. This means that you rarely use a MIL Concord PoE system with the Matrox Concord PoE base model.

For this reason, in the reference, information pertinent to using a MIL Concord PoE system is identified with a column for the Matrox Concord PoE with ToE; most of the functions and constants are typically only available to this model. If the information is applicable to the Matrox Concord PoE base model, there will be a note included to specify this.

The following are the only functions and constants that can be used with a MIL Concord PoE system (using MsysAlloc() with M_SYSTEM_CONCORD_POE) when allocated for a Matrox Concord PoE base model:

Function	Constants supported
MsysAlloc()	M_SYSTEM_CONCORD_POE with M_DEVn or user-defined board name.
MsysFree()	All functionality is available.
MsysControl()	M_DEVICE_NAME, M_POWER_OVER_CABLE.
MsysInquire()	M_BOARD_TYPE, M_DEVICE_NAME, M_DEVICE_NAME_MAX_SIZE, M_POWER_OVER_CABLE, M_SERIAL_NUMBER, M_SERIAL_NUMBER, M_SYSTEM_DESCRIPTOR, M_SYSTEM_DESCRIPTOR, M_SYSTEM_TYPE.

Action commands are also supported on Matrox Concord PoE base model; however, you need to use a MIL GigE Vision system (using MsysAlloc() with M_SYSTEM_GIGE_VISION).