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
45
SECTION 4. TRACE LOG
The trace log is a file that logs the communications between the driver and a device. The trace
log is used for helping application and device developers during the device development phase.
It can be used for diagnosing problems with existing applications. The log can capture complete
blocks transmitted and received by the driver or just the application message portion of blocks.
The trace file is a text file and can be read using a standard text editor.
The trace log utility can be enabled and configured using device instance properties. Details of
these properties are in the device instance properties section of this document. These properties
control enabling/disabling logging of the entire block, enabling/disabling logging of only the
application message portion of the block, the name and path of the trace log file, the size of the
trace log file and clearing of the trace log file. The properties are
Port.TraceEnabled,
Core.TraceEnabled, TraceFilePath, MaxTraceFileSize and AppendTraceFile
respectively.
Each line in the trace file has the following format:
<datetime stamp> <origin> <direction> <data>
C
R
L
F
where each field is described below:
<datetime stamp>:
The datetime stamp format is as follows:
MM/dd/YYY
hh:mm:ss:ms
Under Windows 98, Me, time is calculated at GMT.
Under Windows 2000, NT and XP time is the local time.
<origin>:
Origin of entry: MSG – application message portion of block
FRM – entire block including frame
<direction>:
Direction of data with respect to the host: In – incoming
Out - outgoing
<data>:
Data logged in hexadecimal format.
C
R
L
F:
Carriage Return / Line Feed
The following is an example of a trace entry for an application message request and response
(Device application Get Model Number property):