Frontline Test System FTS4BT. User Manual

Transcription

1 Frontline Test System FTS4BT User Manual 5-May-06 FTS4BT-UM-001

2

3 Copyright Frontline Test Equipment, Inc. All rights reserved. FTS4BT is a trademark of Frontline Test Equipment, Inc. 5-May-06 i FTS4BT-UM-001

4 Table of Contents Table of Contents Introduction and Installation Introduction to FTS4BT FTS4BT Sniffer Modes Minimizing Windows About Dialog Air Sniffing Hardware Setup Air Data Source Dialog Channel Map Info Hardware Settings I/O Settings Determining Master and Slave in Bluetooth Role Switches Specifying the Synchronization Device Selecting a Synchronization Mode Optional Hardware Settings Advanced Settings Dialog Inquiry Access Code Capture Filtering Encryption High Speed UART (HSU) HSU Hardware Requirements and Configuration Hardware Settings I/O Settings USB HCI Sniffing USB HCI Data Source Dialog USB HCI Sniffing Sniffing the Microsoft Bluetooth Keyboard and Mouse Serial HCI Hardware Settings Choosing Mode and Com Ports Spy Source DTE, No Cables Detect Now button Advanced Hardware Settings functions Notify if Auto Cable Detection Fails Disabling Control Signal Interrupts UART FIFO Settings May-06 ii FTS4BT-UM-001

5 Table of Contents Set the FIFO buffers in Windows 2000/XP Serial Port Info button Cable Configuration Dual Port Monitor Mode Cable Configuration Dual Port Source DCE Mode Cable Configuration Dual Port Source DTE Mode Cable Configuration Single Port Monitor DCE Mode Cable Configuration Single Port Monitor DTE Mode Cable Configuration Single Port Source DCE Mode Cable Configuration Single Port Source DTE Mode Cable Configuration RS-232 Pin-outs I/O Settings I/O Settings Window Operating Mode - Choosing to Monitor or Source Setting Baud, Parity, Word Length and Stop Bits Defining Your Own Baud Bit Order Flow Control Names Custom Protocol Stack button Saving Configurations Saving A Configuration to File Opening a Saved Configuration Selecting a Protocol Stack Protocol Stack Wizard Information Screen Create a Custom Stack Where To Connect FTS For BCSP How FTS4BT Auto-traverses the Bluetooth Stack Reframe Function Unframe Function Decoder Parameters Providing Context For Decoding When Frame Information Is Missing Predefined Stacks Adding a New Predefined Stack Capturing Data Control Window The Control Window Toolbar Capturing Data to Buffer Capturing Data to Disk Statistics May-06 iii FTS4BT-UM-001

6 Table of Contents Statistics Window Session, Resetable and Buffer Tabs Copying Statistics To The Clipboard Changing Frame Size Ranges Information on the Tables Statistics Tables Data Table Errors Table Frame Sizes Table Utilization Table Chars Per Second Table Frames Per Second Table Octets Per Second Table Buffer Information Table Graphs Statistics Graphs Viewing Percentages or Values Printing Graphs Graph Options Analyzing Byte-level Data Event Display The Event Display Toolbar Switching Between Live Update and Review Mode Opening Multiple Event Display Windows Calculating Delta Times and Data Rates Calculating CRCs List of All Event Symbols Data Formats and Symbols Switching Between ASCII, EBCDIC and Baudot Switching Between Hex, Decimal, Octal or Binary Switching Between Viewing All Events and Viewing Data Events Viewing Only ASCII (or EBCDIC or Baudot) Viewing Only Hex (Or Decimal or Octal or Binary) Mixed Sides Font Size Analyzing Protocol Decodes Frame Display Window Frame Display Panes Protocol Tabs Comparing Frames Quick Export of the Summary Pane May-06 iv FTS4BT-UM-001

7 Table of Contents The Frame Display Toolbar Summary Layer drop-down box Text with Protocol Stack Sorting Frames Working With Panes Hiding (and Revealing) Protocol Layers Working With Multiple Frame Displays Filters and Multiple Frame Displays Synchronization Between the Event and Frame Displays Physical vs. Logical Byte Display Frame Display Status Bar The Panes in the Frame Display Summary Pane Customizing Fields in the Summary Pane Frame Symbols in the Summary Pane Decode Pane Radix, or Hexadecimal, Pane Character Pane Binary Pane Event Pane Protocol Layer Colors What The Color Of Data Bytes Means Changing Protocol Layer Colors Red Frame Numbers or Bytes Protocol Navigator Window Protocol Navigator Hiding and Revealing Protocols The Difference Between Filtering and Hiding Expanding and Collapsing Protocol Layers Protocol Navigator Status Bar Analyzing Control Signal Changes Viewing Signal Changes in Real-time Breakout Box Window The Breakout Box Toolbar Reading the Breakout Box Window Breakout Box Options Viewing Historical Signal Changes Signal Display Window Reading the Signal Display Signal Display Options The Signal Display Toolbar May-06 v FTS4BT-UM-001

8 Table of Contents Transmitting Data Transmit Window Transmit String Transmit String Formats Transmit File Transmitting FTS Capture Files Flow Control When Transmitting Changing Control Signals Delays and Max Burst Size Transmit Options The Transmit Toolbar Pause Transmit Searching Searching Go To Search by Pattern Searching for Data Errors Searching for Control Signal Changes Searching within Decodes Searching for Frame Errors Searching for Special Events Side Restriction Changing Where the Search Lands Searching by Time Searching By Time Absolute Timestamp Search Relative Timestamp Search Choosing "On or Before" or "On or After" Subtleties of Timestamp Searching Entering Search Patterns Entering Characters Entering Hex or Binary Entering Control Characters Using Wildcards Examples of Search Strings Bookmarks Bookmarks Adding a Bookmark Modifying or Deleting a Bookmark Moving Between Bookmarks Viewing All and Searching For Bookmarks May-06 vi FTS4BT-UM-001

9 Table of Contents Filtering Include and Exclude Radio Buttons Display and Filter Within Results Filters Display Filters How To Create and Use a Display Filter Compound Display Filters How to Remove Display Filters Defining Node and Conversation Display Filters Predefined Display Filters Advanced Display Filtering Techniques Filter Within Results Filters How to Create and Use a Filter Within Results Filter How to Remove a Filter Within Results Filter Saving and Loading Display and Filter Within Results Filter Files About Saved Filters Naming and Saving Display and Filter Within Results Filters to a File Opening Display and Filter Within Results Filter Files Editing Display and Filter Within Results Filters How to Modify a Condition in a Display or Filter Within Results Filter How to Delete a Condition in a Compound Display or Filter Within Results Filter Delete Saved Display and Filter Within Results Filters Protocol Filtering from the Frame Display Easy Protocol Filtering Filtering on the Summary Layer Protocol Quick Filtering on a Protocol Layer Filtering on All Frames With Errors Protocol Filtering from the Protocol Navigator Hiding and Revealing Protocols Filtering on a Protocol Layer Using Named Filters Filtering on All Frames With Errors Saving Data Saving Your Data Saving the Entire Capture Buffer Saving a Portion of a Capture File or Buffer Confirm CFA Changes Capture File Notes Loading and Importing Capture Files Loading a Capture File Importing Capture Files Importing Timestamps May-06 vii FTS4BT-UM-001

10 Table of Contents File Format for Merlin Files Printing Printing From The Event Display About Event Display Print Print Background Colors Using Internet Explorer Print Background Colors Using Netscape 8.0 and Mozilla Accessing the Event Display Print Dialog Print Preview Troubleshooting Printing Problems Exporting Exporting Data Event Display Export Advanced Export Export Fields Exporting Baudot Export Filter Out Other Export Options Exporting Frames Frame Print/Export Frame Export File Format General Section General Formatting Summary Section Summary Formatting Decode Section Decode Formatting Decode Section - Data Display Error Section Quick Export Export Templates Export Templates Monitoring Internal Ports Spy Spy Mode Settings on the I/O Settings Window FIFOs and Spy How to Turn Off the FIFO Buffers in Windows System Settings and Program Options System Settings Common Options Buffer/File Options Advanced System Options May-06 viii FTS4BT-UM-001

11 Table of Contents Max Percent Of Free Disk Space for Capture File Max Percent Of Available Virtual Memory Used for Capture Buffer Driver Receive Buffer Size in Operating System Pages Driver Action Queue Size In Operating System Pages Capture Buffer Read Cache Size In Kbytes Capture File Write-Through Cache Size In Pages Return Unused Space in Capture File When Closing (Yes/No answer) Maximum Number of Bytes Decoded Per Frame Maximum Number of Bytes Used to Store Supplementary Capture File Information Capture Buffer System Page Size Multiplier Non-Realtime Event Queue Size Changing Default File Locations Start Up Options Timestamping Enabling/Disabling Timestamping Changing the Timestamping Resolution Switching Between Relative and Absolute Time Displaying Fractions of a Second Timestamping Options Performance Issues For High Resolution Timestamps Frame Decoder Frame Decoder Technical Info and Support Contacting Technical Support Technical Information Performance Notes Note Concerning Ring Indicator RS-232 Pin-outs Event Numbering BPF Copyright Notice Clear Capture Buffer Warning The Serial Driver The FTS Driver Windows 2000 Driver Handy Character Tables ASCII Codes EBCDIC Codes Baudot Codes Communication Control Characters Glossary H HBookmark H123 5-May-06 ix FTS4BT-UM-001

12 Table of Contents Buffer Wrapping Capture Buffer CD - Carrier Detect CRC Error CTS - Clear to Send DCE Device Display Filters Driver Buffer Overflow DSR - Data Set Ready DTE Device DTR - Data Terminal Ready Event FIFO buffers Frame Recognizer Frame Transformation Framing Error Hardware Flow Control Information Node Logical Frame Overrun Error Parity Error Physical Frame Radix RI - Ring Indicator RS RTS - Request to Send Snapshot Software Flow Control UART Underrun Error Index May-06 x FTS4BT-UM-001

13 Introduction and Installation Introduction and Installation Introduction to FTS4BT Welcome to the Frontline Test System! Frontline Test System (FTS) is a family of products designed to let you conduct data analysis using your personal computer, of which FTS4BT is the Bluetooth analysis component. The FTS interface is easy to use without training, but you will want to read the online help to learn how to take maximum advantage of all the features. We have tried to make the help complete and easy to use. The Table of Contents will guide you towards general information on different areas of the product, and the Index will help you find specific information on a particular topic. If you need to print out a topic, click on the Print Topic button. If you would like to print out an entire section from the help (a section corresponds to one of the books in the Table of Contents), click on the section you want, and then click on the Print button. All of the topics listed in the section will be printed. If you need assistance setting up the cables, please refer to the Cable Configuration section of the Help file. For assistance on choosing which COM ports to use with FTS, please refer to the Hardware Settings help. FTS4BT Sniffer Modes FTS4BT has different sniffing modes to accommodate various applications. The desktop folder contains shortcuts for the following different modes that allow you to sniff different situations. Air Sniffer (Basic) This is the standard Air Sniffer using the Bluetooth ComProbe (USB dongle) as the hardware interface to Bluetooth air traffic. Air Sniffer (Mixed Piconet) Mixed Piconet mode is used to sniff a V1.1 Bluetooth specification device and a V1.2 Bluetooth specification device on the same piconet. A master must use a different Frequency Hopping Pattern when communicating with the V1.2 specification device than with a V1.1 device. FTS4BT will use a second Bluetooth ComProbe to follow the second Frequency Hopping pattern. The data collected by both ComProbes will be shown in the same GUI. There are two I/O Parameter setups for the two different (V1.1 and V1.2) devices. Synchronization setup is the same for both Data Sources. Air Sniffer (Redundant) This mode uses two ComProbes to sniff the same Piconet to ensure that no data is being missed. Air Sniffer (Scatternet) In Bluetooth a device can be a slave in one Piconet and a master in another, this is called Scatternet. Again, as in Mixed Piconet, there is more than one hopping pattern. FTS4BT employs a second Bluetooth ComProbe to follow the second hopping pattern, as it does in Mixed Piconet. If there are more than two Piconets in the Scatternet then additional ComProbes may be added as needed. Capture File Viewer The Capture File Viewer is used for analyzing previously captured data. 5-May FTS4BT-UM-001

14 Introduction and Installation Serial HCI Sniffer (BCSP), (H4), (H5). Serial HCI sniffing is used to monitor data going between a Host and Host controller, FTS4BT includes a set of custom cables for Serial RS-232 sniffing. Using HCI sniffing in conjunction with air sniffing, a complete picture of the Bluetooth transmission can be captured. Serial BCSP stands for Blue Core Serial Protocol. This was developed by CSR. Serial H4 is the normal Serial UART. Serial H5 is a new specification 3 wire UART (close in specification to BCSP). USB HCI Sniffer (H2) The USB HCI Data source dialog allows the user to select which Bluetooth device to sniff and to Start and End the sniffing process. The dialog has a list containing the Bluetooth Devices connected to your system. If the Show Connected Only checkbox is unchecked then all USB devices that have ever been connected to your system will be listed. If you have connected or disconnected a device while this dialog is open, click on Refresh List to update the list. To sniff a USB device, just select it with your mouse and click on Start Sniffing. Note: Start USB HCI sniffer before you run an application on the USB port. Virtual Sniffer The Virtual Sniffer is a live import facility within FTS4BT that makes it possible to access any layer in a stack that the programmer has access to and feed this data into the Virtual Sniffer FTS4BTV. Please refer to the "Show Live Import Information" button on the Virtual Sniffer Datasource window in FTS4BT. More information is available in the Options Folder in FTS4BT Desktop folder, and a white paper is available at Minimizing Windows Windows can be minimized individually or as a group when the Control window is minimized. To minimize windows as a group, go to the Window menu on the Control window, and select Minimize Control Minimizes All. FTS will put a check next to the menu item, indicating that when the Control window is minimized, all windows will minimize. Select the menu item again to deactivate this feature. About Dialog The About dialog contains the following: Information on serial number expiration or maintenance period Product logo Product name Product version number Product serial number A brief explanation of the purpose of the software Component list and save button Company contact information Copyright and trademark information 5-May FTS4BT-UM-001

15 Introduction and Installation The component list is a record of all the components loaded for the session. Note that the content of this list varies for one or more of the following reasons: Between products According to whether the product is idle or running According to whether the product is live or a capture file viewer According to the state of the session - observers loaded or not The "Save Components" button allows a user to save the contents of the component list to a text file. 5-May FTS4BT-UM-001

16 Air Sniffing Air Sniffing Hardware Setup 1. Connect the Bluetooth ComProbe to an available USB port. 2. Open the FTS4BT folder on your desktop and double-click FTS4BT Air Sniffer. FTS4BT will start and the Bluetooth ComProbe icon will appear in your system tray (usually found in the lower right corner of your screen) in red. Also, the Data Source Control dialog box will appear. 3. Click the Hardware Settings button and select which Bluetooth ComProbe to use. Click OK to return to the Data Source dialog. 4. Click the I/O Settings button on the Data Source Control dialog and enter all the necessary Bluetooth ComProbe setup information. Click OK when finished to return to the Data Source Control window. 5. Start data capture so that when data begins arriving FTS will be capturing it. On the Control Window, click the green arrow to capture to memory or the green arrow on top of a floppy disk to capture to disk. 6. Click the Start Sniffing button to begin synchronizing to the piconet. Air Data Source Dialog The Data Source Control window gives access to and shows the status of the Bluetooth ComProbe. As data is being captured, the Status message at the top of the window will indicate the synchronization status of the Bluetooth ComProbe. Also, the color of the Bluetooth ComProbe icon in the system tray will change depending on the synchronization state. There are four states: Blue = running and in sync with the piconet. Green = running and waiting to resynchronize. Yellow = will attempt to resynchronize in 5 seconds. Red = initializing Red with a "Not" symbol = stopped. The Functions of the Buttons Resync Now - resynchronizes to the piconet. I/O Settings - opens a dialog box where you can change synchronization mode, device to sync to, and other parameters related to encryption and packet capture. Hardware Settings - opens a dialog box where you can change which Bluetooth ComProbe device to use and get information on the Bluetooth ComProbe's board address. Advanced Settings Dialog Opens up a dialog that will allow you to modify the Advanced Settings. Channel Map Info Click this button to toggle the display of the Channel Map. This display is used to determine which channels are available with Adaptive Frequency Hopping. Start Sniffing - sets up the Bluetooth ComProbe using the settings from the I/O Settings window and synchronizes to the piconet. Note that you must click the Start Capture to Buffer or Start Capture to Disk buttons on the Control window in order to capture data. This button will change its name to Stop Sniffing when it is in sniffing mode. Stop Sniffing - stops monitoring data. 5-May FTS4BT-UM-001

17 Air Sniffing Generate Empty Slot Placeholders This will put a placeholder packet for every timeslot so you can easily see if your packets are appearing in the correct timeslot. When this option is set, all Capture Filtering set in the I/O Settings will be turned off. Channel Map Info This display is used to determine which channels are available with Adaptive Frequency Hopping. Green Channel is currently available for use. Red When Adaptive Frequency Hopping is in use; red indicates that the channel has been marked unavailable. Blue Indicates that a packet was captured on the channel. The Clear button will reset each indicator back to the green state. The indicators are also reset whenever a new Channel Map goes into effect. Note Because of hardware filtering of packets; as selected on the I/O Settings dialog, some packets are not captured and therefore some active channels may not be indicated in the Channel Map Display. Hardware Settings Choose a Bluetooth ComProbe device to use from the drop down list. Click Refresh to update the list if you change or add devices. If you just have one Bluetooth ComProbe connected to your PC, that device will be used automatically and you don't need to select it. The dialog also lists information on the current device connection, the board address of the Bluetooth ComProbe, the hardware type, and the firmware version. I/O Settings The I/O Settings window has all the setup information FTS needs in order to synchronize with the piconet and capture data. FTS requires information on the clock synchronization method and the board address of the device to initially sync to. You may optionally specify an inquiry access code to limit the board addresses FTS looks at, choose whether or not to capture certain packet types and specify any encryption information needed to correctly decode data. Determining Master and Slave in Bluetooth In Bluetooth, the device that initiates the connection is always the master at connection time. You only need to know the master and slave at connection time when setting up the I/O Settings. Afterwards a role switch may occur, but FTS will automatically follow the role switch. Role Switches After the connection has been made, a role switch can take place. A good example of why this happens would be when a mouse connects to the PC. The mouse initiates the connection, so it is the master. After the connection is made, a role switch occurs so that the PC becomes the master and the mouse becomes a slave. The role switch takes place because the PC may be working with multiple devices at the same time, and as such, the PC would not be a slave of more than one device. Let us say that a piconet exists between a PC and a keyboard with the PC a master. If the mouse wants to become a member of the piconet it will initiate the connection. Since the mouse initiated the connection, it is the master of a new piconet and the PC is the slave. The PC is still the master of the piconet between the PC and keyboard. A role switch now occurs between the PC and the mouse, and the PC is now the master of a piconet with two slaves: the mouse and keyboard. 5-May FTS4BT-UM-001

18 Air Sniffing Specifying the Synchronization Device FTS needs to know the board address of the device to synchronize to. If you have selected Slave Inquiry Mode or Slave Page Mode, you must specify a Slave address. You may optionally specify a Master device if you want to be certain of sniffing a specific piconet. If you have selected Master Inquiry Mode, you must specify a Master address, and may optionally specify a Slave address. You can specify the board address in multiple ways. 1. Select the board address from a list of available devices. The list of available devices is stored in the Device Database. To add to the list, press the Discover Bluetooth Devices button. A device inquiry will be performed and all discoverable devices (subject to matching up with the Inquiry Access Code) will then be available from the pick list. If you want to limit the list of devices by class of device, select a class from the Class list. 2. Type in the number as a 12 digit hex number. The "0x" will be automatically typed in by the control. Any devices entered this way will be added to the Device Database. 3. Type in the number as LAP-UAP-NAP. Just click on the "LAP-UAP-NAP" check box and all items in the list will display in the LAP-UAP-NAP format. "0x-" will be automatically typed in by the control. Any devices entered this way will be added to the Device Database. 4. Pressing the Choose Pair button. This button will take you to the Device Database Dialog, which will allow you select a pair of devices and a Link Key from a list. Click the Swap button to switch the Slave and Master addresses. Selecting a Synchronization Mode FTS needs to know how to synchronize with the piconet. FTS supports three Synchronization Modes. Slave Inquiry Mode - This is the preferred synchronization mode to use. FTS performs an inquiry of the slave device to obtain its Bluetooth clock. FTS then enters continuous page scan mode, using the slave's Bluetooth clock and address to calculate the correct page scan frequencies. When the master pages the slave, FTS switches to the master s Bluetooth clock and then follows the master s frequency hopping sequence. This synchronization mode requires that the slave has inquiry scan enabled and is page scanning prior to being paged by the master. Master Inquiry Mode FTS performs an inquiry of the master device to obtain its Bluetooth clock then follows the master s frequency hopping sequence. This synchronization mode requires that the master have inquiry scan enabled. Slave Page Mode FTS pages the slave device to obtain an estimate of its Bluetooth clock; however, the paging process does not get completed so the slave device times out and returns to page scanning. FTS then enters continuous page scan mode, using the slave's estimated Bluetooth clock and the slave s address to calculate the page scan frequencies. When the master pages the slave, FTS switches to the master s Bluetooth clock and then follows the master s frequency hopping sequence. This synchronization mode requires that the slave is page scanning prior to being paged by the master. This synchronization mode is considered to be passive because the Bluetooth host is never made aware of the page made by FTS since the paging process does not get completed. 5-May FTS4BT-UM-001

19 Air Sniffing Optional Hardware Settings Advanced Settings Dialog There are three levels of decoding in the FTS4BT Air Sniffer. 1. There is the full protocol level decoding as shown in the Frame Display and Protocol Navigator. 2. The Air Data Source also inspects the LMP packets to look for LMP_DETACH. 3. The firmware of the sniffer also does some low-level decoding to learn about the piconet it is sniffing. In previous versions the firmware would decode the low-level information for all members of the piconet. To support AFH the firmware must only decode this information for one member. All packets will still be sniffed and decoded at the higher levels but the low-level decoding will only be followed on the first member of the piconet it sees. You can use this dialog to change which member the firmware follows or to have it follow all members. Inquiry Access Code The Inquiry Access Code controls which devices are placed into the pick list when the Discover Bluetooth Devices button (used when selecting a board address to synchronize to) is pushed. Capture Filtering FTS filters out a number of packet types by default. If you would like to see these packet types, uncheck the box next to the type of packet. Some of these packet types can be so numerous that they may make it more difficult to locate data packets in the Frame Display and Protocol Navigator windows. Encryption Bluetooth devices can have their data encrypted when they communicate. They secure this by sharing a common Link Key that is never transmitted over the air. FTS needs the Link Key to be able to sniff this communication. There are three ways that FTS can know the Link Key. You are able to switch between these methods in the I/O Settings window. First if you know the Link Key in advance you may enter it directly. Select Link Key in the Encryption list and then enter the Link Key in the edit box. If the link key is already in the database the Link Key will automatically be displayed in the edit box if the after the Master and Slave have been selected. You can also pick Choose Pair to select a Master, Slave and Link Key from the device database. The second way is to use a PIN Code to generate the Link Key. The devices generate link Keys during the Pairing Process based on a PIN Code. The Link Key generated from this process is also based on a random number so the security cannot be compromised. If FTS is given the PIN Code it can determine the Link Key using the same algorithm. Since FTS will also need the random number, FTS must catch the entire Pairing Process or else it will not be able to generate the Link Key and decode the data. If you want to enter the PIN Code for encryption select PIN Code (ASCII) or PIN Code (Hex) from the Encryption List. 5-May FTS4BT-UM-001

20 High Speed UART High Speed UART (HSU) HSU Hardware Requirements and Configuration System requirements for the EB ComProbe: Windows XP SP1 One USB 2.0 High Speed enabled port. The EB ComProbe will not run on USB 1.1 Full Speed ports. Pin outs for the EB ComProbe: Wire Label Wire Color Signal Meaning 0 Black TxD Transmit Connection 1 Brown RxD Receive Connection 2 Red RTS Request to Send 3 Orange CTS Clear to Send 4 Yellow DSR Data Set Ready 5 Green DTR Data Terminal Ready 6 Blue CD Carrier Detect 7 Violet RI Ring Indicator TRG White Not Used N/A CLK Gray Not Used N/A GND Black Ground Ground Hardware Settings Select Hardware Settings from the Options menu on the Control Window and choose a device to use from the drop down list. Click Refresh to update the list if you change or add devices. If you just have one device connected to your PC, that device will be used automatically and you don't need to select it. I/O Settings Click the I/O Settings icon on the Control window. The analyzer requires information on Bit Rate, Parity, Length, and number of Stop bits in order to operate properly. If you are capturing framed data, the analyzer needs to know what protocols are present on your circuit to decode them correctly. There are two rows of settings, one for the TxD (transmit connection), and one for the RxD (receive connection). To change the bit rate, parity, word length or number of stop bits, click on the down arrow next to the setting box and choose an option from the list. For bit rate, you can either choose a listed rate or enter a rate. After entering the settings for TxD, click the Copy TxD button to apply the same settings to the RxD row. 5-May FTS4BT-UM-001

21 HC USB HCI Sniffing USB HCI Sniffing USB HCI Data Source Dialog The USB HCI Data Source Dialog allows the user to select which Bluetooth device to sniff and to initiate and terminate the sniffing process. The dialog has a large list control containing the Bluetooth Devices connected to your system. If the Show Connected Only checkbox is unchecked then all USB devices that have ever been connected to your system will be listed. Select the device you wish to sniff then click on the Start Sniffing button. You must click on the Start Capture to Buffer or Capture to Disk buttons in FTS capture data. For more details see USB HCI Sniffing. Click on Refresh List if you have connected or disconnected a device while this dialog is open to update the list. USB HCI Sniffing FTS restarts the USB Bluetooth Device when the Start Sniffing button is pressed. Some USB Bluetooth devices are unable to restart if they are connected to another Bluetooth Device. If this is the case you should 4. Break the connection between the device you want to sniff and any devices it is communicating with. 5. Click the Start Sniffing button. 6. Reconnect the devices so that you can sniff the connection. Sniffing the Microsoft Bluetooth Keyboard and Mouse To sniff the Microsoft Keyboard and Mouse start the USB HCI sniffer, select the Wireless Transceiver and select the Start Sniffing button. On some versions of Windows the Windows USB driver cannot reset when it is in use. In this case you will get an error saying "Invalid Selection device may be in use". To get around this problem use the following steps to sniff the Keyboard and Mouse. 1. The first thing you need to do is to break the connections from the keyboard and mouse to the Wireless Transceiver. There is a button on the bottom of the keyboard. Press this button and hold for a bit to make sure it took effect. There is a similar button at the bottom of the mouse. Press and hold it too. We need to break all connections to the Wireless Transceiver or we will not be able to restart. 2. Start the USB HCI sniffer. On the data source find the Microsoft Wireless Transceiver and hit the Start Sniffing button, and hit the Start Capturing button. 3. Go to the Start menu and find the Microsoft Keyboard program and use it to reconnect the keyboard. 4. Go to the Start menu and find the Microsoft Mouse program and use it to reconnect the mouse. 5. All traffic should now be sniffed. 5-May FTS4BT-UM-001

22 Serial HCI Serial HCI Hardware Settings The Hardware Settings box is used to tell FTS which product mode you want to use and which COM ports to use. This box will appear the first time you start the program. If you need to change your COM ports, you can do so at any time by choosing Hardware Settings from the Options menu in the Control Window. Choosing Mode and Com Ports There are three radio buttons at the top of the Hardware Settings box. These are: "Use FTS Cables", "Spy Mode", "Source DTE, No Cables". Click on a radio button to choose the mode you want to use. Choose Use FTS Cables when you want to monitor an external circuit or transmit data to an external device using the cable set. Choose this mode also when you have connected your circuit directly to the serial ports on your PC. Use Spy to "spy" on the data going in and out of an internal COM port or internal modem. Use Source DTE, No Cables to transmit data to an external or internal modem or other communications device without using the cable set. Choose COM ports To change your COM ports, click on the down arrow in the top port box and choose one of the COM ports listed. This list is generated from the registry of your computer, and so it will only list the COM ports that are available on your computer. Next, click on the down arrow of the second box and choose a second COM port to use. (If you chose Spy or Source DTE, No Cables, you will only be able to choose one COM port.) Note that if you have more than one serial card in your PC, you must choose two ports from the same card. In other words, if you have a serial card from manufacturer A and a card from manufacturer B, you must choose either the two ports on card A or the two ports on card B. You can t select one port from A and one from B. If you have only one COM port on your computer, choose a port in the first box, and choose Not Used for the second box. FTS will only allow you to choose options appropriate for single port mode once you get into the program. Changes in your COM ports will take effect when you click on the OK button, or the next time you start FTS if you changed them from outside the program. Choose Options Detect Now button - Click to determine what cables are connected to your computer. Notify If Auto Detect of Cables Fails - FTS will look for the cables each time data capture is started. Uncheck this box if you do not want FTS to look for the cables before starting capture. Info button - Click to see whether FIFOs are available on the selected COM ports and if they are enabled. Disable control signal interrupts - When checked, FTS will ignore all interrupts generated by the control signals. This is mostly a troubleshooting tool used when monitoring a circuit which has large numbers of rapid signal changes. 5-May FTS4BT-UM-001

23 Serial HCI Spy Spy lets you run FTS on a computer, and Spy on the data going in and out of a COM port or internal modem. This means that you can run both FTS and a communications application on the same computer, and use FTS to monitor the conversation between the application and another device. Since internal modems look like COM ports to the computer, FTS can monitor data passing through an internal modem as well as a regular COM port. There are some limitations on using Spy. FTS uses a custom version of the standard serial device driver in order to Spy on COM ports and internal modems. This means that FTS must be started before the communications application to ensure that FTS's driver is being used by both FTS and the application. As a corollary, the port you are monitoring must normally use the standard serial driver, and not a custom driver. To enter Spy, you must follow the steps below in the order given. For SPY: 6. Start FTS. FTS must be started before the application you are monitoring is started, or the application will not use the correct driver and FTS will not be able to monitor the port. 7. Start the application. Be sure to have the application use the same COM port as the one chosen for FTS. 8. Monitor data. 9. Close your application when finished. If you want to monitor another application, repeat steps Close FTS. For Serialtest Async + Spy: 1. Start FTS. FTS must be started before the application you are monitoring is started, or the application will not use the correct driver and FTS will not be able to monitor the port. 2. From the Options menu on the Control window, choose Hardware Settings. 3. Click on the radio button labeled Spy. 4. Select the COM port you want to monitor. 5. Exit the Hardware Settings window. 6. Start the application. Be sure to have the application use the same COM port as the one chosen for FTS. 7. Monitor data. 8. Close your application when finished. If you want to monitor another application, repeat steps Close FTS. It is important to follow the steps in the order given because this ensures that FTS's driver is the one being used by the application you are monitoring. Please note that FTS's driver is designed to behave like the standard serial driver when used by any other application. However, because it is not the standard serial driver, total compatibility cannot be guaranteed. See The FTS Driver for more information. The use of FIFO buffers may cause incorrectly sequenced data when in Spy. See FIFOs and Spy for more information. 5-May FTS4BT-UM-001

24 Serial HCI Source DTE, No Cables To switch to this mode 1. Open the Hardware Settings window by choosing Hardware Settings from the Options menu on the Control window. 2. Click the Source DTE, No Cables radio button. 3. Choose which COM port you want to communicate with. If you are testing a modem, choose the COM port that the modem is connected to. 4. Close the Hardware Settings window. 5. In FTS, click the I/O Settings icon and set the baud rate, parity and other parameters. 6. Click the Transmit icon to transmit data. 7. Use the Event Display to view the data you transmitted, plus the response from the device. Source DTE, No Cables lets you transmit DTE data without using the cable set, which means that you can transmit data directly to an internal device on your computer such as an internal modem or COM port. This is probably most useful for testing internal modems. Using the Transmit window, you can send commands directly to the internal modem, and use the Event Display window to see the modem's response. Ring Indicator control signal changes may not always be properly captured when using Source DTE, No Cables mode. See the note on Ring Indicator changes for more information. Detect Now button To access this function 1. Open the Hardware Settings window by choosing Hardware Settings from the Options menu on the Control window. 2. Click the Detect Now button to check that the cables are attached to the correct ports. FTS will respond with a message saying what cables it has found. To use the Detect Now button, you must have your cables connected to the computer (see Cable Configuration for help connecting your cables.) Advanced Hardware Settings functions Notify if Auto Cable Detection Fails To access this function 1. Open the Hardware Settings window by choosing Hardware Settings from the Options menu on the Control window. 2. Uncheck the Notify If Auto Detect Fails box. This feature should be left on unless there is a reason why FTS cannot detect the cables but can still capture data. FTS automatically checks to see if the cables are present when the software is first started, and every time data capture is initiated. If unchecked, FTS will still look for the cables when the program first starts up, but will not check when data capture is initiated. 5-May FTS4BT-UM-001

25 Serial HCI Disabling Control Signal Interrupts To reach this option Open the Hardware Settings window by choosing Hardware Settings from the Options menu on the Control window. Check the Disable Control Signal Interrupts box on the Hardware Settings window to disable processing of control signals. This option is used as a troubleshooting device on circuits where a control signal lead is toggling too quickly for FTS to keep up with. The result is that FTS spends all its time processing signal interrupts and no time updating the user interface, giving the appearance that the computer has frozen. Check this box only on advice of technical support. FTS always checks the state of the control signals when retrieving a data byte, so the Breakout Box will still show control signal changes provided data is being received. However, FTS will not capture control signal changes that occur independent of data bytes when interrupt processing is disabled. FTS polls for control signal changes whenever it is not in Use FTS Cables mode in order to catch Ring Indicator changes. This polling will still occur when interrupt processing is disabled, which means that FTS will capture control signal changes that occur independent of data, but may not capture them at the exact moment the change occurred. It also means that it is possible for FTS to miss a change if the signal changes state twice in a short period of time. Polling does not occur in Use FTS Cables mode. UART FIFO Settings To access this function 3. Open the Hardware Settings window by choosing Hardware Settings from the Options menu on the Control window. 4. Choose Use Optimal Settings for Serial Data Analysis. This is the default setting. Timestamping and control signal information are the most accurate with this setting. 5. If you are getting UART overruns, choose Use Windows Device Manager Settings. With this setting, timestamps will not be as accurate and some control signal changes may be lost, but it will help reduce or eliminate the loss of data from overruns. For more information, see Performance Notes. You may need to change the depth of the buffers in order to minimize problems with timestamping and signal changes while allowing for enough of a buffer to eliminate overruns. Note that changes to the buffer depth will remain after FTS exits. Set the FIFO buffers in Windows 2000/XP 1. Click on the Start button and choose Settings -> Control Panel. 2. Double-click on the System control panel icon. 3. Click on the Hardware tab, then click the Device Manager button (2nd button in the middle section). 4. Expand the Ports section, and double-click on the port you want to change. The Port Properties dialog box will open. 5. Click on the Port Settings tab, followed by the Advanced button at the bottom of the screen. 6. Use the slider bars to adjust the level of the transmit and receive buffers. If you are using FTS solely to monitor data and not transmit it, then you only need to change the level of the receive buffer. 7. Click OK on all windows to close the windows. 5-May FTS4BT-UM-001

26 Serial HCI Serial Port Info button To access this function 8. Open the Hardware Settings window by choosing Hardware Settings from the Options menu on the Control window. 9. Click the Info button to get information on the status of the FIFO buffers for the selected ports. FTS will provide information on whether the selected ports have FIFO buffers, and if they do, whether the buffers are enabled. This information is useful in Spy for determining whether the application being monitored is using the FIFO buffers on the port, which would affect how the data is displayed in Spy. See FIFOs and Spy for more information. Cable Configuration The cables included with FTS are: 1. a routing cable, which is a y-cable with a 25-pin connector on one end and two 9-pin connectors labeled DTE and DCE on the other ends, used to connect to the monitor or source head 2. a monitor head 3. a source head 4. two 25-pin female to 9-pin male adapters 5. one 25-pin male to 9-pin female adapter The 25-pin female adapters are used to connect the 9-pin routing cable connectors to 25-pin serial ports. One of the 25-pin female adapters can be used in conjunction with the 25-pin male adapter to connect the monitor head to a 9-pin circuit. All cables have their name molded into the plastic on one end. Dual Port Monitor Mode Cable Configuration 1. Attach the DTE connector of the routing cable to one COM port, and the DCE connector to the other COM port. Adapters are provided for attaching the 9-pin connectors to 25- pin serial ports. 2. On the end of the routing cable, attach the monitor head. The monitor head has the words "Monitor Head" molded into the plastic on the connector that hooks up to the routing cable. 5-May FTS4BT-UM-001

27 Serial HCI 3. Place the monitor head between the two devices you wish to monitor. If you have a y- cable connecting your two devices, you can also connect the monitor head to the third end of the y-cable. Adapters are provided for attaching the 25-pin monitor head to a 9- pin circuit. Note: the monitor head is a straight-through RS-232 cable. You can insert it between your two devices and they will be able to communicate with each other through the monitor head, whether or not FTS is running. Dual Port Source DCE Mode Cable Configuration 1. Attach the DTE connector of the routing cable to one COM port, and the DCE connector to the other COM port. Adapters are provided for attaching the 9-pin connectors to 25- pin serial ports. 2. On the end of the routing cable, attach the source head. The source head has the words "Source Head" molded into the plastic on the connector that hooks up to the routing cable. It also has the words "DTE" and "DCE" on the other end, with arrows pointing to each side of the source head. 3. Connect your DTE device to the side of the source head marked "DCE ". This arrow means that your DCE data will be coming out of this side of the source head, and so that is the side your DTE device needs to be connected to. An adapter is provided for attaching the 25-pin source head to a 9-pin circuit. 5-May FTS4BT-UM-001

28 Serial HCI Dual Port Source DTE Mode Cable Configuration 1. Attach the DTE connector of the routing cable to one COM port, and the DCE connector to the other COM port. Adapters are provided for attaching the 9-pin connectors to 25- pin serial ports. 2. On the end of the routing cable, attach the source head. The source head has the words "Source Head" molded into the plastic on the connector that hooks up to the routing cable. It also has the words "DTE" and "DCE" on the other end, with arrows pointing to each side of the source head. 3. Connect your DCE device to the side of the source head marked "DTE ". This arrow means that your DTE data will be coming out of this side of the source head, and so that is the side your DCE device needs to be connected to. An adapter is provided for attaching the 25-pin source head to a 9-pin circuit. Single Port Monitor DCE Mode Cable Configuration 1. Connect the DCE connector of the routing cable to your COM port. An adapter is provided for attaching the 9-pin connector to a 25-pin serial port. 2. On the end of the routing cable, attach the monitor head. 3. If you are monitoring one side of a circuit, you can connect the monitor head between your two devices. The monitor head is a straight-through RS-232 cable, so your 2 devices will still be able to communicate, but FTS will only monitor the DCE side. 5-May FTS4BT-UM-001

29 Serial HCI 4. If you are monitoring a DCE device only, connect the DCE device to either side of the monitor head. It does not matter which side you choose. An adapter is provided for attaching the 25-pin monitor head to a 9-pin circuit. Note: If you are monitoring a circuit, you can switch to monitoring DTE by going into the Set I/O Parameters screen and switching to Monitor DTE mode. Then disconnect the DCE head of the routing cable from your COM port and connect the DTE head, and you will see DTE data. You will not need to do anything with the monitor head cable. Single Port Monitor DTE Mode Cable Configuration 1. Connect the DTE connector of the routing cable to your COM port. An adapter is provided for attaching the 9-pin connector to a 25-pin serial port. 2. On the end of the routing cable, attach the monitor head. 3. If you are monitoring one side of a circuit, you can connect the monitor head between your two devices. The monitor head is a straight-through RS-232 cable, so your 2 devices will still be able to communicate, but FTS will only monitor the DTE side. 4. If you are monitoring a DTE device only, connect the DTE device to either side of the monitor head. It does not matter which side you choose. An adapter is provided for attaching the 25-pin monitor head to a 9-pin circuit. Note: If you are monitoring a circuit, you can switch to monitoring DCE by going to the I/O Settings window and switching to Monitor DCE mode. Then disconnect the DTE head of the routing cable from your COM port and connect the DCE head, and you will see DCE data. You will not need to do anything with the monitor head cable. 5-May FTS4BT-UM-001

30 Serial HCI Single Port Source DCE Mode Cable Configuration 1. Connect the DTE connector of the routing cable to your COM port. Even though you are in source DCE mode, you will need to use the DTE connector on the routing cable. An adapter is provided for attaching the 9-pin connector to a 25-pin serial port. 2. On the end of the routing cable, attach the source head. 3. Connect your DTE device to the side of the source head marked "DCE ". This arrow means that your DCE data will be coming out of this side of the source head, and so that is the side your DTE device needs to be connected to. An adapter is provided for attaching the 25-pin source head to a 9-pin circuit. Note: You will be able to send data to your DTE device and set the DCE control signals, but FTS will not be able to see any responses from your DTE device. Single Port Source DTE Mode Cable Configuration 1. Connect the DTE connector of the routing cable to your COM port. An adapter is provided for attaching the 9-pin connector to a 25-pin serial port. 2. On the end of the routing cable, attach the source head. 5-May FTS4BT-UM-001

31 Serial HCI 3. Connect your DCE device to the side of the source head marked "DTE ". This arrow means that your DTE data will be coming out of this side of the source head, and so that is the side your DCE device needs to be connected to. An adapter is provided for attaching the 25-pin source head to a 9-pin circuit. Note: You will be able to send data to your DCE device and set the DTE control signals, but FTS will not be able to see any responses from your DCE device. RS-232 Pin-outs 25-pin connector Pin Name Abbreviation 1 Frame Ground FG 2 Transmit Data TxD 3 Receive Data RxD 4 Request To Send RTS 5 Clear to Send CTS 6 Data Set Ready DSR 7 Signal Ground GND 8 Carrier Detect CD or DCD 20 Data Terminal Ready DTR 22 Ring Indicator RI 9-pin connector Pin Name Abbreviation 1 Carrier Detect CD or DCD 2 Receive Data RxD 3 Transmit Data TxD 4 Data Terminal Ready DTR 5 Signal Ground GND 6 Data Set Ready DSR 7 Request To Send RTS 8 Clear to Send CTS 9 Ring Indicator RI 5-May FTS4BT-UM-001

32 Serial HCI I/O Settings I/O Settings Window To open this window Click the I/O Settings icon on the Control window. The I/O Settings window allows you to configure FTS for both monitor and source operating modes. FTS requires information on baud, parity, word length, and number of stop bits in order to operate properly. If you are capturing framed data, FTS needs to know what protocols are present on your circuit to decode them correctly. Configuration files store I/O settings. If a configuration file is open, it will be listed at the top of the I/O Settings window. If no configuration file is being used, FTS will revert to its default settings. You can return to the default settings at any time by clicking on the Revert to Factory Defaults icon on the I/O Settings toolbar. There are two rows of settings, one for the DTE device, and one for the DCE device. Depending on your operating mode, you will need to configure one or both sides. FTS will only allow you to change the settings relevant to your operating mode. All other settings will be grayed out. Some settings apply only to specific modes. For example, Flow Control settings only apply in source mode. Operating Mode - Choosing to Monitor or Source Monitor Mode If you specified two COM ports in the Hardware Settings window, choose Monitor Both from the pulldown list. This means that FTS will monitor both sides of your circuit. To do this, you must use the routing cable and the monitor head. You can also choose to monitor only one side of the circuit by choosing Monitor DTE or Monitor DCE. If you specified one COM port in the Hardware Settings window, you will be able to monitor either the DTE or the DCE side of a circuit, but not both. Choose Monitor DTE or Monitor DCE from the pulldown list to specify which side you want to monitor. Source Mode FTS can act as either a DTE or a DCE device. Choose Source DTE or Source DCE from the pulldown menu to specify which type of device you want to emulate. If you have two COM ports, you will be able to send data to another device, change the state of the appropriate control signals, and see data and control signal states from the other device. If you have one COM port, you will be able to send data to another device and see data sent by the device. If you are emulating a DTE device, you will be able to change DTR and RTS, and you will be able to see changes made by your DCE device on DSR and CTS, but you will not be able to see changes on CD and RI. If you are emulating a DCE device, you will be able to change DSR and CTS, but not CD and RI, and you will be able to see DTR and RTS signal changes coming from your DTE device. You must use the routing cable and the source head when in source mode. The device under test must be connected to the correct side of the source head. See Cable Configuration for assistance on setting up the cables. Setting Baud, Parity, Word Length and Stop Bits To change the baud, parity, word length or number of stop bits, click on the down arrow next to the setting box and choose an option from the list. For baud, you can either choose a listed rate or enter a rate. 5-May FTS4BT-UM-001

33 Serial HCI If you have chosen to monitor both DTE and DCE, you will have to set the configuration for both sides. To make things easier, you can set the configuration for the DTE side, and click on the DTE-to-DCE icon. This will change the settings on the DCE side to match those of the DTE. If you have chosen to monitor only DTE or only DCE, or if you have chosen to be a source, you will only need to set the configuration for the appropriate side. The other side will be grayed out and you will not be able to change those settings. Defining Your Own Baud To define your own rate, highlight the text in the baud field and type in a new rate. Not all baud rates are supported. Supported rates vary depending on the rates supported by the serial port. If you choose a baud that is not supported, FTS will display a box asking you to choose between the two nearest supported rates. You must choose a rate in order to continue working. Bit Order Choose LSB (least significant bit) first or MSB (most significant bit) first. LSB first is normal, while MSB first is considered "reversed" from normal. This option reverses the order of the bits within each byte. All options on the I/O Settings window are valid when in MSB mode except for parity. The parity must be None when using MSB bit order. Bit reversal occurs both when monitoring data and when transmitting data. For example, if FTS is monitoring data in LSB mode and sees on the circuit, it will display this as hex 01. In MSB mode, FTS will reverse the order of the bits as they come in and display this byte as , or hex $80. When transmitting data, FTS reverses the bits before they are sent out over the circuit. For example, if you are transmitting data in LSB mode and you enter the pattern $01, FTS will send out If you are transmitting in MSB mode and you enter the pattern $01, FTS will bit reverse this and transmit FTS remembers what bit order was used to capture the data with. If you create a capture file with the bit order set to MSB, the data will always be displayed in that form. If you are monitoring HDLC or SDLC data and the bit order is set to MSB, it is probable that the CRC's will not be calculated correctly. Flow Control Flow control (sometimes called "handshaking") is only available in source mode. There are four flow control options: None, RTS/CTS, DTR/DSR or Xon/Xoff. The default option is None. If you choose None, FTS will not employ any flow control techniques. Hardware flow control can be accomplished using either the RTS /CTS pair or DTR /DSR pair. Choose which pair you would like FTS to use. To use software flow control, choose the Xon/Xoff option. FTS will use the Xon/Xoff characters given in the boxes below the flow control option. These numbers must be specified in hexadecimal (hex) characters. By default, FTS uses hex 11 for Xon and hex 13 for Xoff. Names Following is a list of all the labels used in FTS to identify errors, control signals, and sides. To change the labels, click the Names button on the I/O Settings window, or choose Names from the Options menu on the Control window. Changes to the labels will be used throughout the program. 5-May FTS4BT-UM-001

34 Serial HCI To change a label, click on the name given in the current column, and then click again to modify the name (a slow double-click.) To restore the default values, click the Defaults button. Sides The Sides section allows you to give each side on a network more descriptive names. This is useful on network with more than one side, such as an asynchronous serial circuit. Errors This section allows you to change the error labels. The errors listed will be appropriate for the type of circuit/network you are monitoring. Signals Signals refers to the six control signals used in RS-232 data communications. Labels for the six control signals monitored by FTS are given below. Label Control Signal RTS Request to Send CTS Clear to Send DSR Data Set Ready DTR Data Terminal Ready CD Carrier Detect RI Ring Indicator If you are used to different abbreviations for the same signals, you can change them in this section. For example, if you normally refer to Carrier Detect as DCD, highlight CD and type in DCD. Custom Protocol Stack button To change the protocol stack, click on the Custom Protocol Stack button to start the Protocol Stack Wizard. If you are capturing framed data but did not select a protocol stack before capturing, your data will need to be framed. Select a protocol stack, and then go to the Control window and choose Reframe from the File menu. See Reframe Function for more information. Saving Configurations Saving A Configuration to File 1. Set up your configuration on the I/O Settings window. 2. If a configuration is already open and you have altered it, go to the File menu and choose Save As; otherwise, click on the Save Settings icon. 3. In the File name box, type a name for your configuration. You do not need to add an extension. FTS will add a.cfg extension automatically. 4. By default, FTS will save the configuration in the My Configurations directory under C:\\Program Files\\Frontline Test System II\\[Product Name]. Choose a different directory to save the configuration elsewhere. (Click here to see how to change the default location for configurations.) 5. Click on Save. If you make a new configuration and do not save it, FTS will ask you if you want to save your configuration when you exit the program. If you want to save your configuration, choose Save 5-May FTS4BT-UM-001

35 Serial HCI and the Save File dialog box will appear. If you do not want to save your configuration, choose Cancel. Opening a Saved Configuration 1. Click on the Open Configuration icon, or choose Open Configuration from the File menu. If other configurations have been used recently, a menu listing the last four configurations used will be displayed. 2. Select a recent configuration file, or choose Open to load an unlisted configuration. 3. If you have saved your configurations in the default directory, they will be in listed in the window. Choose a different directory if your configurations are saved elsewhere. 4. Select the configuration you want to use, and click on Open. Configurations are saved with a.cfg extension, and are located in the C:\\Program Files\\Frontline Test System II\\[Product Name]\\My Configurations directory by default. The name of the open configuration file is displayed at the top of the Set I/O Configuration window. If no configuration file is open, "Untitled" will be displayed. 5-May FTS4BT-UM-001

36 Selecting a Protocol Stack Selecting a Protocol Stack Protocol Stack Wizard The Protocol Stack wizard is where you define the protocol stack you want FTS to use when decoding frames. To start the wizard, choose Protocol Stack from the Options menu on the Control window or click the Protocol Stack icon on the Frame Display. Select a protocol stack from the list, and click Finish. Most stacks are pre-defined here. If you have special requirements and need to set up a custom stack, choose Build Your Own from the top of the list, and click Next. If you have selected a custom stack (i.e. one that was defined by a user and not included with FTS), the Remove Selected Item From List button will become active. Click the Remove button to remove the stack from the list. You cannot remove stacks provided with FTS. If you remove a custom stack, you will need to define it again in order to get it back. If you are changing the protocol stack for a capture file, you may need to reframe. See Reframing for more information. You cannot select a stack or change an existing one for a capture file loaded into the Capture File Viewer. (The Capture File Viewer is used only for viewing capture files and cannot capture data.) Protocol Stack changes can only be made from a live session. Note for BCSP: If you are using the BCSP protocol stack, you must connect FTS to the circuit such that the data on the DTE line comes from the host, and data on the DCE line comes from the controller. Information Screen The second screen of the Protocol Stack Wizard gives information to help you decide if you need to define a custom stack or if a pre-defined stack has what you need. Create a Custom Stack There are two steps to creating a stack: defining the protocols in the stack and choosing whether to have FTS automatically determine higher layer protocols (called auto-traversal). There is a third optional step of saving the stack so that it appears in the Protocol Stack List on the first screen of the Protocol Stack Wizard. Defining a custom stack means that FTS will use the stack for every frame. Frames that do not conform to the stack will be decoded incorrectly. 1. Select Protocols Select a protocol from the list on the left. Click the right arrow button to move it to the Protocol Decode Stack box on the right, or double-click the protocol to move it to the right. To remove a protocol from the stack, double-click it or select it and click the left arrow button. If you need to change the order of the protocols in the stack, select the protocol you want to move, and click on the Move Up and Move Down buttons until the protocol is in the correct position. The lowest layer protocol is at the top of the list, with higher layer protocols listed underneath. 2. Auto-traversal (Have FTS Determine Higher Layers) If you need to define just a few layers of the protocol stack, and the remaining layers can be determined based on the lower layers, click the All additional stack layers can be determined automatically button. If your protocol stack is complete and there are no additional layers, click the There are no additional stack layers button. If you select this option, FTS will use the stack you defined for every frame. Frames that do use this stack will be decoded incorrectly. 5-May FTS4BT-UM-001

37 Selecting a Protocol Stack 3. Save the Stack To save your stack click the Add To Predefined List button, give the stack a name, and click Add. In the future, the stack will appear in the Protocol Stack List on the first screen of the Protocol Stack wizard. To remove the stack, select it in the first screen and click Remove Selected Item From List. Where To Connect FTS For BCSP For BCSP, it is important that the data from the host be on the DTE side and data from the controller be on the DCE side in order for the decode to be correct. This is true because the only way to know if a frame contains a command or an event is to know what side it came from. There isn't anything in the data to indicate whether the frame is carrying a command or an event otherwise. If you have a custom protocol and need help connecting FTS to the right location, see Generic Channel Dependent Decodes Setup for diagrams. BCSP (BlueCore Serial Protocol) Host data must be on the DTE (TxD) side. Controller data must be on the DCE (RxD) side. How FTS4BT Auto-traverses the Bluetooth Stack In the course of doing service discovery, devices ask for and receive a Protocol Descriptor List defining which protocol stacks the device supports. It also includes information on which PSM to use in L2CAP, or the channel number for RFCOMM, or the port number for TCP or UDP. The description below talks about how FTS auto-traverses from L2CAP using a dynamically assigned PSM, but the principle is the same for RFCOMM channel numbers and TCP/UDP port numbers. FTS looks for SDP Service Attribute Responses or Service Search Attribute Responses carrying protocol descriptor lists. If FTS sees L2CAP listed with a PSM, it stores the PSM and the UUID for the next protocol in the list. After the SDP session is over, FTS looks at the PSM in the L2CAP Connect frames that follow. If the PSM matches one FTS has stored, FTS stores the source channel ID and destination channel ID, and associates those channel IDs with the PSM and UUID for the next protocol. Thereafter, when FTS sees L2CAP frames using those channel IDs, it can look them up in its table and know what the next protocol is. In order for FTS to be able to auto-traverse using a dynamically assigned PSM, it has to have seen the SDP session giving the Protocol Descriptor Lists, and the subsequent L2CAP connection using the PSM and identifying the source and channel IDs. If FTS misses any of this process, it will not be able to auto-traverse. It will stop decoding at the L2CAP layer. For L2CAP frames carrying a known PSM (0x0001 for SDP, for example, or 0x0003 for RFCOMM), FTS looks for Connect frames and stores the PSM along with the associated source and destination channel IDs. In this case FTS does not need to see the SDP process, but does need to see the L2CAP connection process, giving the source and destination channel IDs. Reframe Function If you need to change the protocol stack used to interpret a capture file and the framing is different in the new stack, you will need to reframe in order for the protocol decode to be correct. You can also use the Reframe function to frame unframed data. The original capture file is not altered during this process. 5-May FTS4BT-UM-001

38 Selecting a Protocol Stack Reframing can only be done from a live session. You cannot reframe from the Capture File Viewer (accessed by selecting Capture File Viewer or Load Capture File to start the software and used only for viewing capture files). 1. Load your capture file. To do this, choose Open from the File menu on the Control window, and select the file to load. 2. Select the protocol stack. To do this, choose Protocol Stack from the Options menu on the Control window, select the desired stack and click Finish. 3. If you selected a protocol stack that includes a frame recognizer different from the one used to capture your data, the Protocol Stack Wizard will ask you if you want to reframe your data. Choose Yes. 4. FTS will add frame markers to your data, put the framed data into a new file, and open the new file. The original capture file will not be altered. To manually reframe your data, load your capture file, select a protocol stack, and then select Reframe from the File menu on the Control window. Reframe will only be available if the frame recognizer used to capture the data is different from the current frame recognizer. See Unframe Function for instructions on removing framing from data. Unframe Function This function will remove start-of-frame and end-of-frame markers from your data. The original capture file is not altered during this process. Unframing can only be done from a live session. You cannot unframe from the Capture File Viewer (accessed by selecting Capture File Viewer or Load Capture File to start the software and used only for viewing capture files). 1. Load your capture file. To do this, choose Open from the File menu on the Control window, and select the file to load. 2. Remove the protocol stack. To do this, choose Protocol Stack from the Options menu on the Control window, select None from the list, and click Finish. 3. The Protocol Stack Wizard will ask you if you want to reframe your data and put it into a new file. Choose Yes. 4. FTS will remove the frame markers from your data, put the unframed data into a new file, and open the new file. The original capture file will not be altered. To manually unframe your data, select Unframe from the File menu on the Control window. Unframe will only be available if a protocol stack was used to capture the data and there is currently no protocol stack selected. See Reframe Function for instructions on framing unframed data. Decoder Parameters Some protocol decoders have user-settable parameters. These are protocols where some information cannot be discovered by looking at the data and must be entered by the user in order for the decoder to correctly decode the data. For example, such information might be a field where the length is either 3 or 4 bytes, and which length is being used is a system option. If you have decoders loaded which require decoder parameters, a window with one tab for every decoder that requires parameters will appear the first time the decoder is loaded. For help on setting the parameters, click the Help button on each tab to get help information specific to that decoder. If you need to change the parameters later, choose Set Decoder Parameters from the Options menu on the Control, Frame Display or Protocol Navigator windows. 5-May FTS4BT-UM-001

39 Selecting a Protocol Stack If you do not have decoders loaded that require parameters, the menu item will not appear and you don't need to worry about this feature. Providing Context For Decoding When Frame Information Is Missing There may be times when you will need to provide information to FTS because the context for decoding a frame is missing. For example, if FTS captured a response frame, but didn't capture the command frame that says what command is being responded to, the decode for the response may be incomplete. FTS provides a way for you to tell FTS what the context is for any frame, provided that the particular decoder supports it. (The decoder writer has to include support for this feature in the decoder, so not all decoders support it. Note that not all decoders require this feature.) If there is a decoder that supports user-provided context, three items will be active on the Options menu of the Control, Frame Display and Protocol Navigator windows. (These items will not be present if no decoder is loaded that supports this feature.) These items are Set Decoder Parameters, Automatically Request Missing Decoding Information, and Show/Modify Decoding Rules. Preset Decoder Parameters is used to provide required information to decoders that is not context dependent but instead tends to be system options for the protocol. Choose Set Decoder Parameters in order to provide initial context to FTS for a decoder. A dialog will appear that shows the data for which you can provide information. If you need to change this information for a particular frame, right-click on the frame in the Frame Display window and choose Provide <context name>. Alternatively, you can choose Show/Modify Decoding Rules from the Options menu. This will bring up a dialog showing all the places where context data was overridden. If you know that information will be missing but you can't provide it and you don't want to see dialogs asking for it, uncheck Automatically Request Missing Decoding Information. This is a checkable item and when unchecked, FTS won't bother you with dialogs asking for frame information that you don't have. In this situation, FTS will decode each frame until it can go no further and then simply stop decoding. Predefined Stacks Adding a New Predefined Stack From the Control window Options menu, choose Protocol Stack. Choose Build Your Own from the list, and click Next. Define your protocol stack, and click the Add to Predefined List button. Give the stack a name, and click Add. In the future, the stack will appear with the system provided stacks in the Protocol Stack List on the first screen of the wizard. To remove a custom stack, open the Protocol Stack window, select the stack from the list, and click Remove Selected Item From List. If you remove the stack, you will need to recreate it if you need to use it again. 5-May FTS4BT-UM-001

40 Capturing Data Capturing Data Control Window Information in FTS is displayed in multiple windows, with each window showing a different type of information. The Control window is used to provide access to each window as well as give a brief overview of the data in the capture file. Each icon on the toolbar represents a different data analysis function. Because the Control window can get lost behind other windows, every window has a Home icon that brings the Control window back to the front. Just click on the Home icon to restore the Control window. The title bar of the Control window shows what hardware FTS is using. The status bars (below the toolbar) show the current settings from the I/O Settings window, the state of the analyzer (Not Active, Paused, Running, etc.), how full the capture buffer or file is, current utilization and total number of events seen. FTS continuously monitors the circuit and gathers statistics on the data on the circuit. This means that if there is data on the circuit, the utilization counters will be active, even if not capturing data. The Control Window Toolbar Available options will be in color, while unavailable options will be grayed out. All toolbar buttons have corresponding menu items, most of which can be found in the Window menu. The exceptions are Start Capture to Buffer, Start Capture to Disk, Pause/Resume, Clear, and Close Capture File, which are found in the Live menu. I/O Settings - Use this window to tell FTS the characteristics of the circuit you are monitoring or sourcing. Characteristics include baud, word length, parity, and stop bits. Capture to Buffer - Begins data capture to a capture buffer in memory. Capture to Disk - Begins data capture to a file on disk. Pause/Resume - Available after data capture has started. Click once to pause data capture. Data can be reviewed and saved, but no new data will be captured. Click this button again to resume capture. Clear Buffer - Stops data capture to buffer and clears the capture buffer. Close Capture File - Closes a capture file and stops data capture to disk. Statistics - Keeps track of useful statistics such as total number of characters, average number of characters/second, and number of errors by type. FTS always gathers statistics, even when it is not actively capturing data, making this screen a useful monitoring tool. Statistics are kept on the entire session (the time since FTS was started) and for each set of events in the capture buffer or file. Breakout Box - Functions as a passive breakout box, showing control signal changes for RTS, CTS, DTR, DSR, CD and RI in real-time. 5-May FTS4BT-UM-001

41 Capturing Data Event Display - The main data viewing window. View data live or in review mode. Search for errors or data patterns. Data can be viewed in hex and/or character display format. Other events such as signal changes are also shown. Frame Display - Shows summary information and a detailed decode for each frame. Focus Protocol Navigator - Brings up the Protocol Navigator window, with the currently selected frame highlighted. Signal Display - Shows the state of the control signals over time, beginning with the first event in the buffer or file. You can zoom in to view control signal states for just one event, or zoom out to view changes for the entire buffer. Filters - Define and apply capture and display filters. Capture filters filter out data while it is being captured, putting only data that matches the filter in the capture buffer. Display filters filter out data in the capture buffer. All data is captured, but only the data matching the filter is displayed in the Frame Display window. Filtering can only be done with framed data. Transmit - Transmit data and set control signals. Available only in source mode. Cascade Windows - Cascade all windows (brings them home), with the first window being placed directly below the Control window. Capturing Data to Buffer 1. Click the Capture to Buffer icon to begin capturing to buffer. This icon is located on the Control, Event Display, Frame Display and Transmit windows. 2. Watch the status bar on the Control window to find out how full the buffer is. When the buffer is full, it will begin to wrap, throwing out the oldest data to make room for the new. 3. Click the Pause icon to temporarily stop data capture. Click the Pause icon again to resume capture. 4. Click the Clear Capture Buffer icon to stop capture. 5. FTS will ask if you want to save your data first. If you do, click Save First. FTS will prompt you for a file name. If you don't want to see this prompt again, click the Don't Show This Warning Again box. FTS will not show the warning again during this session of FTS. FTS does not remember the state of the warning from session to session as a precaution. You will need to check the box again the next time FTS is started. To change the size of the capture buffer, choose System Settings from the Options menu on the Control window. To prevent the buffer from wrapping, go to the System Settings. Capturing Data to Disk 1. Click the Capture to Disk icon to begin capturing to a file on disk. This icon is located on the Control, Event Display, Frame Display and Transmit windows. 5-May FTS4BT-UM-001

42 Capturing Data 2. Choose a name for your capture file. Files are placed in My Capture Files by default and have a.cfa extension. Choose Directories from the Options menu on the Control window to change the default file location. 3. Watch the status bar on the Control window to find out how full the file is. When the file is full, it will begin to wrap, throwing out the oldest data to make room for the new. 4. Click the Pause icon to temporarily stop data capture. Click the Pause icon again to resume capture. 5. Click the Close Capture File icon to stop capture and close the file. To change the size of the capture file, choose System Settings from the Options menu on the Control window. 5-May FTS4BT-UM-001

43 Statistics Statistics Statistics Window To open the Statistics window, click the Statistics icon on the Control window toolbar, or choose Statistics from the Window menu on the Control window. The Statistics window supplies basic information about the data on the network. When reviewing a capture file, the Statistics window shows a summary of the data in the file. FTS monitors the network and collects statistics all the time, even when data is not actively being captured. Click the Freeze icon to stop the window from updating. Click the Freeze icon again to resume updating. FTS will continue to monitor network traffic while the Statistics window is frozen, so you may see the numbers jump right after updating has resumed, reflecting all the statistics that were gathered while the window was frozen. Session, Resetable and Buffer Tabs Information about all data collected since FTS was started is shown in the Session tab. The Session tab cannot be reset; in this sense, it is like the odometer on a car. The odometer on a car shows you all the miles driven since the car was built, and the Session tab shows you all the data collected since FTS was started. If you think of the Session tab as the odometer, then the Resetable tab is the trip odometer. It can be reset, and allows you to record statistics for a new "trip." In this way you can effectively start a new session without having to restart FTS. The Buffer tab shows information on the data that is currently in the capture buffer. The tab will reset when you clear the buffer. If the capture buffer becomes full, FTS will begin to throw out the oldest data and put new data in its place. This is called "wrapping." If the buffer wraps, the count for the total number of events will remain roughly the same, since the buffer will remain full until it is cleared and therefore always contains approximately the same number of events. Occasionally some of the statistics will read n/a, for Not Available. This happens for various reasons. For example, many of the items on the Buffer tab will become n/a if the buffer should become full and wrap. When this happens, FTS can no longer provide accurate statistics for the data in the buffer, because some of the data that the statistics are based on has been lost. Copying Statistics To The Clipboard To copy the information from an individual table to the clipboard (where it can be pasted into any application), choose the name of the table from the Edit menu. To copy the contents of all the tables, choose Copy All to Clipboard. Changing Frame Size Ranges FTS tracks the length of each frame it receives in the Frame Sizes table on the Statistics window. You can change both the minimum and maximum values for each range and the total number of ranges. To change the frame size ranges, click the Statistics icon and choose Set Frame Size Ranges from the Options menu. on the Control window toolbar, In the Frame Size Range window, click to place the cursor in the High column and enter a new value. FTS will automatically adjust the Low values. To add a new range, place the cursor in the empty last cell in the High column and type in a new value. 5-May FTS4BT-UM-001

44 Analyzing Byte-Level Data If you want to know how many frames are of an exact size, make both the low and high value equal to the size. For example, if you want to know how many 64 byte frames there are on your network, make the High value 64, and the previous High value end at 63. This will have the effect of creating a row labeled 64-64, and it will count the number of frames that are exactly 64 bytes in length. You can also type a description of each range (for example, "short" for frames that are too short or "error" for frames that are too large). Place the cursor in the Description column and type in a description. The Preview column shows what the range label on the Frame Sizes table in the Statistics window will look like. Click OK when you are finished. FTS will remember the new ranges from session to session. To reset to the default ranges, click Reset. Information on the Tables Statistics Tables The information on the Statistics window is organized into tables. Fields marked "n/a" are fields for which there is currently no data. This can happen for a variety of reasons. On the buffer tab, fields are n/a when there is no data in the buffer (i.e. no capturing is being done). On the Errors table, some fields may be n/a depending on the statistics supported by your Ethernet card. Data Table Frames total number of frames, if applicable, with a breakdown by device. Octets total number of octets, with a breakdown by device. Events total number of events captured. Events include data bytes, start and end-offrame markers, etc. For a description of all events and their symbols, see the List of Event Symbols. Errors Table To graph, click the bar graph icon on the Errors table header. Overrun number of overrun errors broken down by DTE and DCE device. See Performance Notes for more on overrun errors. Parity number of parity errors broken down by DTE and DCE device. If you have a large number of parity errors, check your I/O Settings for accuracy. Framing number of framing errors broken down by DTE and DCE device. If you have a large number of framing errors, check your I/O Settings for accuracy. Frame Sizes Table To graph, click the bar graph icon on the Frame Sizes table header. Displays the number of frames in each size range, and the average frame size at the bottom. To change the ranges used, go to the Options menu and choose Set Frame Size Ranges. Utilization Table Current current number of bits per second divided by the maximum speed of the network, expressed as a percentage. Average average number of bits per second divided by the maximum speed of the network, expressed as a percentage. 5-May FTS4BT-UM-001

45 Statistics Peak highest utilization. Chars Per Second Table Baud current baud Current current number of characters per second. Average average number of characters per second. Peak highest number of characters per second. Frames Per Second Table Current current number of frames per second. Average average number of frames per second. Peak highest number of frames per second. Octets Per Second Table Speed maximum speed of the network expressed in megabits Current current number of octets per second. Average average number of octets per second. Peak highest number of octets per second. Buffer Information Table Driver Buffer Overflow number of bytes lost due to driver buffer overflow. Buffer overflow occurs when data is coming in too fast for FTS to process it. This error does not indicate a problem on the circuit. See Performance Notes for more on buffer overflow. Graphs Statistics Graphs To open any graph window Click on the picture of a graph on the table header, or choose the graph name from the Graph menu on the Statistics window. To open the Statistics window, click the Statistics icon on the Control window toolbar. The Frame Sizes Graph window has Session, Resetable and Buffer tabs that correspond to the tabs on the Statistics window. Each tab shows the data that corresponds to the appropriate tab on the Statistics window. The Frame Sizes Graph window displays the number of frames of each length in either a pie chart or bar graph format. Click the Pie icon to display a pie chart, and click the Bar icon to display a bar graph. For networks with more than one side, FTS will display one graph for each side. To view the aggregate of all sides, click the Aggregate icon. Viewing Percentages or Values Click the Percentages icon icon appear pressed down. to view data expressed as a percentage. This will make the 5-May FTS4BT-UM-001

46 Analyzing Byte-Level Data Click the Percentages icon again to view the actual number of items of each type. Click the Show Data Grid icon to view both the number and percentage of the total for each item. FTS will place a grid in the legend. Printing Graphs Click the Print icon Graph Options To open this window to print the graph. FTS will print exactly what's shown on the window. Click the Statistics icon on the Control window. On the Statistics window, click the Options icon. The graphs window refreshes once every second. To change the refresh rate, enter a new refresh rate in milliseconds in the Window Refresh Rate box. 5-May FTS4BT-UM-001

47 Analyzing Byte-Level Data Analyzing Byte-level Data Event Display To open this window Click the Event Display icon on the Control window toolbar. The Event Display window provides detailed information about every captured event. Events include data bytes, data related information such as start-of-frame and end-of-frame flags, and FTS information, such as Data Capture Was Paused. Data bytes are displayed in hex on the left side of the window, with the corresponding ASCII character on the right. Click on an event to find out more about it. The three status lines at the bottom of the window will update with information such as the time the event occurred (for data bytes, the time the byte was captured), the value of the byte in Hex, Decimal, Octal, and Binary, any errors associated with the byte, and more. Events with errors are shown in red to make them easy to spot. When capturing data live, FTS continually updates the Event Display as data is captured. Click the Freeze icon on the toolbar to prevent the display from updating. While frozen, you can review your data, run searches, determine delta time intervals between bytes, and check CRCs. To resume updating the display, click the Freeze icon again. You can have more than one Event Display open at a time. Click the Duplicate View icon to create a second, independent Event Display window. You can freeze one copy of the Event Display and analyze your data, while the second Event Display updates as new data is captured. The Event Display Toolbar Home Brings the Control window to the front. Open File - Opens a capture file. Capture to Buffer - Begins data capture to the buffer only. Capture to Disk - Begins data capture to disk. Pause/Resume - Available after data capture has started. Click once to pause data capture. Data can be reviewed and saved, but no new data will be captured. Click again to Resume capture. Clear Buffer - Clears the capture buffer and stops data capture to buffer. Close Capture File - Closes a capture file and stops data capture to disk. Freeze Display - Freezes the window so you can review a portion of data. Data capture will continue in the background. Click on the button again to unfreeze the window. When you do this, the screen will quickly fill in the data captured since the screen freeze and jump you down to view incoming data again. 5-May FTS4BT-UM-001

48 Analyzing Byte-Level Data Duplicate View - Creates a second Event Display window identical to the first. Frame Display - (framed data only) Brings up a Frame Display, with the frame of the currently selected bytes highlighted. Focus Protocol Navigator - (framed data only) Brings up the Protocol Navigator window, with the currently selected frame highlighted. Show Only Data - (framed data only) Brings up a Frame Display showing just the data in the frame (also called the payload). Display Capture Notes - Brings up the Capture Notes window where you can view or add notes to the capture file. Add/Modify Bookmark - Add a new or modify an existing bookmark. Display Bookmarks - Shows all bookmarks and lets you move between bookmarks. Save - Save the currently selected bytes or the entire buffer to file. Find - Search for errors, string patterns, special events and more. Go To - Opens the Go To dialog, where you can specify which event number to go to. CRC - Change the algorithm and seed value used to calculate CRCs. To calculate a CRC, select a byte range, and the CRC will appear in the status lines at the bottom of the Event Display. Mixed Sides - By default, FTS shows data with the DTE side above the DCE side. This is called DTE over DCE format. DTE data has a white background and DCE data has a gray background. FTS can also display data in mixed side format. In this format, FTS does not separate DTE data from DCE data but shows all data on the same line as it comes in. DTE data is still shown with a white background and DCE data with a gray background so that you can distinguish between the two. The benefit of using this format is that more data will fit onto one screen. Character Only - FTS shows both the number (hex, binary, etc.) data and the character (ASCII, EBCDIC or BAUDOT) data on the same screen. If you do not wish to see the hex characters, click on the Character Only button. Click again to go back to both number and character mode. Number Only - Controls whether FTS displays data in both character and number format, or just number format. Click once to show only numeric values, and again to show both character and numeric values. All Events - Controls whether FTS shows all events in the window, or only data bytes. Events include control signal changes and framing information. Font Size - Brings up the Font Dialog box, allowing you to change the font size. 5-May FTS4BT-UM-001

49 Analyzing Byte-Level Data Timestamping Options Brings up the timestamping options window which has options for customizing the display and capture of timestamps. Switching Between Live Update and Review Mode The Event Display and Frame Display windows can either update to display new data as it is captured, or be frozen to allow data to be analyzed. By default, the Event Display continually updates with new data, and the Frame Display is frozen. Click the Freeze icon to freeze the display and prevent it from scrolling. Click the Freeze icon again to resume live update. FTS will continue to capture data in the background while the display is frozen. When live update is resumed, the display will update with the latest data. You can have more than one Event Display or Frame Display window open at a time. The Freeze/Resume function is independent on each window. This means that you can have two Event Display windows open simultaneously, and one window can be frozen while the other continues to update. Click the Duplicate View icon Display windows. Opening Multiple Event Display Windows to open additional Event or Frame Click the Duplicate View icon from the Event Display toolbar to open a second Event Display window. You can open as many Event Display windows as you like. Each Event Display is independent of the others and can show different data, use a different radix or character set, or be frozen or live. The Event Display windows are numbered in the title bar. If you have multiple Event Displays open, click on the Event Display icon on the Control window toolbar to show a list of all the Event Displays currently open. Select a window from the list to bring it to the front. Synchronization Between the Event and Frame Displays Calculating Delta Times and Data Rates 1. Click on the Event Display icon on the Control window to open the Event Display window. 2. Use the mouse to select the data you want to calculate a delta time and rate for. 3. The Event Display window will show the delta time and the data rate in the status lines at the bottom of the window. Calculating CRCs 1. Open the Event Display window. 2. Click and drag to select the data you want to generate a CRC for. 3. Click on the CRC icon. 4. In the CRC dialog box, click on the down arrow to show the list of choices for CRC algorithms. Choose an algorithm to use. 5. Enter a seed value in hexadecimal if desired. 5-May FTS4BT-UM-001

