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 3. Installation
35
Adding a Device Instance from Command Line – RS-232
Use the following command to add a new device instance:
mcpcfg a <name> Port.Name=<port> [Transport=<xpt> [<more settings>]]
where:
<name> is a name chosen for the new device instance. This name must contain
only characters that are valid for a file name and should have no ‘\’
characters. The name must be unique, i.e.; no other MCP device should be
using it. The new device will be visible under this name to applications
using the MCP API.
<port> specifies the connection port to which the device is attached. It should
specify a valid serial port. If the port name is not one of the pre-defined
system port names (COM1..COM4), a Transport setting must also be
specified (see below). If one of the standard names is used, MCPCFG will
automatically assign the transport type (“Serial” for COMx)
<xpt> specifies the transport type to be used for the device. This setting is
optional if a standard connection port is used. If specified, it should be
“Serial”.
<more settings> other device settings may be specified at the time the device instance is
created. Any number of additional settings may be specified. The syntax
for these is the same as for the mcpcfg s command (see below). If other
device settings are not specified, the default property values will be used.
These defaults are listed in the properties sections.
For Windows NT Administrator privilege is required to execute this command.
Example:
mcpcfg a IntelliStripe Port.Name=COM1
The informational and diagnostic messages displayed by this command can be suppressed by
using the “quiet” version:
mcpcfg aq <name> ...
Adding a Device Instance from Command Line – USB
Device Instances are automatically added. If the device has a serial number, the instance name is
DeviceName.SerialNumber.