5.1 USB Bus Analyzers Integration

To further assist you in the testing and debugging process, USBTester enables you to view the output of selected USB bus analyzers via the test application.
The supported analyzers are listed in the following sections.

To integrate USBTester with your bus analyzer, you need to check the Analyzer Capture check-box in the Test Execution form and select your desired analyzer before starting the tests, as indicated in section 3.4. If you have selected this option, when the tests execution is completed you can view the analyzer capture for any of the tests by selecting the test in the Tests pane and clicking the View analyzer capture for selected test button at the bottom of the Test Execution form. This will open the analyzer's application with the capture of the test's traffic.

5.1.1 Ellisys's USB Explorer 200 USB 2.0 Protocol Analyzer

USBTester supports integration with Ellisys's USB Explorer 200 USB 2.0 protocol analyzer, available from Jungo: http://www.jungo.com/st/usb_explorer.html.

To use this analyzer with the test application, follow these guidelines:

1. Install version 2.2.3300 or later of the Ellisys software.

2. Connect the analyzer to a separate USB host controller - i.e. not to the controller used for the USBTester tests.

5.1.2 Ellisys's USB Tracker 110 USB 1.1 Protocol Analyzer

USBTester supports integration with Ellisys's USB Tracker 110 USB 1.1 protocol analyzer, available from Jungo: http://www.jungo.com/st/usbtracker_a.html.

To use this analyzer with the test application, follow these guidelines:

1. Install version 2.2.3300 or later of the Ellisys software.

2. Connect the analyzer to a separate USB host controller - i.e. not to the controller used for the USBTester tests.

3. Connect the analyzer to the host controller via a high-speed hub, as explained in section 2.1.1.

5.1.3 LeCroy's USBMobile Hi-Speed Bus and Protocol Analyzer

USBTester supports integration with LeCroy's USBMobile HS (Hi-Speed) bus and protocol analyzer, version 2.50: http://www.lecroy.com/tm/products/ProtocolAnalyzers/usbhs.asp?menuid=67.

When using this analyzer with the test application, note the following:

1. Before executing the tests, verify that the USBMobile HS application is not running.

2. The support for the USBMobile HS analyzer is currently in a beta stage. Known issues associated with the beta version of this feature include:
   • When closing the USBMobile HS application after viewing the analyzer's USBTester tests capture, you will see a message regarding connection of an automation client. This does not indicate a problem. When the messages appears, simply select OK.

   • On occassion, the USBMobile HS application may take too long to start, and as a result the capture will not be done. If this happens, close the analyzer application and rerun the test.

5.1.4 Total Phase's Beagle USB 480 Analyzer

USBTester supports integration with Total Phase's Beagle USB 480 protocol analyzer, version 2.00: http://www.totalphase.com/products/beagle/usb480/.

To use this analyzer with the test application, follow these guidelines:

1. Modify the USBTester BeagleConfig.xml file to correctly describe your local setup and desired usage options.
   The configuration file is located in the <USBTester installation directory>Plugins directory.

   The default USBTester installation directory is C:Program FilesJungoUSBTester, therefore by default the file will be found at C:Program FilesJungoUSBTesterPlugins.

   The BeagleConfig.xml configuration file contains the following values:

   host:

   The host name or IP of the computer executing the Beagle capture application (Beagle-GUI.exe).

   port:

   The TCP port number for communication with the Beagle application.
   This must be the same port number that you provide as an argument to the Beagle application, as explained in step #2 below.

   device-port:

   The number of the Beagle analyzer to use (zero-based).
   This is the same value that you provide to the Beagle application when clicking the application's Connect button.

   timeout:

   Timeout period, in milliseconds, for awaiting the return of TCP transfers performed to/from the Beagle application.
   This is an optional parameter. The default timeout, which is used when no timeout is set in the configuration file, is 1,000 ms.

2. Start the Beagle application with the argument -r <port-number>.
   This must be done before entering the USBTester test application's Test Execution form.