50 Analyzing Byte-Level Data 6. Click OK to generate the CRC. It will appear in the byte information lines at the bottom of the Event Display window. Whenever you select a range of data, a CRC using the algorithm you selected will be calculated automatically. FTS will calculate the CRC for either the DTE or DCE side. Which side it calculates is determined by the first byte selected. If the first byte is from the DTE side, then FTS will calculate the CRC for just the DTE bytes in the selected group. If the first byte is from the DCE side, FTS will calculate the CRC for just the DCE bytes. If you are calculating CRCs using the CRC16 algorithm and the CRCs do not match what you know they should be, try CRC16rev. What hardware often calls CRC16 is what software calls CRC16rev. List of All Event Symbols By default, the Event Display shows all events, which includes control signal changes, start and end of frame characters and flow control changes. If you want to see only the data bytes, click on the All Events button. Click again to display all events. Click on a symbol, and FTS will display the symbol name and sometimes additional information in the status lines at the bottom of the Event Display window. For example, clicking on a control signal change symbol will show you which signal(s) changed. In addition to data bytes, the events shown are (in alphabetical order): Abort Broken Frame - The frame did not end when FTS expected it to. This occurs most often with protocols where the framing is indicated by a specific character, control signal change, or other data related event. Buffer Overflow - Indicates a buffer overflow error. Control Signal Change - One or more control signals changed state. Click on the symbol, and FTS will show you which signal(s) changed at the bottom of the Event Display window. Data Capture Paused - The Pause icon was clicked, pausing data capture. No data is recorded while capture is paused. Data Capture Resumed - The Pause icon was clicked again, resuming data capture. Dropped Frames - Some number of frames were lost. Click on the symbol, and FTS will show how many frames were lost at the bottom of the Event Display window. End of Frame - Marks the end of a frame. Flow Control Active - An event occurred which caused flow control to become active (i.e. cause FTS to stop transmitting data). Events which activate flow control are signal changes or the receipt of an XON character. Flow Control Inactive - An event occurred which caused flow control to become inactive (i.e. cause FTS to transmit data). Events which deactivate flow control are signal changes or the receipt of an XOFF character. Frame Recognizer Change - A lowest layer protocol was selected or removed here, causing the frame recognizer to be turned off or on. I/O Settings Change - A change was made in the I/O Settings window which altered the baud, parity, or other circuit setting. 5-May FTS4BT-UM-001

51 Analyzing Byte-Level Data Long Break Low Power - The battery in the ComProbe is low. Short Break Spy Event (Spy Mode only) - Spy events are commands sent by the application being spied on to the UART. Start of Frame - Marks the start of a frame. Begin Sync Character Strip End Sync Character Strip Sync Dropped Sync Found Sync Hunt Entered Sync Lost Test Device Stopped Responding - FTS lost contact with the ComProbe for some reason, often because there is no power to the ComProbe. Test Device Began Responding - FTS regained contact with the ComProbe. Timestamping Disabled - Timestamping was turned off here. Events following this event will not be timestamped. Timestamping Enabled - Timestamping was turned on here. Events following this event will have timestamps. Truncated Frame- A frame that is not the same size as indicated within its protocol. Underrun Error Unknown Event Data Formats and Symbols Switching Between ASCII, EBCDIC and Baudot FTS displays data in ASCII by default. There are several ways to change the character set used to display data. 1. Go to the View menu and select the character set you want. A check mark next to the character set indicates which set is currently being used. 2. Right-click on the "ASCII" header label and choose a different character set. If you want to see only characters, click on the Characters Only toolbar. icon on the Event Display Switching Between Hex, Decimal, Octal or Binary FTS displays data in Hex by default. There are several ways to change the radix used to display data. 1. Go to the View menu and select the radix you want. A check mark next to the radix indicates which set is currently being used. 2. Right-click on the "Hex" header label and choose a different radix. 5-May FTS4BT-UM-001

52 Analyzing Byte-Level Data If you want to see only the numerical values, click on the Numbers Only icon on the Event Display toolbar. Switching Between Viewing All Events and Viewing Data Events By default, FTS shows all events, which includes data bytes, start-of-frame and end-of-frame characters and FTS events such as Data Captured Was Paused. Click on the Display All Events icon to remove the non-data events. Click again to display all events. Viewing Only ASCII (or EBCDIC or Baudot) Click on the Characters Only icon on the Event Display toolbar. To add the numerical values back to the display, click the Characters Only icon again. Viewing Only Hex (Or Decimal or Octal or Binary) Click on the Numbers Only icon on the Event Display toolbar. To add the characters back to the display, click the Number Only icon again. Mixed Sides If you want to get more data on the screen, you can switch to mixed sides mode. This mode puts all the data together on the same line. Data from one side is shown on a white background and data from the other is shown on a gray background. Click once on the Mixed Sides button to put the display in mixed sides mode. Click again to return to side over side mode. You can also right click on the labels in the center of the data display window to change between mixed and side over side modes. Choose Display Sides Together to go to Mixed Sides Mode, and Display Sides Separately to go to side over side mode. Font Size 1. Click on the Font Size icon. 2. Choose a font size from the list. 3. Click OK. The font size can be changed on several windows. Changing the font size on one window does not affect the font size on any other window. 5-May FTS4BT-UM-001

53 Analyzing Protocol Decodes Analyzing Protocol Decodes Frame Display Window To open this window Click the Frame Display icon on the Control window toolbar, or select Frame Display from the Window menu. Frame Display Panes The Frame Display window is used to view all frame related information. It is composed of a number of different sections or "panes", where each pane shows a different type of information about a frame. The image below gives the name of each pane. Click on the links below the image to learn more about each pane. Summary - a one line summary of each frame. Can display a summary for every protocol found in the data, and can be sorted by field for every protocol. Click here for an explanation of the symbols next to the frame numbers. Decode - detailed decode of the highlighted frame. Fields selected in the Decode pane have the appropriate bit(s) or byte(s) selected in the Radix, Binary, Character and Event panes. Radix - logical data bytes in the frame displayed in either hexadecimal, decimal or octal. Binary - binary representation of the logical data bytes. Character - character representation of the logical data bytes in either ASCII, EBCDIC or Baudot. Event - physical data bytes in the frame, as received on the network. 5-May FTS4BT-UM-001

54 Analyzing Protocol Decodes By default, all panes but the Event pane are shown when the Frame Display is first opened. Protocol Tabs The Frame Display will add tabs to the top of the Summary Pane for every protocol found in the in the data. You can click on these tabs to filter on the protocol. Select the All Protocols tab to stop filtering. The All Protocols tab will be automatically selected when multiple protocols are being filtered in using other filtering methods. Comparing Frames If you need to compare frames, you can open additional Frame Display windows by clicking on the Duplicate View icon. You can have as many Frame Display windows open at a time as you wish. Quick Export of the Summary Pane There is also a quick export that will dump the contents of the Summary Pane into a Comma Separated File (CSV). The Frame Display Toolbar The buttons that appear in the Frame Display window vary according to the particular configuration of FTS. Show Control Window - Brings the Control window to the front. Open File - Opens a capture file. Save - save the currently selected frames or the entire buffer I/O Settings Capture to Buffer - Begins data capture to the buffer only. Start Capture to Disk Pause/Resume - Available after data capture has started. Click once to pause data capture. Data can be reviewed and saved, but no new data will be captured. Click again to Resume capture. Clear Buffer - Clears the capture buffer and stops data capture to buffer. Close Capture File - Closes a capture file and stops data capture to disk. Event Display Focus Protocol Navigator - Brings up the Protocol Navigator window, with the currently selected frame highlighted. Statistics are kept on the entire session (the time since FTS was started) and for each set of events in the capture buffer or file. Duplicate View - Creates a second Frame Display window identical to the first. 5-May FTS4BT-UM-001

55 Analyzing Protocol Decodes Display Filter - Define a Display Filter. Filter Within Results Filter Define a Filter Within Results Filter. Undo Filter - Remove the currently active filter. The active filter is displayed on the far right of the Frame Display toolbar. Choose Previously Defined Filters. Quick Protocol Filter - brings up a dialog box where you can filter or hide one or more protocol layers. Find - Search for frame errors or string patterns in the decode. Display Capture Notes - Brings up the Capture Notes window where you can view or add notes to the capture file. Add/Modify Bookmark - Add a new or modify an existing bookmark. Display Bookmarks - Shows all bookmarks and lets you move between bookmarks. Protocol Stack - brings up the Protocol Stack Wizard where you can change the stack used to decode framed data Reload Decoders Packet Error Rate Stats Opens the Packet Error Rate Stats Window. Audio Extraction Opens the Audio Extraction Window. Filter Text giving the filter currently in use. If no filter is being used, the text reads "All Frames" which means that nothing is filtered out. To see the text of the entire filter, place the cursor over the text and a ToolTip will pop up with the full text of the filter. The following icons all change how the panes are arranged on the Frame Display. Additional layouts are listed in the View menu. Reset Pane Positions - Returns the panes to their default settings. Show Summary Only - Displays only the Summary pane. Toggle Expand Decode Pane - Makes the Decode pane taller and the Summary pane narrower. Toggle Display Freeze Prevents the display from updating. Show Only Data - changes the summary layer being displayed to Data, which displays just the data in the frame (also called the payload) Go To - Opens the Go To dialog, where you can specify which event number to go to. 5-May FTS4BT-UM-001

56 Analyzing Protocol Decodes First Frame - Moves to the first frame in the buffer. Previous Frame - Moves to the previous frame in the buffer. Next Frame - Moves to the next frame in the buffer. Last Frame - Moves to the last frame in the buffer. Note that if the frames are sorted in other than ascending frame number order, the order of the frames in the buffer will be the sorted order. Therefore the last frame in the buffer may not have the last frame number. Summary Layer drop-down box Lists all the protocols found in the data in the file. This box does not list all the protocol decoders available to FTS, merely the protocols found in the data. Selecting a protocol from the list changes the Summary pane to display summary information for that protocol. Text with Protocol Stack To the right of the Summary Layer box is some text giving the protocol stack currently in use. Sorting Frames By default, frames are sorted in ascending numerical sequence by frame number. Click on a column header in the Summary pane to sort the frames by that column. For example, to sort the frames by size, click on the Frame Size column header. An embossed triangle next to the header name indicates which column the frames are sorted by. The direction of the triangle indicates whether the frames are in ascending or descending order, with up being ascending. Note that it may take some time to sort large numbers of frames. Working With Panes By default, all panes but the Event pane are displayed when the window is first opened. To view all the panes, click the Show All Panes icon menu and choose Show [Pane Name]. on the toolbar, or go to the View The Toggle Expand Decode Pane icon view lengthy decodes. will make the decode pane longer in order to better The Reset Panes icon will return the window to its default setting. To close a pane, right-click on the pane and deselect the Show [Pane Name] option, or deselect the pane from the View menu. To open a pane, select Show [Pane Name] from the View menu. To resize a pane, place the cursor over the pane border until a double-arrow cursor appears. Click and drag on the pane border to resize the pane. Hiding (and Revealing) Protocol Layers Hiding protocol layers refers to the ability to prevent a layer from being displayed on the Decode pane. Hidden layers will remain hidden for every frame where the layer is present, and can be revealed again at any time. You can hide as many layers as you wish. Note: 5-May FTS4BT-UM-001

57 Analyzing Protocol Decodes Hiding from the Frame Display affects only the data shown in the Frame Display and not any information in any other window. There are two ways to hide a layer. 1. Right-click on the layer in the Decode pane, and choose Hide [protocol name] Layer In All Frames. 2. Click the Set Protocol Filtering button on the Summary pane toolbar. In the Protocols to Hide box on the right, check the protocol layer(s) you want hidden. Click OK when finished. To reveal a hidden protocol layer, right-click anywhere in the Decode pane, and choose Show [protocol name] Layer from the right-click menu, or click the Set Protocol Filtering button and uncheck the layer(s) you want revealed. Working With Multiple Frame Displays To create a second Frame Display, click the Duplicate View icon on the Frame Display toolbar. This will create another Frame Display window. You can have as many Frame Displays open as you wish. Each Frame Display is given a number in the title bar to distinguish it from the others. Multiple Frame Displays are useful for comparing two frames side by side. They are also useful for comparing all frames against a filtered subset, or two filtered subsets against each other. To navigate between multiple Frame Displays, click on the Frame Display icon in the Control window toolbar. A drop-down list will appear, listing all the currently open Frame Displays. Select the one you want from the list and it will come to the front. Filters and Multiple Frame Displays When you apply a filter, you can choose to have the filter applied to the current Frame Display or to a new one. The filter being used on any Frame Display is given in the upper right of the toolbar in a ToolTip. If you click the Filter button on the Control window, the assumption is that you are applying the filter to the original, unfiltered Frame Display. If you click the Filter button on a Frame Display, the filter will be applied to the data in the Frame Display. If the data in the Frame Display is already filtered, the effect is the same as applying two filters to the data. For example, open the Frame Display to look at some captured data. This data is unfiltered. From the Frame Display, you click the Filter icon and create a filter which keeps only frames where the source IP address is in them. You choose to apply the filter to a new Frame Display. Frame Display #2 is created and only frames with that source IP address are listed in the Summary pane. Now you want to see only those frames from that address carrying HTTP. Click on the Filter icon in Frame Display #2, create an HTTP filter and apply it to a new Frame Display. Frame Display #3 opens and shows only frames where the source IP address is and which carry HTTP. If you wish, you can now go back to Frame Display #2 (which shows all frames where the source IP address is ), click on the Filter icon and create a filter which keeps all FTP frames. Apply it to a new Frame Display. Frame Display #4 opens, which shows all frames where the source IP address is and which carry FTP. 5-May FTS4BT-UM-001

58 Analyzing Protocol Decodes Synchronization Between the Event and Frame Displays The Frame Display is synchronized with the Event Display. Click on a frame in the Frame Display and the corresponding bytes will be highlighted in the Event Display. Each Frame Display has its own Event Display. As an example, here's what happens if the following sequence of events occurs. 1. Click on Frame Display icon in Control window toolbar to open the Frame Display. 2. Click on Duplicate View icon to create Frame Display #2. 3. Click on Event Display icon in Frame Display #2. Event Display #2 opens. This Event Display is labeled #2, even though there is no original Event Display, to indicate that it is synched with Frame Display #2. 4. Click on a frame in Frame Display #2. The corresponding bytes are highlighted in Event Display #2. 5. Click on a frame in the original Frame Display. Event Display #2 does not change. Physical vs. Logical Byte Display The Event Display window and Event Pane in the Frame Display window show the physical bytes. In other words, they show the actual data as it appeared on the circuit. The Radix, Binary and Character panes in the Frame Display window show the logical data, or the resulting byte values after escape codes or other character altering codes have been applied (a process called frame transformation). As an example, bytes with a value of less than 0x20 (the 0x indicates a hexadecimal value) cannot be transmitted in Async PPP. To get around this, a 0x7d is transmitted before the byte. The 0x7d says to take the next byte and subtract 0x20 to obtain the true value. In this situation, the Event pane will show 0x7d 0x23, while the Radix pane will show 0x03. Frame Display Status Bar The Frame Display Status bar appears at the bottom of the Frame Display. It contains the following information: Total Frames: The total number of frames in the capture buffer or capture file in realtime Frames Filtered In: The total number of frames displayed in the filtered results from user applied filters in real-time Frame #s Selected: Displays the frame number(s) of selected (highlighted) frames, and the total number of selected frames in parentheses The Panes in the Frame Display Summary Pane The Summary pane displays a one-line summary of every frame in a capture buffer or file, including frame number, timestamp, length and basic protocol information. The protocol information included for each frame depends on the protocol selected in the summary layer box (located directly below the main toolbar). On a two-channel circuit, the background color of the one-line summary indicates whether the frame came from the DTE or the DCE device. Frames with a white background come from the DTE device, frames with a gray background come from the DCE device. Frame numbers in red indicate errors, either physical (byte-level) or frame errors. If the error is a frame error in the displayed protocol layer, the bytes where the error occurred will also be displayed in red. The Decode pane will give precise information as to the type of error and where it occurred. 5-May FTS4BT-UM-001

59 Analyzing Protocol Decodes The Summary pane is synchronized with the other panes in this window. Click on a frame in the Summary pane, and the bytes for that frame will be highlighted in the Event pane while the Decode pane will display the full decode for that frame. Any other panes which are being viewed will update accordingly. If you use one pane to select a subset of the frame, then only that subset of the frame will be highlighted in the other panes. Use the navigation icons, keyboard or mouse to move through the frames. The icons and will move you to the first and last frames in the buffer, respectively. Use the Go To icon to move to a specific frame number. Customizing Fields in the Summary Pane Changing Column Widths To change the width of a column, place the cursor over the right column divider until the cursor changes to a solid double arrow. Then click and drag the divider to the desired width. To auto-size the columns, double-click on the column dividers. Hiding Columns To hide a column, drag the right divider of the column all the way to the left. The cursor will change to a split double arrow when a hidden column is present. To show the hidden column, place the cursor over the divider until it changes to a split double arrow, then click and drag the cursor to the right. The Frame Size and Timestamp columns can be removed entirely by right-clicking on the header and selecting Show Frame Size or Show Timestamp Column. Follow the same procedure to display the columns again. Moving Columns - Changing Column Order To move a column, click on the column header and drag the mouse over the header row. A small white triangle indicates where the column will be moved to. When the triangle is in the desired location, release the mouse. Restoring Default Column Settings To restore columns to their default locations and show any hidden columns, right-click on any column header and choose Restore Default Columns, or select Restore Default Columns from the Summary menu. Frame Symbols in the Summary Pane One green dot means the frame was decoded successfully, and the protocol listed in the Summary Layer drop-down box exists in the frame. No dot means the frame was decoded successfully, but the protocol listed in the Summary Layer drop-down box does not exist in the frame. A green circle means the frame was not fully decoded. There are several reasons why this might happen. One reason is that the frame compiler hasn't caught up to that frame yet. It takes some time for FTS to compile and decode frames. Frame compilation also has a lower priority than other tasks, such as capturing data. If FTS is busy capturing data, frame compilation may fall behind. When FTS catches up, the green circle will change to either a green dot or no dot. Another reason is if some data in the frame is context dependent and we don't have the context. An example is a compressed header where the first frame gives the complete header, and subsequent frames just give information on what has changed. If FTS does not capture 5-May FTS4BT-UM-001

60 Analyzing Protocol Decodes the first frame with the complete header, it cannot decode subsequent frames with partial header information. A magenta triangle indicates that a bookmark is associated with this frame. Any comments associated with the bookmark will appear in the column next to the bookmark symbol. Decode Pane The Decode pane is a post-process display that provides a detailed decode of each frame. The decode is presented in a layered format that can be expanded and collapsed depending on which layer(s) you are most interested in. Click on the plus sign to expand a layer. The plus sign will change to a minus sign. Click on the minus sign to collapse a layer. Select Show All or Show Layers from the Format menu to expand or collapse all the layers. Layers will retain their expanded or collapsed state between frames. Protocol layers can be hidden, preventing them from being displayed on the Decode pane. Right-click on any protocol layer and choose Hide [protocol name] from the right-click menu. Each protocol layer is represented by a color, which is used to highlight the bytes that belong to that protocol layer in the Event, Radix, Binary and Character Panes. The colors are not assigned to a protocol, but are assigned to the layer. The Event, Radix, Binary, Character and Decode panes are all synchronized with one another. Clicking on an element in any one of the panes will highlight the corresponding element in all the other panes. Click the Toggle Expand Decode Pane icon to make the Decode pane taller. This allows for more of a lengthy decode to be viewed without needing to scroll. Radix, or Hexadecimal, Pane The Radix pane displays the logical bytes in the frame in either hexadecimal, decimal or octal. The radix can be changed from the Format menu, or by right-clicking on the pane and choosing Hexadecimal, Decimal or Octal. Because the Radix pane displays the logical bytes rather than the physical bytes, the data in the Radix pane may be different from that in the Event pane. See Physical vs. Logical Byte Display for more information. Colors are used to show which protocol layer each byte belongs to. The colors correspond to the layers listed in the Decode pane. The Event, Radix, Binary, Character and Decode panes are all synchronized with one another. Clicking on an element in any one of the panes will highlight the corresponding element in all the other panes. Character Pane The Character pane represents the logical bytes in the frame in ASCII, EBCDIC or Baudot. The character set can be changed from the Format menu, or by right-clicking on the pane and choosing the appropriate character set. Because the Character pane displays the logical bytes rather than the physical bytes, the data in the Character pane may be different from that in the Event pane. See Physical vs. Logical Byte Display for more information. Colors are used to show which protocol layer each byte belongs to. The colors correspond to the layers listed in the Decode pane. 5-May FTS4BT-UM-001

61 Analyzing Protocol Decodes The Event, Radix, Binary, Character and Decode panes are all synchronized with one another. Clicking on an element in any one of the panes will highlight the corresponding element in all the other panes. Binary Pane The Binary pane displays the logical bytes in the frame in binary. This pane is synchronized with the Decode pane so that individual bit fields can be highlighted. Because the Binary pane displays the logical bytes rather than the physical bytes, the data in the Binary pane may be different from that in the Event pane. See Physical vs. Logical Byte Display for more information. Colors are used to show which protocol layer each byte belongs to. The colors correspond to the layers listed in the Decode pane. The Event, Radix, Binary, Character and Decode panes are all synchronized with one another. Clicking on an element in any one of the panes will highlight the corresponding element in all the other panes. Event Pane The Event pane shows the physical bytes in the frame. You can choose between displaying only the data events or displaying all events by clicking the All Events icon. Displaying all events means that special events, such as Start of Frame/End of Frame and any signal change events, will be displayed as special symbols within the data. The status lines at the bottom of the pane give the same information as the status lines in the Event Display window. This includes physical data errors, control signal changes (if appropriate), and timestamps. Because the Event pane displays the physical bytes rather than the logical bytes, the data in the Event pane may be different from that in the Radix, Binary and Character panes. See Physical vs. Logical Byte Display for more information. Colors are used to show which protocol layer each byte belongs to. The colors correspond to the layers listed in the Decode pane. The Event, Radix, Binary, Character and Decode panes are all synchronized with one another. Clicking on an element in any one of the panes will highlight the corresponding element in all the other panes. Protocol Layer Colors What The Color Of Data Bytes Means The color of the data in the panes specifies which layer of the protocol stack the data is from. All data from the first layer is bright blue, the data from the second layer is green, the third layer is pink, etc. The protocol name for each layer in the Decode pane is in the same color. Note that the colors refer to the layer, not to a specific protocol. In some situations, a protocol may be in two different colors in two different frames, depending on where it is in the stack. You can change the default colors for each layer. Red is reserved for bytes or frames with errors. In the Summary pane, frame numbers in red mean there is an error in the frame. This could be a physical error in a data byte or an error in the protocol decode. Bytes in red in the Radix, Character, Binary and Event panes mean there is a physical error associated with the byte. Changing Protocol Layer Colors Click the Colors icon to change the colors used to differentiate different protocol layers in the Decode, Event, Radix, Binary and Character panes. 5-May FTS4BT-UM-001

62 Analyzing Protocol Decodes To change a color, click on the arrow next to each layer and select a new color. Red Frame Numbers or Bytes Red is reserved for bytes or frames with errors. In the Summary pane, frame numbers in red mean there is an error in the frame. This could be a physical error in a data byte or an error in the protocol decode. Bytes in red in the Radix, Character, Binary and Event panes mean there Protocol Navigator Window Protocol Navigator The Protocol Navigator window shows the decode for more than one frame at a time, and has several features for controlling what parts of the decode you see. The main part of the window shows the decode for multiple frames. When you first open the window, every protocol layer of every frame is expanded. This is the equivalent of the Decode pane on the Frame Display, simply with multiple frames visible at a time. There are three methods for controlling what is displayed in the window: expanding/collapsing protocols, filtering and hiding. Hiding and Revealing Protocols Hiding means that the selected protocol is not displayed in the window, even though it may be present in the frame. This allows you to zoom in on a particular protocol by hiding every protocol but the one of interest. This is especially effective when all the layers are expanded. Note: Hiding affects only the view in the Protocol Navigator and not the view in any other window. There are two ways to hide a protocol in the Protocol Navigator window. 1. Right-click on the protocol and choose Hide [Protocol Layer Name]. 2. There are three panes on the left side of the window. The middle box is the Hidden From View pane. Check the boxes next to the protocols you want to hide. To reveal a hidden protocol, right-click anywhere in the main window and select the protocol you want to show from the right-click menu, or uncheck the box next to the protocol name in the Hidden From View pane. When one or more layers are hidden, a note will appear at the top of the Protocol Navigator saying, "Some layers are hidden. Right-click to see." This warns you that some layers are hidden. Two special options are All But the Last Layer and All Special Information Nodes. All But the Last Layer hides all layers in each frame except for the last one, regardless of which protocol is present in the last layer. All Special Information Nodes hides the information line present in some protocol decoders. The Difference Between Filtering and Hiding You can filter on one or more protocol layers. The filter is inclusive, which means that filtering on a protocol means that only frames that contain that protocol will be shown in the window. Frames that do not contain the protocol will not appear. You can filter on one protocol or several. (Filtering on the Protocol Navigator window is display filtering only.) Hiding means that the selected layer is not displayed in the window, even though it may be present in the frame. This allows you to zoom in on a particular layer by hiding every layer but the one of interest. An example using the IP stack may help to illustrate the difference. 5-May FTS4BT-UM-001

