all | frequencies |
|
|
exhibits | applications |
---|---|---|---|---|---|
manuals |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 2 |
|
15 LM961-0650 UserMan part1 | Users Manual | 4.00 MiB | ||||
1 2 |
|
15 LM961-0650 UserMan part2 | Users Manual | 3.87 MiB | ||||
1 2 | ID Label/Location Info | |||||||
1 2 | External Photos | |||||||
1 2 | Internal Photos | |||||||
1 2 | Test Setup Photos | |||||||
1 2 | Test Report | |||||||
1 2 | Operational Description | |||||||
1 2 | RF Exposure Info | |||||||
1 2 | Cover Letter(s) | |||||||
1 2 | Test Report |
1 2 | 15 LM961-0650 UserMan part1 | Users Manual | 4.00 MiB |
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 co nsent of original maker. Copyright LM Technologies Ltd Page of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. Date v1.0, 7/11
(2017 First revision of this document v1. 8/12/2017 Minor document revisions. 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: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
-Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
-Consult the dealer or an experienced radio/TV technician for help. NOTE 2: 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. Please notice that if the FCC identification number is not visible when the module is installed inside another device, then the outside of the device into which the module is installed must also display a label referring to the enclosed module. This exterior label can use wording such as the following: Contains FCC ID: VVXLM961 any similar wording that expresses the same meaning may be used. This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. The module is limited to OEM installation ONLY. The OEM integrator is responsible for ensuring that the end-user has no manual instruction to remove or install module. A separate approval is required for all other operating configurations, including portable configurations with respect to Part 2.1093 and difference antenna configurations. There is requirement that the grantee provide guidance to the host manufacturer for compliance with Part 15B requirements. Copyright LM Technologies Ltd Page of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. Contents Introduction Functionality of SPP with GAP Central application LM961 GAP Central Role 3.1 GAP Central AT commands in brief 3.2 Enable GAP Central functionality:
3.3. BLE discovery commands:
3.4 BLE security commands:
3.5 BLE connection commands:
3.6 BLE Services/characteristic scan commands:
3.8 BLE write data on Character istic:
22 LM961 AT commands and Default configuration 238 41 AT commands 29 42 Module Settings commands:
31 4.3 UART Settings commands:
35 4.4 Bluetooth Security Settings commands:
38. 45 SPP Related commands:
40 46 Firmware Upgrade commands:
44 LM961 Over The Air Firmware Upgrade Procedu re 45 S41 Pre. requisites for Firmware upgrade:
45 5.2 Firmware upgrade procedure Flow chat 46 5.3 Possible Failure points and corrective actions. 48 Simple Secure Pairing between LM961 and remote device 55 6.1 Pairing of LM961(BT2.1) with BT2.0 devices 55 6.2 Pairing of LM961 (BT2.1) with BT2.1 devices 55 Appendix 58 71 Abbreviations 58 7.2 58 7.3 GATT UUID type 59 7.4 GATT_Status_code 60 7.5 BLE Service UUIDs 61 Copyright LM Technologies Ltd Page of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. Table of Figures Figure 1: Firmware Upgrade Flowchart. 47 Figure 2: UART messages when the module is not connected to the peer device 50 Figure 3: UART messages when the module opens a partition to write a new image 51 Figure 4: UART messages w_ hen the CRC of the received image does not match 52 Figure 5: UART messages showing a failure in image verification Figure 6: UART messages showing successful firmware upgrade 54 Copyright LM Technologies Ltd Page of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. Introduction This document describes the f unctionality of the SPP with GAP Central application. SPP with GAP Central application specific AT commands and information
|| AT commands and default configurations on device Over the Air Firmware Upgrade procedure Secure simple pairing procedure The LM961 is a ual. ode module with the capability for simultaneous connections to Bluetooth v1.0. 3.0) and Bluetooth low en roy. Jevices. _M Technologies supports various firmware applications on the LM961 module enabling users to develop their own applications with AT commands. Functionality of SPP with GAP Central application he SPP with GAP M961 can ither Ee SPP
(aster or Slave ual mode with one SPP connection at a time The SPP role suppo rts BOND, ACON, and features similar to those of LM Technologies. legacy pr. oducts such as the LMO48, LMO72 and LM400, 3luetooth low energy it will be in. the:
SAP Central role an
| can establish connections to up to low energy peripherals simultane ously. Users can have maximum of active connections with this application:
ive low energy and one SPP) transfer between devices AT commands. For 1e uetooth low energy SAP Central ale, the user can perform functions. normally performed by Android tablets or phone s.Au ser can discover nearby Bluetooth low energy yeripherals, ind up to ten devices will be reported. The then connect to any of those device s and read or write data on various services or characteristics with t he help of AT commands. The Bluetooth low energy connection also support. whitelist 1g you add the paired devices to the vhitelist. t will only report advertising packets from the devices added to the whitelist or only connect to devices on the whitel ist. Copyright LM Technologies Ltd Page of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. LM961 GAP Central Role This section describes the AT commands for SAP C ntral role to initiate connection, pair hitelist, or read write data to BLE peripheral device AT commands for the SPP role and generic device config uration are desc ribed section LM961 AT commands and Default configuration. Every command is termina. dule will begin parsing the AT. command string after receiving the CR LF sequence. Fore ery AT command issued by user via JART 12 th nodu esponds with IK/ERR. the user issues an incorrect AT command string (e.g. instead of "AT*Setting:
the user issues "AT*Setting:
or issues orrect AT command string but in an nvalid state (e.g. the user issues connection command "AT*CONI 01122334455" while the SPP role is. Slave) the module will respond with ERR. AT commands are used. to enable or disable the GAP Central role of the module. By default this mode is disa led ind he nodule only initiates SPP functionality. To enable GAP entral functions, use the AT command AT*ENBGAP=ON. The m odule will perform oft reset and iitialize itself wi s0th SPP and GAP C ntral functions nitialized
.When the module has the GAP C entral role disabl ed, for every AT command of GAP Central func tionality or settings, module will respond with ERI When the. odule or the GAP C entral role. upports BLE device discovery, connection initiation, ind reading/writing data. Jsers can use different AT commands to read/write data on BLE pe ripherals or receive updates from BLE peripherals via UART. The SPP with GAP. Central a pplication enables the SPP and BLE connections. If the module is in he ve role it is ready to accept in PP connection at any moment. If. the use r application requires GAP Central roles, then set the SPP role as Master and ACON as OFF This means hat module will nly onnect to. remote SPP device when the connection is initiated by the LM961 module with an AT command. ser application requires SPP connection wi 1 ACON ON an BLE connections it's possible that the LM961 might connect with a remote SPP master device while reading/writing data on 3LE Peripheral or while performing some other task:
This will be indicated to user with. IND*:
ONNECTED=0011223344 55
" If so the user should use the escape sequence
. +++ to come out of SPP Online Connected mode and then issue. the required AT commands. Copyright LM Technologies Ltd Page of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. 3.1 GAP Central AT commands in brief The table te below shows the ATc ommands for the GAP Central role with example for reference. Sr Sr no no AT command string Default Default setting setting for reference AT*ENBGAP Query and Set OFF AT*ENBGAP=?
AT*ENBGAP=ON AT*ENBGAP=OFF AT*LESEC Query and set OFF AT*LESEC=ON
/ AT*LESECOFF T*GETCID Query only AT*LEFIND Execution only AT*LEFIND=ON, AT*LEFIND=OFF AT*LECONN Execution only AT*LECONN=0011223 34455 AT*LEDROP Execution only AT*LEDROI 4455 AT*TENBCCFG Execution only AR Jandle e.g. At*enbccfg=5,0019 AT*BLECONN Query only AT*BLECONI AT*INDRESP Execution only AT*INDRESP=CID e.g. At*indresp=5 AT*FINDSERV. Execution only AT*FINDSER\
e.g. At*findserv=5. AT*FINDCHA Execution only AT*FINDCHAR=CID,St art Handle,End Handle e.g. At*findchar=5,0001, ffff. AT*CLRWHITE Execution only AT*CLRWHITE Copyright LM Technologies Ltd Page of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. Sr no no nmand AT command string nand type Default setting setting AT command format reference AT*WRWORE Sp Execution only AT*WRWORES!
1D,C har Handle,no of bytes,actualbytes e.g. at*wrworesp=5,0012,14
,012345678901234 567 89 AT*RDCHARV. AL Execution only AT*RDCHARVAL=CID, char handle e.g. 0020 AT*WRCHARV AL Execution only AT*WRCHARVAL=CID, char handle,no of bytes,actualbytes e.g. at*wrcharve
,0012,14
,012345678901234567 89 AT*LEAUTOS. CA Query and Set AT*LEAUTOSCAI AT*LEAUTOSCAI AT*LEAUTOSCAT AT*RDMULTC HAR Execution only AT*RDMULTCHAR=CI D,no of read,char handlet,char jandle 2,char handle3,char handle4, char. handleS e.g. At*rdmultchar=5,05,00, 03,0005,0008,0008,0 00a AT*RDLONGC HAR Execution only AT*RDLONGCHAR=CI D,Char Handle e.g. at*rdlongchar=5,0029 AT*SIWRWOR ESP Execution only AT*SIWRWORESP=CID Char Handle,no of bytes,actual bytes e.g. 14,0123456789012345 6789 Copyright LM Technologies Ltd Page of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. 3.2 Ena ble GAP 3.2.1 AT*ENBGAP Query and Set command. To query setting use the command AT*ENBGAP=?"
Response to the query command will be OK"/"ERR and eport will be REP*:GAP_ENABLE=ON or REP*:GAP_ENABLE=OFF By default, thi s setting is OFF i.e. the GAP Central role is disabled. The m odule is onl initialized for the SPP functionality. To enable:
the GAP C entral role, use the command AT*ENBGAP=ON". vi. The module will respond with OK and display the message Module soft. Reset. to indicate that the module is performing soft reset to enable the GAP Central role. vii. After reset.
,the module shows. the ower on sequence:
SPP+GapCentral_Message_Loop the module currently has. ENBGAP set to OFF and command is. issued to turn it OFF, the module shows an ERR response. Similarly, the current setting is ON and the command is issued to turn it ON, the module will output an. ERR response. Response of the AT*SETTINGS=?" query command depends on the ENBGAP setting. Response of the AT*SETTI NGS=? Command display s the settings of LESEC, LE Auto. Scan only if the ENBGAP is ON. SPP+GapCentral_Message_Loop at*enbgap=?
at*enbgap=?
OK REP*:GAP_ENABLE=OFF atsettings="
atsetting:
OK NAME=LM961_GAP_Central ADDR=0002 Sb 00aSa5 FLOW=OFF SPPRole=S. AVE ACON=OFF BOND=0000 00 000000 GAP_ENABLI VER=961LM_GAPCEN_01.01 REP*:SETTING:
at*enbgap-=off at*enbgap=off. ERR at*enbgap=on at*enbgap=on OK Module soft. Reset..SPP+GapCentral_Message_Loop Copyright LM Technologies Ltd Page 10 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. GATT Initialised REP*:LESEt cess atsettinag:
atsetting:
OK NAME=LM961_GAP_Central ADDR=0002 Sb 00aS5a5 FLOW=OFF SPPRole=SLAVE. ACON=OFF BOND=0000 00 000000 LE_AUTO_SCAN=ON VER=961LM_GAPCEN_01.01 REP*:SETTING:
at*enbgap=?
at*enbgap=?
OK REP*:GAP_ENABLE=ON at*enbgap=on at*enbgap=on ERR at*enbgap-=off at*enbgap=off. OK Module soft. Reset..SPP+GapCentral_Message_Loop 3.3 BLE discovery commands:
3.3.1 AT*LEFIND Execution only command. To begin. discovery of nearby BL use the command The m odule responds with OK scanning the devices otherwise it responds as ERR. The m odule reports the name and BT address of the device as. soon as it fi nds the advertisement packet and keep on updating the report as devices are discovered. The m odule 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. |
the user wants to terminate the scanning process, they should issue the AT*LEFIND=OFF command. Copyright LM Technologies Ltd Page 1 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. vii. the module is displaying the scan report and user issues. onnect. ion request to any of the device
, then thes can is. terminated and connection procedure is started. The m odule indicates the beginning and end of discovery response as REP*:BLE_SCAN_REF and REP*:BLE_SCAN_RET ND respectively. Below is an example report for BLE scanning:
t*lefin at*lefind=on OK REP*:BLE_SCAN_REP=STA. RT 1028 ole) 5b0002 :0 00 5b0002 :0 333333 :0 3333 33 333333, LM Serial Server 4:8863 if O00 ole) 000000 :3 00 5b0012, 10, sbO012 SR HR Sensor 00 5b0012, at*lefind=off liefind=off. at*lefind=off atlefin OK"
the user terminates the scanning process by issuing the AT*LEFINI FF" command, the module responds to it with an OK/ERR message but it does not issue an end of repor t message. xi. When the module finds a BLE advertising tl report, it does not show. the device in the report immedia tely, it waits for the advertising packet in which BLE Device name is included. the module find address and name same packet, it displays both. the module finds address only it shows address and waits for name. When the module finds name of the device for which it has reported address previously, it will show name in. report with the serial number as O to indicate this is not new device but onl y name is appended for the device already reported. xii. the LM961 has setting AT*LESEC=OFF", LM961 reports BLE devices even if not present in its Whitelist. If setting is. AT*LESEC=ON", LM961 will only report advertising devices which are in its whitelis xiii. the discovery report, after the BD address there is an indication for advertising Indication type ranging from O to 5 as mentioned below. ble_adv_event_connectable_undirected = 0 =
Connectable Undirected Advert. ble_adv_event_connectable_directed =
Connectable Directed Advert. ble_adv_event_discoverable = 2 = Discoverable advert. Copyright LM Technologies Ltd Page 12 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. ble_adv_event_non_connectable = 3 = Non. connectable. ble_adv_event_scan_response = 4 = Scan Response. ble_adv_event_unknown = 5 = Unknown event type. xiv. The LM961 SPP with GAP central applicatio n also supports SPP connection. The module may establish SPP connection while performing LE discovery. When the module connects. with the SPP device, it enters in SPP. Data mode and shows data from the remote device on UART. It. treat s data sent on local UART as data to be sent to remote device. To access UART for commands and responses, the user need to use. the escape sequence and then continue with other AT commands. XV Refer to the screenshots below atlefinc at*lefind=on OK REP*:
ILE_SCAN_REP=START 1032 00 5b0002 :0 10, 5bO002 :0 3 3333 33 333333 :0 3333 333333, LM Serial Server 4:8863 df be936c MLS IND*:CONNECTEI 1012, 6f 0819c2
+++OK ca 20126e :0 1053 10126f :0 at*lefind=of atlefin OK xvi. Data during the SPP connection and receive of escape command is lost in this report (data is lost as UART is given to SPP connection). 3.4 BLE security commands:
3.4.1 AT*LESEC Query and Set command. LESEC stands for Low Ene. rgy Security i.e. whether to apply whitelist security or not. Query command to query the setting is. AT*LESEC=?"
Query report is. REP":LE_SE(
FF"
or. REP":LE_SE When LESEC is ON, the m odule will scan advertising packets only from whit elist added devices and connect to the devices already added to whitelist (i
. already BLE paired devices) vi. When LESEC is OFF, the m odule will scan and connect to any BLE discoverable and connectable device (module will discover and connect any device even if it is not paired with module before) Note:
the LM961 wants to add a new device in its whitelist then while establishing the connection with the Jevice at first time user should use setting AT*LESEC=OFF". his enables the Copyright LM Technologies Ltd Page 13 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. authentication procedure o start to add a new device to the:
white list. Once the module completes the pairing procedure successfully BLE device is added to the w hite list. Then. the LM961 can use the setting AT*LESEC=ON"
for further connections with the same device. 3.4.2 AT*CLR WHITE Execution only command. This command is used to delete all the devices from BLE paired devices list i.e. White list. Command format is. Module responds OK and deletes all the devices from the whitelist. 3.5 BLE conn ection commands:
3.5.1. AT*LEAUTOSCAN Query and set command. Enable or disable the feature to scan the connected BLE peer device automatically for its services. Low energy auto scan query:
AT*LEAUTOSCAN-
Low energy auto scan query report:
REP*:
LE_AUTOSCAN_SERVER=ON"
(Module default setting as. LE Auto:
Scan enabled) Low energy auto scan enable command:
REP*:LE_AUTOSCAN_SERVER=ON"
lf LE Auto Scan is. enabled, after connection module starts scanning Peer device for its services and characteri stics automatically. vi. Low energy auto scan disable commant REP*:LE_AUTOSCAN_SERVER=OFF _ If disabled, module does not scan the Peer device for its services and characteristics automatically. Module will wait for AT*FindServ command from. user. 3.5.2 AT*B LECONN Query only command. User can query how many BLE connections module is having and details for those connections. Command format is :
AT*BLECONN=?"
GAP Central application can have maximum 5 BLE connections simultaneously. Example report for this command shall be as shown below at"BLECONN=?
at*BLECONN=?
Copyright LM Technologies Ltd Page 14 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. OK REP*:BLE_CONN 3333 333333 : 0101 1030 00 5b0012 : 0182 3:1032 00 5b0002 : 0203 Open pen REP*:BLE_CONN END vi. The report. above shows that the modul eis now connected with three. devices. The report lists connection ID given by module, remote device BD Address and Connection ID i.e. CID given by BLE stack. vii. Start and end of report is mentioned. E.g. In above report, row, 3:1032 00 5b0002 : 0203"
men tions. tis module has 3rd connection with 1032 00 5b0002 device and CID given by BLE stack is 0203. CID given in above response is referred while reading/writing data with AT commands, reporting disconnection, notification etc. User should note this carefully. Response to this module depends on current state of the module for BLE connections. xi. In a scenario where module has established 3 connections as shown above and if it drops connection 2 then the response to. command AT*BLECONI Will be at"BLECONN=?
at*BLEC ONN=?
OK REP*:BLE_CONN 3333 33 333333 : 0101 pen 1032 00 5b0002 : 0203 Open pen REP*:BLE_CONN END 3.5.3 AT*LECONN Execution only command GAP Central application gives more details on connection parameters when connection is successful and error code value if connection fails. User need to mention the BD address of the remote device with which the BLE connection is to be established, e.g. at*leconn=1031 00 5b0012 tries to establish connection with 1031 00 5b0012 device. Response to this command will be ERR if any of the following is true string format is incorrect BT address is invalid 5 BLE connections are already established Response to this command will be OK if all the following conditions are true. Com mand string format is correct BT address is valid Copyright LM Technologies Ltd Page 15 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. Module has at least one BLE connection open vi. After displaying OK response, module starts the BLE connection procedure. vii. lf the connection is failed the report is given with the error code e. N_FAIL:=1031 00 5b0012,4 err_code:0014, Refer the Error code list mentioned in the appendix section. the module is successfully connected to remote device it will show a report with details about the connection E.q. REP*:BLE_CONNECTED:+1030 00 5b0012 0:1:0080: 0017:
0008 Here report includes extra information for the connection details as below. 1030, 00 5b0012 is BD address of the remote BLE device. O with the address mentions Address type of remote BLE device. TYPED_BDADDR_PUBLIC. is noted as O, TYPED_BDADDR_RANDONM is noted as 1. 1 indicates Connection ID given by LM961 module (refer to BLEconn=? report). 0080 mentions CID given by BLE stack (hex value 0x0080). 0017 is MTU i. e. Maximum Transfer Unit for this BLE connection (hex val ue 0x0017). 0008 is Connection configuration flag (hex value Ox0008) xi. ser should take note of MTU mentioned in connection report, S while reading and writing data on this device, using one command
(rdcahval/wrworesp etc) up to MTU number of bytes can be sen t/received. If user need to read/write more than MTU number of bytes, it needs two commands. at*lecont OK REP*:BLE_CONNECTEI 1030 00 5b0012 0:1: 0080: 0017:
0008 BLE Auth start. OK REP*:SERVICE START: =1030 00 5b001 1801: 0001: 0004
{800 : 0005 : O00b 480f : 0014 : 0017 REP*:BLE_PAIR=1030 10, 5b0012,Success 10001016d10211e19b2300025b00a5a5 : 0018 : 0021 REP*:SERVICE END: =1030 00 5b001 xii. After module is connected with Peer device, If LESEC i.e. LE Security is OFF, module starts BLE Authentication process and Shows message BLE Auth start. to indicate start of authentication process. if LESEC is ON, module will report or co. nnect to only with previously Paired devices which are present in its whitelist. Copyright LM Technologies Ltd Page 16 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. Pairing Success or Failure indication report is given to user as. REP*:BLE_PAII 1030 00 5b0012,Success or REP*:BLE_PAII 1030 00 5b0012,Fail" . After module completes the pai. ring procedure successfully, module adds this device to its whitelist. 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. 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 Exec. ution only command Command is used to disconnect the BLE connection. Command requires peer devices BT address. BLE connection disconnection command format:
AT*LEDROP=1030005b0012", 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. 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 sh ows a report for the disconnection command e.g. at*ledrop=1030005b0012, at*ledrop=1030005b0012. OK REP*:BLE_DIS_CONI 00 5b0012,2 err_code:0000 vii. Error code 0000 mentions the device has terminated connection gracefully i.e. either device started disconnect ion procedure. Number 2 near the BD address mentions the BLE Connection ID
(refereed to BLEconn=? response). lf disconnection is started by remote device or due to link loss the indication for disconnection is shown as below with the reason code. REI 030 10, 5b0012,2 err_code:0019 Refer to the error code in the appendix. Copyright LM Technologies Ltd Page 17 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. 3.6 BLE Services/characteristic scan commands:
3.6.1 AT*FINDSERV Execution only command Command is used to scan services supported on connected BLE device. User need to state connection |D for the device whose services. are to be scanned. E. g. at*findserv=1"
finds services on 1st connected device. Module provides a detailed report for the services supported by the remote device. the BLE device has any se rvice with 128 bit UUID then it is indicated with all bytes. vi. IN below report the row mentions:
4:1800: 0001: 0005"
where is 16bit UUID for service, 0001 is start handle of the service and 0005 is end handle of the s ervice. vii. Report is marked for start and end. For e.g refer below report. at*findserv=1 at*findserv=1 OK REP*:SERVICE STAR 3333 33. 333333 2:180a : 0006 : 0016 00005500d10211e19b2300025b00a5a5 : 0017 : OO1a 4:180f OO'1b : ffff REP*:SERVICE END:
3333 33. 333333 3.6.2 AT*FINDCHAR Execution only command Command used to scan characteristics supported by services on the BLE device. User need to mention connection ID for the device whose services are to be scanned. And start and end handle of the:
services for which scan is to be performed. User can scan characteristics for only one service or multiple services or for all services in single command. at*findserv=1 at*findserv=1 OK REP*:SERVICE STAR 3333 33. 333333
+1800 : 0001: 0005. 2:180a : 0006 : 0016 00005500d10211e19b2300025b00a5a5 : 0017 : OO1a 4180f : OO'b : ffff REP*:SERVICE END:
3333 33. 333333 Considering the above report for services, below are the possible commands. Copyright LM Technologies Ltd Page 138 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. Scan characteri stics of single service i.e. 1800 service, handles are 0001 and 0005. Command should be AT*findchar=1,0001,0005"
Scan characteristics for first two services i.e. 1800 and 180a. User shall issue command as. at*findchar=0001,0016". Scan characteristics of a ll services in single command, user shall issue command at*findchar=1,0001,ffff. vi. Report is marked for start and end. vii. The example report. below shows characteristic scan command. report. at*findchar=1,0001,001b at*findchar=1,0001,001b OK REP*:CHAR start. 1a00 : 0003 : 0:
2a25 : 0008 : 02 : O007[ Rd) 2a24 : 000a : 02 : 0009[ Rd) 2: 000b/ Rd}
2a27 : O00e : 02: OOOd| Rd}
2a26 : 0010 : 02 : OOOF! Rd}. 2: OO Rd}
1013 [Rd]
2a50 : 0016 : 02 : O015[ Rd]
00005501 : 0019 : 14 : 0018 [ Wr_cmd CCFG }
REP*:CHAR END For report:
above
, the row 2a00 : 0003 : 02 : 0002 Rd }"
indicates 1 as serial number, 2a00" as 16 bit characteristic UUID, 0003" is characteristic handle, O2 is properties value and 0002 is declaration value for that characteristic. For details on Characteristic value and Declaration values refer appendix A. 00005501:
0019 : 14: 0018 | Wr_cmd CCFG
|" row indicates the characteristic has 128 bit UUID, but here only lower 32 bits are displayed. 0019 is characteristic handle. 14 is properties value, this characteristic has two properties as WR cmd and CCFG. declaration value for that characteristic. xi. User need to use characteristic Handle to read or write data on that characteristic. 3.7 BLE read data from Characteristic:
3.7.1 AT*RDCHARVAL Execution only command This command is used to read data f rom. the BLE device for the characteristic which has properties as read
"Rd" i.e. Ox02. The c ommand format is AT*RDCHARVAL=conn ID, char Handle. e.g. at*rdcharval=1,0003"
command is used to read data from 1 connected device, for characteristic 0003. Copyright LM Technologies Ltd Page 19 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. he module shall output an. OK response if the CID and the Char handle is correct. vi. After the module gives OK response to read command, module shows data received from remote device as a report. vii. E.q. REP*:RDCHARVAI cvd_Bytes:0010 LM Serial Server isa eport of read data for characteristic 0003. Repo t shows connection ID as 1, Received bytes as Ox10 ie. 16 bytes, and the actual bytes are LM Serial Server. If module receives an error response it is reported to user with the error code. Users can refer to error codes as mentioned in the appendix. section. at*rdcharve at*rdcharve OK REP*:RDCHARVAI xi. Below show some reference reports for read command. at*rdcharve at*rdcharve OK REP*:RDCHARVAI Revd_Bytes:0010 LM Serial Server at*rdcharve at*rdcharve OK REP*:RDCHARVAI at*rdcharve at*rdcharve OK REP*:RDCHARVAI Revd_Bytes:0016 CSR GATT SERVER MODEL at*rdcharve at*rdcharve OK REP*:RDCHARVAI Err_code:02. xii. Above screen shots are taken on Hercules software on Windows PC, it does not show non printable characters in received response. If user analyse the RX line on Oscilloscope or protocol analyser, all bytes can be seen. 3.7.2 AT*R DMULTCHAR Ex ecution only command This command is used to read data from multiple characteristic on single remote device. Read data from BLE device for the characteristic which has. properties as
"Rd" i.e. Ox02. Maximum of 5 characteristics data can be read in one si ngle command. Command format is. AT*RdMultChar=conn ID, no of chars to read, char Handle1, char Handle2, char Handle3, char Handle4, char Handle5,. Copyright LM Technologies Ltd Page 20 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. vi. e.g. command to read data from 3 characteristics shall be at*rdmultchar=1,03,0008,000a,0010" command is us ed to read data from 1st connected device, on characteristic 0003, 0008 and 0010. at*rdcharve at*rdcharve OK REP*:RDCHARVAI SR_no at*rdcharve at*rdcharve OK REP*:RDCHARVAI mod_nos at*rdch arval=1,0010 at*rdcharve OK REP*:RDCHARVAI FW_Ver atrdmultchar=1,03,0008,000a,0010 at*rdmultchar=1,03,0008,0 00a,0010 OK REP*:RDMULTCHAI SR_nomod_noFW_Ver vii. lf the read number of bytes from characteristics excee ds than MTU. bytes then lower bytes are lost and only first MTU bytes are reported. This is limitation of BLE stack and not of LM961 application. E.g. refer below response. (last bytes form 0003 characteristic are lost while reading multiple characteristic s in one command) at*rdcharve at*rdcharve OK REP*:RDCHARVAI SR_no at*rdcharve at*rdcharve OK REP*:RDCHARVAI mod_nos at*rdcharve at*rdcharve OK REP*:RDCHARVAI 06 FW_Ver at*rdcharve at*rdcharve OK REP*:RDCHARVAI Revd_Bytes:0007. App_ver at*rdcharve at*rdcharve OK REP*:RDCHARVAI Revd_Bytes:000b. Copyright LM Technologies Ltd Page 21 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. CSR101x AOS at*rdmultchar=1,05,0008,000a,0010,0012,000e. at*rdmultchar=1, 05,0008,000a,0 010,0012,000e OK REP*:RDMULTCHAI SR_nomod_noFW_VerApp_v Above screen shots are taken on Hercules software on Windows PC, it does not show non printable characters in received response. If user analyse the RX line on Oscilloscope or pr. otocol analyser, all bytes can be seen. 3.7.3 AT*RDLONGCHAR Execution only command When the Characteristic Value is longer than can be sent in a single Read Response message, user can use this command to. read that value in one command. Read data from B LE device for the characteristic which has properties as
"Rd" i.e. Ox02. Command format is. AT*RdLongChar=conn ID, char Handle. Commands which support rdcharval can also be read by this. command. vi. Response to the command shows bytes received, offset of cu rrent. data with respect to the whole data, and MoreToCome (MTC) flag if there is next data packet expected on the same characteristic read. vii. Refer following read examples for more detail. atleconi 3333333333 OK REP*:BLE_CONNECTEI 3333 33. 333333 0:1: 0100: 0017 0008 BLE Auth start. OK REP*:SERVICE STAR 3333 33. 333333 2:180a : 0006 : 0016 00005500d10211e19b2300025b00a5a5 : 0017 : OO1a 4180f : OO1b : ffff REP*:SERVICE END:
3333 33. 333333 at*rdlongchar=1,0008 at*rdlongchar=1,0008 OK REP*:RDLONGCHAF MTC:0. SR_no atrdlongchar=1,000a, at*rdlongchar=1,000a OK REP*:RDLONGCHAF 000a:Success Revd:0024 Offset:0000 MTC:0. abcdEFGHIJkimnopQRSTUvwxyz0123. abcdEF Copyright LM Technologies Ltd Page 22 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. at*rdlongchar=1,000c at*rdlongchar=1,000c OK REP*:RDLONGCHAI Err_code:0002 at*rdlongchar=1,0005. at*rdlongchar=1,0005, OK REP*:RDLONGCHAF MTC:0. at*rdlongchar=1,0003. at*rdlongchar=1,0003. OK REP*:RDLONGCHAS 000 3:Success Rcvd:0010 Offset:0000 MTC:0. LM Serial Server 3.8 BLE write data on Characteristic:
3.8.1 AT*ENBCCFG Execution only command. Command used to enable the Client Configuration Flag (CCFG) on specific characteristic. When the tl mod ule sca ns the characteristics of the device, it shows. the CCFG flag if supported by that characteristic. E.g Serial Over Gatt service supports this flag (highlighted yellow in below report). hile issuing command, user should. hil mention the device connection ID and characteristic handle. E.q The device 1 has CCFG flag characteristic with handle 0019. To enable the CCFG flag use command at*enbccfg=1,0019". vi. Module shall give OK response if the characteristic has CCFG flag otherwise module shall give ERR response if wr. ong characteristic handle is mentioned. vii. After the module. responds with OK the module receives feedback from the BLE dev. ice regarding success or failure, which reported to the user. The report. REP*:WRCHARVAI shows enable CCFG operation is performed successfully. at*findchar=1,0001,001b at*findchar=1,0001,001b OK REP*:CHAR start. 1a00 : 0003 : 0:
2a25 : 0008 : 02 : O007[ Rd) 2a24 : 000a : 02 : 0009[ Rd) OOb [ Rd}
2a27 : O00e : 02: OOOd| Rd}
2a26 : 0010 : 02 : OOOF! Rd}. O11, Rd}
1013 [Rd]
Copyright LM Technologies Ltd Page 23 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. 2a50 : 0016 : 02 : O015[ Rd]
00005501 : 0019 : 14 : 0018 [ Wr_cmd CCFG }
REP*:CHAR END at*enbccfg=1,0019 at*enbecfg=1,0019 OK REP*:WRCHARVAL=1:Success 3.8.2 AT*INDESP Execution only command. This command gives feedback to server/peripheral for notification indication from server/peripheral. This command is used to acknowledge the sever that client(BLE Centra l) has received characteristic v alue Indication, and server(BLE Peripheral) may send another indication. Command format is. at"INDRESP=Conn e.g. AT*INDRESP=1" gives indication response for 1 connected BLE device for re ceiving notification indication. vi. OK/ERR response is given by LM961 after checking the Connection ID and Connection status. vii. After OK response is given Response is forwarded to remote by BLE Stack. No feedback form BLE Stack is provided to this comma nd. 3.8.3 AT*WRWORESP Execution only command This command is used to send data to BLE device for the. characteristic which has properties as. Wr_cmd i.e. 0x04. Command format is. AT*WRWORESP=conn ID, char Handle, length, actual bytes ". e.g. at"wrwore:
sp=1,0019,10,12345abcdefl()12 command is used to send data to 1 connected device, on characteristic 0019. No of bytes to write are 0x10 i.e. 16 and actual bytes are. As shown in the example command number of bytes to tra nsmit 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 1is sent, the data buffer is copied and sent to remote device transparently. vii. Note :
The actual data bytes to be sen t shall not have n as the data itself because it is the terminating string for AT command parser. Copyright LM Technologies Ltd Page 24 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. For command AT*WRWORESP=conn. ID, char Handle, length, actual bytes module gives OK response if all the following connection ID is correct (if module is connected to 3 devices and CID mentions 4, then it is invalid) Characteristic handle has WR_cmd properties Value of length field is less than 21 i.e. (Ox15). Actual data bytes are same as value of length field. After the modul e responds t o the command with OK, the module sends the data to the remote BLE device. If the remote dev ice receives the data and sends. feedback to. the LM961, that feedback is displayed on UART. xi. E.g. report shows, REP*:WRWORESP=1:0019:Success which dicates the data has been received by the remote device successfully. 1is the CID given by module and 0019 is the:
characteristic handle. at*wrworesp=1,0019,05,12345 at*wrworesp=1,0019,05,12345 OK REP*:WRWORES!
at"wrworesp=1,0019,10,12345abcd efl()12. at*wrworesp=1,0019,10,1 2345abcdefl(12 OK REP*:WRWORES!
3.8.4 AT*WRCHARVAL Execution only command This command is used to send data to BLE device for the. characteristic which has properties as. Wr_req i.e. Ox08. Command format is.
"AT*WRCHARVAL=conn ID, char Handle, length, actual bytes. e.g. it" WRCHARVAL=1,0019,10,12345abcdefl{}12, command is used to send data to 1 connected device, on characteristic 0019. No of bytes to write are 16 (0x10) and actual bytes are 12345abcdefl()1 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 1is sent, the data buffer is copied and sent to remote device transparently. vii. Note :
The actual da ta bytes to be sent should ti not have as the data itself because it is the terminating string for AT command parser. For command AT*WRWORESP=conn. ID, char Handle, length, actual bytes module gives OK response if a
| the following connection ID is correct (if module is connected to 3 devices and CID mentions 4, then it is invalid) Copyright LM Technologies Ltd Page 25 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. Characteristic handle has Wr_req properties Value of length field is less than 21 i.e. (Ox15). Actual data bytes. are same as value of length field. After module responds to this command as. OK, module sends the data to remote BLE device. at*findchar=2,0001,ffff at*findchar=2,0001, ffff OK REP*:CHAR start.
[ Indi}
006
[Rd Wr_req ]
[ Rd Wr_req ]
008
[Rd]
2a04 : O00b : 02: 000a
[Rd]
000d
[ CCFG]
: 2a38 : 0011: 02: 0010
[Rd]
2a39 : 0013 : 08 : 0012
[ Wr_req ]
2al9 : 0016 : 12: 0015
[Rd CCFG]
[Rd Wr_req ]
00001018 : OO1c : 08 : O01b
[ Wr_req ]
REP*:CHAR END at*wrcharval=2,0013,05,12345. at*wrcharve
.0013,05,12345, OK REP*:WRCHARVAL:
).0007,05,12345 at*wrcharve
.0007,05,12345 OK REP*:WRCHARVAL=2:Success. 1 0007,05,abCDE at*wrcharve 1.0007,05,abCDE OK REP*:WRCHARVAL=2:Success.
}.001c,05,abCDE at*wrcharve
.001c,05,abCDE OK REP*:WRCHARVAL-
at*wrcharval=2,001a,05,abCDE at*wrcharve
.001a,05,a bCDE OK REP*:WRCHARVAL:
1.0013,05,abCDE at*wrcharve
..0013,05,abCDE OK REP*:WRCHARVAL:
lf the remote device receives the data and sends feedback to. the LM961, that feedback is displayed on UART. Copyright LM Technologies Ltd Page 26 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. xi. Above report shows t he WRCharval command is successful only on characteristic 0005 and 0007. xii. lf 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 Appendi x section for more details on error code. 3.8.5 AT*SIWRWORESP Execution only command This command is used to send data to BLE device for the. characteristic which has properties as. Si_Wrt 0x40. Command format is.
"AT*WRCHARVAL=conn ID, char Hand!
length, actual bytes. e.g. at"WRCHARVAL=1,0019,10,12345abcdefi()12 command is used to send data to 1st connected device, on characteristic 0019 No of bytes to write are 16 (Ox10) and actual bytes are 12345abcdef\()12 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 1is sent, the data buffer is copied and sent to remote device transparently. vii. Note : Thea ctual da ta bytes to be sent should ti not have as the data itself because it is the terminating string for AT command parser. For command AT*WRWORESP=conn. ID, char Handle, length, actual bytes module gives OK response if all the following conditions are tru connection ID is correct (if module is connected to 3 devices and CID mentions 4, then it is invalid) Characteristic handle has Wr_req properties Value of length field is less than 21 i.e. (Ox15). Actual data bytes are same as value of length fiel After module responds to this command as. OK, module sends the data to remote BLE device. 3.8.6 NOTIF_IND notification Indication Indication given by module. When the tl module receives data from the remote BLE device, it notifies the:
user on UART. E.g. the c ommand below shows some indication reports:
IND*:NOTIF_IND:
1019 R_bytes:0014 dataFromBLEDev123456 Copyright LM Technologies Ltd Page 27 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. IND*:NOTIF_IND:
1019 R_bytes:0003. 789 IND*:NOTIF_IND:
1019 R_bytes:0014 abcdefghijkimnoparst. IND*:NOTIF_IND:
1019 R_bytes:0006 UVWxYyZ IND*:NOTIF_IND=
1019 R_bytes:0014 abcdefghijkimnoparst. IND*:NOTIF_IND:
1019 R_bytes:0006 UVWxYyZ In report IND*:NOTIF_IND-
1019 R_bytes:0014 dataFromBLEDev123456"
the m odule shows CID as 1, Characteristic from which data is received is 0x0019, the actual receive:
d bytes are 0x0014, and then the actual bytes as dataFromBLEDev123456 The m odule can receive maximum of 20 bytes i.e. Ox14 bytes in one notification packet. vi. the remote device sends more than 20 bytes in one packet then the module shows two notific. ation indication messages. E.q. if. the remote device sends the string dataFromBLEDev123456789", the module shows dataFromBLEDev123456
" first and then 789. Copyright LM Technologies Ltd Page 28 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. LM961 AT commands and Default configurs This section describes the AT command structure for the LM961 module. Serial terminals (such as. Jercules, HyperT rminal, Tera Term or Putty. can be used for serial communication with the LM961. Every command is terminated with CR LF. parsing the AT command strings after receiving CR LF sequenc AT Commands are case insensitive e.g. At*Resp=On", at*resp=on and AT*RES!
IN are all valid. Following are the AT command types:
Query only commands Commands to query Module state, firmware version number etc. Query and Set commands Commands to query the setting and modify Module setting e.g. discoverability, Role, Baud, etc. Execution only command commands to perform specific action e.g. start discovery for Bluetooth devices, start connection procedure, start upgrade procedure etc. The LM 961 outputs indication messages to the user through the serial port for indications like connection/pairing request, result of connection/pair procedure, result of Bluetooth devices discovery, disconnection indication etc. After the indication message is lisplayed, the LM961 waits for inputs from the:
user to execute further action. For example, after incoming pairing indications, enter accept/reject pair response or after indication for PASSKEY_cfm, provide yes/no confirmation for the passkey etc. The m le responds to each AT command as OK
.or ERR
). After this response. the module takes requested action or it will output report to the user on UART. If module does not receive AT as a start of new command, 1e module may not respond to this com mand even if it is terminated with n (e.g. instead of AT*NAME=?", user issues A*tname=?). Module will neglect the received string and is ready to receive new AT command and to process it. When he nodule does not receive any c mmand on UART for mor than 30 econds, the module enters deep sleep mode. The m odule can come out of this mode on UART activity or BT activity. If. the user enters AT command while. the module is in deep sleep, ne nodule may lose irst character of an.
\T command, e.g. for command AT*NAME:
module may show the echo as. iame=?" or Nnam
"12.50 1e garbage character at start. The m dule will not respond to AT command s such as ERR/OK, but it ignores this data and waits for new AT command to process. AT commands e xpects the BT address in the string. In this document. 0126f357215" is considered a reference BT address, whereas 0012 is nap, 6f is Copyright LM Technologies Ltd Page 29 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. uap and 357215 is lap in the BT address. Users should use the BT address of their devices. 41 AT commands The table below sh Ws all. AT commands iat are upported on _M961 module and the default settings wherever applicable for quick reference. 4.1.1 General settings AT command:
Sr no nmand string type AT*ADDR:
Query only AT*NAME Query and set. Firmware version dependent e.g. O68LM_SPP_0104 AT*ECHO Query and set ON AT*RESP Query and set ON AT*DCOV Query and set ON AT*PAIR, Query and set ON AT*STATE Query only AT*VER:
Query only AT*RESET Execution only AT*
SETTINGS Query only Refer command details. 4.4.2 UART settings AT commands:
Sr no nmand string type AT*BAUD Query and set 19200 (5) AT*PAR. Query and set No parity (0) AT*STOP Query and set One stop bit (0) AT*FLOW Quer y and set Off AT*CTS Query only AT*RTS Set only AT*DTR Set only AT*DSR Query only AT*MODEM. Query and set NONE Note: CTS, RTS, DTR, DSR, MODEM commands are not applicable for LM961 module. Copyright LM Technologies Ltd Page 30 of 62 www.lm technologies.com. TECHNOLOGIES LM961 SPP with GAP Central Applicat ion v1. 41.3 Bluetooth security settings comman ds:
Sr no AT command string AT*PIN. Query and set 1234 AT*DPIN. Query and set OFF AT*MITM Query and set OFF AT*IOTYPE Query and set NO_InOut AT*DEL Execution only AT*PASSKEY Execution only AT*PASSCFM. Execution only AT*STOPPAIR Execution only AT*PAIRLIST. Query only 41.4 SPP related AT commands:
Sr no AT command string AT*FIND Execution only AT*ROLE Query and set Dual AT*ACON Query and set OFF AT CONN Execution only Escape sequence Execution only AT*AUTO. Execution only AT*DROP Execution only AT*BOND Query and set Default bond device address 0000, 00 000000, 415 Firmware Upgrade AT commands:
Sr no AT command AT command string Co mand AT*UPGRADE Execution only
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2018-06-15 | 2402 ~ 2480 | DSS - Part 15 Spread Spectrum Transmitter | Original Equipment |
2 | 2402 ~ 2480 | DTS - Digital Transmission System |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 2 | Effective |
2018-06-15
|
||||
1 2 | Applicant's complete, legal business name |
LM Technologies Ltd.
|
||||
1 2 | FCC Registration Number (FRN) |
0017206053
|
||||
1 2 | Physical Address |
Unit19, Spectrum House
|
||||
1 2 |
London, N/A NW5 1LP
|
|||||
1 2 |
United Kingdom
|
|||||
app s | TCB Information | |||||
1 2 | TCB Application Email Address |
j******@eurofins.com
|
||||
1 2 | TCB Scope |
A4: UNII devices & low power transmitters using spread spectrum techniques
|
||||
app s | FCC ID | |||||
1 2 | Grantee Code |
VVX
|
||||
1 2 | Equipment Product Code |
LM961
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 2 | Name |
M******** S********
|
||||
1 2 | Title |
Managing Director
|
||||
1 2 | Telephone Number |
+44(0********
|
||||
1 2 | Fax Number |
+44(0********
|
||||
1 2 |
l******@lm-technologies.com
|
|||||
app s | Technical Contact | |||||
n/a | ||||||
app s | Non Technical Contact | |||||
n/a | ||||||
app s | Confidentiality (long or short term) | |||||
1 2 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 2 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 2 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 2 | Equipment Class | DSS - Part 15 Spread Spectrum Transmitter | ||||
1 2 | DTS - Digital Transmission System | |||||
1 2 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | LM961 Bluetooth v4.1 Dual Mode Module | ||||
1 2 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 2 | Modular Equipment Type | Single Modular Approval | ||||
1 2 | Purpose / Application is for | Original Equipment | ||||
1 2 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | Yes | ||||
1 2 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 2 | Grant Comments | Power listed is conducted. Singular Modular Approval. Compliance of this device in all final host configurations is the responsibility of the Grantee. OEM integrators and end-users must be provided with specific operating instructions for satisfying RF exposure compliance. OEM integrators are instructed to ensure that the end user has no manual instructions to remove or install the device. SAR evaluation is valid for portable applications with an minimum distance of 5mm to human bodies. | ||||
1 2 | Power listed is conducted. Singular Modular Approval. Compliance of this device in all final host configurations is the responsibility of the Grantee. OEM integrators and end-users must be provided with specific operating instructions for satisfying RF exposure compliance. OEM integrators are instructed to ensure that the end user has no manual instructions to remove or install the device. SAR evaluation is valid for portable applications with an minimum distance of 5mm to human bodies. | |||||
1 2 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 2 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 2 | Firm Name |
Shenzhen SEM Test Technology Co. Ltd
|
||||
1 2 | Name |
J******** S********
|
||||
1 2 | Telephone Number |
86 75******** Extension:
|
||||
1 2 | Fax Number |
86-75********
|
||||
1 2 |
j******@semtest.com.cn
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 15C | 2402.00000000 | 2480.00000000 | 0.0028000 | ||||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
2 | 1 | 15C | 2402.00000000 | 2480.00000000 | 0.0036000 |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC