User's Guide

© Copyright LM Technologies Ltd Page 30 of 70
www.lm-technologies.com
LM074 SPP with GAP Central Application v1.1
xi. Above report shows the WRCharval command is successful only on
characteristic 0005 and 0007.
xii. If the WrCharVal command fails in execution, then the error code
reported by BLE-stack is reported to user in failure report. E.g.
Err_code:fd , Err_code:0e, Err_code:0d
xiii. Refer Appendix section for more details on error code.
3.8.5 “AT*SIWRWORESP”\r\n
i. Execution only command
ii. This command is used to send data to BLE device for the
characteristic which has properties as “Si_Wrt” i.e. 0x40.
iii. Command format is “AT*WRCHARVAL=conn-ID, char-Handle,
length, actual-bytes”.
iv. e.g. “at*WRCHARVAL=1,0019,10,12345abcdef!()12” command is
used to send data to 1st connected device, on characteristic 0019.
No of bytes to write are 16 (0x10) and actual bytes are
12345abcdef!()12.
v. As shown in the example command, no of bytes to transmit is hex
value
vi. As shown in the example command, actual data bytes are not
separated by comma. When the value 0x31 is sent i.e. ASCII 1 is
sent, the data buffer is copied and sent to remote device
transparently.
vii. Note : The actual data bytes to be sent should not have “\r\n” as
the data itself because it is the terminating string for AT command
parser.
viii. For command “AT*WRWORESP=conn-ID, char-Handle, length,
actual-bytes” module gives OK response if all the following
conditions are true:
a. connection ID is correct (if module is connected to 3 devices
and CID mentions 4, then it is invalid)
b. Characteristic handle has Wr_req properties
c. Value of “length” field is less than 21 i.e. (0x15).
d. Actual data bytes are same as value of “length” field.
ix. After module responds to this command as OK, module sends the
data to remote BLE device.