18
www.lairdtech.com
Laird Technologies
BTM510/511
Bluetooth
®
Multimedia Module
Inquiry Response Format
The format of an inquiry result will be:
<cr,lf><bd_addr>,<dev_class>,<friendly_name>,<rssi>,<eir_data><cr,lf>
<bd_addr> = 12 digit, hexadecimal;
<dev_class> = six digit, hexadecimal;
<friendly_name> = printable ASCII character, enclosed by ‘ “ ‘
<rssi> = signed two digits decimal
<eir_data> = printable ASCII character whenever possible, otherwise a byte is displayed as ¬2 digit
hexadecimal with preceding ‘\’, enclosed by ‘ “ ‘
For example the data block 01 41 42 43 44 02 03 45 46 04 0A 0D will be presented as
“\01ABCD\02\03456\04\0A\0D”
No validation is performed on incoming EIR data.
If a higher significant flag is set and a lower significant bit is not set in S 330, for each disabled item
a comma is printed.
Example: S330 = 9 (ADDR enabled, COD and FN disabled, RSSI enabled)
Inquiry Response:
<cr,lf>123456789012,,,-54
<cr,lf>123456789014,,,-54
<cr,lf>OK<cr,lf>
2. AT+BTIV<devclass> { Inquire }
As per AT+BTI but the response comprises for all inquiry responses:
1.
the Bluetooth device address
2.
device class code
S register 330 is not referenced.
3. AT+BTIN<devclass>
{ Inquire }
As per AT+BTI but the response comprises for all inquiry responses:
1.
the Bluetooth device address
2.
device class code
3.
friendly name
S register 330 is not referenced.
4. AT+BTIR<devclass> { Inquire }
As per AT+BTI but the response comprises for all inquiry responses:
1.
the Bluetooth device address
2.
device class code
3.
friendly name
4.
rssi (receiver signal strength indicator)
S register 330 is not referenced.
5. AT+BTIE<devclass> { Inquire }
As per AT+BTI but the response comprises for all inquiry responses:
1.
the Bluetooth device address
2.
device class code
3.
friendly name
4.
rssi (receiver signal strength indicator)
5.
extended inquiry data
S register 330 is not referenced.
AT COMMAND SET
REFERENCE
