LM074 SPP with GAP Central Application USER GUIDE © All rights reserved. All trade names are registered trademarks of respective manufacturers listed. This manual may not be copied in any media or form without the written consent of original maker.
LM074 SPP with GAP Central Application v1.1 Revision v1.0 v1.1 Date 17/11/2017 25/09/2018 © Copyright LM Technologies Ltd www.lm-technologies.com Changes Description First revision of this document. Added firmware revision history and LED indication information.
LM074 SPP with GAP Central Application v1.1 Contents 1. Introduction ......................................................................................... 7 2. Functionality of SPP with GAP Central application .............................. 7 3. LM074 GAP Central Role ...................................................................... 8 4. 5. 6. 7. 8. 3.1 GAP Central AT commands in brief ...................................................... 9 3.2 Enable GAP Central functionality: ....
LM074 SPP with GAP Central Application v1.1 8.4 GATT_Status_code ........................................................................... 68 8.5 BLE Service UUIDs ........................................................................... 70 © Copyright LM Technologies Ltd www.lm-technologies.
LM074 SPP with GAP Central Application v1.1 Table of Figures Figure Figure Figure Figure Figure Figure 1: 2: 3: 4: 5: 6: Firmware Upgrade Flowchart ............................................................... 52 UART messages when the module is not connected to the peer device ... 55 UART messages when the module opens a partition to write new image . 56 UART messages when the CRC of the received image does not match .... 58 UART messages showing a failure in image verification .......................
LM074 SPP with GAP Central Application v1.1 Firmware Revision History Version:0107 1. Up to Version_0106, the device will indicate the input pairing request to use and process it as per the Accept or Reject response from the user. 2. In Version_0107, this dependency is removed (like the LM048) and the device will accept all the pairing requests. The device will indicate the success or failure of the pairing procedure. Version:0107 – Recreated images for Ver_0107 – 20Th June 2018 1. 2. 3. 4.
LM074 SPP with GAP Central Application v1.1 1. Introduction This document describes the functionality of the “SPP with GAP Central” application. 1. 2. 3. 4. SPP with GAP Central application specific AT commands and information All AT commands and default configurations on device Over the Air Firmware Upgrade procedure Secure simple pairing procedure The LM074 is a dual mode module with the capability for simultaneous connections to Bluetooth (v1.0 – v3.0), and Bluetooth low energy devices.
LM074 SPP with GAP Central Application v1.1 3. LM074 GAP Central Role This section describes the AT commands for the GAP Central role to initiate a connection, pair, whitelist, or read/write data to a BLE peripheral device. AT commands for the SPP role and generic device configuration are described in section 4 “LM074 AT commands and Default configuration”. Every command is terminated with “CR-LF”. The module will begin parsing the AT command string after receiving the “CR-LF” sequence.
LM074 SPP with GAP Central Application v1.1 3.1 GAP Central AT commands in brief The table below shows the AT commands for the GAP Central role with examples for reference.
LM074 SPP with GAP Central Application v1.1 Sr no AT command string Command type Default setting AT command format for reference 13 “AT*WRWORE SP” Execution only - AT*WRWORESP=CID,Ch ar-Handle,no-ofbytes,actualbytes e.g. at*wrworesp=5,0012,14, 01234567890123456789 14 “AT*RDCHARV AL” Execution only - AT*RDCHARVAL=CID,ch ar-handle e.g. At*rdcharval=5,0020 15 “AT*WRCHARV AL” Execution only - AT*WRCHARVAL=CID,ch ar-handle,no-ofbytes,actualbytes e.g.
LM074 SPP with GAP Central Application v1.1 3.2 Enable GAP Central functionality: 3.2.1 “AT*ENBGAP”\r\n i. Query and Set command. ii. To query settings use the command “AT*ENBGAP=?” \r\n iii. Response to the query command will be “OK”/”ERR” and report will be “REP*:GAP_ENABLE=ON” or “REP*:GAP_ENABLE=OFF” iv. By default, this setting is OFF i.e. the GAP Central role is disabled. The module is only initialized for the SPP functionality. v. To enable the GAP Central role, use the command “AT*ENBGAP=ON”. vi.
LM074 SPP with GAP Central Application v1.1 ERR at*enbgap=onat*enbgap=on OK Module soft-Reset..SPP+GapCentral_Message_Loop GATT Initialised REP*:LESEC=Success at*settings=?at*settings=? OK NAME=LM074_GAP_Central ADDR=0002-5b-00a5a5 FLOW=OFF SPPRole=SLAVE ACON=OFF BOND=0000-00-000000 DPIN=OFF PIN=1234 GAP_ENABLE=ON LE_SEC=OFF LE_AUTO_SCAN=ON VER=074LM_GAPCEN_01.06 REP*:SETTINGS=END at*enbgap=?at*enbgap=? OK REP*:GAP_ENABLE=ON at*enbgap=onat*enbgap=on ERR at*enbgap=offat*enbgap=off OK Module soft-Reset..
LM074 SPP with GAP Central Application v1.1 iv. The module reports the name and BT address of the device as soon as it finds the advertisement packet and keeps on updating the report as devices are discovered. v. The module stops the BLE scanning process when it finds 10 BLE devices and displays END of report message. vi. There is no time limit set in the firmware to end the BLE scanning process. If the user wants to terminate the scanning process, they should issue the “AT*LEFIND=OFF” command. vii.
LM074 SPP with GAP Central Application v1.1 xii. If the LM074 has setting “AT*LESEC=OFF”, LM074 reports BLE devices even if not present in its Whitelist. If setting is “AT*LESEC=ON”, LM074 will only report advertising devices which are in its whitelist. xiii. In the discovery report, after the BD-address there is an indication for “advertising Indication type” ranging from 0 to 5 as mentioned below. a. ble_adv_event_connectable_undirected = 0 = Connectable Undirected Advert. b.
LM074 SPP with GAP Central Application v1.1 3.4 BLE security commands: 3.4.1 “AT*LESEC”\r\n i. Query and Set command. ii. LESEC stands for Low Energy Security i.e. whether to apply whitelist security or not. iii. Query command to query the setting is “AT*LESEC=?”\r\n. iv. Query report is “REP*:LE_SEC=OFF”\r\n or “REP*:LE_SEC=ON”\r\n. v. When LESEC is ON, the module will scan advertising packets only from whitelist added devices and connect to the devices already added to whitelist (i.e.
LM074 SPP with GAP Central Application v1.1 3.5 BLE connection commands: 3.5.1. “AT*LEAUTOSCAN”\r\n i. Query and set command. ii. Enable or disable the feature to scan the connected BLE peer device automatically for its services. iii. Low energy auto scan query: “AT*LEAUTOSCAN=?”\r\n. iv. Low energy auto scan query report: “REP*:LE_AUTOSCAN_SERVER=ON” (Module default setting as LE-Auto-Scan enabled) v. Low energy auto scan enable command: “REP*:LE_AUTOSCAN_SERVER=ON”\r\n.
LM074 SPP with GAP Central Application v1.1 vii. Start and end of report is mentioned. viii. E.g. In above report, row “= 3 : 1032-00-5b0002 : 0203” mentions module has 3rd connection with 1032-00-5b0002 device and CID given by BLE stack is 0203. ix. CID given in above response is referred while reading/writing data with AT commands, reporting disconnection, notification etc. User should note this carefully. x. Response to this module depends on current state of the module for BLE connections. xi.
LM074 SPP with GAP Central Application v1.1 ix. If the module is successfully connected to a remote device it will show a report with details about the connection. E.g. “REP*:BLE_CONNECTED:=1030-00-5b0012-0 : 1 : 0080 : 0017 : 0008”\r\n x. Here report includes extra information for the connection details as below. a. 1030-00-5b0012 is BD address of the remote BLE device. b. -0 with the address mentions Address type of remote BLE device. c.
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.
LM074 SPP with GAP Central Application v1.1 3.6 BLE Services/characteristic scan commands: 3.6.1 “AT*FINDSERV”\r\n i. Execution only command ii. Command is used to scan services supported on connected BLE device. iii. User needs to state connection ID for the device whose services are to be scanned. E. g. “at*findserv=1” finds services on 1st connected device. iv. Module provides a detailed report for the services supported by the remote device. v.
LM074 SPP with GAP Central Application v1.1 v. Considering the above report for services, below are the possible commands. a. Scan characteristics of single service i.e. 1800 service, handles are 0001 and 0005. Command should be “AT*findchar=1,0001,0005” b. Scan characteristics for first two services i.e. 1800 and 180a. User shall issue command as “at*findchar=0001,0016”. c. Scan characteristics of all services in single command, user shall issue command “at*findchar=1,0001,ffff”. vi.
LM074 SPP with GAP Central Application v1.1 3.7 BLE read data from Characteristic: 3.7.1 “AT*RDCHARVAL”\r\n i. Execution only command ii. This command is used to read data from the BLE device for the characteristic which has properties as read “Rd” i.e. 0x02. iii. The command format is “AT*RDCHARVAL=conn-ID, char-Handle”. iv. e.g. “at*rdcharval=1,0003” command is used to read data from 1st connected device, for characteristic 0003. v.
LM074 SPP with GAP Central Application v1.1 response. If user analyse the RX line on Oscilloscope or protocol analyser, all bytes can be seen. 3.7.2 “AT*RDMULTCHAR”\r\n i. Execution only command ii. This command is used to read data from multiple characteristic on single remote device. iii. Read data from BLE device for the characteristic which has properties as “Rd” i.e. 0x02. iv. Maximum of 5 characteristic’s data can be read in one single command. v.
LM074 SPP with GAP Central Application v1.
LM074 SPP with GAP Central Application v1.
LM074 SPP with GAP Central Application v1.1 3.8 BLE write data on Characteristic: 3.8.1 “AT*ENBCCFG”\r\n i. Execution only command. ii. Command used to enable the Client-Configuration-Flag (CCFG) on specific characteristic. iii. When the module scans the characteristics of the device, it shows the CCFG flag if supported by that characteristic. E.g Serial-OverGatt service supports this flag (highlighted yellow in below report). iv.
LM074 SPP with GAP Central Application v1.1 3.8.2 “AT*INDESPr\n i. Execution only command. ii. This command gives feedback to server/peripheral for notification indication from server/peripheral. iii. This command is used to acknowledge the sever that client(BLECentral) has received characteristic value Indication, and server(BLE-Peripheral) may send another indication. iv. Command format is “at*INDRESP=Conn-ID”. v. e.g.
LM074 SPP with GAP Central Application v1.1 ix. After the module responds to the command with “OK”, the module sends the data to the remote BLE device. x. If the remote device receives the data and sends feedback to the LM074, that feedback is displayed on UART. xi. E.g. report shows, “REP*:WRWORESP=1:0019:Success” which indicates the data has been received by the remote device successfully. 1 is the CID-given by module and 0019 is the characteristic handle.
LM074 SPP with GAP Central Application v1.
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.
LM074 SPP with GAP Central Application v1.1 3.8.6 NOTIF_IND notification Indication i. Indication given by module. ii. When the module receives data from the remote BLE device, it notifies the user on UART. iii. E.g.
LM074 SPP with GAP Central Application v1.1 4. LM074 AT commands and Default configuration This section describes the AT command structure for the LM074 module. Serial terminals (such as Hercules, HyperTerminal, Tera Term or Putty) can be used for serial communication with the LM074. Every command is terminated with “CR-LF”. The module will begin parsing the AT command strings after receiving “CR-LF” sequence. AT Commands are case insensitive e.g. “At*Resp=On”, “at*resp=on” and “AT*RESP=ON” are all valid.
LM074 SPP with GAP Central Application v1.1 AT commands expects the BT address in the string. In this document “0126f357215” is considered a reference BT address, whereas 0012 is nap, 6f is uap and 357215 is lap in the BT address. Users should use the BT address of their devices. 4.1 AT commands The table below shows all the AT commands that are supported on the LM074 module and the default settings wherever applicable. 4.1.
LM074 SPP with GAP Central Application v1.1 4.1.3 Bluetooth security settings commands: Sr no 1 2 3 4 5 6 7 8 9 AT command string AT*PIN AT*DPIN AT*MITM AT*IOTYPE AT*DEL AT*PASSKEY AT*PASSCFM AT*STOPPAIR AT*PAIRLIST Command type Default setting Query and set Query and set Query and set Query and set Execution only Execution only Execution only Execution only Query only 1234 OFF OFF NO_InOut ------ 4.1.
LM074 SPP with GAP Central Application v1.1 4.2 Module Settings commands: 4.2.1 “AT*ADDR”\r\n i. Query only command ii. Address query: “AT*ADDR=?”\r\n iii. Address query report: “REP*:ADDR=00025b00a5a5” 4.2.2 “AT*NAME”\r\n i. ii. iii. iv. v. Query and set command Name query: “AT*NAME=?”\r\n Name query report: “REP*:NAME=LM074_2_Default” Name set command: “AT*NAME=testname” Default name: (Depends on firmware version number) 4.2.3 “AT*ECHO”\r\n i. ii. iii. iv. v. vi.
LM074 SPP with GAP Central Application v1.1 REP*:RESP=ON at*name=?at*name=? OK REP*:NAME=068LM_SPP_0104 x. Below is the sequence of messages when ECHO is OFF and RESP is ON. at*echo=offat*echo=off OK at*echo=?OK REP*:ECHO=OFF at*resp=?OK REP*:RESP=ON at*name=?OK REP*:NAME=068LM_SPP_0104 xi. Below is the sequence of messages when ECHO and RESP are both off. The module will show only reports for the query commands. The module will not show any indication messages for connect or disconnect.
LM074 SPP with GAP Central Application v1.1 viii. Enabling pair-ability may generate further events of incoming pairing/connection requests. ix. Module displays the message “IND*:PAIR=00126f357215” to indicate that the device with BT-address 00126f357215 is requesting to pair. x. To accept the pairing request the user should respond as “AT*PAIR=00126f357215,accept”\r\n. xi. To reject the pairing request user should respond as “AT*PAIR=00126f357215,reject”\r\n. xii.
LM074 SPP with GAP Central Application v1.1 4.2.10 “AT*SETTINGS”\r\n i. Query only command ii. Module settings query: “AT*SETTINGS=?”\r\n iii. Report for “AT*SETTINGS=?” command is multiple line, at the end of the report a message “REP*:SETTINGS=END” is delivered. iv. Module settings query report varies according to DPIN setting. If DPIN is OFF i.e. supporting to BT2.0, Module PIN is displayed. If DPI is ON, i.e. support to BT2.1, then settings for IO-capability, MITM are displayed.
LM074 SPP with GAP Central Application v1.1 ACON=OFF BOND=0000-00-000000 DPIN=OFF PIN=1234 GAP_ENABLE=ON LE_SEC=OFF LE_AUTO_SCAN=ON VER=074LM_GAPCEN_01.06 REP*:SETTINGS=END FLOW=OFF SPPRole=SLAVE ACON=OFF BOND=0000-00-000000 DPIN=ON MITM=OFF IOTYPE=NO_InOut GAP_ENABLE=ON LE_SEC=OFF LE_AUTO_SCAN=ON VER=074LM_GAPCEN_01.06 REP*:SETTINGS=END v. Also, Module response depends on ENBGAP settings. Refer section 1.2 “Enable GAP Central role” for more details. vi.
LM074 SPP with GAP Central Application v1.1 4.3.2 “AT*PAR”\r\n i. Query and set command ii. Parity query command: “AT*PAR=?”\r\n iii. Parity query report: “REP*:PARITY=None(0)” (Module uses default parity , parity = none). Number in curly brackets shows the serial number as per below table. iv. Parity set command: “AT*PAR=1” (Set Module parity as odd) v. Module need to not to perform power-on-off after change of parity setting. vi.
LM074 SPP with GAP Central Application v1.1 iv. Flow control set command: “AT*FLOW=ON” (Set module flow control ON) v. If the user is changing the flow control of device, after accepting command with OK response, module shows report as “REP*:FLOW_CHANGE= IN_Progress” vi. Module will perform reboot in changed flow control mode vii. If module is in flow control OFF mode and user gives command to make the flow control OFF, then module will respond as OK but shall not perform reboot.
LM074 SPP with GAP Central Application v1.1 4.3.9 “AT*MODEM”\r\n: i. Query and set command ii. MODEM query command: “AT*MODEM=?”\r\n iii. MODEM query report: “REP*:MODEM=NONE” (module uses default MODEM settings as “none”) iv. MODEM set command: “AT*MODEM=LOCAL” or “AT*MODEM=Remote”. v.
LM074 SPP with GAP Central Application v1.1 ii. Dynamic PIN query command: “AT*DPIN=?”\r\n iii. Dynamic PIN query report: “REP*:DPIN=OFF” (module uses default DPIN as off) iv. Dynamic PIN set enable or disable command: “AT*DPIN=ON” or “AT*DPIN=off”. v. When module has DPIN setting as OFF, Module uses a fixed PIN provided default as 1234. vi. When module has DPIN setting as ON, module expects the dynamic PIN from customer as per the MITM and IO-Type settings. vii. For further on BT2.
LM074 SPP with GAP Central Application v1.1 4.4.5 “AT*DEL”\r\n i. ii. iii. iv. Execution only command. User issues this command to delete the device from its paired list. DEL command: “AT*del=00126f357215”\r\n “OK” response will be provided if the string entered has valid BT address. Module deletes the device from its pairing list. v. “Err” response will be provided if invalid BT address, invalid length of address is provided. vi.
LM074 SPP with GAP Central Application v1.1 iii. Pairlist report may be multiple line if module is paired with more than one device. Paired devices report is shown in following format “REP*:PAIRLIST=00126f357201, REP*:PAIRLIST=00126f357215, REP*:PAIRLIST=END” iv. Pairlist report can be multiple line, to indicate end of the report “REP*:PAIRLIST=END” is displayed at end. 4.5 SPP Related commands: 4.5.1 “AT*FIND”\r\n i. ii. iii. iv. v. vi. vii. viii. Execution only command.
LM074 SPP with GAP Central Application v1.1 3 SPP Master only At*role=master REP*:SPPRole=MASTER iv. When the module is in Dual mode, it can accept incoming SPP connection as well as initiate outgoing SPP connection whereas module cannot accept or initiate new connection when it is already connected to any remote device. E.g. if module has established an outgoing connection, then after terminating the outgoing connection it can accept incoming connection. v. In slave-only role 1. BOND=Valid-BD-address.
LM074 SPP with GAP Central Application v1.1 4.5.4 “AT*BOND”\r\n i. Query and set command. ii. Set command: “AT*BOND=00126f357215”\r\n. Device will establish connection only with remote device having BD address as 00126f357215. iii. Set command: “AT*BOND=000000000000”\r\n. Device will establish connection with any device. iv. v. This setting is applicable for Master-only, slave-only role.
LM074 SPP with GAP Central Application v1.1 1. “IND*:CONN_FAILURE=00126f357215” message is shown to indicate the failure in connection with BD address 00126f-357215. 2. “IND*:CONNECTED=00126f357215” message is shown to indicate the SPP connection is successfully established and the devices are in connected state. 3. Once the devices are connected, LM951/LM074 is in SPPconnected-online-data mode. Every string entered by host on UART is treated as data and is transmitted to connected device. 4.
LM074 SPP with GAP Central Application v1.1 iv. connection termination command: e.g. “AT*DROP=00126f357215”\r\n v. “OK” response will be provided if the string entered has valid BT address and module is connected to the device with entered BT address and module is in online-command mode. vi. “Err” response will be provided if invalid BT address, invalid length of address is provided, module is not connected to any device. vii.
LM074 SPP with GAP Central Application v1.1 5. LM074 Over The Air Firmware Upgrade Procedure This section describes the procedure to perform an over the air firmware upgrade for the LM074 module. Users can use serial terminals like Hercules, HyperTerminal, Tera term or Putty etc. for serial communication with LM074 module. In this document, the term “new image” refers to the firmware image to which the LM074 will be upgraded to.
LM074 SPP with GAP Central Application v1.1 5.1.4 LM074 requirements: i. LM074 can be SPP master (initiate connection with remote device) or SPP Slave (Accept connection request from remote device). 5.2 Firmware upgrade procedure Flow chart: The flow chart below illustrates the firmware upgrade procedure, highlighting messages when the upgrade operation is successful. The comments show the failure points as FP1 to FP5.
LM074 SPP with GAP Central Application v1.1 Figure 1: Firmware Upgrade Flowchart Note: The firmware upgrade password is dependent on the current firmware version. © Copyright LM Technologies Ltd www.lm-technologies.
LM074 SPP with GAP Central Application v1.1 5.3 Possible Failure points and corrective actions The following section describes the possible failure points while performing an Over the Air firmware upgrade. It also covers possible reasons for errors what a user can do to correct them. 5.3.1 Failure point 1: i. After entering the escape sequence “+++”, the module should respond as OK and enter in Online-connected-command-mode. ii.
LM074 SPP with GAP Central Application v1.1 e. If the module replies as “ERR”, the user should try entering the correct password and try to get the message “Ready to receive OTA file”. f. The module can process successfully even though it already had more than one failure attempt while getting “Ready to receive OTA file” message. 5.3.3 Failure point 3: i. Once the module enters in Online-connected-command-mode, the user should provide the firmware upgrade password through AT command. ii.
LM074 SPP with GAP Central Application v1.1 Figure 2: UART messages when the module is not connected to the peer device 5.3.4 Failure point 4: i. After the module shows the message “Ready to receive OTA file”, it is ready to receive the upgrade image. ii. After the peer device begins sending the file, the module opens internal memory partition2 or partition3 to write this image iii. The message “PTN2”/”PTN3” indicates that the module is writing the file to partition2/partition3. iv.
LM074 SPP with GAP Central Application v1.1 Figure 3: UART messages when the module opens a partition to write a new image © Copyright LM Technologies Ltd www.lm-technologies.
LM074 SPP with GAP Central Application v1.1 5.3.5. Failure point 5: i. The message “PTN2”/”PTN3” indicates that the module is writing a file to partition2/partition3, module is receiving the file and writing it to the partition. ii. After the peer device shows that it has successfully sent the file, LM074 will close the partition. iii. After the partition is closed, the message “Sign_OK” indicates that the module has received Signature. iv.
LM074 SPP with GAP Central Application v1.1 Figure 4: UART messages when the CRC of the received image does not match vii. If the module shows “failed-Sign” message: a. If module shows the “failed-Sign” message, it indicates that the signature of module firmware is different than the signature of the new image. b. This indicates that the firmware upgrade procedure has been followed correctly but there is error in new image provided for the firmware upgrade. c.
LM074 SPP with GAP Central Application v1.1 Figure 5: UART messages showing a failure in image verification 5.3.5 Successful firmware Upgrade: i. The image below depicts the messages shown by the module during a successful firmware upgrade procedure ii. After showing message “V_Pass_2” or “V_Pass_3”, the module performs warm reset and starts executing the new image. iii. In the image below, the message “Entering Message Loop” indicates that the device has performed warm reboot.
LM074 SPP with GAP Central Application v1.1 Figure 6: UART messages showing successful firmware upgrade © Copyright LM Technologies Ltd www.lm-technologies.
LM074 SPP with GAP Central Application v1.1 6. Simple Secure Pairing between LM074 and remote device This section describes the indication messages given by the LM074 module during the pairing procedure. It also covers the AT commands that a user will need to provide as per the settings of DPIN, MITM and IOTYPE.`` The LM074 uses BT2.1 security supporting the dynamic PIN, but is also compatible with BT2.0 devices which shares fixed PIN during the pairing procedure. 6.1 Pairing of LM074(BT2.1) with BT2.
LM074 SPP with GAP Central Application v1.1 If IO-type is keyboard only, the LM074 will expect the passkey from the user and use it internally for the pairing procedure. When the IO-type is display only, the LM074 will display the passkey and the user should use the same passkey on the remote device to complete the pairing procedure. When IO-type is Display with yes/no confirmation, the LM074 displays passkey and expects confirmation from the user whether the passkey for remote device is the same.
LM074 SPP with GAP Central Application v1.1 ii. iii. iv. v. vi. with “AT*PAIR=00126f357215, accept”, LM074 starts pairing procedure. When the LM074 starts the pairing procedure with a remote device and has IO-capability as Display only, LM074 shows the Passkey for remote device as message “IND*:PASSKEY=311303” here number 311303 is for reference only and should vary for every device.
LM074 SPP with GAP Central Application v1.1 6.2.5 LM074 has settings DPIN=on, MITM=off, IO-type=noInput-no-output i. Pairing with the remote device might be successful if the remote device also has DPIN=on, MITM=off and IO-type as no one. ii. If the remote device has MITM=on or IO type other than no input no output, the LM074 cannot pair with that device. 7. LED Indication 7.1 Power on LED sequence 1. All LEDs blink fast during power on for 3 seconds.
LM074 SPP with GAP Central Application v1.1 7.4 LED2 SPP Connected state: 1. LED2 (Blue LED) shall be constantly ON when the module/adapter is connected to the remote device over a SPP connection. 2. LED2 will be constantly ON when it is connected to a remote device while its role is slave or master. 3. Slave-mode: 1. When the module/adapter is in slave mode, LED2 will keep blinking fast until the module/adapter enters into Connected state or Pairing mode. Master-mode: 1.
LM074 SPP with GAP Central Application v1.1 8. Appendix 8.1 Abbreviations SSP BT BLE BD-Address BT2.0 BT2.1 MITM IOTYPE DPIN PIN 8.2 Simple Secure Pairing Bluetooth Bluetooth low energy Bluetooth address of device Bluetooth 2.0 stack Bluetooth 2.
LM074 SPP with GAP Central Application v1.1 8.3 1. 2. 3. 4. write 0x08 "Wr_req " Writes of the Characteristic Value with response. User can write on this characteristic with AT*WRCHARVAL command notify 0x10 "CCFG " Client configuration flag for notification enable If user enables this flag, remote device shows notification indicate 0x20 "Indi " Indications of a Characteristic Value with acknowledgement.
LM074 SPP with GAP Central Application v1.1 5. uuid[0] = 0x00112233, uuid[1] = 0x44556677, uuid[2] = 0x8899aabb, and uuid[3] = 0xccddeeff. 6. If the service-UUID is 128-bit, it is completely mentioned in the report of FindServ e.g. “00005500-d102-11e1-9b23-00025b00a5a5” 7. If the characteristic has 128-bit UUID then only first 32 bits are shown e.g. 8.
LM074 SPP with GAP Central Application v1.
LM074 SPP with GAP Central Application v1.1 8.5 BLE Service UUIDs BLE Service UUIDs for reference only.
2.2 List of applicable FCC rules FCC Part 15.247 2.3 Specific operational use conditions This product is a Dual-modular transmitter policy independent of any host. Not applicable. 2.4 Limited module procedures This product is a S Dual-modular transmitter. It is not a limited module. Not applicable. 2.5 Trace antenna designs This product has an Integral antenna. Not applicable. 2.
2.9 Information on test modes and additional testing requirements Contact LM Technologies Ltd. will provide stand-alone modular transmitter test mode. Additional testing and certification may be necessary when multiple modules are used in a host. 2.10 Additional testing, Part 15 Subpart B disclaimer To ensure compliance with all non-transmitter functions the host manufacturer is responsible for ensuring compliance with the module(s) installed and fully operational.
FCC Warning This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. NOTE 1: Any changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
FCC Radiation Exposure Statement: This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. End users must follow the specific operating instructions for satisfying RF exposure compliance. This module certified that complies with RF exposure requirement under mobile or fixed condition, this module is to be installed only in mobile or fixed applications.
Note 7: For all products market in US, OEM has to limit the operation channels in CH1 to CH11 for 2.4G band by supplied firmware programming tool. OEM shall not supply any tool or info to the end-user regarding to Regulatory Domain change. IC WARNING This device contains licence-exempt transmitter(s) that comply with Innovation, Science and Economic Development Canada’s licence-exempt RSS(s). Operation is subject to the following two conditions: (1) This device may not cause interference.
environnement non contrôlé. Cet équipement doit être installé et utilisé avec un minimum de 20cm de distance entre la source de rayonnement et votre corps. This module is limited to OEM installation only and must not be sold to end-users, end-user has no manual instructions to remove or install the device, only software or operating procedure shall be placed in the end-user operating manual of final products. Additional testing and certification may be necessary when multiple modules are used.
