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
42
CATC MERLIN MOBILE 1.00 CHAPTER 5
User’s Manual Recording Bluetooth Traffic
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
DRAFT
• FLOW — The 1-bit flow indication field can be set to 1 (flow-on) or 0 (flow-off).
Selecting Don’t care causes Merlin Mobile to ignore this field.
• Length — Use the Length field definition to specify the length, in bytes, of the payload
body (the payload minus the payload header and CRC code). For single-slot packets, the
length value may range from 1 to 29 bytes. For multi-slot packets, the length may be
from 1 to 339 bytes. To define the Length field, select an operator (=, >, <, >=, or <=)
from the drop-down list and enter a value, in bytes, in the text box.
Data Pattern
The Data Pattern event allows the user to specify an 8-byte payload data pattern.
To specify a data pattern, enter the pattern into the text box or click the Edit button to open
the Data Editor dialog.
Data Editor dialog
The Data Editor dialog can be used to define the data pattern. Enter bit pattern, Mask, or
Match values for data bytes 00 through 07. Bit patterns should be entered in binary (1 or 0);
use “X” for irrelevant values. Mask and Match values should be entered in hexadecimal.
Errors
Use the Errors event to set up actions based on one or more of these errors:
• CRC Error — A CRC error in the packet data payload of the previous Bluetooth data
packet.
• HEC Error — An HEC (header error check) error in the packet header for the previous
Bluetooth data packet.
• FEC Error — An uncorrectable FEC (Forward Error Correction) error in the packet
header for the previous Bluetooth data packet.
• FEC Threshold Exceeded — Indicates that the number of single-bit FEC errors detected
since the current recording started has exceeded the specified value.
• Invalid Packet Type — An invalid value was detected in the packet type field of the
packet header for the previous Bluetooth data packet.
• Header Length Error — Indicates that a Bluetooth data packet was terminated before all
bits of the packet header were received.
• Payload Length Error — Indicates that the payload of a Bluetooth data packet was
either longer than expected, or that a Bluetooth data packet terminated before the
expected end of the payload data.
• Sync Lost — Indicates that a loss of piconet synchronization occurred during the fre-
quency slot prior to this slot.