Exporting a Capture File

You can view a previously recorded capture file from ScopeCfg or you can export a capture file into a different data format. To convert a capture file choose the "Convert" option from the "Run" menu inside ScopeCfg.

• Capture File Name: Enter the name and path of the capture file to convert.
• Output File Name: Enter the name and path of the converted file.
• Output File Format: Convert can produce the following file types

  • Binary Mode: This format is useful for users who want to write their own program to analyze their data in a language that is best suited for fixed length record handling. When in binary mode a sequential binary file will be created with the following 10 byte record format:

OFFSET	SIZE IN BYTES	DESCRIPTION
0	1	Port Number
1	1	Data Received
2-5	4	Seconds
6-9	4	Milliseconds

• Text Mode: This format is useful for users who want to write their own program to analyze the output in a language that is designed for parsing and string handling. Creates a sequential text file in the following format: PORT _ DATA _ TIME ______.______
• ASCII Mode:This format is best suited for importing your data into a spread sheet. To create a plain ASCII file that is delimited by a character of your choice use the /a: switch. Type the character you want to use as a delimiter after the ":".
  For example to create a ASCII file delimited by pound signs use the following syntax:
   convert output.dat  /a:#
• ASCII Hex Mode: Creates a text file in a format similar to that of many popular disk editing programs. This is the most readable file format and is recommended for most users. Data is displayed in hex and ASCII and signal changes are displayed in abbreviated form with a +/- to indicate the signal state. If you are going to use Windows Notepad to view the file it is recommended that you change the font type to "Terminal".

In all formats data received from the DTE device will be indicated as port 1 and data from the DCE device as port 2. If you are running SI_SCOPE with the optional Active Cable then SI_SCOPE will write all your keyboard and macro activity with a port code of hex 0x80 OR'ED with the port it was sent to. For example if you are using an Active Cable and send a ASCII Z to the DTE device this will show up in your converted file as a byte received from device 0x81 with the data as 0x5A.

Signal changes will be indicated as being received on port 0. The data field will contain a one byte value that signifies which signal has changed and what the voltage level of the signal changed to. The voltage level of the changed signal is in the high order nibble (upper 4 bytes) of the data and will be a 0 or a 1. The signal that changed will be in the low order nibble as shown in the following table:

SIGNAL NAME	VALUE
Data Carrier Detect	1
Data Set Ready	2
Clear To Send	3
Data Terminal Ready	4
Ring Indicator	5
Request To Send	6

Line status errors will have the port field set to the number of the device that generated the error OR'ED with hex 0x40. The data field will contain one of the following hexadecimal values indicating the type of error detected:

ERROR NAME	VALUE
Overrun Error	2
Parity Error	4
Framing Error	8
Break State	10