This page is a part of DuplexDr online Help Manual.
|< previous | content|
The XVCTRC utility is designed for setting a number of trace flags (by toggling related check boxes to filter out data of your interest) and passing them to the DuplexDr driver. According to the Trace Flags set, utilities of the package will filter out and save related information into corresponding trace files you can analyse later. The tracing could be used to document the virtual serial port traffic between your software applications that communicate using a VSP pair channel.
Normally, users should not arbitrarily turn on/off Trace Flags. The flags can noticeably slow down the traffic and can generate a great amount of data. The XVCTRC utility is primarily meant for testing and analysing how your software VSP applications interface to each other while using serial port communication features.
To set up Trace Flags, you should launch the XVCTRC utility. You can do this by double-clicking on the XVCTrc icon in the DuplexDr Programs' folder:
When you start up XVCTRC (with the DuplexDr driver installed), the Virtual ComPort Trace Flags window appears:
If you click the Close button, XVCTRC closes the window with no changes.
Pressing the Apply button passes the Trace Flags set to the DuplexDr driver and closes the window. The Trace Flags will take effect immediately.
Select All makes all the Trace Flags enabled. Clear All makes all the Trace Flags disabled.
Refresh restores all Trace Flags to their initial states (when loaded the XVCTRC utility or after the latest Apply).
With the Save to use in next sessions check box enabled, you can store the current settings (by pressing Apply) and load them later (when loading the XVCTRC utility).
Note: with L=1, the Tracing=L entry line in the ini-file specifies DuplexDr to save tracing information into corresponding tracing files. With L=0, DuplexDr will not write tracing data into the files.
The DumpFile button in the Virtual ComPort Trace Flags window brings up the dialog box:
You can specify a full path name for one of system dump files to be read (when system crash) and a log file name to store the driver tracing information extracted from that dump file that you can analyse later. Normally, you can use the default file names shown.
|< previous | content|
|Copyright © 1999 - 2006 LabtamTM Inc.|