63 Analyzing Protocol Decodes Assume that you only want to see frames that have TCP in them. You create a filter on TCP. The results displayed in the Protocol Navigator (or Frame Display) window will have only those frames that carry TCP. Now you're ready to look at the TCP decode in your frames. You don't care about what has happened at the IP layer or any other layer, so you hide everything but TCP. What the window will show is just the TCP decode for each frame. With those two steps, you've eliminated looking at any frame that doesn't have TCP in it, and you've narrowed down what you see to just the TCP decode. Expanding and Collapsing Protocol Layers You can expand any collapsed frame or protocol layer by clicking on the plus sign next to the frame number or protocol name. Expanding a protocol layer in one frame will expand it for all frames. To collapse a layer or frame, click on the minus sign next to the frame number or protocol name. What do you want to see? Everything. Choose Show All from the Format menu. Everything for just one frame. Click the plus sign next to the frame you want to see. Then click the plus signs next to each protocol name to see the full decode. Just the stack for each frame. Choose Show Frames AND Show Protocol Stack When Frame Is Completely Collapsed from the Format menu. This makes the display look similar to the following: Frame 1: Len=104 Ethernet -> IP -> TCP Frame 2: Len=98 Ethernet -> IP -> TCP -> NBSS Just the stack without summary information. Choose Show Layers AND uncheck Show Summary Decode When Detailed Decode Is Collapsed on the Format menu. This makes the display look similar to the following: Frame 1: Len=104 + Ethernet: + IPv4: + TCP: Frame 2: Len=98 + Ethernet: + IPv4: + TCP: + NBSS: Just the stack including summary information. Choose Show Layers AND Show Summary Decode When Detailed Decode Is Collapsed from the Format menu. This makes the display look similar to the following: Frame 1: Len=104 + Ethernet: --- Dest. Address: BROADCAST Source Address: XYZ etc. + IPv4: --- Protocol: TCP Length: 80 etc. + TCP: --- Source Port: 9988 Destination Port: NETBIOS etc. 5-May FTS4BT-UM-001

64 Analyzing Protocol Decodes Frame 2: Len=98 + Ethernet: --- Dest. Address: etc. + IPv4: --- Protocol: TCP Length: 56 etc. + TCP: --- Source Port: NETBIOS Destination Port: 9988 etc. + NBSS: --- Length: 23 Fragment: Entire Message The full decode for a protocol layer. Click on the plus sign next to the protocol name. This will expand just that protocol in every frame. The decode for just the last layer in each frame. Choose Collapse All Nodes AND Show Last Layer When Frame is Completely Collapsed from the Tree menu. Protocol Navigator Status Bar The Protocol Navigator Status bar appears at the bottom of the Protocol Navigator. It contains the following information: Total Frames: The total number of frames in the capture buffer or capture file in realtime Frames Filtered In: The total number of frames displayed in the filtered results from user applied filters in real-time Frame #s Selected: Displays the frame number(s) of selected (highlighted) frames, and the total number of selected frames in parentheses 5-May FTS4BT-UM-001

65 Analyzing Control Signal Changes Analyzing Control Signal Changes Viewing Signal Changes in Real-time Breakout Box Window The Breakout Box window provides a real-time graphical view of control signals. The window is customizable based on the control signals you wish to view and your preference of indicators (+/-, 1/0, T/F, arrows, and simulated LEDs). Also included are counters showing the number of times a control signal has changed. To open this window Click the Breakout Box icon on the Control window. FTS monitors six RS-232 control signals. These are: DTE Signals DTR - Data Terminal Ready RTS - Request to Send DCE Signals CTS - Clear to Send DSR - Data Set Ready CD - Carrier Detect RI - Ring Indicator (see the special note on capturing Ring Indicator changes) The Breakout Box Toolbar Home - brings the Control window to the front. Reset - resets the Breakout Box window. Freeze - freezes the display. Click once to freeze the display, and click again to resume. Options - Brings up the Breakout Box Options window. This window allows you to change the window refresh rate and choose which control signals to display. Reading the Breakout Box Window The Breakout Box display is divided into three main parts. The first part (to the far left of the screen) shows the abbreviated name of the control signal being monitored. These names can be changed in the I/O Settings window by clicking the Names button. The second part shows the control signal counters. The counters show how many times each control signal has changed state. This is useful in situations when signals may be changing state too rapidly to be displayed graphically. The third part of the Breakout Box shows the current states of the control signals. The indicators show the state that the control signal is currently in, and the line graph displays the state of the signal over time. A single line means that the signal is logically off, while a double line means that the signal is logically on. A half-height "tick" means that a signal has gone 5-May FTS4BT-UM-001

66 Analyzing Control Signal Changes through one full transition (from off to on to off, or vice versa) since FTS last updated the screen. To change the indicators or the rate at which FTS updates the window, click the Options icon. Breakout Box Options To open this window Click the Options icon on the Breakout Box toolbar. Display Signal This box shows which control signals FTS monitors. A check mark next to a control signal name indicates that the breakout box will display the status of that control signal. To prevent FTS from displaying the status of a signal, uncheck the box next to it. Window Refresh Rate The refresh rate is the rate at which FTS updates the window. By default, FTS refreshes the display once every 1,000 milliseconds (one second.) To change the rate, highlight the number in the box and enter a new number. See Performance Notes for information on how Window Refresh Rate can affect performance. Indicators You can choose what type of indicators FTS will use. The default indicators are a green "+" sign to show a logically high state, and a red "-" sign to show a logically low state. To change the indicators, click on the down arrow and choose a pair of indicators from the list. As a reminder, FTS gives the definition of the indicators in the top part of the Breakout Box window. Viewing Historical Signal Changes Signal Display Window The Signal Display window provides a graphical view of control signal transitions that you can manipulate. You can zoom in to view the state of control signals for a range of events, or zoom out to view control signal changes over the course of an entire capture session. To open this window Click the Signal Display icon on the Control window toolbar, or choose Signal Display from the Window menu. The Signal Display window does not provide a real-time view of control signal changes. It is intended to be used as a post-process review screen. Use the Breakout Box window to view real-time control signal changes. Note that if you bring up the Signal Display window while data is being captured, the window will show you the state of the control signals at the time the window was opened. This is called a "snapshot" because it is a picture of the buffer at the time the Signal Display was opened. To update the display to reflect the current state of the buffer, use the New Snapshot icon. The Signal Display window will display only the control signals you are interested in. Click the Options icon to choose which control signals to display. Reading the Signal Display Control signal changes are displayed in a graphical format. On the left side of the screen is a list of the signals currently being displayed, and to the right of each name is a line displaying 5-May FTS4BT-UM-001

67 Analyzing Control Signal Changes the state of the signal over time. A single line means that the signal was logically off, while a double line means that the signal was logically on. Dotted lines are used for signals that were not present at the time of capture. For example, if you are monitoring a circuit that does not use CD, that line will appear as a dotted line in the control signal display. The four information lines at the bottom of the window tell you what events are being shown in the window, and where you are in relation to the buffer as a whole. The first line tells you what event numbers are in the current snapshot, the total number of events, and the amount of time that passed between the first event in the snapshot and the last event (called Delta). The second line gives the same information about the events that are currently visible in the window. Because you can zoom in and out, often the events being shown in the window are not the same as the number of events in the current snapshot. The third line gives the same information for the currently selected events. You can highlight a range of events by clicking at any point on the graphical display and dragging the mouse to the left or the right. The third line will show information for the selected range. The fourth and last line shows the exact timestamps of the first and last bytes in the currently selected range. Note that this does not tell you the timestamp for the entire snapshot or the events displayed in the window, just the highlighted events. A single mouse click will place the cursor in the window. FTS highlights all six signal changes in one color, and uses a different color to specify the control signal line clicked on. You can highlight a range by clicking and dragging the mouse to the right or left. You can also use the arrow keys to move the cursor to the right or left. The Signal Display window is synchronized with other windows in FTS. A range highlighted in the Signal Display window will also be highlighted in the Event Display and Frame Display windows. The Snap to Nearest Change icon lets you place the cursor on the signal change you want to look at without needing to click on exactly the right spot. Find the line corresponding to the control signal you want to look at. Click on the line, and FTS will move the cursor to the nearest change. If you highlight a range, FTS will "snap to" the nearest changes on either side. This feature is active when the Snap To button is pressed, and inactive when the button is not pressed. Use the Zoom In and Zoom Out buttons to increase and decrease the magnification of the window. FTS will change the magnification by a factor of 2, 4 or 8, depending on the option selected in the Signals menu. If you want to see a range in greater detail, highlight the range you want to view and click on the Zoom to Selection icon. FTS will zoom in to show only that range in the window. If the range is small, FTS may add additional events to fill up the window. To view the entire snapshot in the window, click on the Display Entire Buffer icon. Note that if you bring up the Signal Display window while data is being captured, the window will show you the state of the control signals at the time the window was opened. To update the display, use the New Snapshot icon. Signal Display Options Choose which control signals to display in the Signal Display window. A check mark next to a control signal name means that the signal will be displayed. Click on a box to check or uncheck it. To open this window 5-May FTS4BT-UM-001

68 Analyzing Control Signal Changes Click the Signal Display icon icon. The Signal Display Toolbar on the Control window toolbar, and then click the Options Show Control Window - Bring control window to the front. Take New Snapshot - Takes a new "picture" of the capture buffer. If you are capturing data when you open the Signal Display window, the window will show only the state of the control signals that were in the buffer when the window was opened. Click this button to update the window with the contents of the current buffer. Zoom In - "Zooms in" on the signal display. How much you zoom in is determined by your selection in the Signals menu. You can zoom in by a factor of 2, 4, or 8. Zoom Out - Reverse of Zoom In. Zoom to Selection - Zooms to show only the region highlighted on the screen. If the highlighted area contains few events, the Signal Display window may also display additional events in order to fill up the screen. Display Entire Buffer - Zooms all the way out to display the contents of the entire buffer in the window. Find - Opens the Find Control Signal change window. Options - Open the Signal Display options window, where you can change which control signals are displayed in the window. Snap to Nearest Change - Moves the cursor to the nearest signal change whenever you click on the line graphics in the window. Find the line for the control signal whose changes you want to see. Click on that line, and FTS will move to the nearest signal change for that control signal. You can also highlight a range, and FTS will snap to the 2 nearest changes on either side of the range. Timestamping Options - Opens the Timestamping Options window, where you can change the timestamping resolution and how timestamps are displayed. 5-May FTS4BT-UM-001

69 Transmitting Data Transmitting Data Transmit Window To open this window: Click the Transmit icon on the Control window. If the Transmit icon is not active, open the I/O Settings window and set the Operating Mode to Source. The Transmit window is used to tell FTS what string or file you want to transmit, and start and stop data transmission. Transmit String To access this feature: Click the Transmit icon on the Control window. If the Transmit icon is grayed out, you will need to go to the I/O Settings window and choose Source for your operating mode. On the Transmit window, click the String tab. 1. Type the string you want to send in the large text box. FTS will interpret your string on the basis of whatever character set is currently active. Click on the History button to the right of the string window to choose a previously used string. 2. Click the Transmit Once radio button to indicate that the string should be sent once. Choose Transmit Continuously to send the string continuously. Click Times to Transmit and enter a number in the box to specify how many times to send the string. 3. Click on either the Capture to Buffer icon or Capture to Disk icon. 4. Click on the Send icon to transmit your string. The Send icon will gray out while the string is being transmitted, and become active once transmitting is finished. If you chose to transmit once or multiple times, FTS will send your string and then stop transmitting. If you chose to transmit continuously, FTS will send the string until you click on the Pause Transmit icon or the Stop icon. Pause Transmit and Stop pause and stop transmission only; they have no effect on data capture. Switching Character Sets, information on how to use a different character set. Transmit String Formats, information on how to transmit in hex and binary, and other string formats. Transmit String Formats Note that any of the formats below can be combined. It is legal to transmit the ASCII string ABC$65$30, for example. Entering Normal Text Characters FTS will send your string in whatever character set you are currently using. To change the character set, go to the Data menu in the Control Window, and choose a character set. Examples: To send the string "qwerty", you would type qwerty. To send the string "hello, world", you would type hello, world. 5-May FTS4BT-UM-001

70 Transmitting Data Entering Characters in Hex To transmit in hex, type a $ in front of your two digit byte. The $ symbol tells FTS that you are sending in hex. If you want to send more than one hex byte, you will have to type the $ symbol in front of each byte. You must have a two digit hex number after the $ for FTS to interpret the bytes as hex properly. Otherwise, FTS will interpret the characters as if they belonged to a character set. For example, if you want to send an ASCII NUL, which is hex 00, and you type $0, FTS will send hex 24 followed by hex 30. The $ symbol is hex 24 in ASCII, and zero is hex 30. To send a hex 00, you must type $00. Example: To send hex , you would type $31$00$97. Entering Control Characters The ^ symbol is used to specify that what follows is a control character. You can transmit the control characters Ctrl-A through Ctrl-Z, and Ctrl-@, Ctrl-[, Ctrl-\, Ctrl-], and Ctrl--. For example, ^A will send Ctrl-A ($01) and ^@ will send ASCII NUL ($00). The Escape Character The \ is the escape character. It is used when transmitting special characters, in order to specify that the next character should be taken literally. These special characters are: $^&*()\. For example, to put an * in a string, enter \*. To transmit a \, enter \\. Specifying a Range of Characters You can also send a range of characters by placing two periods between your first and last characters. For example, A..I will generate the string ABCDEFGHI. It is important to note that A..I in ASCII is very different from A..I in EBCDIC. In ASCII, A..I is equivalent to $41..$49, while in EBCDIC A..I is equivalent to $C1..$C9. It is also legal to specify a descending range. For example, I..A will generate IHGFEDCBA. Subexpressions Subexpressions are enclosed in (). The parentheses are not part of the subexpression and will not be transmitted. For example, (ABC) yields ABC. Subexpressions are useful because you can specify a repeat count for them using the *. For example (ABC)*3 will yield ABCABCABC. Entering Baudot Characters Since Baudot is only 5 bits it includes two shift characters. Shift In ($1F) means interpret all following characters as letters; Shift Out ($1B) means interpret all following characters as figures (punctuation, numbers, control codes, etc.) When the analyzer is activated it assumes the letters mode. The shift characters are captured in the buffer just as other bytes. In source mode FTS automatically supplies the shift characters to the string you enter. For example, if you are in letter mode and enter the string 12AB, FTS will send $1B (Shift Out), $17 (1), $13 (2), $1F (Shift In), $03 (A), $19 (B). NOTE: When you use hex notation to input a Baudot string, FTS will not insert shift characters. More Examples Enter \\\$\^\(\)\* \$.ABC. To Generate \$^()* $.ABC. 5-May FTS4BT-UM-001

71 Transmitting Data Enter (ABC)*3\9 ($6b..$68)*2 (A(BC)*2)*3 Aa..iZ To Generate ABCABCABC9 kjihkjih ABCBCABCBCABCBC AabcdefghiZ Transmit File To access this feature: Click the Transmit icon on the Control window. If the Transmit icon is grayed out, you will need to go to the I/O Settings window and choose Source for your operating mode. On the Transmit wndow, click the File tab. FTS will transmit files as is. For example, if you transmit a text file, FTS will send the text characters, but will also send any formatting instructions such as carriage returns, tab characters, etc., as their hex equivalents. FTS capture files must first be exported to binary format before being transmitted. FTS capture files are in a special format, and if you transmit a FTS capture file in its native format, what you will see will bear no resemblance to the data you want to transmit. See Transmitting FTS Capture Files for more information. 1. Type in the name of the file you want to send in the File to Transmit box, or click the Browse button to locate your file. 2. Click on the appropriate radio button to choose how many times you want to transmit your file. You can transmit once, transmit multiple times, or send the file continuously. If you choose to transmit multiple times, type in the number of times you want to send the file in the box to the right of the Times to Transmit line. 3. Click on either the Capture to Buffer icon or Capture to Disk icon. 4. Click on the Send button to transmit your file. The Send icon will gray out while the file is being transmitted, and become active once transmitting is finished. If you chose to transmit once or multiple times, FTS will send your file and then stop transmitting. If you chose to transmit continuously, FTS will send the file until you click on the Pause Transmit icon or the Stop icon. Pause Transmit and Stop affect transmission only; they have no effect on data capture. If you want to transmit the data in a FTS capture file, you will need to convert the file to a generic format using the Export function. If you transmit a FTS capture file without converting it first, FTS will send the data, but it will also send all the other information stored in the capture file, such as timestamping information. See Transmitting FTS Capture Files for more information. Transmitting FTS Capture Files To transmit the data in a FTS capture file, you will first need to export it to a binary format. 1. Open the capture file containing the data you want to transmit. 2. On the Control window, choose Export Events from the File menu. 5-May FTS4BT-UM-001

72 Transmitting Data 3. Choose Binary Output. 4. In the Available Fields box, choose Char/Event Name. Click the Move One Item Right button (looks like ">") to add it to the Displayed Fields box. Remove any other fields in the Displayed Fields box. 5. Choose a filename in the Export box. The default file name will be the name of your capture file, followed by the word "Events" (to distinguish it from a Frame export), with a.bin extension. 6. By default the file will be saved in the same directory as the original capture file. Click on the Browse button to save your file to another location. 7. If you want to transmit just DTE data or DCE data, be sure to filter out the side you do not want. Also, you will probably want to filter out Special Events. 8. Click Export. The result will be a.bin file, which you can transmit from the File tab of the Transmit window. Flow Control When Transmitting Flow Control is enabled in the I/O Settings window. When flow control is active, FTS will wait for a specified condition before sending data. This feature will typically be used for testing printers, stat muxes, and other devices which must throttle the data flowing to them. FTS has a flow control status line at the bottom of the transmit window which will tell you when flow control is active or inactive. FTS supports both software and hardware flow control. Software flow control uses the Xon and Xoff values specified in the I/O Settings window. This means that if FTS receives an Xoff character while in source mode it will stop sending data until an Xon character is received. DC1 and DC3 (hex 11 and hex 13 respectively) are most often used for software flow control. If you need to use other characters, simply enter the hex values that you want to use in the flow control boxes on the I/O Settings screen. FTS supports both RTS/CTS and DTR/DSR hardware flow control. Selecting RTS/CTS means that FTS will use the RTS/CTS control signals to control data transmission. When sourcing DTE FTS will automatically assert RTS and send data when CTS is asserted. While CTS is not asserted, FTS will NOT send data. When FTS is finished sending data, it will deassert RTS. In DCE mode FTS will reverse the meaning of RTS and CTS, responding to RTS as the flow control indicator even though this is a non-standard use of the signal. Selecting DTR/DSR tells FTS to use the DTR/DSR control signals for flow control. When sourcing DCE FTS will automatically assert and deassert DSR and will respond to DTR. When sourcing DTE FTS will automatically assert and deassert DTR and respond to DSR. Changing Control Signals Next to the Transmit String or File box are boxes for changing control signal states. You will be able to change control signals only for the device which you are emulating. For example, if you are a DTE source, you will only be able to change RTS and DTR. If you are a DCE source, you will be able to change CTS, DSR, CD and RI. To change a control signal, click on the box. A check mark means that the signal is high, while an empty box means that the signal is low. Delays and Max Burst Size When FTS transmits data, it first puts the data to be sent in a transmit buffer, and then sends the data out the serial port. There is a limit on the amount of data that can fit into the transmit buffer at one time. The Max Burst Size option allows you to control how many bytes are put 5-May FTS4BT-UM-001

73 Transmitting Data into the transmit buffer before the data is transmitted, while the Delays allow you to control the timing of data bursts. Max Burst Size Max Burst Size allows you to control how many bytes are put into the transmit buffer at a time. Example: Assume that the transmit buffer can hold up to 1000 bytes. If the Max Burst Size is set to 1000, FTS would fill up the buffer with 1000 bytes and then send the 1000 bytes. However, if you want to send only 500 bytes at one time, you would set the Max Burst Size to 500. FTS would put only 500 bytes into the transmit buffer before sending them, even though the buffer could hold up to 1000 bytes. String and File Delays String Delay inserts a delay between each transmission of a string. To set this type of delay, click on the radio button for String Delay. Type a value in the box to tell FTS how long to set the delay, and then click on the down arrow to choose a time increment of milliseconds, seconds or minutes. A delay of 0 (zero) means that FTS will not insert a delay. Timing under 2000/XP is often dealt with in increments of 10 milliseconds. This means that if you request a delay that is not a multiple of 10, the actual delay will be rounded up to the nearest 10 milliseconds. Example: A delay of 40 seconds will cause FTS to transmit the string, wait 40 seconds, and transmit the string again. This pattern will repeat until either the string has been transmitted the specified number of times, or the user chooses to stop transmitting. File Delay works in exactly the same way as String Delay. Burst Delay Burst Delay will insert a delay between each transmission of the transmit buffer. Remember that the Max Burst Size option effectively sets the size of the transmit buffer. FTS will fill the buffer with data up to the Max Burst Size, and send the data. If a Burst Delay is set, FTS will pause the length of the delay, before filling up the transmit buffer again and repeating the process. To set the size of the burst, type how many bytes to send in the Max Burst Size box. Set the delay by typing in the length of the delay in the Burst Delay box, and then choose a time increment of Milliseconds, Seconds or Minutes from the pulldown menu. Example: You want to send 1000 bytes, wait 2 minutes, and repeat the pattern. Type in 1000 in the Burst Size box, and set the delay to 2 minutes. FTS will send 1000 bytes, using as many repetitions of the string or file as necessary to achieve the correct number of bytes, wait 2 minutes and send the string again. Example: You want to send a 1000 byte file continuously, and insert a five second delay between each transmission of the file. However, you also want to send the file in increments of 400 bytes each, with a ten second delay between each group of 400 bytes. To set this up, you would set your Max Burst Size to 400, your File Delay to five seconds, and your Burst Delay to ten seconds. FTS would send 400 bytes, wait ten seconds, send 400 bytes, wait ten seconds, send 200 bytes, wait five seconds (because the end of the file has been reached), and repeat the process until transmission was paused or stopped. 5-May FTS4BT-UM-001

74 Transmitting Data Transmit Options To open this window: Click the Transmit icon on the Control window toolbar. On the Transmit window, click the Options icon. The Transmit Priority determines how much of a priority the system places on transmitting data versus updating the screen. On slower PC's, so much processor time can be taken up transmitting data, especially at higher data rates, that the screen never updates, making it appear that the PC has locked up. The Transmit Priority slider bar determines how much time to take transmitting data. When the Transmit Priority is high, FTS will ensure that data gets transmitted before it updates the user interface. If the Transmit Priority is low, FTS will allow the user interface more time. The length of your transmit string plays a role in the amount of throughput achieved. Longer strings are more efficient and will result in higher throughputs than shorter strings. The Transmit Toolbar Capture to Buffer - Begins data capture to the buffer. You must begin capture to either the buffer or a file before you can transmit. Capture to Disk - Begins data capture to a file. You must begin capture to either the buffer or a file before you can transmit. Send - Tells FTS to begin transmitting. Pause Transmitter - Pauses transmission. While transmitting is paused, FTS does not send data but it will continue to capture data coming from the other device. Stop Transmitting - Stops data transmission. FTS will continue to capture data. Transmit Options - Brings up the options window, which lets you change the transmit priority. Pause Transmit Pause Transmit temporarily halts data transmission. When transmission is resumed, FTS continues to send the rest of the data. Stop halts transmission completely, and any unsent bytes are thrown away. For example, if you are sending the ASCII string ABCD, and you paused transmission after AB had been sent, FTS would remember that it needed to send the CD. When transmission is resumed, FTS would send the CD. However, if you stop transmission after the AB has been sent, FTS will throw away the CD. If you start transmission again with the same string, FTS will transmit the string from the beginning. 5-May FTS4BT-UM-001

75 Searching Searching Searching You can search your data in several different ways. Some types of searches are relevant only for framed data and will not be offered if the data is not framed. Types of Searches String or Pattern in the Data String or Pattern in the Protocol Decode (framed data only) Byte Error (such as parity or framing errors) Frame Error (such as an FCS Error or error in the decode - framed data only) Control Signal Changes Time (move to data captured at a specific time or move through the data by time interval) Special Event Go To a Specific Byte or Frame Number Go To a Bookmark To Begin a Search 1. Capture some data to the buffer, or open a capture file to search. 2. Open the Event Display or Frame Display window. 3. Click on the Find icon or choose Find from the Edit Menu. 4. The Find window has a tab for each type of search. Click on the appropriate tab for the type of search you want to do. 5. Select the parameters for your search, and click Find Next. Find Next will look for the next occurrence of the search criteria, while Find Previous will look for an earlier occurrence of the search criteria. 6. Press F3 to repeat the last search. Search results are highlighted in the Event or Frame Displays, or both if appropriate. The selection in the Event Display appears on the third line down from the top of the window by default: this value can be changed. Go To This type of search allows you to go to a particular frame or event, or to move through the data X number of events or frames at a time. You can move either forward or backwards through the data. To go to a particular frame, select the Frame Number radio button and type the frame number in the box. Then click the Go To button. To move forward or backward a set number of frames, type in the number of frames you want to move, and then click the Move Forward or Move Backward button. To go to a particular event, select the Data Event Number or All Events Number radio button, type the number of event in the box, and click the Go To button. To move forward or backwards through the data, type in the number of events that you want to move each time, and then click on the Move Forward or Move Backward button. For example, to move forward 5-May FTS4BT-UM-001

