User's Guide

© Copyright LM Technologies Ltd Page 19 of 70
www.lm-technologies.com
LM074 SPP with GAP Central Application v1.1
d. After module completes the pairing procedure successfully,
module adds this device to its whitelist.
e. Pairing procedure runs at the background and can show the
status of pairing at any time. e.g. above report shows the
pairing report has displayed while showing Service-scan
report.
xiii. If LEAutoScan server setting is ON then, module starts scanning
services supported on the remote device and displays the report.
If LEAutoScan server setting is OFF, module waits for commands
from user to scan the services (FINDSERV).
3.5.4 “AT*LEDROP”\r\n
i. Execution only command
ii. Command is used to disconnect the BLE connection. Command
requires peer devices BT address.
iii. BLE connection disconnection command format:
“AT*LEDROP=1030005b0012”\r\n
iv. Response for BLE drop connection will be OK if the module is
connected to the BLE device with the same address provided in
Drop command.
v. Response for BLE drop connection will be ERR if the module is not
connected with any BLE device or BD address mentioned in the AT
command is not same as the connected BLE device.
vi. Module shows a report for the disconnection command e.g.
at*ledrop=1030005b0012at*ledrop=1030005b0012
OK
REP*:BLE_DIS_CONN:=1030-00-5b0012,2 err_code:0000
vii. Error code 0000 mentions the device has terminated connection
gracefully i.e. either device started disconnection procedure.
viii. Number 2 near the BD address mentions the BLE Connection ID
(refereed to BLEconn=? response).
ix. If disconnection is started by remote device or due to link loss the
indication for disconnection is shown as below with the reason
code.
“REP*:BLE_DIS_CONN:= 1030-00-5b0012,2 err_code:0019”
x. Refer to the error code in the appendix.