Owner manual
Table Of Contents
- REGISTERED TO ISO 9001:2000
- SECTION 1. OVERVIEW
- SECTION 2. SYSTEM REQUIREMENTS
- SECTION 3. INSTALLATION
- INSTALLING THE MCP DRIVER
- CHANGING THE MCP DRIVER:
- REMOVING THE MCP DRIVERS
- DEVICE INSTANCE MANAGEMENT
- Device Instance Overview
- MCPCFG Utility Overview
- MCPCFG Command Summary
- Adding a Device Instance from Command Line – RS-232
- Adding a Device Instance from Command Line – USB
- Adding a Device Instance from Windows Based Application (WINDOWS 2000, XP) – RS-232
- Adding a Device Instance from Windows Based Application (WINDOWS 2000, XP) – USB
- Modifying a Device Instance Properties from Windows Based Application (WINDOWS 2000, XP) – RS-232 and USB
- Removing a Device Instance from Windows Based Application (WINDOWS 2000, XP) – RS232
- Removing a Device Instance from Windows Based Application (WINDOWS 2000, XP) – USB
- Removing a Device Instance from a Command Line – RS-232
- Removing a Device Instance from a Command Line – USB
- Displaying the List of Device Instances from Command Line
- Displaying Device Instance Properties from Command Line
- Modifying Device Instance Properties from Command Line
- Modifying Device Instance Properties From Windows Based Application
- Restarting the MCP Driver
- Stopping the MCP Driver From Command Line
- Windows Configuration Utility
- DEVICE INSTANCE PROPERTIES
- SECTION 4. TRACE LOG
- SECTION 5. APPLICATION PROGRAMMABLE INTERFACE
- TYPICAL OPERATION
- DEVICE CHANNEL LIFE CYCLE
- PROPERTIES
- COMMANDS
- NOTIFICATIONS
- FUNCTIONS
- Summary
- MCPBUS Structure
- Members
- Remarks
- The MCPBUS is used as an input parameter to many of the MCP API functions. The MCP driver modifies only those members explicitedly defined by the individual functions. For example, the API will not modify the lpOutBuffer or dwOutBufferSize members (the buffer that lpOutBuffer points to will of course be modified); therefore, the caller may set these values once and not need to reset them prior to invoking subsequent MCP API functions. The only structure members modified by an MCP API function are those explicitly identified as output parameters.
- McpEnum
- McpOpen
- McpClose
- McpReset
- McpGet
- McpCall
- McpWait
- CONSTANT DEFINITIONS
- FUNCTION PROTOTYPES
- INDEX

MagTek Communications Protocol, Driver Reference Manual
52
MCPBUS Structure
The MCPBUS structure represents a common structure (bus) used to pass arguments to the MCP
API functions. Not all members of this structure are used for every function; refer to each
function description below to determine how the members are used.
typedef struct _MCPBUS
{
DWORD dwOperAttribute ; // operation attribute
DWORD dwApplicationID ; // application ID
DWORD dwCommandID ; // command ID
DWORD dwResultCode ; // command/notification result code
LPSTR lpszPropertyName ; // pointer to property name
DWORD dwPropertyID ; // property ID
DWORD dwPropertyType ; // property type
LPVOID lpInBuffer ; // pointer to input buffer
DWORD dwInBufferLen ; // length of data in input buffer
LPVOID lpOutBuffer ; // pointer to output buffer
DWORD dwOutBufferSize ; // output buffer size
DWORD dwResponseLen ; // length of response in output buffer
DWORD dwTimeout ; // notification timeout value
DWORD dwContext ; // device enumeration context
} MCPBUS, *PMCPBUS;
Members
dwOperAttribute
Operation Attribute. Some MCP API functions require this member to be set prior to invoking
the function to distinguish how the operation is processed. The following table defines the
attributes and for which functions they apply.
Function Code Meaning
MCP_ATTR_NONE Do not discard any queued notifications
before responding.
McpWait
MCP_ATTR_WAIT_NEW Discard any notifications that may have
been queued before returning a response.
MCP_ATTR_NONE MCP Device specific property McpGet, McpSet
MCP_ATTR_PROP_DRIV
ER
MCP Driver Device instance specific
property