76 Searching 10 events, type the number 10 in the box, and then click on Move Forward. Each time you click on Move Forward, FTS will move forward 10 events. See Event Numbering for why the Data Event Number and All Events Number may be different. As a general rule, if you have the Show All Events icon pressed down on the Event Display window or Frame Display Event pane, choose All Events Number. If the Show All Events button is up, choose Data Event Number. Search by Pattern Search by Pattern lets you to do a traditional string search. You can search one or both sides of the circuit, and your search can include wildcards. You can combine any of the formats when entering your string. Searching for Data Errors FTS can search for several types of data errors. You can choose which errors you want to search for, and you can choose whether to search just the DTE or DCE data, or both. Bytes with errors are shown in red in the Event Display window, making it easy to find errors visually when looking through the data. Selecting Which Errors to Search The section with the check boxes allows you to choose which errors FTS should look for. If you want to search only for overrun errors, you would check the overrun box, and uncheck the other boxes. To search for all types of errors, check all boxes. Click on a box to check or uncheck it. Searching for Error Conditions The first three options are all fairly similar, and are described together. These options are searching for an event where: one or more error conditions changed one or more error conditions occurred one or more error conditions were off (i.e. no errors occurred). The most common search is looking for a few scattered errors in otherwise clean data. To do this type of search, choose to search for an event where one or more error conditions occurred, and then choose which errors to look for. By default, FTS will look for all types of errors. In contrast, searching for an event where one or more error conditions were off means that FTS will look for an event where the error(s) were not present. For example, if you have data that is full of framing errors, and you know that somewhere in your 20 megabyte capture file the framing got straightened out, you could choose to search for an event where one or more error conditions were off, and choose to search only for framing. FTS would search the file, and find the point at which framing errors stopped occurring. Searching for an event where the error conditions changed means that FTS will search the data and stop at every point where the error condition changed from on to off, or off to on. For example, if you have data where sometimes the framing is wrong and sometimes right, you would choose to search framing errors where the error condition changed. This would first take you to the point where the framing errors stopped occurring. When you click Find Next, FTS will stop at the point when the errors began occurring again. FTS takes the current selected byte as its initial condition when running searches that rely on finding events where error conditions changed. FTS will search until it finds an event where error conditions changed or it reaches the end of the buffer, at which point FTS will tell you that 5-May FTS4BT-UM-001

77 Searching there are no more events found in the buffer. If you are searching for an exact match, FTS will ask you if you want to continue searching from the beginning of the buffer. Searching for Exact Error Conditions To search for an exact state means that FTS will find events that exactly match the error conditions that you specify. First select the "This exactly describes the state" radio button. This will change the normal check boxes to a series of radio buttons labeled On, Off and Don t Care for each error. On means that the error occurred, Off means that the error did not occur, and Don t Care means that FTS will ignore that error condition. Select the appropriate state for each type of error. Example: If you need to find an event where just an overrun error occurred, but not any other type of error, you would choose overrun error to be On, and set all other errors to Off. This will cause FTS to look for an event where only an overrun error occurred. If you want to look for events where overrun errors occurred, and other errors may have also occurred but it really doesn t matter if they did or not, choose overrun to be On, and set the others to Don t Care. FTS will ignore any other type of error, and find events where overrun errors occurred. To find the next error, click the Find Next button. To find an error that occurred earlier in the buffer to where you are, click the Find Previous button. Searching for Control Signal Changes Control signal searching allows you to search for changes in control signal states for one or more control signals. You can also search for a specific state involving one or more control signals, with the option to ignore those control signals whose states you don t care about. FTS takes the current selected byte as its initial condition when running searches that rely on finding events where control signals changed. Selecting Control Signals to Search The section with the check boxes allows you to specify which control signals FTS should pay attention to when doing the search. FTS will pay attention to any control signal with a check mark. Click on a box to place a check mark next to a control signal, and click again to uncheck the box. By default, FTS will search all control signals, which means all boxes start out checked. For example, if you are only interested in finding changes in RTS and CTS, you would check those two boxes and uncheck all the other boxes. This will tell FTS to look only at the RTS and CTS lines when running the search. The other signals will be ignored. Searching for On, Off, or Changed States The first three options are all fairly similar, and are described together. These options are searching for an event where: one or more control signals changed one or more control signals changed from off to on one or more control signals changed from on to off. Searching for an event where one or more signals changed means that FTS will look at every control signal that you checked, and see if any one of those signals changed state at any time. If you want to look at just one control signal, you would check the box for that signal and uncheck all the other boxes, and then choose to search for an event where one or more signals changed. FTS will note the state of the selected signal at the point in the buffer where 5-May FTS4BT-UM-001

78 Searching the cursor is, search the buffer, and stop when it finds an event where RTS changed state. If the end of the buffer is reached before an event is found, FTS will tell you that no matches were found. Searching for events where control signals changed state from off to on, or vice versa, is most useful if the signals are usually in one state, and you want to search for occasions where they changed state. For example, if DTR is supposed to be on all the time but you suspect that DTR is being dropped, you would tell FTS to look only at DTR by checking the DTR box and unchecking the others, and then do a search for where one or more control signals changed from on to off. FTS would search the DTR signal and stop at the first event where DTR dropped from on to off. Searching for an Exact State To search for an exact state means that FTS will find events that match exactly the state of the control signals that you specify. First choose to search for an event where your choices exactly describe the state. This will change the normal check boxes to a series of radio buttons labeled On, Off and Don t Care for each control signal. Choose which state you want each control signal to be in. Choose Don t Care to have FTS ignore the state of a control signal. When you click Find Next, FTS will search for an event that exactly matches the conditions selected, beginning from the currently selected event. If the end of the buffer is reached before a match is found, FTS will ask you if you want to continue searching from the beginning. If you want to be sure to search the entire buffer, place your cursor on the first event in the buffer. Example If you need to find an event where RTS, DSR and DTR are on, CTS is off and you don t care about the state of CD and RI, you would set the buttons as illustrated. 5-May FTS4BT-UM-001

79 Searching Searching within Decodes Search For String in Decode lets you to do a string search on the data in the Decode Pane of the Frame Display window. You can search one or both sides of the circuit, and your search can include wildcards. You can use characters, hex or binary digits, wildcards or a combination of any of the formats when entering your string. Searching for Frame Errors There are two options for error searching. Click the appropriate radio button for the type of search you want to perform, and then click Find Next. Search for All Errors will find frame errors as well as frames with byte-level errors (such as parity or CRC errors). Search for Frame Errors will find Frame specific errors, such as Frame Check errors. Searching for Special Events FTS inserts or marks events other than data bytes in the data stream. For example, FTS will insert start-of-frame and end-of-frame markers into framed data, marking where each frame begins and ends. If a hardware error occurs, FTS will show this using a special event marker. To search for a special event, check the event or events you want to look for in the list of special events. Then click Find Next. Not all special events are relevant to all types of data. For example, control signal changes are relevant only to serial data and not to Ethernet data. Side Restriction Side Restriction means that FTS will look for a pattern coming wholly from the DTE or DCE side. If you choose to search without regard for data origin, FTS will look for a pattern coming from one or both sides. For example, if you choose to search for the pattern ABC and you choose to search without regard for data origin, FTS will find all three instances of ABC shown below. The first pattern, with the A and the C coming from the DTE device and the B coming from the DCE is a good example of how using a side restriction differs from searching without regard to data origin. While searching without regard for data origin will find all three patterns, searching using a side restriction will never find the first pattern, because it does not come wholly from one side or the other. If you choose to search for the pattern ABC, and you restrict the search to just the DTE side, FTS will find the following pattern: 5-May FTS4BT-UM-001

80 Searching In this example, FTS will find only the second pattern (highlighted above) because we restricted the search to just the DTE side. The first pattern doesn't qualify because it is split between the DTE and DCE sides, and the third pattern, though whole, comes from just the DCE side. If we were to choose both the DTE and the DCE sides in the above example, FTS would find the second pattern followed by the third pattern, but not the first pattern. This is because each side has one instance in which the whole pattern can be found. FTS will completely search the DTE side first, followed by the DCE side. Side Restriction is available for pattern and error searching. Changing Where the Search Lands When you do a search in FTS, the byte or bytes matching the search criteria are highlighted in the Event Display, with the first selected byte appearing on the third line of the display. To change the line on which the first selected byte appears, open fts.ini (located in the root directory FTS was installed to), go to the [CVEventDisplay] section and change the value for SelectionOffset. If you want the selection to land on the top line of the display, change the SelectionOffset to 0 (zero). Searching by Time Searching By Time FTS can search by time in two different ways. An absolute timestamp search means that FTS will search for an event at the exact date and time specified. If no event is found at that time, FTS will go to the nearest event either before or after the selected time, based on the "Go to the timestamp" selection. A relative search means that FTS will begin searching from whatever event you are currently on, and search for the next event a specific amount of time away. Use the radio buttons to indicate which type of search you would like to do. Note that some special events like frame markers do not have timestamps and so will be skipped in the search. Data events that do not have timestamps because timestamping was turned off either before or during capture will likewise be skipped. Absolute Timestamp Search Specify the time to search for using the counters in the middle of the window. Click on the arrows next to each item to increase or decrease the value of each counter. By default, the 5-May FTS4BT-UM-001

81 Searching counters are filled in with the timestamp of the first event in the buffer. When you have finished selecting the time to search for, click on the Go To button to start the search. Sometimes there can be more than one event with the same timestamp. FTS will highlight all events with the same timestamp. Relative Timestamp Search Click on the event in the Event Display window that you want to begin the search from. The event must have a timestamp in order for relative timestamp search to work. In the Find window, use the counters in the middle of the window to specify the time interval you want to jump. You can specify intervals in days, hours, minutes, seconds, and fractions of a second, or any combination of these. When you have specified the time interval you want to use, click on the Move Forward or Move Backward buttons to start the search from the current event. For example, to search for an event occurring 10 seconds after the currently selected event, choose to do a relative timestamp search, use 10 seconds for your time interval, and click on Move Forward. As with absolute timestamping, FTS will highlight all events with the same timestamp. Choosing "On or Before" or "On or After" FTS will search for an event that matches the time specified. If no event is found at that time, FTS will go to the nearest event either before or after the specified time. Choose whether to have FTS go to the nearest event before the specified time or after the specified time by clicking the appropriate radio button in the "Go to the timestamp" box. If you are searching forward in the buffer, you will usually want to choose the "On or After" button. If you choose the "On or Before" option, it may be that FTS will finish the search and not move from the current byte, if that byte happens to be the closest match. Subtleties of Timestamp Searching Timestamping can be turned on and off while data is being captured. As a result, the capture buffer may have some data with a timestamp, and some data without. When doing a search by timestamp, FTS will ignore data without a timestamp. Entering Search Patterns Entering Characters Place the cursor in the Pattern box and type in your string. Click Find Next in order to find the next occurrence of the string. You can click on Find Next as many times as necessary until FTS has searched all the data. Clicking on Find Previous will search the buffer backwards. You can enter any character from a character set, with the following exceptions: \$&^?. These characters are used as prefixes to let you to enter hex, binary, control or wildcard characters. The escape character is the backslash \. Use this character when you want to search for one of the above restricted characters. For example, to search for a $, you would enter \$. To search for a \, enter \\. Check Ignore Case to do a case-insensitive search. Entering Hex or Binary To enter a hex value, enter a $ followed by two hex digits. For example, to search for hex 00 01, enter $00$01. If you need to specify the $ as a character, use \$. 5-May FTS4BT-UM-001

82 Searching Just as the $ symbol tells FTS that the following characters are hex digits, the & symbol tells FTS that a binary number comes next. For example, to search for binary , you would use & If you need to specify the & as a character, use \&. Entering Control Characters The ^ (caret) is used to enter the control characters Ctrl-A through Ctrl-Z and Ctrl-@,[,\,],- when using the ASCII character set. For example, ^A specifies Ctrl-A ($01) and ^@ specifies ASCII NUL ($00). If you need to specify the ^ as a character, use \^. Note that neither the ^ character nor control characters exist in Baudot, so attempts to search for the ^ character will result in an error message. The ^ character exists in EBCDIC, but control characters do not. A search for ^A in EBCDIC will match any occurrence of ^A ($5F$C1). You do not need to use the escape character to search for a ^ character in EBCDIC. Using Wildcards The wildcard character is the question mark (?). FTS supports wildcard searching at the byte, nibble and bit level. Wildcards can be used in place of characters, hex digits, and binary digits. If you need to search for a?, you can use \?. Examples of Search Strings To search for any single byte in the range of hex $10 through $1F, type $1?. &111111?? will search for binary numbers beginning with and ending with any combination of 1 and , , , and are all strings that match the search criteria. To search for any four character string which starts with an L and ends with an ES, type L?ES. You can combine formats in one string. For example, another way to specify a search for the string L?ES is $4C&????????& S. 5-May FTS4BT-UM-001

83 Bookmarks Bookmarks Bookmarks Bookmarks are a way of marking frames or events of interest in a capture file. You can search for bookmarks and move quickly between bookmarks. Bookmarks appear as a magenta triangle next to the frame number in the Frame Display window. Any comment associated with the bookmark appears in the Bookmark column. When you add or change a bookmark, you will be asked if you want to save your changes when you close the capture file, and given the option of saving the bookmarks to the current file or to a new one. See Confirm CFA Changes for more information. Adding a Bookmark 1. Select the frame or event you want to attach the bookmark to. 2. Click the Modify Bookmark icon on the toolbar. 3. In the dialog box, add a comment if you wish. 4. Click OK. You can also add a bookmark by right-clicking on the frame and choosing Add Bookmark. Modifying or Deleting a Bookmark 1. Select the bookmarked frame or event. 2. Click the Modify Bookmark icon. 3. To modify a bookmark, change the comment in the dialog box and click OK. 4. To delete a bookmark, click the Delete button. You can also modify or delete a bookmark by right-clicking on the frame and choosing Modify Bookmark from the right-click menu. Moving Between Bookmarks There are two ways to move between bookmarks. 1. Press the F2 key to move to the next bookmarked frame or event. 2. Click the Display All Bookmarks icon. Select the bookmark you want to move to and click the Go To button, or simply double-click on the bookmark. Click the Move Forward and Move Back buttons to cycle through the bookmarks. Viewing All and Searching For Bookmarks Click the Display All Bookmarks icon, or click the Find icon and choose the Bookmark page. Use the Move Forward and Move Back buttons to cycle through the bookmarks. To go to a specific bookmark, select the bookmark and click the Go To button, or double-click on the bookmark. To delete a bookmark, select it and click the Delete button. To modify a bookmark, select it and click the Modify button. Click Remove All to delete all the bookmarks. 5-May FTS4BT-UM-001

84 Saving Data Filtering Include and Exclude Radio Buttons All Set Conditions dialog boxes contain an "Include" and an "Exclude" radio button. These buttons are mutually exclusive. The "Include/Exclude" selection becomes part of the filter definition, and appears as part of the filter description displayed to the right of the Toolbar. Include: A filter constructed with the "Include" button selected, returns a data set that includes frames that meet the conditions defined by the filter and omits frames that do not. Exclude: A filter constructed with the "Exclude" button selected, returns a data set that excludes frames that meet the conditions defined by the filter and consists of frames that do not. Display and Filter Within Results Filters Display Filters How To Create and Use a Display Filter There are two steps to using a display filter. Define the filter conditions, and then apply the filter to the data set. FTS combines both filter definition and application in one dialog. 1. Click the Display Filters icon on either the Protocol Navigator or the Frame Display window or select "Apply/Modify Display Filters" from the filter menu to open the Set Condition dialog box. 2. Select the initial condition for the filter from the dropdown menu. 3. Set the parameters for the selected condition in the fields provided. The fields that appear in the dialog box are dependent upon the previous selection. Continue to enter the requested parameters in the fields provided until the condition statement is complete. 4. Click OK. The Set Condition dialog box closes and FTS applies the filter. 5. When a display filter is applied, a description of the filter appears to the right of the toolbar in both the Protocol Navigator and the Frame Display windows. Note: The OK button is unavailable (grayed out) until the condition selections are complete. Compound Display Filters Compound filters use Boolean logic to create complex and precise filters. There are three primary Boolean logic operators: AND, OR, and NOT. The AND operator narrows the filter, the OR operator broadens the filter, and the NOT operator excludes conditions from the filtered results. Include parentheses in a compound filter to nest condition sets within larger condition sets, and force the filter-processing order. Construct compound filters for both Display filters and Filter Within Results filters. There are two steps to using a compound filter. Define the filter conditions, and then apply the filter to the data set. FTS combines both filter definition and application in one dialog. 5-May FTS4BT-UM-001

85 Saving Data 1. Click the Display Filters icon on either the Protocol Navigator or the Frame Display window or select "Apply/Modify Display Filters" from the filter menu to open the Set Condition dialog box. Or 2. Select the window on which to apply the Filter Within Results filter (Protocol Navigator or Frame Display) 3. Click the Filter Within Results icon on the selected window (Protocol Navigator or Frame Display), or select "Apply Filter Within Results Filters" from the filter menu on the selected window to open the Set Condition dialog box. 4. Click the Advanced button on the Set Condition dialog box. 5. Select the initial condition for the filter from the dropdown menu. 6. Set the parameters for the selected condition in the fields provided. The fields that appear in the dialog box are dependent upon the previous selection. Continue to enter the requested parameters in the fields provided until the conditions statement is complete. 7. Click the Plus button on the left side of the dialog box and repeat steps 3 and 4 for the next condition. Continue adding conditions until your filter is complete. 8. Include parentheses as needed and set the Boolean operators. 9. Click OK. The Set Condition dialog box closes and FTS applies the filter. Note: Use the Up and Down arrow buttons on the left side of the dialog box to order your conditions, and the Delete button to delete conditions from your filter. The OK button is unavailable (grayed out) until each condition in the compound filter is complete, and all open parentheses are closed. How to Remove Display Filters Remove a display filter by clicking on the Remove Filters button on either the Protocol Navigator or the Frame Display window. Defining Node and Conversation Display Filters There are two steps to using Node and Conversation display filter. Define the filter conditions, and then apply the filter to the data set. FTS combines both filter definition and application in one dialog. 1. Click the Display Filters icon on either the Protocol Navigator or the Frame Display window or select "Apply/Modify Display Filters" from the filter menu to open the Set Condition dialog box. 2. Choose "frames with the conversation" as the initial condition from the Select dropdown menu. 3. Select an address type from the Type drop down menu (The address type selection populates both Address drop down menus with node address in the data set that match the type selection). 4. Select a node address from the first Address drop down menu. 5-May FTS4BT-UM-001

86 Saving Data 5. Choose a direction arrow from the Direction box. The left arrow filters on all frames where top node address is the destination, the right arrow will filter on all frames where top node address is the source, and the double arrow will filter on all frames where top node address is either the source or the destination. 6. If you want to filter on just one node address, skip step 7 & 8, and continue with step If you want to filter on traffic going between two address nodes (i.e. a conversation), select an address type for the second node address from the Type drop down menu. 8. Select a node address from the second Address drop down menu. 9. Click OK. The Set Condition dialog box closes and FTS applies the filter. When a display filter is applied, a description of the filter appears to the right of the toolbar in both the Protocol Navigator and the Frame Display windows. Note: The OK button is unavailable (grayed out) until the condition selections are complete. Predefined Display Filters FTS comes packaged with some useful predefined display filters. Applying a predefined filter is similar to applying a user defined filter (saved filter). 1. Click the Display Filters icon on either the Protocol Navigator or the Frame Display window or select "Apply/Modify Display Filters" from the filter menu to open the Set Condition dialog box 2. Click the Load/Save Toolbar button on the Set Condition dialog box. 3. Under Named Condition, click the Open icon. The system displays a popup list of the user defined saved filters, followed by a line, and then a list of the predefined filters. 4. Select the desired predefined filter from the list that appears below the line in the menu. 5. Click OK. The Set Condition dialog box closes and FTS applies the selected filter. Advanced Display Filtering Techniques Intermediate to advanced users, with a solid knowledge of filter definition and application, may find useful to create some of the more common filters "on the fly" using the advanced filtering techniques. In one of the panes in either the Frame Display or Protocol Navigator windows, place the cursor over a parameter you wish to filter on such as a node address or protocol type, and right click. A pop up menu appears with selections for filtering. Select the filter, and the system either closes the menu and applies the filter, or displays the Set Conditions dialog box with the know parameters filled in and the additional options available to complete the conditions statement. Filter Within Results Filters How to Create and Use a Filter Within Results Filter Use a Filter Within Results filter to refine the results of a previously applied Display filter. Filter Within Results filters provide an easy way to apply additional conditions to an existing filter without changing the original filter conditions. They also perform the added benefit of displaying the Filter Within Results in a separate Frame Display window for easy comparison with the original filter results. 1. Select the window on which to apply the Filter Within Results filter (Protocol Navigator or Frame Display) 5-May FTS4BT-UM-001

87 Saving Data 2. Click the Filter Within Results icon or select "Apply Filter Within Results Filters" from the filter menu on the selected window. The system displays the Set Condition dialog box, and the previously applied conditions appear in the Starting Filter pane at the top of the dialog box. 3. Select the initial condition for the filter from the dropdown menu 4. Set the parameters for the selected condition in the fields provided. The fields that appear in the dialog box are dependent upon the previous selection. Continue to enter the requested parameters in the fields provided until the condition statement is complete. 5. Click OK (at the bottom right side of the window). The Set Condition dialog box closes and FTS applies the filter to the outcome of the previously applied filter and displays the results in a new window. Note: To display the results of the Filter Within Results filter in another window such as the Protocol Navigator window when the filter results appear in the Display Frame window select the desired window from the View menu. How to Remove a Filter Within Results Filter Because a Filter Within Results filter displays its results in a new window, simply close the window by clicking the Close button in the top right corner of the window. The system preserves the original display in the window on which the Filter Within Results filter was applied. The new window that displays the results of the Filter Within Results filter can be distinguished from the original window by examining the filter description displayed to the right of the Toolbar. Saving and Loading Display and Filter Within Results Filter Files About Saved Filters FTS treats all saved filters in the same way, regardless of the method used to create the filter. A filter created as Filter Within Results filter and saved, can be applied as a Display filter and conversely. A Compound filter created as a Display filter and saved, can be applied as a Filter Within Results filter. Naming and Saving Display and Filter Within Results Filters to a File Perform the steps for one of the following: How to Create and Use a Display Filter Or How to Create and Use a Filter Within Results Filter Or Compound Display Filters 1. Click the Load/Save Toolbar button on the Set Condition dialog box. 2. Under Named Condition, click the Save icon. 3. The system displays the Save Named Conditions dialog box. Enter a name for the filter in the Name This Condition field, and click OK. 5-May FTS4BT-UM-001

88 Saving Data The Save Named Conditions dialog box closes and the name of the condition appears under Named Conditions on the Set Condition dialog box, and in the Named Frame Filters pane on the Protocol Navigator window. 4. Click OK. The Set Condition dialog box closes and FTS applies the filter. Opening Display and Filter Within Results Filter Files To apply a user defined filter, do one of the following: 1. Click the Choose Previously Defined Filters icon on the Frame Display window. The system displays a popup list of all the saved filters (both user defined and predefined). 2. Select the desired filter from the list. The popup list closes and FTS applies the selected filter. Or 1. Click the Display Filters icon on either the Protocol Navigator or the Frame Display window or select "Apply/Modify Display Filters" from the filter menu to open the Set Condition dialog box. 2. Click the Load/Save Toolbar button on the Set Condition dialog box. 3. Under Named Condition, click the Open icon. The system displays a popup list of all the saved filters. 4. Select the desired filter from the list. 5. Click OK. The Set Condition dialog box closes and FTS applies the selected filter. Editing Display and Filter Within Results Filters How to Modify a Condition in a Display or Filter Within Results Filter 1. Click the Display Filters icon on either the Protocol Navigator or the Frame Display window or select "Apply/Modify Display Filters" from the filter menu to open the Set Condition dialog box. The Set Condition dialog box displays the current filter definition. 2. Edit the desired parameter of the condition. Because the required fields for a condition depend upon previously selected parameters, the Set Condition dialog box may display additional fields that were not present in the original filter. In the event this occurs, continue to enter the requested parameters in the fields provided until the condition statement is complete. 3. Click OK. The Set Condition dialog box closes and FTS applies the modified filter. The description of the modified filter appears to the right of the toolbar in both the Protocol Navigator and the Frame Display windows. How to Delete a Condition in a Compound Display or Filter Within Results Filter 1. Click the Display Filters icon on either the Protocol Navigator or the Frame Display window or select "Apply/Modify Display Filters" from the filter menu to open the Set Condition dialog box. The Set Condition dialog box displays the current filter definition. 2. Select the desired condition from the list. 3. Click the Delete button. 4. Edit the Boolean operators and parentheses as needed. 5. Click OK. The Set Condition dialog box closes and FTS applies the edited filter. 5-May FTS4BT-UM-001

