The information contained in this document has been carefully checked and
is believed to be reliable. However, no responsibility can be assumed for
inaccuracies that may not have been detected.
CATC reserves the right to revise the information presented in this
document without notice or penalty.
This document may be printed and reproduced without additional
permission, but all copies should contain this copyright notice.
FCC Conference Statement
This equipment has been tested and found to comply with the limits for a
Class A digital device and an intentional radiator, pursuant to Part 15 of the
FCC Rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a
commercial environment. This equipment generates, uses, and can radiate
radio frequency energy and, if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely
to cause harmful interference in which case the user will be required to
correct the interference at their own expense. The end user of this product
should be aware that any changes or modifications made to this equipment
without the approval of CATC could result in the product not meeting the
Class A limits, in which case the FCC could void the user's authority to
operate the equipment.
Important Notice: To comply with FCC RF exposure requirements
(sections 1.1307 and 1.310 of the Rules) only the antenna supplied by
CATC must be used for this device. The antenna must be located at least 20
cm away from all persons.
EU Conference Statement
This equipment complies with the R&TT Directive 1999/5/EC. It has been
tested and found to comply with EN55022:1994/A1:1995/A2:1997 Class A,
EN61000-4-2:1995, EN61000-4-3:1995, EN61000-4-4:1995,
EN61000-4-5:1995, EN61000-4-6:1995, EN61000-4-11:1994,
EN61010-1:1993, and ESTI EN 300 328-1 V1.2.2 (2000-07).
The CATC BTTracer™ Protocol Analyzer is a member in CATC's
industry-leading line of high performance, serial bus protocol analyzers.
PrecededbyCATC’sUSBChief™ and IEEE 1394 FireInspector™
Analyzers, BTTracer has been designed using the same modular software
and hardware architecture that made its predecessors highly successful in
the serial bus protocol analyzer market worldwide.
1.1 Bluetooth™ Overview
The Bluetooth™ wireless technology is set to revolutionize the personal
connectivity market by providing freedom from wired connections. It is a
specification for a small-form factor, low-cost radio solution providing links
between mobile computers, mobile phones and other portable handheld
devices, and connectivity to the internet.
The Bluetooth™ Special Interest Group (SIG), comprised of leaders in the
telecommunications, computing, and network industries, is driving
development of the technology and bringing it to market. The Bluetooth™
SIG includes promoter companies 3Com, Ericsson, IBM, Intel, Lucent,
Microsoft, Motorola, Nokia and Toshiba, and more than 2500 SIG
members.
Bluetooth™ is a radio technology specification designed to transmit both
voice and data wirelessly, providing an easier way for a variety of mobile
computing, communications and other devices to communicate with one
another without the need for cables. Bluetooth™ could make possible what
is being called the personal-area network by allowing users to transmit small
amounts of data at 1M bit/sec with a range of 10 to 100 meters, depending
the power of the radio, over the 2.4-GHz radio frequency. The key benefits
of the Bluetooth™ technology are robustness, low complexity, low power
and low cost. Bluetooth™ employs a rapid frequency hopping mechanism
to minimize the effects of ‘collisions’ with other protocols and devices
operating in the same frequency band. Mechanisms exist for a Bluetooth™
device to determine all devices in range as well as to request connection to
a piconet as either a master or a slave.
Please refer to the Bluetooth™ Specification, version 1.1 for details on the
protocol. The Bluetooth™ specification is available from the Bluetooth™
SIG at its web site http://www.bluetooth.org/
The BTTracer Protocol Analyzer is designed as a stand-alone unit that can
be easily configured and controlled by a portable or desktop PC connected
via its USB port. BTTracer provides customers with the familiar ‘CATC
Trace’ user interface that is the de facto industry standard for documenting
the performance of high-speed serial protocols.
BTTracer supports the functionality required to analyze all levels, including
the baseband, of the Bluetooth™ wireless protocol. The featured Radio
Interface allows users to probe and analyze transactions at the lowest level
within the Bluetooth™ architecture. By creating this "Point of Observation"
or probing point within the radio level packet view, the user can analyze all
levels of the protocol stack.
BTTracer is a non-intrusive testing tool for Bluetooth™ piconets providing
network traffic capture and analysis. Hardware triggering allows real-time
events to be captured from a piconet. Hardware filtering allows the filtering
out of fields, packets, and errors from the recording. Filtering allows users
to focus recordings on events of interest and to preserve recording memory
so that the recording time can be extended.
Recorded data is presented in colored graphics in a trace viewer application.
This application has advanced search and viewing capabilities that allow the
user to quickly locate specific data, errors and other conditions, thereby
focussing the user’s attention on events of interest.
The BTTracer Protocol Analyzer functions with any personal computer
using the Windows 98, Windows 98SE, Windows 2000, Windows NT 4.0,
Windows ME, or Windows XP operating systems and equipped with a
functional USB interface. For an updated set of system requirements for the
host machine, please refer to the readme file.
The Analyzer is configured and controlled through a personal computer
USB port. It can be used with portable computers for field service and
maintenance as well as with desktop units in a development environment.
The Analyzer is easily installed by connecting a cable between the
computer’s USB port and the Analyzer’s USB port.
Sample Bluetooth™ Piconet with BTTracer Protocol Analyzer
BTTracer provides on-the-fly detection of and triggering on such events as
Packet Headers and Errors. Whether recording manually or with a specified
trigger condition, BTTracer continuously records the bus data in a
wrap-around fashion until manually stopped or until the Trigger Event is
detected and a specified post-Trigger amount of bus data is recorded.
Upon detection of a triggering event, the analyzer continues to record data
up to a point specified by the user. Real-time detection of events can be
individually enabled or disabled to allow triggering on events as they
happen. This includes predefined exception or error conditions and a
user-defined set of trigger events. The unit can also be triggered by an
externally supplied signal. An external DB-9 connector provides a path for
externally supplied data or timing data to be recorded along with bus traffic.
This DB-9 connector also provides a path for BTTracer to transmit
externally two control, timing, or recovered signals for purposes of probing
and use by other circuitry.
The BTTracer software provides powerful search functions that enable
investigation of particular events and allow the software to identify and
highlight specific events. In addition to immediate analysis, you can print
any part of the data. Use the Save As feature to save the data on disk for later
viewing. The program also provides a variety of timing information and
data analysis reports.
1.3 Automation
The BTTracer software includes an Application Program Interface (API) for
developing testing programs and scripts in C++ and Visual Basic. The API
reproduces most of the commands embodied in the BTTracer trace viewer
software. This API allows users to automate procedures that otherwise have
to be run manually via the trace viewer software. The Automation API can
be run locally on the PC attached to BTTracer or remotely over a network
connection.
For further details, download the BTTracer Automation ApplicationProgramming Interface User’s Manual from the CATC website:
http://www.catc.com/support.html
1.4 Features
General
•Flexible design - reconfigurable hardware for future enhancements.
•User friendly - the Graphical User Interface software of BTTracer
Analyzer is designed to be consistent with the ‘CATC Trace’ using color
and graphics to display Bluetooth™ traffic.
•Radio Level Point of Observation and Capture - traffic capture at the
Radio Level for comprehensive analysis.
•Complies with Bluetooth™ v1.1 specification.
•Supports point-to-point and point-to-multipoint Bluetooth™ piconets.
•Supports both 79 frequency hop and 23 frequency hop standards.
•Automatic tracking of changes in the hopping scheme.
•Compliant with FCC class A requirements / meets all CE mark
requirements.
•One year warranty and hot-line customer support.
Physical Components
Note For an updated description of requirements for the host machine, please refer to the
readme file.
•Trace viewer software support for all of the above plus Windows 95.
•Recording memory of 128MB - enough to record twenty five minutes of
high volume traffic.
Display Options
•Analyzes and displays a transaction-level view of piconet traffic with
accurate time-stamps and frequency hop information.
•Software analysis and data presentation at several protocol levels:
Baseband, LMP, L2CAP, SDP, RFCOMM, TCS, OBEX, HDLC, BNEP,
PPP, AT, and HID Commands.
Recording Options
•Flexible advanced triggering capabilities including - multiple triggering
modes, selective views, timing analysis, search functions, protocol
packet errors, transaction errors, packet type and destination device, data
patterns, or any of these trigger types in combination.
•User defined trigger position.
•Support for various piconet characteristics by enabling the user to
configure the synchronization method and recording parameters.
•Real-time hardware filtering of captured traffic for optimizing analyzer
memory usage.
Traffic Generation
Traffic generation capability is provided by BTTrainer.
CATC’s BusEngine™ Technology is at the heart of the new BTTracer
Analyzer. The revolutionary BusEngine core uses state-of-the-art EPLD
technology and incorporates both the real-time recording engine and the
configureable building blocks that implement data/state/error detection,
triggering, capture filtering, external signal monitoring and event counting
& sequencing. And like the flash-memory-based firmware that controls its
operation, all BusEngine logic is fully field upgradeable, using
configuration files that can be downloaded from the CATC Website.
The BTTracer Protocol Analyzer components and software are easily
installed and quickly ready to run on most Windows-based personal
computer systems. You can begin making Bluetooth™ recordings after
following these initial steps. However, if you are new to personal computers
and protocol analyzers, or if you are unsure about what to do after reading
the Quick Installation instructions, or if your analyzer does not work after
you follow these instructions, read through the subsequent sections in this
manual.
2.1 Setting Up the Analyzer
Step 1Attach the Antenna to the ANT connection point. The
antenna should point up.
Step 2Connect the AC power cable to the rear of the analyzer.
Step 3Turn on the power switch on the rear of the analyzer.
Step 4Insert the BTTracer CD into the CD ROM drive of the PC
that will be administering the Analyzer. If you prefer to
install from diskette, insert the first BTTracer diskette (Disk
1 of 6) into the floppy disk drive.
Step 5Connect the USB cable between the USB port on the back of
the analyzer and a USB port on the analyzing PC.
Step 6Follow Windows on-screen Plug-and-Play instructions for
the automatic installation of the BTTracer Analyzer as a
USB device on your analyzing PC (the required USB files
are included on the BTTracer CD and the first BTTracer
diskette).
2.2 Installing the Software
Step 1From the setup directory, run setup, and follow the on-screen
instructions to install the BTTracer application on the
analyzing PC hard disk.
Step 2To start the application, launch the CATC BTTracer
program from the Start Menu:
Start>Programs>CATC>BTTracer.
After installing and launching the software, you can test BTTracer by
creating a recording of a General Inquiry. In this test, BTTracer will issue
a General Inquiry that asks local devices to identify themselves. BTTracer
then records the responses.
Step 1Select Recording Options under Setup on the Menu Bar.
The Recording Options dialog box will open showing factory default
settings such as “manual trigger” and 1 Mbytes buffer size. For the
General Inquiry recording you are about to create, these settings can be
left unchanged.
The following dialog box will open showing factory default settings.
BTTracer defaults to “General Inquiry.” For this recording, leave most
of these settings unchanged. If you are recording a Hop Frequency that
is not 79 Hops Standard, you will need to select the appropriate
standard from the Hop Frequency menu below.
Step 3Click OK to close the Recording Options window and
activate the recording options you selected.
At this point, BTTracer will be ready to record.
Step 4Clickon the Tool Bar.
BTTracer starts to record the Bluetooth™ traffic immediately. The
Bluetooth™ Inquiry process will proceed for 20 seconds. After 20
seconds has elapsed, the analyzer uploads the data and displays the
packets.
Step 5If you wish to terminate the recording before the snapshot
After a few moments, the recording will terminate and the results will
display. The screen should look like the sample recording below which
shows the FHS packets generated during the Inquiry process.
When the recording session is finished, the bus traffic is saved to the hard
drive as a file named data.blt or whatever name you assign as the default
filename. While the file is being saved, you should see a brown progress
bar at the bottom of the screen. When the bar turns white, it indicates that
the data has been saved to disk.
Step 6To save a current recording for future reference, Select Save
As under File on the Menu Bar.
OR
Clickon the Tool Bar.
You see the standard Save As screen.
Step 7Give the recording a unique name and save it to the
•One External Interface Breakout Board with a 9-pin ribbon cable
•One 6-foot (2-meter) USB cable
•BTTracer software program installation CD and diskettes
•Product documentation
3.2 The Installed BTTracer Unit
The BTTracer Analyzer has several user-accessible controls and LEDs on
its front and rear panels of the OmniBus.
Figure 1: Front Panel
•RedPWR (power) indicator LED (lights when the unit power is
switched on).
•GreenREC (recording) LED (lights when the unit is recording).
•Yellow TRG (triggered) LED (lights when the unit triggers an event).
Note TRG also lights during power-on testing and will be turned off at the end of the
power on cycle. If the LED blinks at the end of this cycle, the hardware is faulty.
•GreenSYNC (synchronized) LED (lights when the unit is locked onto a
specific piconet, based on the Master Address).
•Manual Trigger push-button (allows a manual Trace capture)
— After beginning a recording session, press the Manual Trigger switch to
force a Trigger condition. The session completes when a specified
post-Trigger amount of bus data is recorded or when you manually stop a
recording session.
•ANT Bluetooth™ Antenna connector
13
Figure 2: Rear Panel
• Wide range AC connector module
Warning: For continued protection against fire, replace fuse only with the
type and rating specified above.
• External Clock (EXT CLK) input for future enhancement (Note: THIS PORT
— Enclosed 5x20 mm 2.0A 250 V fast acting glass fuse
— Power on/off switch
IS NOT USED)
• USB type “B” host computer connector
• Data In/Out DB-9 (9-pin) external interface connector
Warning:Do not open the BTTracer Analyzer enclosure. There are no
operator servicable parts inside. Refer servicing to CATC.
3.3 BTTracer System Setup
The BTTracer Analyzer is designed to work with either desktop or laptop
computers equipped with a functional USB interface. To set up the system
hardware,
• Attach the Antenna to the ANT connector. Set the antenna to
point up.
• Connect the Analyzer to an AC power source.
• Connect the External Interface Breakout Board to the DataIn/Out connector (optional).
• Connect to the analyzing PC via USB.
3.4 AC Power Source
Step 1Connect the Analyzer box to a 100-volt to 240-volt, 50 Hz to
60 Hz, 100 W power outlet using the provided power cord.
Note The Analyzer is capable of supporting supply voltages between 100-volt and
240-volt, 50 Hz or 60 Hz, thus supporting all known supply voltages around the
world.
Step 2Use the power switch located on the rear panel to turn the
analyzer unit on and off.
Note At power-on, the analyzer initializes itself in approximately ten seconds and
performs an exhaustive self-diagnostic that lasts about five seconds. The Trigger
LED illuminates during the power-on testing and turns off when testing is
finished. If the diagnostics fail, the trigger LED blinks continuously, indicating a
hardware failure. If this occurs, call CATC Customer Support for assistance.
3.5 External Interface Breakout Board
The External Interface Breakout Board is an accessory that allows
convenient access to several potentially useful standard fast TTL output and
input signals. It also offers a simple way to connect logic analyzers or other
tools to the BTTracer Analyzer unit. Four ground pins and one 5-volt pin are
provided.
The Breakout Board connects via a ribbon cable to the Data In/Out
connector located on the rear of the analyzer box. Each pin is isolated by a
100Ω series resistor and a buffer inside the Analyzer box.
Figure 3: Data In/Out Connector
Table 1 lists the pin-out and signal descriptions for the Data In/Out
connector.
The "TRG OUT" and "G.P. OUT" pins found on the Analyzer’s Breakout
Board have similar functions. Both pins serve to transmit output signals
when a trigger event occurs. The main differences between the two pins is
in the number of signals that the Analyzer will send through them (TRG
OUT will transmit just one signal whereas G.P. OUT may transmit several
sequential signals), and in their initial state (TRG OUT is always enabled by
the Analyzer whereas G.P. OUT must be enabled in the recording options
before it can be utilized).
TRG OUT
When an event trigger occurs, TRG OUT transitions from ground to a
continuous 5 V signal on the first instance of a trigger event. TRG OUT is
a one-time event: it will not re-signal or change signals with subsequent
triggering events. When this first trigger event occurs, the Trigger LED will
illuminate (so this pin can be thought of as a reflection of the state of this
LED).
G.P. OUT needs to be enabled before it will output signalling. See “Blue
Dot Menus for the Event Buttons” on page 88 for details on how to enable
output signalling.
If enabled, G.P. OUT will provide signalling each time a trigger event is
detected by the Analyzer. G.P. OUT’s signalling can be set to three different
formats - "Pulse High" provides a 16.66 ns (ground to +5V) signal, "Pulse
Low" a 16.66 ns (+5 V to ground) signal or "Toggle", a signal with an initial
High (+5V) state that alternates with each trigger event between continuous
High (+5 V) and continuous Low (Ground). "Pulse High" is the default
condition. To change the format, see “Enabling High Pulse, Low Pulse or
Pulse Toggle Signal Outputs” on page 88 for details.
Prototype Rework Area
The Breakout Board contains a prototype rework area for making custom
circuits for rapid development. The area consists of plated-through holes, 20
columns wide by 27 rows long. The top row of holes is connected to GND
and the bottom row is connected to +5V. The remaining holes are not
connected. Use the rework area to insert custom components and wire-wrap
their respective signal, power, and ground pins.
3.6 PC Connection
Use the USB cable provided to connect the host computer to the BTTracer
Analyzer.
3.7 Antenna Information
According to the Bluetooth™ specifications, Bluetooth™ Antennas should
be placed at least 10 cm apart. It is recommended that BTTracer be placed
at least 1 meter away from the nearest device in the piconet under
observation.
3.8 Analyzer PC Requirements
For an updated description of requirements, please refer to the readme file.
Note If installing BTTracer software on a Windows NT 4.0 system, you will need a
separate set of diskettes, which is available from CATC.
The CATC BTTracer software is provided on a CD and also on six 3½ inch
diskettes. The software is also available on zip files at the CATC web site:
http://www.catc.com/support.html
If you are downloading the files from the CATC web site, you will be
retrieving several zipped files. The first of these has an executable called
install.exe. Double-click on this file and follow the on-screen instructions.
Installation of the analyzer software requires a Windows 98, Windows
98SE, Windows 2000, Windows ME, or Windows XP operating system. If
you are loading BTTracer onto Windows NT 4.0 you will need to get a
separate diskette and instructions from CATC.
Loading the BTTracer USB Drivers
Before you can install the BTTracer Windows application, you will need to
install BTTracer as a USB device:
Step 1Insert the BTTracer program CD into the CD ROM drive of
the PC that will be administering the Analyzer. If you prefer
to install from floppy diskette, install the floppy for your
operating system labeled Disk 1 of 6 into the a: drive.
Step 2Power-on the BTTracer Analyzer.
Step 3Connect the USB cable to the rear of the analyzer and to the
personal computer.
The host operating system detects the analyzer and begins to install the
USB driver.
Step 4Follow the installation instructions provided on your screen
to complete the installation of the driver.
Note When Windows prompts you for a file, browse to the CATC floppy in the a: drive.
Installing the BTTracer Application Program
Run Setup.exe from the BTTracer CD or from the BTTracer floppy disk 1
of 6.
The CATC BTTracer Install Wizard automatically installs the necessary
files to the computer’s hard drive. BTTracer software is installed in the
C:\Program Files\CATC\BTTracer directory unless you specify otherwise.
Follow the installation instructions on your screen.
You can start the BTTracer program from the Desktop or from the installed
directory. The program always begins with its main screen active:
The software may be used with or without the analyzer box. When used
without an analyzer box attached to the computer, the program functions in
a Trace Viewer mode to view, analyze, and print captured protocol traffic.
When the program is used with the BTTracer Protocol Analyzer attached to
the computer, you can set trigger conditions, record, monitor and analyze
the activity of your Bluetooth™ device or piconet.
After installation, the software is configured to make a manual recording
("Manual Trigger") of General Inquiry traffic.
To make your first recording of this traffic,
Step 1Clickon the Tool Bar.
After 20 seconds, Inquiry timeout occurs and the analyzer will uploadthe
data and display the packets.
To terminate the recording before Inquiry timeout occurs,
Step 2Clickon the Tool Bar at any time before recording
automatically terminates.
When the recording session is finished, the traffic is saved to the hard
drive as a file named data.blt or whatever name you assign as the default
filename.
To save a current recording for future reference,
Step 3Select Save As under File on the Menu Bar.
OR
Clickon the Tool Bar.
You see the standard Save As screen.
Step 4Give the recording a unique name and save it to the
From time to time as modifications are made to BTTracer, it is necessary to
update the Firmware and/or BusEngine for optimal performance. Updates
can be performed two ways: either automatically or manually. This chapter
describes both procedures.
4.1 Software, Firmware, and BusEngine Revisions
The Readme.htm or Readme.txt file on the first installation disk and in the
installed directory gives last-minute updates about the current release.
Included with each release are the most recent downloadable images of the
Firmware and the BusEngine. The Readme file lists the latest versions and
informs you if new Firmware or a new BusEngine needs to be updated in
your hardware.
Once the Analyzer has completed the self diagnostics and is connected to
the PC, you can check the latest revision of the software and BusEngine:
• Selecting About Merlin… in the Help Menu.
You see this screen:
About Merlin details revisions of the following software and hardware:
Merlin Software Version
•
• Merlin Firmware Version
• BusEngine Version
• Unit Serial Number
Note When contacting CATC for technical support, please have available all the
When a new software release is available, it is posted on the Support page
of the CATC website at www.catc.com/support.html.
To update the software,
Step 1In the About Merlin screen,verifywhichversionof
BTTracer Software you are currently running.
Step 2Find the latest released software version on the CATC
website under Support.
If you are running the latest version of the software, no further action is
needed.
If you are not running the latest version, continue to Step 3.
Step 3Click on the first link to download the zipped Disk 1 files for
your operating system.
Step 4Click on the second link to download the zipped Disk 2 files.
Step 5Unzip the files into your choice of directory.
Step 6Click Start, then Run, and browse to where you unzipped
the files.
Step 7Select the program named Setup and click Open.
Step 8Click OK to run the Setup and begin the installation.
Step 9Follow the on-screen instructions to complete the
installation.
Step 10 Read the Readme file for important information on changes
in the release.
4.3 Software License Updates
A license key is a file that CATC provides to you when you enter a
maintenance agreement. You use this file when you make updates to your
CATC software.
Step 2Type the path and filename to the license key or click the
Browse button to map to the directory containing the license
key.
Step 3Click Update Device.
Viewing licensing information
You can also view licensing information to see what version of the license
you are running.
From the Help menu, select Display License Information.
The following window appears containing information about the current
status of your analyzer’s license:
4.4 BusEngine and Firmware UpdateUpdates
BusEngine and Firmware updates often need to be performed when you
update the BTTracer software. These updates can be performed
automatically or manually. Both processes are described.
23
Automatic Updates
When BTTracer’s software is updated, the software may become
incompatible with the BusEngine and Firmware. If a recording is
attempted, BTTracer will display an error message and then automatically
begin an update process for the BusEngine and Firmware. If you prefer, you
can abort this update and undertake the steps manually as described later in
this chapter.
To perform an automatic BusEngine and Firmware update,
Step 1If needed, update the BTTracer software using the steps
Since the BusEngine and/or the Firmware are incompatible with the
current BTTracer software version, an error message will appear
displaying your current versions and indicating what versions you need
to install.
Step 3Click Yes.
The above window closes and the Analyzer Setup window opens.
Step 4Click Update BusEngine or Update Firmware on the
You can select only one item at this point. If both the BusEngine and the
Firmware need to be updated, the update will complete for the first item
and then return to the above screen so the second update can be
performed.
When the second update has finished, you will see the following message
telling you that the update is complete.
Step 5Power cycle BTTracer to complete the update.
Manual Updates to BusEngine and Firmware
You can manually update BTTracer’s Firmware and/or BusEngine by
performing the following steps:
Step 1Select Analyzer under Setup on the Menu Bar.
Yo u s e e t he Analyzer Setup screen:
Step 2Click Reset Analyzer
The Analyzer resets, performs self-diagnostics, and returns to service.
Note The self-diagnostics should complete about five seconds after the trigger LED
lights. If the diagnostics fail, the trigger LED blinks on and off continually,
indicating faulty hardware. If this occurs, contact CATC for customer support.
The BusEngine core is the heart of the Merlin Analyzer. Using
state-of-the-art PLD technology, it incorporates both the high speed
recording engine and the configurable building blocks that implement
data/state/error detections, triggering, capture filtering, external signal
monitoring, and event counting and sequencing. Both the BusEngine
program and the Firmware that manages the internal microcontroller are
fully field updateable.
Within a new software release, it may be necessary to update the Analyzer’s
BusEngine hardware for proper operation. The Readme file lets you know
if this is necessary.
To update the BusEngine,
Step 1Click Update BusEngine on the Analyzer Setup screen.
Yo u s e e t he Select engine file window:
The program has already automatically searched for the correct file and
displays it in the File name field.
Note The most current Primary BusEngine file (BTTracer.rbf) was copied to your
\CATC\BTTracer directory when you installed the program.
Step 2Click Open.
It is not necessary to restart the Analyzer. Once updated, the Analyzer takes
approximately 15 seconds to reinitialize, with Time Remaining displayed
on the screen. During this time the Trigger LED is on, indicating that
power-on diagnostics are being run. If there is a hardware failure, the
Trigger LED continues to blink after initialization is complete. If this
occurs, contact CATC for customer support.
Updating the Firmware
Within a new software release, it may also be necessary to update the
Analyzer’s firmware for proper operation. The Readme file informs you if
this is necessary.
To update the firmware,
Step 1Click Update Firmware on the Analyzer Setup screen.
Yo u s e e t he Select firmware file window:
The program has already automatically searched for the correct file and
displays it in the File name field.
Step 2Click Open.
The Analyzer updates the Firmware.
Step 3Unplug the USB cable from the back of the Analyzer box
and then reinsert it so the new Firmware update can take
effect.
New WindowSwitches display of the Tool Bar on or off.
C
ascadeDisplays all open windows in an overlapping arrangement.
ileDisplays all open windows in a side-by-side arrangement.
T
Arrange IconsArranges minimized windows at the bottom of the display.
indowsDisplays a list of open windows.
W
Help
Help Topics...Displays online help.
Update License...Opens a dialog box for entering license key information for the
analyzer.
Display License
Information...
A
bout BTTracer...Displays version information about BTTracer.
Displays current license information for the analyzer.
5.2 View Options
The View feature in the Menu Bar allows you to
Control the display of the Tool Bar and the Status Bar.
•
Tool Bar
The Tool Bar provides access to the most popular program functions. Tool tips
describe icon functionality as the mouse arrow is moved over the icon/item.
Hide Frequency HopsView AT Commands Protocol Level
Error Summary
Timing CalculatonsView/Hide HDLC Protocol
Start BTTracer’s WandView/Hide BNEP Protocol
View/Hide RFCOMM Protocol Level
View/Hide P PP
View HID Protocol Layer
32
5.3 Status Bar
The Status Bar is located at the bottom of the main display window.
Depending on the current activity, the bar can be divided into as many as
four segments.
Recording Progress
When you begin recording, the left-most segment of the Status Bar displays
a Recording Progress Indicator:
As recording progresses, the Progress Indicator changes to reflect the
recording progress graphically:
•
In the Progress Indicator, a black vertical line illustrates the location of the
Trigger Position you selected in Recording Options.
— Pre-Trigger progress is displayed in the field to the left of the Trigger
Position in the before-Trigger color specified in the Display Options.
— When the Trigger Position is reached, the progress indicator wiggles as it
waits for the trigger.
— After the trigger occurs, the field to the right of the Trigger Position fills
in the post-Trigger color specified in the Display Options.
— When recording is complete, the upper half of the progress indicator fills
in white, indicating the progress of the data upload to the host computer.
You should be aware of two exceptional conditions:
•
If a Trigger Event occurs during the before-Trigger recording, the
before-Trigger color changes to the after-Trigger color to indicate that not all
the expected data was recorded pre-Trigger.
• When you click Stop before or after a Trigger Event, the Progress Bar adjusts
accordingly to begin uploading the most recently recorded data.
The Progress Bar fills with color in proportion to the specified size and
actual rate at which the hardware is writing and reading the recording
memory. However, the Progress Indicator is normalized to fill the space
within the Status Bar.
33
Recording Status
During recording activity, the current Recording Status is temporarily
displayed in the next segment. When you activate the Record function, this
segment flashes one of the following messages (depending on the selected
Recording Options):
— The flashing message changes to Uploading data–x%done(x%
indicates the percentage completion of the data uploading process).
— The traffic data is copied to disk (overwriting any previous version of this
file) using the default file name data.blt or a new name specified in the
Recording options.
Press Esc on your keyboard
When the data is saved, the Recorded Data file appears in the main display
window and the Recording Status window is cleared.
• If the recording resulted from a Trigger Event, the first packet following the
• If the recording did not result from a Trigger Event, the display begins with the
Analyzer Status
The third segment in the status bar displays analyzer status. During
synchronization, the analyzer status will read:
Inquiring – BTTracer is conducting a General Inquiry
Syncing – BTTracer is syncing to the Master device
No Sync – BTTracer has not yet started syncing to the Master device
OR
Again clickin the Tool Bar.
You are prompted to choose whether to keep the partially uploaded data or to
throw it away.
Trigger (or the packet that caused the Trigger) is initially positioned second
from the top of the display.
first packet in the traffic file.
After the analyzer has synchronized to the Bluetooth™ piconet under
observation, the Status Bar will display activity bars. The activity bars will
increase or decrease with activity. If there are no vertical bars, there is no
recorded activity.
During uploading, this segment displays the percent of the upload process
completed.
Note If packets are filtered from the recording or data are truncated, the recording
activity is reduced.
In addition to showing activity, the third segment of the Status Bar will also
display the radio signal strength in dBm received by the analyzer. BTTracer
can display five possible values:
•below-60dBm
•- 60 dBm
•- 50 dBm
•- 40 dBm
•above - 40 dBm
The valid range for a signal is between -70 and - 20 dBm.
Search Status
The rightmost segment displays the current search direction: Fwd (forward)
or Bwd (backward).
Zoom In
Zoom In increases the size of the displayed elements, allowing fewer (but
larger) packet fields per screen.
•
Clickon the Tool Bar.
Zoom Out
Zoom Out decreases the size of the displayed elements, allowing more (but
smaller) packet fields per screen.
Clickon the Tool Bar.
•
5.4 Tool Tips
Throughout the application, tool tips provide useful information.
To display a tool tip, position the mouse pointer over an item. The tool tip
displays in a short moment if present. Tool tips can also be found over the
Tool Bar and in areas of the packet view screen.
Recording Wizard is an interactive utility that presents a series of
user-friendly dialog boxes for setting up a recording session. Recording
Wizard serves as an alternative method of configuring the Recording
Options dialog box. When you are finished using the Wizard, you can view
your settings in the Recording Options window. By providing data to the
prompts in the Wizard’s dialog boxes, you configure BTTracer for a
recording session.
Starting Recording Wizard
To sta rt the Recording Wizard,
• Clickon the Tool Bar or select Recording Wizard underSetup on the Menu Bar.
Yo u s ee t h e Recording Options window:
The Recording Options window has three buttons marked Next, Back,and
Cancel that allow you to move forward or backward through the wizard or
to cancel the wizard.
To begin advancing through the wizard,
•ClickNext to see the options for the three types of recordings that
the Recording Wizard can make.
The Wizard advances to the next screen which presents three options:
• Establish a new piconet and have BTTracer record traffic on
that piconet.
This option causes BTTracer to perform an Inquiry so it can discover
local devices and then establish a new piconet and record the piconet
traffic.
• Record traffic on a piconet that has already been established.
This option lets BTTracer record traffic from an already established
piconet.
• Record traffic in Test Mode on a test piconet.
This option lets BTTracer create either a single frequency range
recording of a range that you specify or create a recording of a limited
hop frequency range consisting of 5 frequency hops.
6.1 Recording a Traffic on a New Piconet
The New Piconet option shown in the previous screen presents users with
the means of recording the traffic from a new piconet. This option will
cause a sequence of screens to prompt you for information such as the
piconet Master address.
Selecting Perform Inquiry Now will cause BTTracer to perform a
General Inquiry and collect addresses and other details about local
Bluetooth devices. If you already have address information for your
Bluetooth devices you can choose Skip Inquiry. Choosing SkipInquiry will cause the Recording Wizard to advance to Step 6. If you
are not sure what option to select, choose Perform Inquiry Now.
• I want to search for all Bluetooth devices within range
This option will cause BTTracer to search for all Bluetooth devices that
are in range and ready to transmit and receive data (i.e., in Inquiry ScanMode)
• I want to search only for devices corresponding to the
following (hexadecimal) DIAC:
This option will cause BTTracer to search for the class of devices that
you specify in the DIAC text box. DIAC stands for Device InquiryAccess Code. Values are entered in hexadecimal format. You can get
DIAC values from the Bluetooth Specification.
Step 4Select the first option: I want to search for all Bluetooth devices
within range,thenpressNext. The following screen will display.
You will see two options:
Step 5In the text box, enter the length of time you want BTTracer to search
for nearby devices.
The default value is 20. If you do not sure what time value to enter, use
the default value.
Before the Inquiry, BTTracer tests the hardware connection. In the case
of failure, the following screen will display.
Clicking OK will close the message box.
If BTTracer passes the hardware test, it will search for devices. The
Recording Wizard will display a progress bar and a message telling you
that a search is under way:
The Advanced button on the right will open the Recording Options
dialog box shown below. This screen will show the settings you selected
through the Recording Wizard have been applied to the Recording
Options dialog.
Step 13 Press Next to advance the Recording Wizard to the next screen.
The following screen displays:
BTTracer pages the Master and if specified in Step 8, the Slave devices.
If BTTracer is unable to complete its pages, the following screen will
display:
If BTTracer is able to complete its pages, it will enter into a
synchronizing state and then wait for you to create the piconet. During
this waiting period, BTTracer will display the following screen:
Once you have created the piconet, BTTracer will synchronize to the
piconet and begin recording. During the recording, BTTracer will
display the following screen:
At the completion of the recording, BTTracer will display the following
screen:
You can repeat the recording by pressing the Repeat button.
Step 14 To close the wizard, press the Close button.
The wizard will close and your trace will display.
6.2 Recording an Existing Piconet
Using Recording Wizard to record anexisting piconet is similar to recording
a new piconet. The main difference is that you will be asked if your Master
device can support multiple slave devices and whether it can respond to
pages once it has created a piconet with another device.
Step 1To start the Recording Wizard, pressor select Setup >
A screen will display showing the devices that BTTracer discovered
through the General Inquiry:
If you feel that the list is incomplete, you can close this window and press
the button marked Repeat. This will cause BTTracer to repeat the
General Inquiry and recollect information on local Bluetooth devices.
Step 11 Press OK to close the Bluetooth Neighborhood window.
Step 12 Press Next to advance to the next screen.
The following screen will prompt you for the Master device’s address.
The address can be selected from the drop-down menu or typed into the
box:
Step 13 Select or type in the Master device’s address into the box
The following screen will display. This screen asks you which of the
following two options apply to your Master device. For some devices,
both options will apply.
You can select either or both options. They are not mutually exclusive:
If the Master supports inquiries while in a connected state, select the first
option. This will set BTTracer to use the 'Sync & Record' mode in its
attempts to synchronize to the Master. This will also cause the wizard to
skip to step 8.
If the Master can support piconets with multiple slaves, select the second
option. If you select this box alone (i.e., you leave the first box
unchecked), BTTracer will use the 'Passive Sync & Record' mode to
synchronize to the Master. The wizard will then advance to Screen 8*.
If the first checkbox was selected, BTTracer will use 'Sync & Record' no
matter what was set in the second box.
Step 15 If you want to skip the Master verification, put a check in the
box. If you are in doubt, leave the box unchecked.
If you selected only the second option in Step 15 (=’Passive Sync &
Record’), the following screen will display.
This screen asks you for the address of the Page Target device -- which
in this case is BTTracer. Since the devices in your piconet are not able
to respond to inquiries, BTTracer will not be able to page the devices and
join the piconet. Instead, you will assign BTTracer an address here in
this screen, then direct your piconet Master device to connect to
BTTracer. The Master will attempt to connect to BTTracer and therein
give BTTracer the information it needs to record the Master and slave
devices.
Step 16 Type in an address of your choosing for BTTracer (= Page Target).
You are making up an address for BTTracer that the Master will use to
try to connect to BTTracer.
Step 20 Press Retry or Back to re-attempt the process.
If the hardware failure described in Steps 20 and 21 do not occur,
BTTracer will conduct an inquiry. The screen will show that BTTracer
is going to attempt a recording in either ’Passive Sync & Record’ mode
as shown below or in ’Sync & Record’ mode depending on the options
you selected in Step 15.
Step 21 If you are recording in ’Passive Sync & Record’ mode, you will
need to direct your Master device to attempt a connection to
BTTracer. This will provide BTTracer with the information it needs
to record the piconet.
Once BTTracer has the information it needs, it will begin recording. The
following screen will display:
The recording will end following a trigger event or when you press StopRecording button on the screen shown above or when you press the
button on the toolbar.
Step 22 When finished, press Close to close the Recording Wizard.
6.3 Recording in Test Mode
A Test Mode recording allows you to limit the frequency hopping range that
BTTracer will record. Two Test Modes are available: Reduced Hopping
Mode and Single Frequency Mode. Reduced Hopping Mode limits
BTTracer’s recording to the five frequency hops that are described in the
Bluetooth Specification. Single Frequency Mode limits BTTracer’s
recording to a single frequency range that you specify in the Recording
Wizard.
Recording in Reduced Hopping Mode
To record in Reduced Hopping Mode, perform the following steps:
Step 1Start the Recording Wizard by either pressing the button
or selecting Setup > Recording Wizard from the menu.
The Recording Options dialog box lets you configure BTTracer for
recording Bluetooth™ data. This dialog box offers an alternative to the
Recording Wizard described in the previous chapter. At the top of the
Recording Options dialog box are four tabs that provide access to dialog
boxes called General, Modes, Events, and Actions. Using these dialog
boxes, you can configure BTTracer to create event triggers, increase or
decrease memory allocation for recording, and interact with other
Bluetooth™ devices in different ways.
Opening the Recording Options Dialog Box
To open the Recording Options menu, clickon the Tool Bar or select
Recording Options under Setup on the Menu Bar.
The General tab is displayed by default when the Recording Options dialog
box is oppened. It is shown in the previous illustration. The General tab
display four boxes marked Recording Type, Buffer Size, Trigger Position,
and Options.
Recording type
The Recording Type box presents three options that
allow you to set how BTTracer begins and ends a
recording. The options are: Snapshot, Manual Trigger,
and Event Trigger.
Snapshot
A Snapshot is a fixed-length recording whose size is determined by the
"Buffer Size" box in the Recording Options dialog or by a manual click of
the Stop button. Recording begins by clickingon the Tool Bar and ends
when either the selected buffer size is filled or you press the Stop button.
Manual Trigger
A Manual Trigger recording is a one that is manually begun and ended.
Recording is begun by pressingon the Tool Bar. Recording continues
in a circular manner within the limits set by the buffer size. Recording ends
whenis clicked on the Tool Bar or the Trigger button is pressed on the
analyzer's front panel. If you press the Trigger button, recording will
continue until the post-trigger memory has been filled.
Event Trigger
An Event Trigger recording is one that uses an event trigger to end the
recording. Before recording begins, you define the event trigger in the
Trigger Options dialog box. You begin the recording by clickingon
the Tool Bar. Recording continues in a circular manner within the limits set
by the buffer size. Once the trigger event occurs, some post-trigger
recording occurs, then the recording ends.
Note In this mode, the recording can be stopped manually in the same way as for
The Buffer Size box has a slide bar for adjusting the
recording buffer size from 0.1 megabytes to 128
megabytes.
The Recording Type option determines how this buffer is used. Although
there are 128 megabytes of physical memory in the analyzer, the efficiency
of the recording ranges from 2:1 to 4:1 ratios of physical memory to actual
Bluetooth™ traffic. Shorter Bluetooth™ packets yield a less efficient
recording. The non-traffic portion of physical memory is utilized for control
and timing information.
Will cause the PC to beep when a trigger event
has occurred.
Save External Interface Signals
Will enable BTTracer to record input signals
Note The scale is not linear and affords more granularity in the smaller buffer sizes.
Trigger Position
The Trigger Position slide bar sets the amount of
post-trigger recording that BTTracer will perform. It
also allows adjustment of the location of the trigger
within the defined buffer. You can adjust the
Triggering Position between 1 and 99% post-Trigger.
Trigger Position is available only when Manual Trigger or Event
Trigger is selected as Recording type.
As an example, if the buffer size is set to 16MB, then for the following
Trigger Position settings, the amount of pre- and post-Trigger data is
Note When a Trigger occurs, recording continues until the post-Trigger amount of the
buffer is filled.
7.2 Recording Options - Modes
The tab marked Modes opens a window for setting recording mode options.
This window is divided into six boxes marked Recording Mode, Piconet
Addresses, Hop Frequency, Other Parameters, and Debug/Test.
66
Recording Mode
To record Bluetooth™ traffic, the BTTracer analyzer needs to synchronize
to the piconet under observation. BTTracer does not participate in the
piconet and behaves as a passive listener. It needs, however, to
communicate briefly with the devices in the piconet to learn the Master
clock and frequency hopping sequence.
To synchronize to the piconet under observation, BTTracer can be set up in
different recording modes: Inquiry Recording and Piconet Recording.The
option you select affects the types of settings that display in the window.
Inquiry Recording
Selecting the "Inquiry Redcording" button causes the Modes window to
display the options shown in the previous screenshot.
The "Inquiry Recording" option presents two choices for recording
Inquiries: "General (Unlimited)" and "Dedicated (Limited)."
General (Unlimited)
"General" means "General Inquiry" and is used to search for ALL
Bluetooth™ devices that are within range, for the amount of time specified
in the Inquiry Timeout field. Completion of the inquiry process is indicated
by illumination of the "trigger" light on the front of the analyzer. All
responding packets will be displayed when data upload from the analyzer
completes.
"Dedicated" means a specific class or group of Bluetooth™ devices
(designated by the DIAC field of the Recording Options dialog). Selecting
"Dedicated" causes BTTracer to search for all devices from a specific class
or group that are within range, for the amount of time specified in the
Inquiry Timeout field. Completion of the inquiry process is indicated by
illumination of the "trigger" light on the front of the analyzer. All
responding packets will be displayed when stop is selected.
67
Piconet Recording
The "Piconet Recording" option presents three choices for recording piconet
traffic: Sync and Record, Passive Sync & Record, and Page Sync & Record.
A Help button next to the menu briefly explains these options.
Page Sync & Record is the preferred option and should be used whenever
possible. If Page Sync & Record can not be used, then Sync & Record
should be used. Passive Sync and Record should be used only if the first
two options can not be used.
Hop Sequence
Until recently, local regulations in Japan, France, and Spain defined a
Bluetooth™ frequency range that was different than the range used by the
rest of the world. We have included the selections for organizations for
testing of devices developed before all frequencies were made available on
aworld-widebasis.
To set BTTracer to the correct Hop Frequency, select from the drop-down
menu one of the following choices:
• Reduced Hop - Restricts BTTracer to five hop frequencies
defined in the test mode specification of the Bluetooth™
Specification. When Reduced Hop or Single Frequency is
selected, the Sync method is set to Test Mode and cannot be
modified by the user.
• Single Frequency - Allows the the transmit and receive frequency
ranges to be specified. Selecting this option highlights the "DUT
Xmit" and "DUT Recv" text boxes. When Reduced Hop or
Single Frequency is selected, the Sync method is set to Test Mode
and cannot be modified by the user.
• Enter values into the two text boxes to the set the transmit and
receive frequency ranges:
• DUT Xmit Freq, MHz (+2402) – Allows the setting of the
transmit signal for the Device Under Test
• DUT Recv Freq, MHz (+2404) – Allows the setting of the
receive signal for the Device Under Test
Sync Methods
Note If the selected Hop Sequence is "Reduced Hop" or "Single Frequency," the Sync
Method is set to "Test Mode" and cannot be modified by the user.
Page Sync & Record
"Page Sync and Record" is the recommended method of recording. "Page
Sync and Record" should be implemented before a piconet is established.
This mode causes BTTracer to perform a General Inquiry and collect sync
information from the specified slave device when it responds. BTTracer
then waits for the Master to begin paging the Slave devices. When paging
begins, BTTracer synchronizes to the Master and begins recording.
Note In order for this mode to work, the intended Slave must support "inquiry scan".
The following steps describe the simplest way to use this mode:
Step 1Place both the "intended master" as well as its first "intended slave"
Step 2Have BTTracer perform a General Inquiry. You do this by selecting
"General (Unlimited)" from the "Inquiry Recording" drop-down
menu on the "Modes" tab in the "Recording Options" window, and
then depressing the "REC" button found on BTTracer's toolbar.
Step 3After the General Inquiry completes, as indicated by the automatic
uploading and displaying of a CATC trace (approximately 20
seconds), reselect the "Modes" tab in the "Recording Options". At
this point, the addresses of all Bluetooth™ devices that were in
range will be listed in the pull-down windows in the "Piconet
Addresses" area of this window. Using the pull-down windows
select both your "Intended BT Master" as well as your "Intended
Slave" address for display in their appropriate windows.
Step 4After closing this window by pressing the "OK" button at the bottom
of the window, once again depress the "REC" button found on
BTTracer's toolbar. After approximately 20 seconds, the "SYNC"
light on the front of BTTracer will begin to flash, meaning that
BTTracer has acquired all the information it needs to fully
synchronize with the piconet about to be established. At this point,
you should establish the piconet using the devices previously
defined as master and slave.
Step 5When the piconet is established, the "Sync" light on the front of
Note If the "sync" light on the front of BTTracer does not change from
Sync & Record
Sync and Record works just like "Page Sync and Record" except that
BTTracer takes its sync data directly from the Master instead of the Slave
devices. With Sync and Record, BTTracer conducts a General Inquiry to
get hop frequency and clock information from the Master. BTTracer then
waits to detect piconet traffic from the Master device’s piconet. When the
piconet is established, BTTracer is able to synchronize to the Master and
begin recording. In contrast to "Page Sync and Record", "Page Sync and
Record" can be run with or without an established piconet.
Note This mode can only be used to find master devices that support Inquiry Scan.
BTTracer will change from flashing to solid, indicating that
BTTracer is fully synchronized to the piconet and is currently
recording all traffic within that piconet.
flashing to solid it means that BTTracer did not synchronize with the
piconet when it was established.
To perform a "Sync and Record", follow the steps below:
Step 1Turn on the Bluetooth™ devices under observation, and set up the
master device so it is ready to respond to Inquiry scan. For a typical
recording, ensure that the Master and Slave device(s) are not yet
connected.
Step 2In the Modes tab under Recording Options, enter the Master
Device’s address.
Step 3Start BTTracer recording by pressing REC icon in the
toolbar.
Step 4When the analyzer is able to Sync up to the Piconet Master Clock,
the Green Sync LED in the BTTracer front panel will start
blinking.
Step 5Establish connection between the Bluetooth™ devices under
analysis.
Step 6When BTTracer senses Piconet traffic, the Green Sync light goes
ON solid, recording starts and the status bar in the bottom of the
analyzer screen shows activity.
Recording may be stopped manually or when the recording buffer is filled.
Note After the Sync light starts blinking, a connection between the
Bluetooth™ devices should be established within one (1) minute.
Passive Sync & Record
Passive Sync and Record is used in situations where the Master device and
slave devices do not support Inquiry Scan mode. When selected, BTTracer
enters Inquiry Scan and Page Scan mode and waits for a page from the
Master device. When the piconet Master pages BTTracer, BTTracer
obtains the information necessary for synchronization and then attempts to
synchronize to the piconet controlled by that Master.
"Passive Sync and Record" is designed to be used with established piconets
or private device networks.
Running "Passive Sync and Record" with Established Piconets
For most situations, "Passive Sync and Record" will be run after a piconet
has been established. The steps are as follows:
Step 1Establish a connection between two or more Bluetooth™ devices.
Step 2Under General Recording Options, select "Passive Sync & Record."
Step 3Under the Modes tab in Recording Options, enter the address for the
Step 4Make up an address for BTTracer and enter it into the Page Target
address in the Modes tab in Recording Options. Make sure you do
not select an address for any other local device.
Step 5Press the REC button on the toolbar in BTTracer to start a recording
session.
Step 6If necessary, have Master "discover" BTTracer through a General
Inquiry.
Step 7From the Master device, initiate a page to BTTracer’s address. This
action will enable BTTracer to synchronize to the piconet. However,
the analyzer will not complete the page sequence from the Master.
This will cause the Master to time out in this request.
Step 8At the end of this sequence, the green Sync light will go on solid,
recording will begin and activity will be displayed on the status bar
in the bottom of the analyzer screen.
Running "Passive Sync and Record" with Private Device Piconets
Because private device networks do not allow other devices to join the
network, BTTracer needs to temporarily assume the identity of a slave in the
network in order to join that network. To do this requires disabling the slave
and beginning the operation without an established piconet. The following
steps show the process.
Step 1Turn the Master device on and the slave device off. You need the
slave device turned off so that BTTracer can take its place in the
piconet.
Step 2Enter the slave’s address into BTTracer’s "Page Target" field in the
Modes tab in the Recording Options dialog box.
Step 3Run "Passive Sync and Record." The Master will then page the
slave’s address and BTTracer will be able to sync.
Step 4When BTTracer synchronizes to the Master, turn the slave back on.
When the Master re-pages the address the slave will be admitted into
the private network. Since BTTracer is passive in this mode, the
slave and BTTracer do not conflict over the shared address.
BTTracer is then able to record the traffic between the Master and
"Force Re-Synchronization" forces BTTracer to re-synchronize at the
beginning of each "Page Sync & Record," "Passive Sync & Record," or
"Sync & Record" operation. By default, "Force Re-Synchronization" is
disabled (i.e., unchecked).
Unchecking the "Force Re-Synchronization" checkbox tells BTTracer to
use its existing data on Bluetooth™ devices, thereby bypassing the
synchronization process and saving a few seconds from the beginning of the
trace. If you know that BTTracer’s data is correct, you can uncheck this
checkbox and cause BTTracer to try to use the existing data. If the data is
incomplete or incorrect, however, BTTracer will automatically perform a
refresh.
To examine BTTracer’s Bluetooth™ data, open "BT Neighborhood" under
the View menu.
Follow Master/Slave Switch
If enabled, this option allows BTTracer to follow a role switch between a
Master and Slave. This capability allows BTTracer to keep track of changes
in a device’s role when it changes from one role to another.
BTTracer is able to follow a role change by listening to the Slave device’s
Bluetooth clock and hop frequency as soon as it becomes a Master.
Match Clock Rate
Match Clock Rate is a useful option if the Master device’s clock is
inaccurate. Match Clock Rate causes BTTracer to do a General Inquiry to
determine the Page Target's clock rate prior to synchronizing to the piconet.
If unchecked, BTTracer will begin piconet synchronization without first
doing a General Inquiry.
This option only works with Page Sync and Record mode.
Show Paging Traffic
Show Paging Traffic causes BTTracer to capture paging traffic between the
Master and Page Target devices. This option is used only with Page Sync
and Record Mode.
Piconet Addresses (MSB -> LSB)
• Master Addr - Piconet Master Address for device under
observation. Used for all Piconet recording modes.
• Page Target - User selectable address for the BTTracer
Analyzer. Used for Passive Sync & Record and Page Sync &
• DIAC LAP- Device Inquiry Access Code. Used for Device
Inquiry.
• Swap - The "swap" button swaps the addresses between the
Master Addr and Page Target text boxes. This button will allow
addresses to be swapped even if the boxes are grayed out.
Note GIAC - General Inquiry Access Code is hard-coded in the analyzer and does not
require user selection.
Other Parameters
Correlation Value (33-64)
This value tells BTTracer how many bits in the sync word of each received
packet must be matched in order for BTTracer to consider the packet valid
and start recording.
Inquiry Timeout (0-80 secs)
Default value is 20 seconds.
This value specifies how long BTTracer should perform the Inquiry process
for the General (unlimited) and Dedicated (limited) recording modes. After
the specified time has elapsed, BTTracer will illuminate the trigger light on
the front of the analyzer.
Loss of Sync Timeout (1-16 secs)
This value specifies the amount of time that BTTracer will wait for piconet
traffic before determining that synchronization has been lost.
Sync Window
The Sync Window slide bar controls the amount of time that BTTracer
should wait between receiving an Inquiry Response (which will cause the
Sync LED to blink) and detecting Master-Slave piconet traffic (which will
cause the Sync LED to turn solid.)
A "Narrow" setting means that the wait time will be minimal, a "Wide"
setting means it will be "maximal." The default is "Narrow" and this is
suitable for most recordings. However, if significant drift occurs between
BTTracer’s clock and that of the Master, BTTracer may not be able to sync
properly to the piconet. Under these conditions, you should move the slide
bar towards the "Wide" Setting. The slide bar has five discrete settings.
After sync is established, BTTracer will remain in sync as long as there is
piconet traffic.
Debug/Test
Enable CATC debug file
Checking this box enables the creation of a file that can be used by CATC
Support to aid in debugging. This option should always be disabled unless
you are requested to enable it by CATC personnel.
7.3 Recording Options - Events
If you have selected Event Trigger mode under the General tabinthe
Recording Options screen, you may now select specific Bluetooth™ events
using the Events tab on the Recording Option Screen. You can also use the
Actions tab to define specific event sequences that will trigger BTTracer to
record a Bluetooth™ session.
In addition, the Events and Actions screens allow you to specify which
packets you want to include or exclude from the recording.
Events Options
Yo u s e e t he Event Groups window:
• Click the Events tabontheRecording Options screen.
The Event triggering and filtering options allow you to set event conditions
for errors and/or a variety of packet characteristics.
Clicking a check box causes further options to display in the right side of the
window.
Additional Timeslot Filtering
By default, BTTracer records frequency hop and timestamp information for
all time slots in the Piconet under analysis, regardless of whether the time
slot contained a Bluetooth™ packet. This means that in instances where
there is little piconet traffic, BTTracer will display row after row of empty
packets -- each representing an empty time slot. Through the use of timeslot
filtering, these empty packets can be filtered out. Filtering out this
information has the benefit of freeing memory so that more traffic can be
recorded.
Filter Empty Slots
If "Filter Empty Slots" is checked, BTTracer will exclude all empty time
slots from a recording except for those that lie immediately in front of
Bluetooth™ communications packets. These remaining empty packets are
preserved to give timestamp and frequency hop reference data to the packets
that follow.
Filter Slots on Packet Filter
If filters are used to exclude FHS, DM1 or other packets, BTTracer will
exclude these packets from a trace and mark their locations with empty
packets. The result can be rows and rows of empty packets. The option
"Filter Empty Slots" will not exclude these empty slots because they lie
immediately in front of Bluetooth™ communications packets - even though
those packets were not recorded. To eliminate these empty packets, select
"Filter Slots on Packet Filter."
Packet Headers
Clicking "Packet Headers" opens three sets of check boxes and menus on
the right that represent fields within packet headers: Packet Type, Active
Member Address, Flow Control, Acknowledgment, and Sequence Number.
The Packet Type drop down menu lets you select the following packet types
for filtering or triggering: NULL, POLL, FHS, DM1, DH1, HV1, HV2,
HV3, DV, AUX1, DM3, DH3, 1100, 1101, DM5, or DH5.
Select “Don’t Care” if you want BTTracer to ignore this field.
AM_ADDR
(Active Member Address) The AM_ADDR is a three bit slave address. To
select packets from a particular slave device for filtering or triggering, enter
an address into the AM_ADDR text box. You can target up to three devices
using the three text boxes.
SEQN, ARQN, and Flow Control Bits
To set event conditions on SEQN, ARQN, and Flow control, uncheck
"Don't Care." Unchecking "Don't Care" sets the event condition to
SEQN=0 AND ARQN=0 AND Flow=0. This action also puts a checkmark
in the box marked "Packet Headers." A checkmark next to SEQN, ARQN,
77
or Flow changes the value of this field from zero to one. For example, if
SEQN is checked, the event condition becomes "SEQN=1 AND ARQN=0
AND Flow=0.
To cause BTTracer to ignore this set of check boxes, choose "don't care."
Payload Headers
Clicking "Payload Headers" causes a series of options to display on the right
for setting conditions on payload headers. You will see two sets of options
- one for single slot packets such as DM1 packets and a second for multi-slot
packets such as DM3 packets. Within each set is a menu for the Logical
Channel and sub-options for Flow Control, and Payload length. These latter
two options allow you to modify searches based on the Logical Channel.
An example would be "Trigger on a start L2CAP message whose flow
control bit is 1 and whose data field length is less than 20."
Select "Don’t care" if you do not want to set conditions on Logical Channel.
Flow
Three "radio buttons" are presented for
setting conditions based on Flow control:
•0
•1
• Don’t care
Flow works in conjunction with the Logical Channel (L_CH) menu - you
select an option from the L_CH menu and then select an option under Flow.
Select "Don’t care" if you do not want to set conditions on Flow control.
Length (in bytes)
Using both the drop down menu and the text box, you
can set conditions based on data field length. The
maximum length for a single slot packet is 29 bytes. The
maximum length for multi-slot packets is 339 bytes.
The drop-down menu gives you options for selecting
operators such as "greater than" and "equal to." The text box to the right of
the drop-down menu lets you enter values.
The Length option works in conjunction with the Logical Channel (L_CH)
menu - you first select an option from the L_CH menu and then select an
option under Length.
Data Patterns
Clicking "Data Patterns" causes a text box to
appear for entering patterns to be matched in the
raw payload data. Patterns of up to eight
hexidecimal bytes can be entered.
Errors
Clicking "Errors" causes check boxes to appear for setting conditions for
triggering or filtering based on packet/signaling/protocol errors. You can
select one or a combination of errors.
Indicates that a received Bluetooth™ data packet was terminated before all
bits of the packet header were received.
Payload Length Error
Indicates that the payload of a received Bluetooth™ data packet was either
longer than expected, or that a Bluetooth™ data packet terminated before
the expected end of the payload data.
Sync Loss
When set, indicates that a loss of piconet synchronization occurred during
the frequency slot prior to this slot.
External Input Signals
Clicking "External Input Signals" causes two check boxes to appear for
setting conditions based on breakout board input signals. The names of the
two check boxes are the same ones you will find on the break out board:
The Actions screen allows you to specify the type of action that BTTracer
should perform when it encounters the events specified in the Events
window.
Actions Window Layout
The Actions window divides into three sections: a left, a center, and a right
section.
The left section displays Event buttons such as Header buttons and Error
buttons. The number of Event buttons displayed depends on the number of
Events you selected in the Events window. If you selected no Events, no
Event buttons will display. If all Events were selected, eight Event buttons
will display.
The center section displays two Counter buttons marked Count1 and
Count2. These buttons are used for counting events and are permanent
features of this section.
This center section can also hold Event buttons such as Errors and PayloadHdr1. Event buttons in this section are used to create triggers based on a
sequence of Events. Event Sequencing is explained later in the chapter.
The right section has three permanent buttons for setting actions. These
buttons are Trigger, Filter Out/In,andRestart. These buttons allow you
to set actions such as triggering or filtering.
Arrows connect Event, Counting, and Action buttons. Arrows represent
the current associations between actions and events. As will be described
further on, these associations can be easily changed with the mouse.
Action Buttons - Their Functions
The Action buttons in the right side of the window provide the means of
setting triggers, filters, and restarts. To set an action, you simply drag your
mouse from an Event to an Action. As described further on, this movement
will link the two via an arrow.
Trigger
The Trigger button enables event triggering.
Filter In/Out
The Filter In/Out button allows events to be filtered in or out of the
recording.
Restart
The Restart button causes the two counters Count1 and Count2 to be reset
to zero.
Counting Buttons - Their Functions
The center section of the Actions window has two buttons for counting
events called Count1 and Count2. Below these buttons, you can add Event
buttons to create Event Sequencing.
Count1, Count2
Count1 and Count2 are counters for specifying how many events must occur
before an event can cause a trigger. Counters allow conditions to be made
such as "Trigger after the 21st Poll packet" (see screenshot below).
The Actions window showing a condition based on a Poll packet and a
counter. This condition reads "Trigger after the 21st Poll packet."
Connecting Events to Counters
To connect an event to a counter, click an Event button, then click one of the
two counter buttons. An arrow will appear that will join the Event to the
Counter and then to a trigger.
This latter connection between the Counter button and the Trigger button
occurs because counters always work in association with triggers. Counters
act as assistants to triggers.
Setting Multiple Conditions with Counters
You can create multiple event conditions by linking a counter to multiple
events or by linking two counters to two or more events.
Linking Multiple Events to One Counter - When two or more Events are
connected to a counter, it creates a condition that reads "Trigger when the
counter value is reached by any combination of the specified events."
The following example reads "Trigger after any combination of 5 Poll
packets and FHS packets have occurred."
Linking Two Events to Two or More Counters - If an Event is linked to
Count1 and a second event is linked to Count2, it creates an "or" statement.
This statement reads "Trigger when Count1 OR Count2 has reached their
specified values."
Blue Dot Menus
Count1, Count2 and a few other buttons in the Actions
window have blue dots in their top left-hand corners that
indicate the presence of context-sensitive menus. These menus
let you set the button’s values and/or operations. Click the left
mouse button on a dot to open the menu.
This example reads "Trigger when Count1 has counted 5 Poll packets or
Count2 has counted 10 FHS packets."
The Count1 and Count2 blue dot menus allow the value of their counters
to be changed. The value you specify here tells BTTracer how many
instances of an event must take place before a trigger occurs. The counter
can be set between 1 and 65,535.
To set a Counter,
Step 1Click on the blue dot in the upper left corner of the Count
button.
Yo u s e e t he Change Counter Value menu:
Step 2Click Change Counter Value
Yo u s e e t he Input Counter Value menu
Step 3Enter an input value to tell the Analyzer how many times this
event must occur before triggering the end of a recording
Step 4Click OK.
You may connect as many Event buttons to a counter as you like.
However, the Counter does not treat each event as a discrete specification
but treats them all as one event.
As an example, look at the specifications set in the following screen:
Counter 1 has been set to trigger four events after 15 occurrences. But the
Counter does not count 15 occurrences for EACH event. It counts ALL
events as they happen to occur until it reaches a total of 15 and then
triggers.
Filter Out/In Blue Dot Menu
The Filter Out/In button toggles between "Filter Out" and "Filter In".
• Filter In records ONLY those packets related to the specified
event.
• Filter Out records all packets EXCEPT those related to the
specified event.
To filter an event in or out of a recording,
Step 1Click the blue dot on Filter Out. (Note: the button may say
Filter In depending on the last action specified.)
Yo u s ee t h e Filter Out/In menu:
Use this menu to toggle the selection between Filter Out and Filter In.
External Trigger Output" if that is the choice presented.)
If you have chosen "Enable External Trigger
Output", a small arrow will appear on the right side
of the button. This arrow indicates that a condition
has been set for creating an external output signal.
Choosing "Disable External Trigger" will cause the arrow to disappear.
Enabling High Pulse, Low Pulse or Pulse Toggle Signal Outputs
Once External Trigger Output has been enabled, you can configure the
output signal to one of three formats:
Pulse High - This is the default format. The Pulse High setting causes the
Analyzer to transmit a 5 volt, 16.66 nanosecond signal.
Pulse Low - This format causes the Analyzer to transmit a -5 volt, 16.66
nanosecond signal.
Toggle - This format causes the Analyzer to transmit a signal that will
toggle with each trigger event between a continuous 5 volt signal and a
continuous -5 volt signal.
Step 2Drag the arrow to the desired Action button.
Step 3With the pointer over an Actions button, click again the left
mouse button again.
Event Sequencing
If you drag your mouse from one event button to another, you will create a
compound condition known as an Event Sequence. An event sequence is a
condition that says "Trigger when you see the following sequence of
packets." The example below may help to clarify.
This example means "Trigger when you see a packet with an Null Header
followed by a packet with a FHS Header."
The arrow is replaced with a black line connecting the Event button to
the Action button.
90
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.