User Manual Part 2
Table Of Contents
- 7. Recording Options
- 8. Display Options
- 9. Reading a CATC Trace
- 10. Decoding Higher Protocols
- 10.1 Introduction
- 10.2 LMP and L2CAP Messages
- 10.3 Decoding and Viewing Higher Protocol Data
- 10.4 Tooltips
- 10.5 Viewing Packets in LMP and L2CAP Messages
- 10.6 Types of LMP and L2CAP Messages
- 10.7 Viewing L2CAP Channel Connections
- 10.8 Viewing Protocol Messages and Transactions
- 10.9 Changing Protocol Assignments
- 11. Other Features
- 12. How to Contact CATC
- 13. Warranty and License
105
Merlin Protocol Analyzer User’s ManualCATC Version 1.6
10. Decoding Higher Protocols
10.1 Introduction
Merlin can decode LMP and L2CAP messages, and RFCOMM, SDP, TCS,
HDLC, PPP, and OBEX protocols. The default is packet level decoding,
which means that baseband packets will be displayed when you first view a
trace. If these packets are carrying LMP, L2CAP or higher protocols, the
protocols will display as undecoded fields such as the L2CAP packet below.
By issuing a decode command, Merlin can decode these LMP and higher
fields and display the data in summary statements called LMP/L2CAP
Messages, Protocols Messages, and Protocol Transactions.
10.2 LMP and L2CAP Messages
LMP and L2CAP Messages are lines in a trace that summarize LMP and
L2CAP actions such as an LMP connection request. LMP and L2CAP
Messages summarize the type of action, the number of packets involved in
the action, and the device performing the action. If the message is carrying
higher protocol data such as RFCOMM, TCS, OBEX or SDP data, the
message displays this data in an undecoded format that can be decoded later.
Undecoded L2CAP fields
Undecoded higher protocol data