89 Saving Data Delete Saved Display and Filter Within Results Filters 1. Click the Choose Previously Defined Filters icon on the Frame Display window. The system displays a popup list of all the saved filters (both user defined and predefined). 2. Select Delete from the list. The system displays the Delete Named Condition dialog with a list of all user defined filters. 3. Select the filter to be deleted from the displayed list. 4. Click the Delete button. 5. Click OK. The Delete Named Condition dialog box closes and FTS deletes the filter. Protocol Filtering from the Frame Display Easy Protocol Filtering There are two types of easy protocol filtering. The first method lets you filter on the protocol being shown in the Summary pane, and the second lets you filter on any protocol discovered on the network so far. Filtering on the Summary Layer Protocol To filter on the protocol in the Summary pane, open the Summary Layer drop-down box and select the desired protocol. To filter on a different layer, just change the layer selection in the drop down box. Quick Filtering on a Protocol Layer To filter on any protocol layer, open either the Frame Display or Protocol Navigator window. On the Frame Display window, click the starred Filter icon or select "Quick Filtering" from the filter menu. This will open a dialog box listing all the protocols discovered so far. The box on the left shows the protocols you can filter on. Check the small box next to the name of each protocol you want to filter on, and then click OK. If you filter on more than one protocol, the result will be all frames that contain at least one of those protocols. For example, if you filter on IP and IPX NetBIOS, you will get all frames that contain either IP or IPX NetBIOS (or both). Filtering on All Frames With Errors To filter on all frames with errors, open either the Frame Display or Protocol Navigator window. On the Frame Display window, click the starred Filter icon or select "Quick Filtering" from the filter menu Then check the box for All Frames With Errors in the Filtering and Hiding window, and click OK. To remove the filter, uncheck the box. On the Protocol Navigator window, check the All Frames With Errors box in the top pane on the left side of the window. To remove the filter, uncheck the box. Protocol Filtering from the Protocol Navigator Hiding and Revealing Protocols Hiding means that the selected protocol is not displayed in the window, even though it may be present in the frame. This allows you to zoom in on a particular protocol by hiding every protocol but the one of interest. This is especially effective when all the layers are expanded. Note: Hiding affects only the view in the Protocol Navigator and not the view in any other window. 5-May FTS4BT-UM-001

90 Saving Data There are two ways to hide a protocol in the Protocol Navigator window. 1. Right-click on the protocol and choose Hide [Protocol Layer Name]. 2. There are three panes on the left side of the window. The middle box is the Hidden From View pane. Check the boxes next to the protocols you want to hide. To reveal a hidden protocol, right-click anywhere in the main window and select the protocol you want to show from the right-click menu, or uncheck the box next to the protocol name in the Hidden From View pane. When one or more layers are hidden, a note will appear at the top of the Protocol Navigator saying, "Some layers are hidden. Right-click to see." This warns you that some layers are hidden. Two special options are All But the Last Layer and All Special Information Nodes. All But the Last Layer hides all layers in each frame except for the last one, regardless of which protocol is present in the last layer. All Special Information Nodes hides the information line present in some protocol decoders. Filtering on a Protocol Layer You can filter on one or more protocol layers. The filter is inclusive, which means that filtering on a protocol means that only frames that contain that protocol will be shown in the window. Frames that do not contain the protocol will not appear. You can filter on one protocol or several. (Filtering on the Protocol Navigator window is display filtering only.) On the left side of the window are three panes. The top pane is the Filtering pane. In the pane is a list of all the protocols seen so far on the circuit. Check the boxes next to the names of the protocols you want to filter in. Filtering on a protocol layer from the Protocol Navigator affects the contents of the Frame Display window, and vice versa. Three additional filters available are: All Frames With Bookmarks - filters in all frames with a bookmark associated with them. All Frames With Errors - filters in all frames with errors. All Special Information Nodes - filters in all special information nodes. Using Named Filters If you create a filter and name it using the Filters window, the filter will appear in the bottom pane on the left side of the Protocol Navigator window. Check the boxes next to the names of the filters you want to use. Note that using a named filter will affect the contents of the Frame Display window as well. Filtering on All Frames With Errors To filter on all frames with errors, open either the Frame Display or Protocol Navigator window. On the Frame Display window, click the starred Filter icon or select "Quick Filtering" from the filter menu Then check the box for All Frames With Errors in the Filtering and Hiding window, and click OK. To remove the filter, uncheck the box. On the Protocol Navigator window, check the All Frames With Errors box in the top pane on the left side of the window. To remove the filter, uncheck the box. 5-May FTS4BT-UM-001

91 Saving Data Saving Data Saving Your Data You can save all or part of a capture buffer. You can also load a previously saved capture file, and save a portion of that file to another file. This feature is useful if someone else needs to see only a portion of the data in your capture file. For example, you have a ten megabyte capture file and the home office needs to see only two megabytes of that file. You can save only the two megabytes they need to see in a new file. To access the Save As dialog, select Save As from the File menu, or click the Save icon. The Save button and Save menu item are grayed out while data is being captured. You must pause capture before saving. Saving the Entire Capture Buffer 1. If you are capturing data, click on the Pause icon to pause data capture. You cannot save data to file while it is being captured. 2. Open the Event Display or Frame Display window. 3. Click the Save icon, or select Save As from the File menu. 5-May FTS4BT-UM-001

92 Saving Data 4. Click on the radio button labeled Entire Buffer. 5. Choose to save Events or Frames (see note below). 6. Type a filename in the Save As box at the bottom of the screen. Click the Browse icon to browse to a specific directory. Otherwise your file will be saved in the default capture file directory (usually C:\\Program Files\\Frontline Test System II\\[Product Name]\\My Capture Files). 7. When you are finished, click OK. NOTE: Choosing to save Events saves the entire contents of the capture buffer. Choosing to save Frames does not save all events in the capture buffer. When choosing to clear the capture buffer the system recognizes that some content in the capture buffer is not saved and displays the Clear Capture Buffer Warning. Saving a Portion of a Capture File or Buffer 1. If you are capturing data, click on the Pause icon to pause data capture. You cannot save data to file while it is being captured. 2. Open the Event Display or Frame Display window, depending on whether you want to specify a range in bytes or in frames. 3. Select the portion of the data that you want to save. Click and drag to select data, or click on the first item, move to the last item and Shift+Click to select the entire range. If the range you want to save is too large to select, note the numbers of the first and last item in the range. 4. Click the Save icon, or select Save As from the File menu. 5-May FTS4BT-UM-001

93 Saving Data 5. Click on the radio button labeled Selection. If you selected a range, make sure the starting and ending numbers are correct. To specify a range, type the numbers of the first and last items in the range in the boxes, and select either Events or Frames to indicate whether the numbers are event or frame numbers. 6. Type a filename in the Save As box at the bottom of the screen. Click the Browse icon to browse to a specific directory. Otherwise your file will be saved in the default capture file directory (usually C:\\Program Files\\Frontline Test System II\\[Product Name]\\My Capture Files). 7. Click OK when you are finished. Confirm CFA Changes This dialog appears when you close a capture file after changing the Notes, the protocol stack, or bookmarks. The dialog shows what information was added or changed and allows you to select which information to save, and whether to save it to the current file or to a new one. The changes that you have made will appear in a list in the left pane. Check the boxes next to the changes you want to keep. Click on each item to see details in the right pane about what was changed for each item. Save To This File Saves the changes you have made to the current capture file. Save As Saves the changes to a new file. Cancel the Close Operation Cancels closing the file and returns you back to FTS. No changes will be saved. Discard Changes Closes the file without saving any of the changes made to the notes, bookmarks, or protocol stack. Capture File Notes To open the Notes window Click the Show Notes icon. This icon is present on the toolbars of the Control window and several other windows as well. The Notes feature allows you to add comments to a CFA file. These comments can be used for many purposes. For example, you can list the setup used to create the capture file, record why the file is useful to keep, or include notes to another person detailing which frames to look 5-May FTS4BT-UM-001

94 Saving Data at and why. (Bookmarks are another useful way to record information about individual frames.) Type your comments in the large edit box on the Notes window. The Cut, Copy, Paste, Undo and Redo features are all supported. Click the thumbtack icon to keep the Notes window on top of any other windows. When you're done adding comments, close the window. When you close the capture file, you will be asked to confirm the changes to the capture file. See Confirm CFA Changes for more information. 5-May FTS4BT-UM-001

95 Loading and Importing Capture Files Loading and Importing Capture Files Loading a Capture File 1. From the Control Window, go to the File menu. 2. Choose a file from the recently used file list, or choose Open to load a new file. 3. Capture files have a.cfa extension. Browse if necessary to find your capture file. Click on your file, and then click Open. Importing Capture Files 1. From the Control Window, go to the File menu. 2. Choose a file from the recently used file list, or choose Open to load a new file. 3. Change the Files of Type box to All Importable File Types or All Supported File Types. Select the file and click Open. FTS will automatically convert the file to FTS format while keeping the original file in its original format. You can save the file in FTS format, close the file without saving it in FTS format, or have FTS automatically save the file in FTS format (see the System Settings to set this option.) All of these options will keep your original file untouched. When you first open the file, FTS will bring up the Protocol Stack window and ask you what protocol decodes, if any, you want to use. You must choose a protocol decode at this point for FTS to decode the data in the file. If you open a file without using any decodes, and decide later that you want to apply a decode, choose Reframe from the File menu on the Control window. At present, FTS supports the following file types: Frontline Serialtest Async and Serialtest ComProbe for DOS requires the.byt for data and the.tim for timestamps (see note on importing DOS timestamps). Greenleaf ViewComm 3.0 for DOS - requires the.byt for data and the.tim for timestamps (see note on importing DOS timestamps). Frontline Ethertest for DOS requires 3 files: filename.cap, filename.ca0 and filename.ca1. Sniffer Type 1 supports files with the.enc extension. Does not support Sniffer files with a.cap extension. Snoop or Sun Snoop files with a.cap extension based on RFC For file format, see Shomiti Surveyor files in Snoop format files with a.cap extension. For file format, see CATC Merlin - files with a.csv extension. Files must be exported with a specific format. See File Format for Merlin Files for information. CATC Chief - files with a.txt extension. Importing Timestamps FTS4BT uses a timebase of Pacific Standard Time during non daylight savings time hours and Pacific Daylight Time during daylight savings time hours. FTS always uses Greenwich Mean Time (also known as Universal Time Coordinates.) When importing a FTS4BT file, FTS must determine if the file was recorded during daylight savings time or not before converting the timestamps. Because the rules for determining this 5-May FTS4BT-UM-001

96 Saving Data can change, it is possible for FTS to convert the timestamps incorrectly, resulting in timestamps that are off by one hour. File Format for Merlin Files FTS will import Merlin s export files that have been exported with Merlin s default settings. These files should have an extension of ".csv". It is possible with the Merlin software to hide or change a field s format. If you do this before exporting the Merlin file then FTS may have trouble importing the file. If you are experiencing problems importing Merlin files, then check to make sure that no fields were hidden and that the default field formats were being used, when the file was exported from Merlin. 5-May FTS4BT-UM-001

97 Printing Printing Printing From The Event Display About Event Display Print The Event Display Print feature provides the user with option to print either the entire capture buffer or the current selection. The output file format as is in html, and displays in the users default browser. From the browser, the user can select from the browser print functions. Print Background Colors Using Internet Explorer Open the Tools menu on the browser menu bar 2. Select "Internet Options " menu entry. 3. Click Advanced tab. 4. Check "Print background colors and images" under the Printing section 5. Click the Apply button, then click OK Print Background Colors Using Netscape 8.0 and Mozilla Open the File menu. 2. Select "Page Setup " menu entry. 3. Click "Format & Options" tab. 4. Check "Print Background (colors & images)" The Event Display Print feature uses the current format of the Event Display as specified by the user. Note: See About Event Display for an explanation on formatting the Event Display prior to initiating the print feature. Accessing the Event Display Print Dialog Selecting Print to Browser from the File menu in the Event Display brings up the following dialog: Configure the Print File Range in the Event Display Print Dialog Selecting more than one event in the Event Display window defaults the radio button in the Event Display Print dialog to Selection and allows the user to choose the All radio button. When only one event is selected (can t have none selected), the All radio button in the Event Display Print dialog is selected and the Selection radio button is disabled. 5-May FTS4BT-UM-001

98 Printing How to Print Event Display Data to a Browser Select Print to Browser from the File menu on the Event Display window to display the Event Display Print dialog. Select the range of events to include from either All or Selection in the Event Range section of the Event Display Print dialog. Note: See Configure the Print File Range in the Event Display Print Dialog above for an explanation of these selections. Click the OK button. The system displays the Event Display data in the default browser. Use the browser print functions to printout the data. Print Preview Print Preview shows you how the data will look printed. You can scroll through the pages and zoom in on the data to get a closer look. The line of buttons across the top of the window controls the functions of the window. To open the Print Preview window, choose Print Preview from the File menu in any window that supports printing. When Print Preview is chosen, the preview display replaces the regular data display in the window. You can print directly from the Print Preview window. Click on the Print button to bring up the print window. Use the Next Page and Prev Page buttons to navigate through the data. Next Page will show you the next page in your data will look, while Prev Page will take you back to the previous page. Two Page will change the display to show two pages of data. When in the Two Page display, the button will read One Page. Click on the One Page button to return to viewing one page. Zoom In and Zoom Out allow you to change the magnification of the pages. Click on the Zoom In to increase the magnification, and on Zoom Out to decrease the magnification. When you have reached the limit in either direction, the buttons will be grayed out. You can also zoom in and out by clicking on the page itself. When the cursor looks like a magnifying glass, you can click on the page to increase the magnification. When you have reached the top level of magnification, the cursor will change back to an arrow. Click on the page to return to normal magnification. Click on the Close button to return to the regular display. 5-May FTS4BT-UM-001

99 Printing Troubleshooting Printing Problems Some printer drivers may not be able to handle the FTS True Type fonts correctly in the default mode. When this happens, the printer driver substitutes other fonts for the FTS fonts, resulting in printed data that does not look like the data on the screen. Many printers have several options for handling True Type fonts. Changing how your printer handles True Type fonts can often be done from the Printer Properties box. Printer Properties can be reached by choosing Printers from the Settings menu on the Start button, and then right-clicking on your printer and choosing Properties. It can also be reached from the Print window within FTS. Click on the button labelled Properties next to the name of the printer in the Print window. Every printer handles font substitution a little differently, and every printer puts the font settings in a different place. If you cannot easily find the font settings for your printer, please refer to your printer's documentation for help. 5-May FTS4BT-UM-001

100 Exporting Exporting Exporting Data Event Display Export About Event Display Export The Event Display Export feature provides the following options: Export either the entire capture buffer or the current selection Output file format as text, html, or CSV The Event Display Export feature uses the current format of the Event Display as specified by the user. Note: See About Event Display for an explanation on formatting the Event Display prior to initiating the export feature. Accessing the Event Display Export Dialog Selecting Export Events from the File menu in the Event Display brings up the following dialog: Configure the Export File Range in the Event Display Export Dialog Selecting more than one event in the Event Display window defaults the radio button in the Event Display Export dialog to Selection and allows the user to choose the All radio button. When only one event is selected (can t have none selected), the All radio button in the Event Display Export dialog is selected and the Selection radio button is disabled. How to Export Event Display Data to a File Select Export Events from the File menu on the Event Display window to display the Event Display Export dialog. 5-May FTS4BT-UM-001

101 Exporting Enter a file path and name, or click the browser button to display the Windows Save As dialog and navigate to the desired storage location. Select a file type from the Save as type: drop-down List Menu on the Event Display Export dialog. Select from among the following file formats: Text File (*.txt) HTML File (*.htm) CSV File (*.csv) Select the range of events to include in the file from either All or Selection in the Event Range section of the Event Display Export dialog. Note: See Configure the Export File Range in the Event Display Export Dialog above for an explanation of these selections. Click the Save button. Advanced Export The export feature allows you to export your capture files or capture buffer to text or binary format. Text format is used to create readable text files, which can be printed as is or imported into database programs or spreadsheets. Binary format creates a binary file which can be transmitted by FTS or manipulated by a custom application. 1. To begin exporting, go to the Control or Event Display window, and choose Export Events from the File menu. 2. Select the Text Output radio button at the top of the window to create text files, and Binary Output to create binary files. 3. Select the fields you want included in the export file. Click on a field in the Available Fields box, and then click right arrow button to add the field to the list of Displayed Fields. The double-right arrow will move all fields, while the left arrows remove fields from the Display Fields box. Note: When exporting to binary output, Decimal, Char/Event Name, Hexadecimal and Octal are the same. You only need to choose one. 5-May FTS4BT-UM-001

102 Exporting The Example box at the bottom of the window will show you what fields you have added and how they will look in the export file. The Example window uses dummy data, not actual data from your capture buffer. 1. Select a filename. Text files end in a.txt extension, while binary files end in a.bin extension. Underneath the file name, FTS will show you approximately how big the file will be, and what percentage of free disk space it will take up. 2. Click on the Export button to begin exporting. Depending on the amount of data to be exported, the export process may take some time. You can choose to export the entire capture buffer or just a portion of it. If you have the Event Display window open and have selected a range in it, the Export window will automatically fill in the range for you. Export Fields Available fields are: Byte Number Decimal Char/Event Name Errors Event Number Frame Number Hexadecimal Octal Side Signals Timestamp Type number of the data byte decimal value of the data byte character value of data bytes, or name of non-data bytes includes any errors associated with bytes number of the event (see Event Numbering for why Byte Number and Event Number may be different) number of the frame the event is in hexadecimal value of the data byte octal value of the data byte shows which side the data byte originated from (valid only for serial data) gives the state of the control signals (valid only for serial data) shows the timestamp of the event shows whether event was Data or a Special Event (anything other than a data byte) Note: When exporting to binary output, Decimal, Char/Event Name, Hexadecimal and Octal are the same. You only need to choose one. Exporting Baudot When exporting Baudot, you need to be able to determine the state of the shift character. In a text export, the state of the shift bit can be determined by the data in the Character field. When letters is active, the character field will show letters and vice versa. Export Filter Out You can filter out data you don't want or need in your text file. 5-May FTS4BT-UM-001

