● For safety and warning information, please read this
manual before attempting to use the equipment.
● Additional safety and warning information is provided
within the MT8852B Bluetooth Test Set Operation
Manual. Please also refer to it before using the
equipment.
● Keep this manual with the equipment.
ANRITSU CORPORATION
Document No.: M-W3969AE-7.0
Safety Symbols
DANGER
WARNING
CAUTION
To prevent the risk of personal injury or loss related to equipment malfunction, Anritsu
Corporation uses the following safety symbols to indicate safety-related information. Ensure
that you clearly understand the meanings of the symbols BEFORE using the equipment.
Some or all of the following symbols may be used on all Anritsu equipment. In addition, there
may be other labels attached to products that are not shown in the diagrams in this manual.
Symbols Used in Manuals
This indicates a very dangerous procedure that could
result in serious injury or death if not performed properly.
This indicates a hazardous procedure that could result in
serious injury or death if not performed properly.
This indicates a hazardous procedure or danger that could
result in light-to-severe injury, or loss related to equipment
malfunction, if proper precautions are not taken.
Safety Symbols Used on Equipment and in Manuals
The following safety symbols are used inside or on the equipment near operation locations to
provide information about safety items and operation precautions. Ensure that you clearly
understand the meanings of the symbols and take the necessary precautions BEFORE using
the equipment.
This indicates a prohibited operation. The prohibited operation is indicated
symbolically in or near the barred circle.
This indicates a compulsory safety precaution. The required operation is indicated
symbolically in or near the circle.
This indicates a warning or caution. The contents are indicated symbolically in or
near the triangle.
This indicates a note. The contents are described in the box.
These indicate that the marked part should be recycled.
MT8852B
Bluetooth Tes t S et
Remote Programming Manual
All rights reserved. No part of this manual may be reproduced without the prior written permission
of the publisher.
The operational instructions of this manual may be changed without prior notice.
Printed in Japan
Safety-2
Notes On Export Management
This product and its manuals may require an Export License/
Approval by the Government of the product's country of origin
for re-export from your country.
Before re-exporting the product or manuals, please contact us
to confirm whether they are export-controlled items or not.
When you dispose of export-controlled items, the products/
manuals need to be broken/shredded so as not to be
unlawfully used for military purpose.
BLE Extended Signal Generator Mode (Supports Data Length Extension) . . 9-3
BLE Extended Signal Generator Mode (Supports Bluetooth 5 - 2LE and BLR)9-4
BLE Extended Signal Generator Mode (Supports Bluetooth 5.1 - Constant Tone
This manual provides instructions on the remote operation of the following model types:
• MT8852B Bluetooth Test Set (with EDR and Audio)
• MT8852B-040 Bluetooth Test Set (without EDR or Audio)
• MT8852B-041 Bluetooth Test Set (without EDR but with Audio)
• MT8852B-042 Bluetooth Test Set (with EDR but without Audio
• MT8852B-043 Bluetooth Test Set for Low Energy tests only (without EDR or Audio)
Explanations in this manual apply equally to all of the above model types unless otherwise
stated.
Comments on this Manual
Every effort has been made to ensure that this manual is thorough, easy to use, and free from
errors. However, to ensure continued improvement, we would welcome your comments on
this, or any other Anritsu document.
Please contact us at the address below if you have any comments, good or bad, find any errors
or omissions, or have any suggestions on how our documentation could be improved further.
Bluetooth.support@anritsu.com
Your comments will be logged and reviewed, and whenever possible, will be reflected in a
subsequent release of the document.
Software Versions
This manual provides details of the remote operation of the following software versions:
• MT8852B:5.00.020(N)
• MT8852B-040:5.00.020(N)
• MT8852B-041:5.00.020(N)
• MT8852B-042:5.00.020(N)
• MT8852B-043:5.00.020(N)
Some of the features documented in this manual may not be available to users of earlier
software releases. Check the version of software you are using by following the procedure
below.
1. Power up the unit and press .
2. Select "MT8852B" and press .
3. Select "Identity" and press .
4. Check the number that displays to the right of "Version".
1-1
General Information
Notification of Software Release
The MT8852B software is periodically updated as new features are added to meet market
demands. To receive automatic notification of software releases, send a blank e-mail with the
subject heading of "MT8852B Software Notification Request" to
Bluetooth.support@anritsu.com. You will receive an e-mail when new software is available to
download.
Associated Documentation
In addition to this manual, the following document is also available on the Product CD
shipped with the MT8852B Bluetooth Test Set.
Tab le 1-1.Associated Documentation
Part numberDocument
W3968AEMT8852B Bluetooth Test Set Operation Manual
TM
The above document is in PDF format and can be viewed using Adobe Reader
program that can be downloaded from http://www.adobe.com/.
, a freeware
Conventions
The following conventions have been adopted in this manual.
Tab le 1-2.Notation Conventions
ItemConvention
MT8852BUnless otherwise stated, the name “MT8852B” is used generically
throughout this manual to refer to all model types of the MT8852B
Bluetooth Test Set. Refer to the table on the following page for
details of model types.
EUTThe Bluetooth enabled device being tested is referred to as the EUT
(Equipment Under Test).
The five hard keys (Run, Loop/Stop, Script, Config, and Preset) are
depicted using an image of the key in question.
The keys on the numeric keypad are depicted using an image of the
key in question.
[Setup]The names of soft keys appearing on the front panel are enclosed in
square brackets.
“Output Power”Test appearing on the display is enclosed in quotation marks when
used in a body of text. Items with quotation marks are selected by
pressing .
> “MT8852B”A chevron (>) is used to indicate that the user should select the items
or keys in sequential order.
[Log Capture]The names of software windows and dialogs are enclosed in square
brackets.
1-2
Command Format
1-2Command Format
The commands are presented in a structured manner as shown below.
Set command formatFor each command, the command name and syntax are
detailed. For example:
COMMAND<ws>[<param1>,<param2>,<paramN>]
Each of the allowable values for the command argument(s) is
described.
RemarksAn expanded description of the command, how to use it, and
programming hints or restrictions.
ExampleAn example of the command in use.
Query command format The command used when requesting a response from the
MT8852B.
ResponseThe command string returned from the MT8852B.
ExampleAn example of a response from the MT8852B.
1-3
General Information
1-4
Chapter 2 — GPIB Overview
The MT8852B Bluetooth Test Set can be operated remotely through a General Purpose
Interface Bus (GPIB) connection to a host computer. The MT8852B conforms to the
IEEE488.1 and IEEE488.2 standards.
2-1Requirements when using GPIB
A GPIB card, cable, and the associated control software are required to communicate with the
MT8852B over the GPIB bus.
2-2Syntax
The following rules must be adhered to when sending GPIB commands to the instrument.
1. An ASCII space must be present between the command mnemonic and the first
parameter.
2. All subsequent parameters must be separated by commas (,).
3. Multiple commands may be sent on the same line, but each must be separated by a
semicolon (;).
The conventions used are detailed in the table below.
Table 2- 1 .GPIB Syntax Rules
ItemMeaning
The parameters or characters within the angled brackets must be present.
< >
ws
[ ]
,
;
Throughout this document the angled brackets are employed merely as a
convention to help users interpret the commands. They must not be included in the
command string when issuing commands over GPIB.
White space character.
Optional parameters. Do not include the square brackets in the command string.
Parameter separator. All GPIB commands having more than one parameter must
use the comma (,) separator between each parameter.
Message unit terminator. A GPIB command message can be made up of a
number of command units separated by the semicolon, as seen in the following
example.
COMMAND param1a,param1b;COMMAND2 param2a
The mnemonics and all the parameters can use either upper or lower case
characters unless specified otherwise.
2-1
GPIB Overview
2-3Termination
All commands sent over the GPIB interface to the MT8852B must be terminated with either
(or both) of the following:
End Of String (EOS):The ‘\n’ or 0x0A character.
End Of message Indicator (EOI):A hardware line on the GPIB interface bus.
2-4Suffixes
Parameters containing floating-point values can use the E-0x convention or a suffix
multiplier. The GPIB unit conventions specified by the IEEE have been implemented for the
suffix units and multipliers. The suffix unit is always allowed but is not required and is
shown in brackets where appropriate.
The following table lists the numeric suffixes for the MT8852B Bluetooth Test Set. Suffix
units are optional and can be omitted.
Tab le 2-2.Suffix Multipliers and Units
Suffix MultipliersSuffix Units
DefinitionMnemonicDefinitionMnemonic
1E18EXDecibelsDB
1E15PEdB ref to 1 mWDBM
1E12TdB ref to 1 mVDBMV
1E9GdB ref to 1 V
1E6MAPercentPCT
1E3KSecondsSEC
1E-3MSecondsS
1E-6UVoltsV
1E-9NWattsW
1E-12PHertzHZ
1E-15FKilo HertzKHZ
1E-18AMegahertzMHZ
DBUV
For example 10 microseconds can be represented in any of the following formats: -
a. Straight value format0.000010
b. With the E format10E-6
c. Suffix multiplier format10U
2-2
GPIB 488.2 Registers
2-5GPIB 488.2 Registers
The following diagram shows the GPIB event and status registers. The meaning of each bit is
described below.
Status Byte Register and Service Request Enable Register
Figure 2-1.Status Byte and Service Request Enable Registers
Table 2- 3 .STB and SRE Bit Definitions
RQS/MSSWhen the Status byte is read via a Serial Poll operation this bit is RQS (Request
Service). When the Status byte is read via the *STB? Command this bit is MSS
(Master Summary Status). This bit has no function in the Service Request Enable
Register.
(Request service) This bit is set when one of the other bits in the status byte is set
and the corresponding bit in the Service Request Enable Register (SRE) has been
set. When this bit is set an SRQ is indicated over the GPIB interface. The SRQ is
cleared by a serial poll, the status byte returned to the controller and the bit that
caused the SRQ is cleared.
(Master Summary Status) This bit is the inclusive OR of the bitwise combination
(excluding bit 6) of the Status Byte register and the Service Request Enable
register. Note that the *STB? Command does not alter the Status byte, nor will it
clear an SRQ.
2-3
GPIB Overview
Tab le 2-4.
ESB(Event status bit) When a bit is set in the event register and the corresponding bit
has been set in the event status enable register (ESE) the ESB bit in the status
register is set.
MAV(Message available) This bit is always set when there is data available to be read
out from the output buffer and it is cleared when the output buffer is empty.
CHG(Change indication) This bit is cleared at power ON initialisation, following a serial
poll, or upon sending the *CLS command. This bit is set when one of the change
bits has been set and the corresponding bit in the change status enable (CHE)
register has been set.
EPS(EUT Power Status) This bit is cleared at power ON initialisation or upon sending
the *CLS command. This bit is set when the EUT power matches the maximum or
minimum power. Use the status command to read whether max or min was
reached.
ETF(Equipment Test Fail) This bit is cleared at power ON initialisation or upon sending
*CLS. This bit is set to indicate a test failure if the following conditions apply: One of
the tests has failed (the instrument will set the appropriate bit in the ETF or EETF
registers) and the appropriate bit within the ETE or EETE registers has been
enabled by the user prior to running the test. See definitions of the ETF, EETF,
ETE, EETE in this manual for more details.
INS(Instrument status) This bit is cleared on initialisation and when the *CLS command
has been sent. This bit is set when one of the instrument status bits has been set
and the corresponding bit in the instrument status enable (INE) register has been
set.
Note
The Status Byte register is read via a Serial Poll or with the *STB? Command. It
cannot be written to directly by the user. The Service Request Enable Register is
written to with the *SRE command and read with the *SRE? Command. It is
cleared by *CLS.
2-4
GPIB 488.2 Registers
Standard Event Status Register and Standard Event Status Enable Register
Figure 2-2.Standard Event Status and Standard Event Status Enable Registers
Table 2- 5 .ESR and ESE Bit Definitions
PONPower On bit. This bit is set on power up of the device only and cleared if the
instrument is reset or receives a *CLS command. This bit only indicates that a power
on has occurred.
URQUser request
CMDCommand error. Received an unrecognized command.
EXEExecution error. Could not execute a command. For example, a parameter is out of
the allowable range.
DDEDevice Dependent Error. The specific error can be found by using the ERRLST
command.
QYEQuery Error
RQCRequest Control. GPIB controllers only.
OPCOperation Complete. When a program message that includes the *OPC command
has been completed and the GPIB interface is idle with any responses read out of the
output buffer this bit is set. For example, if the last command in a configuration
sequence is *OPC, the OPC bit in the event status register is set when that
configuration list has been completed.
The Standard Event Status Register is read with the *ESR? Command. Reading
Note
the ESR clears it. The Standard Events Status Enable Register is written to with
the *ESE command and read with the *ESE? command. Both registers are
cleared by *CLS.
2-5
GPIB Overview
EUT Fail Register and Fail Enable Register
Figure 2-3.UET Fail and Fail Enable Registers
This EUT register is cleared on the start of a test or script. When a test completes, if it has
failed the test limit parameters enabled to give a fail result the corresponding bit in this
register is set. These events can be programmed to provide an SRQ by setting the
corresponding bit(s) in the Equipment Under Test Fail Enable Register (ETE).
Tab le 2-6.ETF and ETE Bit Definitions
OPOutput power test fail bit. This bit indicates that the output power test failed the limit
criteria set.
PCPower control test fail bit. This bit indicates that the power control test failed the limit
criteria set.
ICInitial carrier test fail bit. This bit indicates that the initial carrier test failed the limit criteria
set.
CDCarrier drift test fail bit. This bit indicates that the carrier drift test failed the limit criteria
set.
MCModulation index test fail bit. This bit indicates that the modulation index test failed the
limit criteria set.
SSSingle slot sensitivity test fail bit. This bit indicates that the single slot sensitivity test
failed the limit criteria set.
MSMulti slot sensitivity test fail bit. This bit indicates that the multi slot sensitivity test failed
the limit criteria set.
MPMaximum input power test fail bit. This bit indicates that the maximum input power
sensitivity test failed the limit criteria set.
NoteThe EUT Fail register is read with the *ETF?.
2-6
GPIB 488.2 Registers
Instrument Status Register and Instrument Status Enable Register
Figure 2-4.Instrument Status and Instrument Status Enable Registers
The INS register displays the present status of the instrument and can be used to provide
SRQs for test or script completion and the connection status of the instrument by setting the
corresponding bits in the INE register.
Table 2- 7 .INS and INE Bit Definitions
LEFGBLE Frame generator counter stopped. This bit is set when the BLE Frame
generator has sent the defined number of packets to the EUT.
OVTInstrument Over temperature Warning.
INQEUT Address Inquiry complete.
CMPScript or test completion. This bit is cleared when a test or script has started and is
set on its completion or termination.
DISDisconnect. This bit is cleared when a connection has been made and set when
disconnected.
CONConnection. This bit is set when a connection has been made and cleared when
the connection no longer exists.
A Device Dependant Error (DDE in the ESR register) will indicate if an error
Note
The INS register is read with the *INS? Command. It cannot be cleared by reading it or by
the *CLS command. The INE register is written to by the *INE command and read by the
*INE? Command. It is cleared by *CLS.
occurred, causing the test or script to be aborted. The ERRLST command can be
used to get the cause of the termination.
2-7
GPIB Overview
Change Register and Change Enable Register
Figure 2-5.Change and Change Enable Registers
The CHG register indicates when a change of state has occurred in the instrument, and can
be used to provide SRQs by setting the corresponding bits in the CHE register.
The CHG register is read with the *CHG? command. It is cleared by reading it or with the
*CLS command.
The CHE register is written to with the *CHE command and read by the *CHE? command. It
is cleared by the *CLS command.
Tab le 2-8.CHG and CHE Bit Definitions
SCCThis bit is set to indicate when a SCO status has changed.
Use the "STATUS" command to retrieve the present SCO status. (MT8852B and
MT8852B-041 only)
USBThis bit is set to indicate when a USB attached status has changed.
Use the "STATUS" command to retrieve the present USB status. (MT8852B and
MT8852B-041 only)
AFHThis bit is set to indicate that a change has occurred to the channel map. Use
"AFHCFG? ACM" to retrieve the present state of the map.
2-8
GPIB 488.2 Registers
EDR EUT Fail Register and EDR EUT Fail Enable Register (MT8852B and
MT8852B-042 only)
Figure 2-6.EDR EUT Fail and EDR EUT Fail Enable Registers
The EDR EETF Test Fail register is cleared at the start of a test or script. If an EDR test
fails any of the test limits applied, the appropriate bit within the EETF register is set (e.g. if
the EDR Sensitivity test fails, the EBS bit is set to '1'). To program the GPIB to provide an
SRQ event upon failure of any of the EDR tests, the appropriate bit(s) must be set within the
EDR EETE Fail Enable register.
Table 2- 9 .EETF and EETE Bit Definitions
EPCEnhanced Power Control test fail bit. This bit indicates whether or not the test failed
the limits criteria set.
EMPEDR Maximum Input Power test fail bit. This bit indicates whether or not the test failed
the limits criteria set.
EFSEDR Floor Sensitivity test fail bit. This bit indicates whether or not the test failed the
limits criteria set.
EBSEDR Sensitivity test fail bit. This bit indicates whether or not the test failed the limits
criteria set.
EDPEDR Differential Phase Encoding test fail bit. This bit indicates whether or not the test
failed the limits criteria set.
ECMEDR Carrier Frequency Stability and Modulation Accuracy fail bit. This bit indicates
whether or not the test failed the limits criteria set.
ERPEDR Relative Transmit Power. This bit indicates whether or not the test failed the
limits criteria set.
NoteThe EDR EUT Fail register is read with the *EETF? query.
2-9
GPIB Overview
2nd EDR EUT Fail Register and 2nd EDR EUT Fail Enable Register (MT8852B
and MT8852B-042 Only)
Figure 2-7.2
nd
EDR EUT Fail and 2nd EDR EUT Fail Enable Registers
Except the test targets, the 2nd EDR EETF Test Fail register and the 2nd EDR EETE Fail
Enable register are same as the EDR EETF Test Fail register and the EDR EETE Fail
Enable register.
nd
Table 2-10. 2
EETF and 2nd EETE Bit Definitions
EGTEDR Guard Time test fail bit. This bit indicates whether or not the test failed the limits
criteria set.
ESTEDR Synchronization Sequence and Trailer test fail bit. This bit indicates whether or
not the test failed the limits criteria set.
Note
The 2
nd
EDR EUT Fail register is read with the *EETF2? Query.
2-10
GPIB 488.2 Registers
BLE EUT Fail Register and BLE EUT Fail Enable Register (MT8852B-043
and units with option 27 only)
Figure 2-8.
The BLE LEETF Test Fail register is cleared at the start of a test or script. If a BLE test fails
any of the test limits applied, the appropriate bit within the LEETF register is set (e.g., if the
BLE Sensitivity test fails, the LESS bit is set to '1'). To program the GPIB to provide an SRQ
event upon failure of any of the BLE tests, the appropriate bit(s) must be set within the BLE
LEETE Fail Enable register.
Table 2- 11. LEETF and LEETE Bit Definitions
LEPRIPER integrity test fail bit. This bit indicates that the PER integrity test failed the limit
criteria set.
LEOPOutput power test fail bit. This bit indicates that the output power test failed the limit
criteria set.
LEICDInitial carrier test fail bit. This bit indicates that the initial carrier test failed the limit
criteria set.
LEMIModulation index test fail bit. This bit indicates that the modulation index test failed the
limit criteria set
LESSSingle slot sensitivity test fail bit. This bit indicates that the single slot sensitivity test
failed the limit criteria set
LEMPMaximum input power test fail bit. This bit indicates that the maximum input power
sensitivity test failed the limit criteria set
LEPSTx power stability test fail bit. This bit indicates that the Tx power stability test failed
the limit criteria set
NoteThe EUT Fail register is read with the *LEETF? query.
2-11
GPIB Overview
2-6GPIB over RS232
Version 1.1 or above of the control software supports the use of RS232 in addition to GPIB
commands. Use the RS232 connector on the rear panel of the unit.
Hardware handshake CTS and RTS lines are used to control the flow of data in and out of the
tester and must be available in the cable as hardware handshaking is always enabled. The
RS232 cable used between the COM port on the PC and the connector on the rear of the
MT8852B must be of a Null Modem type such as that supplied with the MT8852B itself.
The DTR and DSR lines are connected together within the tester.
The MT8852B Bluetooth test set’s serial connector pin-outs are:
Table 2-12. Serial Connector Pin Outputs
PinSignal
1NOT USED
2Rx Data
3Tx Data
4DTR handshake signal
5Signal ground
6DSR handshake signal
7RTS handshake signal
8CTS handshake signal
9NOT USED
The serial interface baud rate can be set using the MT8852B “System Interfaces” menu under
the menu. Available baud rates are; 1200, 2400, 4800, 9600 (default), 19200, 38400,
57600, and 115200. The other RS232 parameters are predefined as 8 bits, no parity and 1
stop bit and cannot be changed.
Commands are entered in the same manner as the GPIB interface, conforming to the GPIB
command format. All GPIB commands are supported. There are some additional commands,
specific to the serial interface that are prefixed with an exclamation mark (!). All GPIB type
commands and command strings should be terminated with a new line character (0A hex).
The special serial mode commands do NOT require a termination character.
Requested data is returned in the same format as GPIB, but with a preceding 'R' and a
terminating new line character.
SRQs are available, and are output as an SRQ message 'S' followed by a terminating new line
character. When the SRQ message has been received, an "!SPL" command (equivalent to the
GPIB serial poll) can be issued. The tester will respond with the serial poll data message,
which is a single character, proceeded by 'P' and terminated by a new line character.
A device clear message !DCL can be sent to clear the tester input and output message queues,
and terminate any GPIB or serial actions pending.
2-12
Summary of RS232 Commands
2-7Summary of RS232 Commands
Table 2- 1 3 . Mnemonic Definitions
MnemonicMeaningComments
!DCLDevice clearClear all queues and
terminates any pending
actions.
!SPLSerial pollClears SRQ cause and returns
the status byte.
PResponse to serial pollStatus byte
RReturn of requested data
2-13
GPIB Overview
2-14
Loading...
+ 304 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.