84
www.lairdtech.com
Laird Technologies
BTM510/511
Bluetooth
®
Multimedia Module
5. Legacy Response Format (BISM2)
Some BISM2 responses have been slightly changed on BTM modules in order to provide enhanced
functionality. If required, a BISM2 compatible response format can be enabled by S Register 329.
Table 3.63 shows the implications of enabled/disabled legacy response format.
Task
S-Register
Comment
Enable legacy response format
(BISM2 compatible)
S329 [0..1]
0 = disabled (default)
1 = enabled
Table 3.62: Enabling/Disabling legacy response format
Command
Legacy response format
enabled (S329=1)
Legacy response format disabled
(S329=0)
“AT+SPH”;”ATH1101”
Response = “NO CARRIER”
If SPP was connected, response =
“NO CARRIER 1101”
If SPP was not connected, re-
sponse = “NO CARRIER”
“AT+APH”;”ATH110D”
Response = “NO CARRIER”
If A2DP was connected, response
= “NO CARRIER 110D”
If A2DP was not connected,
response = “NO CARRIER”
“AT+AVH”;”ATH110E”
Response = “NO CARRIER”
If AVRCP was connected, re-
sponse = “NO CARRIER 110E”
If AVRCP was not connected,
response = “NO CARRIER”
“AT+HSH”;”ATH1108”
Response = “NO CARRIER”
If HS instance was connected,
response = “NO CARRIER 110E”
If HS instance was not connected,
response = “NO CARRIER”
“AT+HSGH”;”ATH1112” Response = “NO CARRIER”
If HSG instance was connected,
response = “NO CARRIER 1112”
If HSG instance was not connect-
ed, response = “NO CARRIER”
“AT+HFH”;”ATH111E”
Response = “NO CARRIER”
If HF instance was connected,
response = “NO CARRIER 111E”
If HF instance was not connected,
response = “NO CARRIER”
“AT+HFGH”;”ATH111F” Response = “NO CARRIER”
If HFG instance was connected,
response = “NO CARRIER 111F”
If HFG instance was not connect-
ed, response = “NO CARRIER”
“AT+DUH”;”ATH1103”
Response = “NO CARRIER”
If DUN was connected, response
= “NO CARRIER 1103”
If DUN was not connected, re-
sponse = “NO CARRIER”
Table 3.63: Implications of S329
AT COMMAND SET
REFERENCE