User's Manual
Table Of Contents
- Conformance Statements
- References
- Table Of Contents
- Chapter 1: Merlin Mobile Overview
- Chapter 2: Getting Started
- Chapter 3: Merlin Mobile User Interface
- Chapter 4: Gathering Device Information
- Chapter 5: Recording Bluetooth Traffic
- 5.1 Assisted Recording with Recording Wizard
- 5.2 Manual Recording with Recording Options
- 5.3 Recording Status
- 5.4 Uploading Piconet Data
- 5.5 Recording Options Dialog
- 5.6 Saving Recording Options
- 5.7 Loading Recording Options
- 5.8 Bluetooth Encryption
- Chapter 6: CATC Trace Files
- Chapter 7: Decoding Trace Data
- Chapter 8: Reports
- Chapter 9: Contact and Warranty Information
85
CATC MERLIN MOBILE 1.00 CHAPTER 8
User’s Manual Reports
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
By default, the Traffic Summary window is docked along the bottom half of the Merlin
Mobile display area. If desired, it may be moved out of the application window to another
area of the screen.
8.4.1 Traffic Summary Tree
The left pane of the Traffic Summary Report window
(Figure 8-5) displays, in the form of a tree diagram, a
summary of the packets and protocols in a Trace file. The
top level of the tree contains branches for Entire Trace and
Packets in Range (x to y). Both branches can be expanded
to show additional levels of the Trace data, including
packets and protocols. Most levels can be expanded
further, providing more and more specific summaries of
the transactions.
Note: Higher-level protocol types won't appear in the tree diagram
unless they have been decoded in the Trace file.
Selecting a level in the tree will cause a detailed summary
of the packets in the selected level to be displayed in the
right pane of the Traffic Summary Report window.
Entire Trace
The Entire Trace branch can be expanded to display these
levels:
• Frequency distribution — Summarizes the traffic
by frequency range.
• Baseband Packets — Summarizes the traffic at the packet level. This level can be
further expanded to show the packets categorized by AM_ADDR (member address)
and role (master and slave).
• Higher-level transaction types — If higher-level transactions have been decoded in
the Trace file, they will be summarized in the Traffic Summary Tree. This level can
Figure 8-4: Traffic Summary report
Figure 8-5: Traffic Summary Tree