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
Section 5. Application Programmable Interface
65
McpCall
This function is used to execute an MCP command request. Commands can be issued to the
MCP device or MCP device application embedded within the MCP device.
DWORD McpCall( HANDLE hDevice, PMCPBUS pMCPBUS );
Parameters
hDevice
Handle to the specified device (communications resource) that is to execute the command. This
handle was returned from the McpOpen function.
pMCPBUS
Pointer to the MCPBUS structure used by the MCP API function to perform this operation.
The following structure members are used as input parameters.
Member Meaning
dwApplicationID Device Application ID.
dwCommandID Command Code. Specific command to be executed by the application.
lpInBuffer Pointer to storage buffer containing addition data associated with the
command.
dwInBufferLen Length (in bytes) of data contained in the Input Buffer pointed to by
lpInBuffer
lpOutBuffer Pointer to storage buffer to receive the response from the application
dwOutBufferSize Size (in bytes) of output storage buffer pointed to by lpOutBuffer
The following members are used as output parameters.
Member Meaning
dwResultCode Result Code. Refer to the device's Command Reference for possible
values.
lpOutBuffer Pointer to storage buffer containing the response from the application
dwResponseLen Length (in bytes) of the response returned in the buffer pointed to by
lpOutBuffer