User's Manual

119
BTTracer Protocol Analyzer User’s ManualCATC Version 1.0
Changing an OBEX Client or Server Status
If the beginning sequence of traffic is not recorded in a trace, the
client/server status of the transmitting devices will not be preserved in the
trace. In this case, the OBEX Client/Server pop-up menu will become
active and you will be able to change the assignment.
Decoding BNEP
BNEP (Bluetooth Network Encapsulation Protocol) is a protocol that allows
devices to encapsulate network protocols such as IP. Since BNEP can carry
different types of network protocols, you need to tell BTTracer what
protocol the BNEP is going to be carrying. You do this via a script file
called bnep.dec that is read during the initialization of the BTTracer
software. This file tells BTTracer how to decode BNEP fields. Once read,
BNEP can be correctly decoded by pressing the button on the toolbar.
If the decode file is not read at initialization, BTTracer will display the data
in an undecoded format.
For more information on BNEP decoding, see a supplemental document on
BNEP in the support directory on the CATC web site:
http://www.catc.com/products/support/sup_BTTracerbluetooth.html
Decoding HID
HID (Human Interface Device) is a profile associated with traffic from
devices such as a mouse or a keyboard. To decode HID traffic, you will
need to tell BTTracer what types of HID traffic it will be recording. You do
this by editing a script file called hid.dec. BTTracer reads this file during the
initialization of the BTTracer software. This file tells BTTracer how to
decode the HID fields. Once read, HID can be correctly decoded by
pressing the button. If the decode file is not read at initialization,
BTTracer will display the data in an undecoded format.
BTTracer has the capability to decode HID (Human Interface Device
profile) based on version 0.90b of the specifications.