103 Exporting (This option is available only for serial data.) In the Filter Out box, choose which side to filter out: the DTE data, the DCE data or neither side (don't filter any data.) For example, if you choose the radio button for DTE data, the DTE data would be filtered out of your export file and the file would contain only the DCE data. You can also filter out Special Events (which is everything that is not a data byte, such as control signal changes and Set I/O events), Nonprintable characters or both. If you choose to filter out Special Events, your export file would contain only the data bytes. Filtering out the nonprintable characters means that your export file would contain only special events and data bytes classified as printable. In ASCII, printable characters are those with hex values between $20 and $7e. Other Export Options Use Footer This option is valid only when doing a binary export. If you are exporting a capture file for the purpose of retransmitting the data, uncheck this box. If you will be manipulating the data using the sample export program, check this box. If the data is exported without the footer, the sample export program will not be able to read the export file. Use Abbreviated Event Names Check this box to abbreviate the names of the Special Events. This is useful to conserve space in the text file. Separate Records with CR/LF Specifies whether to separate each record with a carriage return/line feed. If this option is unchecked, the data will be output as a continuous stream. Align Columns Check this box to have the columns be left-justified. Put Fields in Double Quotes Check this box to put double quotes around the data in each field. Output Header Includes a header at the top of the file with the date and time the file was exported, name of the original capture file or capture buffer, and the event numbers and timestamps for the range exported. Output Field Name Record Includes a record at the top of the file with the field names. Align Field Names with Data Aligns the field name column with the data columns. Timestamp Format Sets the timestamp format. Native format is the month/day/year plus hour:minute:second:millisecond AM/PM in twelve hour format. For other formats, "D" stands for day, "H" stands for hour, "M" stands for minute, "S" stands for second and "m" stands for millisecond. Character Set Choose ASCII, EBCDIC or Baudot. (See note on exporting Baudot.) Signals Characters Defines how control signal states are indicated. Choose from 1/0, T/F, or X/space. "X", "1" and "T" indicate an "on" or "high" signal state. Errors Characters Defines how error conditions are indicated. Choose from 1/0, T/F, or X/space. "X", "1" and "T" indicate that an error occurred. Field Delimiter Defines how the fields will be separated. Choices are None (no delimiter will be used), Comma, Tab, Space, Bar and Semicolon. If a delimiter is chosen, FTS will include the delimiter between each field in the export file. Exporting Frames Frame Print/Export The Frame Print window allows you to print framed data and the Frame Export window allows you to export it to a text file suitable for importing into a spreadsheet or database program. These windows are very similar and so will be documented together. 5-May FTS4BT-UM-001

104 Exporting Frame Print/Export has a number of formatting options. Some options are available only when exporting, others only when printing. Unavailable options will be grayed out. The example space at the bottom of the window shows how the file will look. The example window uses dummy data instead of the data from your capture file. To export your data, open the Frame Display window and select Export Frames from the File menu. To create a text file in an easily readable format, choose Print from the File menu, and select the Send to File option in the Output section. To print your data, open the Frame Display window and choose Print from the File menu. Make your selections from the range of options (for more info on each option, click on the links below), and then choose the range to output in the Output section. You can output the entire buffer or a smaller range of frames. If exporting to file, give the file a name. By default, exported files are stored in the My Capture Files directory. Click the Browse icon to select a different directory location. Frame Export File Format The frame export file format is as follows, starting with the first column on the left: Section marker By default, LSED, where L stands for Summary Label, S for Summary Data, E for Error and D for Decode. These markers can be changed in the General Formatting options. Frame number The frame number assigned by FTS. At this point, the columns vary depending on the section. Summary Label - "L" marker Label This is the same value as given in the column headers on the Summary pane of the Frame Display window. There is one label for each column. Summary Data - "S" marker Data For Summary Data, this is the value listed in the columns of the Summary pane. There is one value for every column given in the summary label section. Error - "E" marker Error Location Where the error occurred. Error Type The type of the error (CRC, Framing, Parity, etc.) Decode - "D" marker Layer indent These numbers identify how far into the decode tree the field is. 0 (zero) is the top layer of the tree, 1 is one indentation to the right from the top layer, 2 is two indentations in from the top layer, etc. Protocol Field The protocol name or protocol field name. Field Value The value of the protocol field, if present. Start of Field Offset [optional] The offset to the start of the field expressed in logical or physical bits. Field Length [optional] The length of the field expressed in logical or physical bits. Field Data [optional] The data bytes containing the field value. 5-May FTS4BT-UM-001

105 Exporting General Section Begin with a file description - includes the capture file name at the start of the printout. This option is available only when printing. Begin with all summary headers - includes the summary section header labels for every protocol at the start of the output. General Formatting General formatting includes the field separator, line width and page height (used only when printing), and the marker to use for the summary header, summary data, errors and decode sections (used only when exporting). Summary Section First choose how many summary layers to include using the radio buttons. Choose All Layers means that the output will have a summary line for every protocol present in the frame. Visible Layer Only means that only the summary line currently selected in the Frame Display window will be included in the output, while No Summary Section means that no summary information will be included. Check Per-frame header label section to include the header line from the summary pane above each frame. Check Align Columns to align the summary columns (available only when printing). Summary Formatting The formatting option for the Summary section is the column width, used only when printing. Decode Section Choose All layers to output the decode for all layers present in the frame. Choose Selected layers only if you want to output the decode for one or more specific layers and don't care about any other layers that may be present. Click the radio button for Selected layers only and then click each layer you want to include in the list box. Choose No decode section if you don't want any decode information to be output. Decode Formatting Formatting options for the Decode section are the number of data bytes to display for each frame, and the number of data bytes per line. Decode formatting options are used only when printing, and not when exporting to file. Decode Section - Data Display Append field linking info will include the start of each field as an offset from the start of the frame and its length in bits to the end of each line of the decode. The offset can be expressed in logical bits or physical bits (this may be the same depending on the protocol stack.) Append field data bytes (available only when exporting) will include the data bytes for each layer of the decode at then end of the line. Change the radix used to represent the data in the Byte Display Radix box. Show physical frame (available only when printing) will include all the physical data bytes for the frame at the start of the frame. Show per-layer logical frame (available only when printing) will include the logical data bytes for each protocol layer in the decode. 5-May FTS4BT-UM-001

106 Exporting Error Section Check Per-frame error section to include error information on each frame. Check Show even if there are no errors to include the error section even if no errors are present (available only when printing). Quick Export You can dump the contents of the Summary pane on the Frame Display into a Comma Separated File (CSV). To access this feature either right click on the Summary Pane and select the Export menu item, or click on the Edit menu and choose Export Summary. Export Templates Export Templates Once you've set up an export format, you can save all your options as a template and use it for future exports. 1. To create a template, set up all the options on the export window exactly as you want them to be in the template. 2. Type a name in the Apply Template box, and click Save Template. 3. To retrieve your template, click on the down arrow next to the Apply Template box, and choose your template from the list. To delete a template, choose the template in the Apply Template box, and click the Delete Template button. There are several templates supplied with FTS that cannot be deleted. 5-May FTS4BT-UM-001

107 Monitoring Internal Ports Monitoring Internal Ports Spy Spy lets you run FTS on a computer, and Spy on the data going in and out of a COM port or internal modem. This means that you can run both FTS and a communications application on the same computer, and use FTS to monitor the conversation between the application and another device. Since internal modems look like COM ports to the computer, FTS can monitor data passing through an internal modem as well as a regular COM port. There are some limitations on using Spy. FTS uses a custom version of the standard serial device driver in order to Spy on COM ports and internal modems. This means that FTS must be started before the communications application to ensure that FTS's driver is being used by both FTS and the application. As a corollary, the port you are monitoring must normally use the standard serial driver, and not a custom driver. To enter Spy, you must follow the steps below in the order given. For SPY: 1. Start FTS. FTS must be started before the application you are monitoring is started, or the application will not use the correct driver and FTS will not be able to monitor the port. 2. Start the application. Be sure to have the application use the same COM port as the one chosen for FTS. 3. Monitor data. 4. Close your application when finished. If you want to monitor another application, repeat steps Close FTS. For Serialtest Async + Spy: Start FTS. FTS must be started before the application you are monitoring is started, or the application will not use the correct driver and FTS will not be able to monitor the port. 1. From the Options menu on the Control window, choose Hardware Settings. 2. Click on the radio button labeled Spy. 3. Select the COM port you want to monitor. 4. Exit the Hardware Settings window. 5. Start the application. Be sure to have the application use the same COM port as the one chosen for FTS. 6. Monitor data. 7. Close your application when finished. If you want to monitor another application, repeat steps Close FTS. It is important to follow the steps in the order given because this ensures that FTS's driver is the one being used by the application you are monitoring. Please note that FTS's driver is designed to behave like the standard serial driver when used by any other application. However, because it is not the standard serial driver, total compatibility cannot be guaranteed. See The FTS Driver for more information. The use of FIFO buffers may cause incorrectly sequenced data when in Spy. See FIFOs and Spy for more information. 5-May FTS4BT-UM-001

108 Monitoring Internal Ports Spy Mode Settings on the I/O Settings Window Most of the settings on the I/O Settings window are grayed out in Spy Mode because they will be determined by the application using the COM port. FTS will update these settings to reflect changes made by the application, allowing you to see the actual settings being used by the application. If you are monitoring framed data, you will need to choose a protocol stack in order to ensure that the data is framed correctly. You can also choose whether to monitor both sides of the circuit, or just the DTE or DCE side. You also have the option of choosing to monitor all incoming data, regardless of whether the application you are monitoring is running, or you can choose to monitor only when the application has opened the COM port and is actively communicating through the port. By default, FTS will monitor all data, all the time, which means that FTS may show captured data before you have opened your application. To monitor the port only when the application has opened it, check the Capture Only When Spied Port is Open box on the Set I/O Configuration window. FIFOs and Spy The 8250 UART generates an interrupt every time a byte enters the UART. If the UART is receiving data at a high rate of speed, it will generate frequent interrupts which the central processor will have to deal with, leaving the central processor less time for other tasks. If the central processor cannot retrieve the bytes quickly enough, data will be lost as new data overwrites the information stored in the UART. The solution to this problem was the development of new UART chips that had buffers. The UART, one of the most common UARTs currently in use, has a 16 byte buffer. The buffer operates on the First In, First Out (FIFO) principle. The first byte in the buffer will be the first byte to go out of the buffer. The buffer allows the UART to store bytes until a specified number of bytes have come in, at which point it generates an interrupt telling the central processor to retrieve the data. The ability to store bytes means that the UART is not generating as many interrupts, giving the central processor more time for other tasks. There are two problems with the buffering system and Spy. One is that data may not be timestamped accurately, and the other is that control signal states may not be correct. FTS timestamps the byte and records the state of the control signals at the time it retrieves the byte from the UART. If the buffers are being used, an interrupt will not be generated until several bytes have already come in, possibly resulting in incorrect timestamps and signal states. FTS solves the problem by telling the UART to generate an interrupt every time a byte comes in, but FTS cannot do this when operating in Spy. In Spy, the application being monitored has control of the UART and specifies how the buffers will be used. The result is that the captured data may not be completely accurate. If you are using Spy, we recommend turning off the FIFOs on the UART if accurate recording of timestamps or control signal states is important. How to Turn Off the FIFO Buffers in Windows Click on the Start button and choose Settings -> Control Panel. 2. Double-click on the System control panel icon. 3. Click on the Hardware tab, then click the Device Manager button (2nd button in the middle section). 5-May FTS4BT-UM-001

109 Monitoring Internal Ports 4. Expand the Ports section, and double-click on the port you want to change to open the Port Properties. 5. Click on the Port Settings tab, followed by the Advanced button at the bottom of the screen. 6. Uncheck the box labeled Use FIFO buffers (requires compatible UART). 7. Click OK on all windows to close the windows. 8. Follow this same process to turn the FIFOs back on. 5-May FTS4BT-UM-001

110 System Settings and Program Options System Settings and Program Options System Settings Open the System Settings window by choosing System Settings from the Options menu on the Control window. To enable a setting, click in the box next to the setting to place a checkmark in the box. To disable a setting, click in the box to remove the checkmark. When viewing a capture file, settings related to data capture are grayed out. Common Options Wrap Buffer/File When enabled, FTS will wrap the buffer when it becomes full. The oldest events will be moved out of the buffer to make room for new events. Any events moved out of the buffer will be lost. This option also applies to capture files. When disabled, FTS will pause capture when the buffer becomes full. Either reset the buffer or close your capture file to continue. Timestamping Options Opens the Timestamping Options window. Options include enabling or disabling timestamping and choosing capture and display resolutions. Automatically Save Imported Capture Files in FTS Format When enabled, FTS will automatically save imported capture files in the FTS capture file format. See Loading Imported Files for more information. Automatically Restart Capturing After 'Clear Capture Buffer' When the capture buffer is cleared, FTS displays a "Clear Capture Buffer" message asking if you want to save the buffer. If the Automatically Restart feature is enabled, FTS will restart capture to the buffer immediately after the "Clear Capture Buffer" warning goes away. Start up Opens the Start up Options window. Start up options let you choose whether to start data capture immediately on opening FTS. Advanced Opens the Advanced System Options window. The Advanced Settings should only be changed on advice of technical support. Buffer/File Options Capture Buffer Size (in K) Enter the maximum size of the capture buffer (data captured in memory). If you enter a number larger than the maximum allowable size, FTS will warn you and automatically set the size to the maximum allowable size. File Size (in K) Enter the maximum size of the capture file. If you enter a number larger than the maximum allowable size, FTS will warn you and automatically set the size to the maximum allowable size. Note: In both cases, FTS does not actually use 100% of available memory or disk space. By default, FTS will limit the maximum size of the buffer or file to 50% of the available resources. We strongly recommend not changing this percentage unless absolutely necessary. If you do need to use more resources, you can change the maximum percentage used in the Advanced Options window. Click on the Advanced button on the System Settings window. If you want to change the maximum percentage for the buffer, find the setting for Max Percent of Available Virtual Memory Used for Capture Buffer. If you want to change the maximum percentage for the file, find the setting for Max Percent of Free Disk Space for Capture File. Both of these settings are expressed as a percentage. We strongly recommend not setting the Capture Buffer Size and File Size options to 100%, as this will take all your system resources, leaving none for any other application. 5-May FTS4BT-UM-001

111 System Settings and Program Options Capture to one file When this option is selected, FTS will capture data to a single file and ask for a file name each time data capture is started. This option takes effect when the "Capture to File" button is clicked or on startup if the "Start capturing to a file immediately" or "Start capturing immediately to the following file" options are selected in the Start Up Options window. Capture to this series of files This option will let you capture to a series of files. The size of each file will be no larger than the number given in File Size (in K). The name of each file is the name you give it in the Name box followed by the date and time and a number. The date and time are the time the series was opened, and the number will increment with each file. This guarantees unique file names. Set the maximum number of files in the series in the Maximum number of files box. The next file will be started when the currently open file is full. If you want to start a new file on a periodic basis, check the box next to or after and put in the number of hours after which a new file will be started. Note that if the currently open file becomes full before the time limit has been reached, a new file will be opened immediately rather than lose data. Capturing will stop if the maximum number of files has been used unless Wrap Files has been checked. If Wrap Files has been checked FTS will erase the oldest file in the series and make a new file. Advanced System Options These parameters affect fundamental aspects of the software, and it is unlikely that you will ever have to change them. If you do change them and need to return them to their original values, the default value is listed in parentheses to the right of the value box. Most technical support problems are not related to these parameters, and as changing them could have serious consequences for the performance of FTS, we strongly recommend contacting technical support before changing any of these parameters. To access the Advanced System Options, go to the Control window, and choose System Settings from the Options menu. On the System Settings window, click the Advanced button. Max Percent Of Free Disk Space for Capture File This setting determines what percentage of free hard drive space can be used for the capture file. By default, FTS will limit the maximum size of the capture file to 50% of the available space on the hard drive. If you need to create a larger capture file than the current settings allow, increase this percentage. Then go back to the System Settings window and increase the maximum file size. Max Percent Of Available Virtual Memory Used for Capture Buffer This setting determines what percentage of available virtual memory can be used for the capture buffer. By default, FTS will limit the maximum size of the buffer to 50% of the available virtual memory. Increasing this percentage will give you a larger capture buffer, but will leave less virtual memory available for other applications. Driver Receive Buffer Size in Operating System Pages This is the size of the buffer used by the driver to store incoming data. This value is expressed in operating system pages. Driver Action Queue Size In Operating System Pages This is the size of the buffer used by the driver to store data to be transmitted. This value is expressed in operating system pages. 5-May FTS4BT-UM-001

112 System Settings and Program Options Capture Buffer Read Cache Size In Kbytes Sets the size of the capture buffer cache. This setting is important when reading data. A larger buffer may mean faster read times. Capture File Write-Through Cache Size In Pages Sets the size of the capture buffer write cache. This setting is important when writing data to disk. Return Unused Space in Capture File When Closing (Yes/No answer) When FTS opens a capture file, it allocates as much disk space as it needs for the maximum capture file size. When the capture file is closed, FTS gives back any unused space. This process can take some time if the maximum capture file size is large. This setting is the threshold that determines if we give back unused space when the file is closed. The default value of "checked" means that FTS will always give back unused space. If unchecked, FTS will not return unused space, which may result in very large, mostly empty capture files. Maximum Number of Bytes Decoded Per Frame This is the largest frame size that FTS will attempt to decode. This is used to prevent FTS from attempting to decode very large bad frames. This number should be large enough to ensure that the largest reasonable frame is handled completely. Maximum Number of Bytes Used to Store Supplementary Capture File Information Sets the amount of space used to store supplementary information in the capture file. The default value is bytes. Capture Buffer System Page Size Multiplier Data in a capture file is indexed by pages to allow for faster retrieval. The page size multiplier determines how often the file is indexed. The default value of 1 means that the capture file is indexed once every page, or once every 4K. Non-Realtime Event Queue Size This is the queue for all non-realtime events. Changing Default File Locations FTS puts user files in specific locations by default. Capture files are placed in the My Capture Files directory and configurations are put in My Configurations. Follow the steps below to change the default locations. 1. Choose Directories from the Options menu on the Control window to open the File Locations window. 2. Select the default location you wish to change. 3. Click Modify. 4. Browse to a new location. Click OK. 5. Click OK when finished. Start Up Options To open this window Choose System Settings from the Options menu on the Control window. On the System Settings window, click the Start Up button. 5-May FTS4BT-UM-001

113 System Settings and Program Options Choose one of the options to determine if FTS starts data capture immediately on starting up or not. Don't start capturing immediately. This is the default setting. FTS begins monitoring data but does not begin capturing data until the Start Capture to Buffer or Start Capture to Disk icons on the Control, Event Display or Frame Display windows are clicked. Start capturing to buffer immediately. When FTS starts up, it will immediately begin data capture to the buffer. This is the equivalent of clicking the Start Capture to Buffer icon. Start capturing to a file immediately. When FTS starts up, it will immediately open a capture file and begin data capture to it. This is the equivalent of clicking the Start Capture to Disk icon. The file is given a name based on the settings for capturing to a file or series of files in the System Settings window. Start capturing immediately to the following file: Enter a filename in the box below this option. When FTS starts up, it will immediately begin data capture to that file. If the file already exists, the data in it will be overwritten. Timestamping Enabling/Disabling Timestamping 1. Choose System Settings from the Options menu on the Control window, and click the Timestamping Options button, or click the click the Timestamping Options icon from either the Event Display or Statistics window. 2. Check the Store Timestamps box to enable timestamping. Remove the check to disable timestamping. If you disable timestamping, you will not be able to do delta or rate calculations. Changing the Timestamping Resolution 1. Choose System Settings from the Options menu on the Control window, and click the Timestamping Options button, or click the click the Timestamping Options icon from either the Event Display or Statistics window. 2. Go to the Capture Options section of the window. 3. Change the resolution listed in the Storage Resolution box. Note that if you change the resolution, you will need to exit FTS and restart in order for the change to take effect. This option affects the resolution of the timestamp stored in the capture buffer or capture file. The default timestamp is 10 milliseconds. This value is determined by the operating system and is the smallest "normal" resolutions possible. It is also possible to use "high resolution" timestamping. High resolution timestamp values are marked by an asterisk as high resolution in the drop down list. Performance and Capture File Issues when using high resolution timestamps 5-May FTS4BT-UM-001

114 System Settings and Program Options Switching Between Relative and Absolute Time 1. Choose System Settings from the Options menu on the Control window, and click the Timestamping Options button, or click the click the Timestamping Options icon from either the Event Display or Statistics window. 2. Go to the Display Options section at the bottom of the window and find the Display Relative Timestamps checkbox. 3. Check the box to switch the display to relative timestamps. Remove the check to return to absolute timestamps. Display Relative Timestamps will show the timestamp as the amount of time that has passed since the first byte was captured. It works just like a stop watch in that the timestamp for the first byte is 0:00: and all subsequent timestamps increment from there. The timestamp is recorded as the actual time, so you can flip back and forth between relative and actual time as needed. The options in this section affect only how the timestamps are displayed on the screen, not how the timestamps are recorded in the capture file. Displaying Fractions of a Second 1. Choose System Settings from the Options menu on the Control window, and click the Timestamping Options button, or click the click the Timestamping Options icon from either the Event Display or Statistics window. 2. Go to the Display Options section at the bottom of the window, and find the Number of Digits to Display box. 3. Click on the arrows to change the number. You can display between 0 and 6 digits to the right of the decimal point. The options in this section affect only how the timestamps are displayed on the screen, not the resolution used to capture the data. Timestamping Options The Timestamping Options window lets you enable or disable timestamping, and change the resolution of the timestamps for both capture and display purposes. To open this window Choose System Settings from the Options menu on the Control window, and click the Timestamping Options button, or click the Timestamping Options icon from either the Event Display or Statistics window. Performance Issues For High Resolution Timestamps There are two things to be aware of when using high resolution timestamps. The first is that high resolution timestamps take up more space in the capture file because more bits are required to store the timestamp. Also, more timestamps need to be stored than at normal resolutions. The second issue is that using high resolution timestamping may affect performance on slower machines For example, if 10 bytes of data are captured in 10 milliseconds at a rate of 1 byte per millisecond, and the timestamp resolution is 10 milliseconds, then only one timestamp needs to be stored for the 10 bytes of data. If the resolution is 1 millisecond, then 10 timestamps will need to be stored, one for each byte of data. If you have two capture files, both of the same size, but one was captured using normal resolution timestamping and the other using high 5-May FTS4BT-UM-001

115 System Settings and Program Options resolution, the normal resolution file will have more data events in it, because less room was used to store timestamps. You can increase the size of your capture buffer or file in the System Settings. 5-May FTS4BT-UM-001

116 Frame Decoder Frame Decoder Frame Decoder For information on Frame Decoder see the Frame Decoder Manual. 5-May FTS4BT-UM-001

117 Technical Info and Support Technical Info and Support Contacting Technical Support Technical support is available in several ways. The online help system provides answers to many user related questions. Frontline s website has documentation on common problems, as well as software upgrades and utilities to use with our products. Web:\tab click on Tech Support\par \tab tech_support@fte.com If you need to talk to a technical support representative, support is available between 9am and 5pm, U.S. Eastern time, Monday through Friday. Technical support is not available on U.S. national holidays. Phone: +1 (434) Fax: +1 (434) Technical Information The following information is provided to assist you with troubleshooting problems both with FTS and communications circuits. Performance Notes As a software-based product, the speed of your computer s processor affects FTS s performance. Overrun errors and buffer overflows are indicators that FTS is unable to keep up with the data. The information below describes what happens to the data as it comes in the port, what the two types of errors mean, and how various aspects of FTS affect performance. Also included are suggestions on how to improve performance. Data captured by the serial port first goes into the buffer of the UART chip of the serial port. The UART generates an interrupt, which tells the FTS driver to check the port. The driver takes the data from the UART and counts each byte as they are put into the driver s own buffer. The driver tells FTS that data is ready to be processed. FTS takes the data from the driver s buffer and puts the data into the capture buffer. Overrun errors occur when the data in the buffer of the UART is not retrieved before new data comes in. In this case, FTS knows that it has lost information but it does not know how much. FTS indicates overrun errors in the Event Display screen by marking a byte near the overrun in red. You can search for overrun errors using the Find feature. Driver buffer overflow errors occur when the data in the buffer of the driver is not retrieved before new data comes in. Since the driver counts the bytes as it retrieves them from the UART, it not only knows that it has lost data, it also knows how much. Buffer overflows are indicated in the Event Display screen by a plus sign within a circle. Clicking on the buffer overflow symbol will show how many events have been lost. The Statistics window is an good place to check for buffer overflow errors. Both overrun errors and buffer overflows indicate that data is coming in too quickly for FTS to process. There are several things that you can do to try and solve this problem. 1. In the Hardware Settings window, click on Use Windows Device Manager Settings. This means that Windows will not generate an interrupt every time a byte comes in, but rather will wait until several bytes have accumulated in the UART buffer before telling FTS to retrieve them. This will increase performance at the cost of timestamp accuracy, since all the bytes in a group will have the same timestamp regardless of when they actually arrived at the UART. Some control signal changes may also be lost. 5-May FTS4BT-UM-001

118 Technical Info and Support 2. FTS s number one priority is capturing data; updating windows is secondary. However, updating windows still takes a certain amount of processor time, and may cause FTS to lose data while the window is being updated. Some windows require more processing time than others, because the information being displayed in them is constantly changing. Refrain from displaying data live in the Event Display and Frame Display windows. Try closing the Breakout Box and Statistics windows. FTS can capture data with no windows other than the Control window open. 3. Increase the value of the window refresh rate for any windows you have open while capturing data. This will decrease the frequency of window updates, leaving more time for capturing data. Changing the refresh rate can be done from the Options screen in each window. 4. If you suspect or know that your circuit has control signals that are changing very rapidly, go to the Hardware Settings window and choose to Disable Control Signal Interrupts. This will prevent FTS from capturing control signal changes on an interrupt basis, giving more time for capturing byte data. (You can use the counters in the Breakout Box to help determine if a control signal is changing quickly.) FTS will still note the state of the control signals whenever a byte is captured. You must restart FTS for this change to take effect. 5. Close all other programs that are doing work while FTS is running. Refrain from doing searches in the Event Display window or other processor intensive activities while FTS is capturing data. 6. Timestamping takes up processor time, primarily not in timestamping the data, but in writing the timestamp to the buffer or file. Try turning off timestamping from the Timestamping Options window. 7. Capture to the buffer instead of capturing to disk. Writing data to the buffer is faster than writing to disk, allowing more time for capturing data. 8. Change the size of the driver buffer. This value is changed from the Advanced System Settings. Go to the Control Window and choose System Settings from the Options menu. Click on the Advanced button. Find the value labeled Driver Receive Buffer Size in Operating System Pages. Take the value listed there and double it. NOTE: This procedure might help buffer overflow errors, but will not help overrun errors. 9. Slow down the speed of the communications circuit, if possible. If you are still experiencing overruns and/or buffer overflows after trying all of the above options, then you may need to use a faster PC. Note Concerning Ring Indicator The following information applies only if you are in Spy Mode or Source DTE, No Cables Mode. When using the cables supplied with FTS to capture or source data, Ring Indicator is routed to a different pin which generates interrupts normally. There is a special case involving Ring Indicator (RI) and computers with 8250 UART s or UARTs from that family where the state of RI may not be captured accurately. Normally when a control signal changes state from high to low or low to high, an interrupt is generated by the UART, and FTS goes to see what has changed and record it. Ring Indicator works a little differently. An interrupt is generated when RI changes from high to low, but not when RI changes from low to high. If Ring Indicator changes from low to high, FTS will not know that RI has changed state until another event occurs that generates an interrupt. This is simply the way the UART works, and is not a deficiency in the software. To minimize the chance of missing a Ring Indicator change, FTS polls the UART every millisecond to see if RI has changed. It is still possible for FTS to miss a Ring Indicator change if RI and only RI changes state more than once per millisecond. 5-May FTS4BT-UM-001

119 Technical Info and Support UARTs in the 8250 family include 8250s, 16450s, 16550s and variants. If you have any questions about the behavior of your UART and Ring Indicator, please contact technical support. RS-232 Pin-outs 25-pin connector Pin Name Abbreviation 1 Frame Ground FG 2 Transmit Data TxD 3 Receive Data RxD 4 Request To Send RTS 5 Clear to Send CTS 6 Data Set Ready DSR 7 Signal Ground GND 8 Carrier Detect CD or DCD 20 Data Terminal Ready DTR 22 Ring Indicator RI 9-pin connector Pin Name Abbreviation 1 Carrier Detect CD or DCD 2 Receive Data RxD 3 Transmit Data TxD 4 Data Terminal Ready DTR 5 Signal Ground GND 6 Data Set Ready DSR 7 Request To Send RTS 8 Clear to Send CTS 9 Ring Indicator RI 5-May FTS4BT-UM-001

120 Technical Info and Support Event Numbering This section talks about how events are numbered when they are first captured and how this affects the display windows in FTS. The information in this section applies to frame numbering as well. When FTS captures an event, it gives the event a number. If the event is a data byte event, it receives a byte number in addition to an event number. There are usually more events than bytes, with the result is that a byte might be listed as Event 10 of 16 when viewing all events, and Byte 8 of 11 when viewing only the data bytes. The numbers assigned to events that are wrapped out of the buffer are not reassigned. In other words, when event number 1 is wrapped out of the buffer, event number 2 is not renumbered to event 1. This means that the first event in the buffer may be listed as event of 16334, because events have been wrapped out of the buffer. Since row numbers refer to the event numbers, they work the same way. In the above example, the first row would be listed as 2d00 (which is hex for ) The advantage of not renumbering events is that you can save a portion of a capture file, send it to a colleague, and tell your colleague to look at a particular event. Since the events are not renumbered, your colleague s file will use the same event numbers that your file does. BPF Copyright Notice This copyright applies to code used in the filter feature. Filtering functionality in FTS is based on Berkeley Packet Filtering (BPF), which is implemented in the UNIX program tcpdump. Copyright (c) 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997 The Regents of the University of California. All rights reserved. This code is derived from the Stanford/CMU enet packet filter, (net/enet.c) distributed as part of 4.3BSD, and code contributed to Berkeley by Steven McCanne and Van Jacobson both of Lawrence Berkeley Laboratory. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California, Berkeley and its contributors. 4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR 5-May FTS4BT-UM-001

121 Technical Info and Support OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Clear Capture Buffer Warning If you clear the capture buffer and haven't saved it, FTS asks you if you want to save the buffer before clearing. The three options are: Save First - asks you for a file name, saves the buffer and then clears it. Clear Buffer - clears the buffer without saving it. Cancel - returns to FTS without clearing the buffer. If you don't want to see the warning again, check the "Don't show this warning again when clearing buffer" box. The option is remembered only for the current FTS session. If you exit FTS, you will need to check the box again the next time you run FTS. The Serial Driver The FTS Driver FTS uses custom versions of the standard Windows serial drivers in order to capture data. How the drivers are loaded differs depending on the operating system. Click on the appropriate link below to find out more information for your operating system. Windows 2000 Driver FTS uses a custom driver which is compatible with serial.sys, the standard serial driver supplied with Windows The FTS driver is called serialnt.fts and is found in the C:\\Program Files\\Frontline Test System II\\[Product Name]\\Executables\\Core directory. Windows 2000 has a feature called System File Checker that prevents system critical files from being replaced. FTS uses a custom version of the standard serial driver in order to capture data with accurate timestamps and control signal information. In Windows 95/98 and NT, FTS swaps its driver in on startup and swaps it back out when exiting. The problem is that Windows 2000 considers the serial driver a system critical file, and will not allow FTS to replace it with the FTS serial driver. For Windows 2000, the solution is to make a backup copy of the Windows 2000 serial driver and then put the FTS driver in place and leave it there. The installation program for FTS knows how to do this. The FTS driver is compatible with the Windows 2000 driver and provides the same functionality, except for power management. Installing Frontline's Driver At the end of the FTS installation, a message box will appear saying that FTS has detected that it is being installed on a Windows 2000 system, and asking if you want to install the FTS serial driver. In order to run FTS serial products, you will need to choose Yes and allow FTS to install the FTS serial driver. You will need to reboot your computer twice before you can use FTS. The installation program will prompt you through the process. If you need to install the serial driver after FTS has already been installed, go to the Start button and choose Programs -> [Product name or Name Selected by User at Installation] -> Windows 2000 Serial Driver Support -> Install FTS Serial Driver. This will install the serial driver and prompt you to reboot. 5-May FTS4BT-UM-001

122 Technical Info and Support Handy Character Tables ASCII Codes EBCDIC Codes 5-May FTS4BT-UM-001