Teledyne LeCroy Merlin - Users Manual - Manual (Page 148)

140
Merlin Protocol Analyzer User’s Manual CATC SW Version 2.0
In the screenshot shown above, for example, AM Address is selected. On
the right, you see that only Address 1 is in bold. This indicates that only a
single device was transmitting traffic in the displayed trace.
Event Groups
Event Groups are categories of events that can occur in a trace. Clicking on
an Event Group will display a list of Event types on the right side of the Find
window that occur within each Event Group.
AM Address
Contains a list of seven Active Member addresses. Bold entries represent
devices that occur in the trace.
Master/Slave
Contains two options labeled Master and Slave. Selecting an option will
cause Merlin to search for traffic based on the selected role.
Packet Type
Contains a list of all Bluetooth packet types. If a packet type occurs in the
trace, it will appear in bold.
Acknowledge
Contains a list of three Acknowledge types: Explicit NAK, Implicit NAK,
and ACK. The three Acknowledge types are responses a device can issue
to attempts to transmit packets to it.
A device can send an Acknowledgment in two ways: through setting the
ARQN field to 0 (= explicitly not acknowledged), to 1 (explicitly
acknowledged) or by sending an empty packet that does not have an ARQN
field (= implicitly not acknowledged).
Explicit NAK - Explicitly not acknowledged. An Explicit NAK is an
explicit response by a device that it did not receive a data packet. The
Explicit NAK is transmitted in the ARQN field (=Acknowledgment
Request Negotiation field). ARQN=0 means ’Explicit NAK.’
Implicit NAK - Implicitly not acknowledged. An Implicit NAK is a NAK
that is implied rather than explicitly stated. If a device responds to a
data packet by sending an empty packet, the NAK is implied.
ACK - Acknowledged. If a data packet is successfully transmitted to a
target device, the target device acknowledges the received packet by
setting the ARQN field to 1.
Acknowledgments are easily seen in Merlin traces because Merlin adds an
Ack’d field on data packets of the transmitting device. This means that you
do not have to hunt through the trace to see if the packet was acknowledged.