WL865E4-P Use Case Reference Guide · 2020-04-09 · WL865E4-P Use Case Reference Guide 1VV0301570 Rev. 3.0 2 2020-04-01 SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICE NOTICE

WL865E4-P Use Case Reference Guide

1VV0301570 Rev. 3.0 1 2020-04-01

WL865E4-P Use Case Reference Guide 1VV0301570 Rev. 3.0 – 2020-04-01


1VV0301570 Rev. 3.0 2 2020-04-01

SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICE

NOTICEWhile reasonable efforts have been made to assure the accuracy of this document, Telitassumes no liability resulting from any inaccuracies or omissions in this document, or from use ofthe information obtained herein. The information in this document has been carefully checkedand is believed to be reliable. However, no responsibility is assumed for inaccuracies oromissions. Telit reserves the right to make changes to any products described herein andreserves the right to revise this document and to make changes from time to time in contenthereof with no obligation to notify any person of revisions or changes. Telit does not assume anyliability arising out of the application or use of any product, software, or circuit described herein;neither does it convey license under its patent rights or the rights of others.

It is possible that this publication may contain references to, or information about Telit products(machines and programs), programming, or services that are not announced in your country.Such references or information must not be construed to mean that Telit intends to announcesuch Telit products, programming, or services in your country.

COPYRIGHTSThis instruction manual and the Telit products described in this instruction manual may be,include or describe copyrighted Telit material, such as computer programs stored insemiconductor memories or other media. Laws in the Italy and other countries preserve for Telitand its licensors certain exclusive rights for copyrighted material, including the exclusive right tocopy, reproduce in any form, distribute and make derivative works of the copyrighted material.Accordingly, any copyrighted material of Telit and its licensors contained herein or in the Telitproducts described in this instruction manual may not be copied, reproduced, distributed, mergedor modified in any manner without the express written permission of Telit. Furthermore, thepurchase of Telit products shall not be deemed to grant either directly or by implication, estoppel,or otherwise, any license under the copyrights, patents or patent applications of Telit, as arisesby operation of law in the sale of a product.

COMPUTER SOFTWARE COPYRIGHTSThe Telit and 3rd Party supplied Software (SW) products described in this instruction manualmay include copyrighted Telit and other 3rd Party supplied computer programs stored insemiconductor memories or other media. Laws in the Italy and other countries preserve for Telitand other 3rd Party supplied SW certain exclusive rights for copyrighted computer programs,including the exclusive right to copy or reproduce in any form the copyrighted computer program.Accordingly, any copyrighted Telit or other 3rd Party supplied SW computer programs containedin the Telit products described in this instruction manual may not be copied (reverse engineered)or reproduced in any manner without the express written permission of Telit or the 3rd Party SWsupplier. Furthermore, the purchase of Telit products shall not be deemed to grant either directlyor by implication, estoppel, or otherwise, any license under the copyrights, patents or patentapplications of Telit or other 3rd Party supplied SW, except for the normal non-exclusive, royaltyfree license to use that arises by operation of law in the sale of a product.


USAGE AND DISCLOSURE RESTRICTIONS

I.License AgreementsThe software described in this document is the property of Telit and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement.

II.Copyrighted MaterialsSoftware and documentation are copyrighted materials. Making unauthorized copies is prohib-ited by law. No part of the software or documentation may be reproduced, transmitted, tran-scribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Telit.

III.High Risk MaterialsComponents, units, or third-party products used in the product described herein are NOT fault-tolerant and are NOT designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life Sup-port, or Weapons Systems (High Risk Activities"). Telit and its supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.

IV.TrademarksTELIT and the Stylized T Logo are registered in Trademark Office. All other product or service names are the property of their respective owners.

V.Third Party RightsThe software may include Third Party Right software. In this case you agree to comply with all terms and conditions imposed on you in respect of such separate software. In addition to Third Party Terms, the disclaimer of warranty and limitation of liability provisions in this License shall apply to the Third Party Right software.TELIT HEREBY DISCLAIMS ANY AND ALL WARRANTIES EXPRESS OR IMPLIED FROM ANY THIRD PARTIES REGARDING ANY SEPARATE FILES, ANY THIRD PARTY MATERIALS INCLUDED IN THE SOFTWARE, ANY THIRD PARTY MATERIALS FROM WHICH THE SOFT-WARE IS DERIVED (COLLECTIVELY “OTHER CODE”), AND THE USE OF ANY OR ALL THE OTHER CODE IN CONNECTION WITH THE SOFTWARE, INCLUDING (WITHOUT LIMITA-TION) ANY WARRANTIES OF SATISFACTORY QUALITY OR FITNESS FOR A PARTICULAR PURPOSE.NO THIRD PARTY LICENSORS OF OTHER CODE SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND WHETHER MADE UNDER CONTRACT, TORT OR OTHER LEGAL THEORY, ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE OTHER CODE OR THE EXERCISE OF ANY RIGHTS GRANTED UNDER EITHER OR BOTH THIS LICENSE AND THE LEGAL TERMS APPLICABLE TO ANY SEPARATE FILES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

1VV0301570 Rev. 3.0 3 2020-04-01


-This page is intentionally left blank-

1VV0301570 Rev. 3.0 4 2020-04-01


Contents

NOTICE ........................................................................................................................................2 COPYRIGHTS ..............................................................................................................................2 COMPUTER SOFTWARE COPYRIGHTS ...................................................................................2 USAGE AND DISCLOSURE RESTRICTIONS ............................................................................3

I.License Agreements ............................................................................................................3 II.Copyrighted Materials .........................................................................................................3 III.High Risk Materials ............................................................................................................3 IV.Trademarks ........................................................................................................................3 V.Third Party Rights ...............................................................................................................3

1 Introduction .................................................................................................................................... 71.1 Scope ......................................................................................................................................71.2 Audience ..................................................................................................................................71.3 Contact Information, Support ...................................................................................................71.4 Text Convention ......................................................................................................................81.5 Related Documents .................................................................................................................8

1.5.1 Related Documents and Download ................................................................................81.5.2 Related Documents requiring a Non Disclosure Agreement ..........................................9

2 Wireless ........................................................................................................................................ 102.1 Wireless Mode .......................................................................................................................10

2.1.1 Station Mode ................................................................................................................102.1.1.1 Use Case 1: Create a Station Mode ....................................................................10

2.1.2 Limited AP Mode ..........................................................................................................112.1.2.1 Use Case 1: Create an Access Point/Network/Limited AP ..................................11

2.2 Concurrent Mode ...................................................................................................................122.2.1 Use Case 1:To configure WL865E4-P module in Concurrent Mode ............................12

2.3 BlueTooth Low Energy (BLE) ................................................................................................152.3.1 Use Case 1:Bluemod+S50 as central role and WL865E4-P as peripheral role ...........152.3.2 Use Case 2:Bluemod+S50 as peripheral role and WL865E4-P as central role ...........172.3.3 Use Case 3:GATT setup on WL865E4-P module ........................................................192.3.4 Use Case 4:GATT setup with Third-Party Device ........................................................23

3 Data Transfer ................................................................................................................................ 283.1 TCP (Transmission Control Protocol) ....................................................................................28

3.1.1 TCP Client ....................................................................................................................283.1.1.1 Use Case 1: .........................................................................................................28

3.1.2 TCP Server ..................................................................................................................293.1.2.1 Use Case 1: .........................................................................................................29

3.2 UDP (User Datagram Protocol) .............................................................................................303.2.1 UDP Client ...................................................................................................................30

3.2.1.1 Use Case 1: .........................................................................................................303.2.2 UDP Server ..................................................................................................................31

3.2.2.1 Use Case 1: .........................................................................................................313.3 HTTP Client (HTTPC) ............................................................................................................32

3.3.1 Use Case 1: .................................................................................................................323.4 MQTT ....................................................................................................................................33

3.4.1 Use Case 1: .................................................................................................................33

1VV0301570 Rev. 3.0 5 2020-04-01


4 Advanced Services ....................................................................................................................... 354.1 Application Features ..............................................................................................................35

4.1.1 Provisioning .................................................................................................................354.1.1.1 Use Case 1: Wi-Fi Provisioning with BLE ............................................................35

4.1.2 Firmware Upgrade ......................................................................................................434.1.2.1 Use Case 1: Firmware upgrade using OTAFU ....................................................434.1.2.2 Use Case 2: Firmware upgrade using HTTPC ....................................................444.1.2.3 Use Case 3: Firmware upgrade using HTTPD ....................................................444.1.2.4 Use Case 4: Firmware upgrade using Web Provisioning ....................................45

Document History ........................................................................................................................... 46

1VV0301570 Rev. 3.0 6 2020-04-01


1 Introduction

• Scope, page 7

• Audience, page 7

• Contact Information, Support, page 7

• Text Convention, page 8

• Related Documents, page 8

1.1 ScopeThis manual provides references for using Telit “AT” commands and it’s usage in different scenarios using different features and protocols. It is to be used as a reference guide for using a set of AT commands customized as per host requirements.

This document provides AT command use cases and examples for all layers and it needs to be used as reference only.

1.2 AudienceThis document is intended for Telit customers, who are integrators, about to implement their applications using our WL865E4-P modules.

Readers of this document should be familiar with Telit modules and their ease of controlling by means of AT Commands.

1.3 Contact Information, SupportFor general contact, technical support services, technical questions and report documentation errors contact Telit Technical Support at:

• [email protected]

For detailed information about where you can buy the Telit modules or for recommendations on accessories and components visit:

https://www.telit.com

Our aim is to make this guide as helpful as possible. Keep us informed of your comments and suggestions for improvements.

Telit appreciates feedback from the users of our information.

1VV0301570 Rev. 3.0 7 2020-04-01


1.4 Text ConventionTable 1, page 8, shows the symbol conventions used in this manual for notification and important instructions.

All dates are in ISO 8601 format, i.e. YYYY-MM-DD

1.5 Related DocumentsPlease refer to http://www.telit.com/ for current documentation and downloads.

1.5.1 Related Documents and Download– Datasheets

– Product User Guides

– EVK User Guides

– Software User Guides

– Application Notes

– TelitView installation and documentation

Table 1 Symbol Conventions

Icon Type Description

NoteProvides helpful suggestions needed in understanding a feature or references to material not available in the manual.

Alert Alerts you of potential damage to a program, device, or system or the loss of data or service.

Caution Cautions you about a situation that could result in minor or moderate bodily injury if not avoided.

Warning Warns you of a potential situation that could result in death or serious bodily injury if not avoided.

Electro-Static Discharge (ESD)

Notifies you to take proper grounding precautions before handling a product.

DangerIndicates information MUST be followed or catastrophic equipment failure or bodily injury may occur

1VV0301570 Rev. 3.0 8 2020-04-01


1.5.2 Related Documents requiring a Non Disclosure Agreement– Authorized Software User Guides

– Product firmware

1VV0301570 Rev. 3.0 9 2020-04-01


2 Wireless

This chapter describes the use cases for configurations and operations related to advanced services of Network and WL865E4-P supported Application features.

• Wireless Mode, page 10

• Concurrent Mode, page 12

• BlueTooth Low Energy (BLE), page 15

2.1 Wireless Mode

2.1.1 Station Mode

2.1.1.1 Use Case 1: Create a Station Mode

Description Demonstrates the configuration of Telit module in Station mode and connects to the AP.

Prerequisite AP or router must be in ON state with specific SSID.

Precondition NA

Setup Architecture The setup requires a AP (router) and a Telit node in Station mode.

Procedure Following commands are used to configure Telit module in station mode, configure the node as STA and connect the STA node to an AP (AE_Hardik).

at+wni=0 // '0' for station modeat+wncn=1,"AE_Hardik" // at+wncn=1,"ssid"

Logs

1VV0301570 Rev. 3.0 10 2020-04-01


2.1.2 Limited AP Mode

2.1.2.1 Use Case 1: Create an Access Point/Network/Limited AP

Description NA

Prerequisite NA

Precondition NA

Setup Architecture NA

Procedure Following commands are used to configure Telit module in AP mode, configure the node as AP, where the IP of the node is set as 192.168.45.3 and the SSID set as GS_LAP.

at+WNI=1 // '1' for AP modeat+WNIPC=0,1,192.168.45.3,255.255.255.0,192.168.45.1at+WNAPIPC=0,192.168.45.4,192.168.45.10,10000at+WNCR=0,"GS_LAP",6,"NONE","NONE"

(Check Wi-Fi AP list of on the laptop -'GS_LAP' has appeared as Limited AP)

1VV0301570 Rev. 3.0 11 2020-04-01


Logs

2.2 Concurrent Mode

2.2.1 Use Case 1:To configure WL865E4-P module in Concurrent Mode

Description NA

Prerequisite NA

Precondition NA


Procedure Following are the steps used to configure WL865E4-P module in concurrent mode.

1.)Enable New AT Commands by using AT+YLC=0.

2.Initial NCM for STA mode by using the command AT+WNI.

3.Connect the module to the Access Point of SSID - “Telit_Demo”, channel – 6 and Passphrase – “Telit123” by using command AT+WNCN.

4.Initial NCM for AP mode by using the command AT+WNI.

1VV0301570 Rev. 3.0 12 2020-04-01


5.Set the static IP configurations for AP (IP address, subnet mask and Gateway) as 192.168.240.1,255.255.255.0,192.168.240.1 by using AT+WNIPC command.

6.Set the range of the IP address as 192.168.240.10 – 192.168.240.25 and DHCP lease time – 8640000(seconds) by using AT+WNAPIPC command so that connected stations will get IP address in the range.

7.Set SSID, channel, security type, Encryption type and passphrase by using command AT+WNCR.

8.Start Web Provisioning server b using the command AT+WNWEBPROV.

9.Issue AT+WNIFCFG to get the current configuration of different interfaces

AT+YLC=0

AT+WNI=0AT+WNCN=1,"Telit_Demo","Telit123"

AT+WNI=1AT+WNIPC=0,1,192.168.240.1,255.255.255.0,192.168.240.1AT+WNAPIPC=0,192.168.240.10,192.168.240.25,8640000AT+WNCR=0,"Telit_AP_Demo",6,"WPA2","AES","123456789"

AT+WNWEBPROV=1

AT+WNIFCFG

10.Connect any other network STA like Laptop or mobile to the AP “Telit_Demo” and ping to Telit STA (192.168.0.122).

Now connect your Laptop to "Telit_AP_Demo"

1VV0301570 Rev. 3.0 13 2020-04-01


11.Open the Chrome Browser. Enter the following URL http://192.168.240.1/telit.html. This will open the webpage and asks to enter Authentication credentials. Enter "admin", “admin” as user name and password.

While ping is responding over the STA Interface, Telit module responds to the Laptop as well by serving the webpages.

Logs

1VV0301570 Rev. 3.0 14 2020-04-01


2.3 BlueTooth Low Energy (BLE)

2.3.1 Use Case 1:Bluemod+S50 as central role and WL865E4-P as peripheral role

Description Demonstrates BlueMod+S50 in central role initiates a scan to search for peripheral devices, BLE device (BlueMod+S50) in central role stops advertising. And, WL865E4-P Module acts as a peripheral which advertises by default to accept the connection from central device.

Prerequisite Change the mode of the BlueMod+S50 to central role using LEROLE command.

Precondition NA

Setup Architecture This setup requires a BlueMod+S50 as Central and WL865E4-P as peripheral role.

Procedure Following are the AT commands to be issued:

BLUEMOD+S50ATi99AT+BOADAT&F1AT+LEROLE=1AT+LESCANATD<PERIPHERAL DEVICE ADDRESS>,<ADDRESS TYPE(t2/t3)>,<TIO/GATT>

WL865E4-PAT+YLC=0AT+YVER=AT+BI=1AT+BADVE=0AT+BOAD

After initiating the ATD command from central device(BlueMod+S50), connection notification will be received on WL865E4-P terminal. Now perform data transfer from BLE device (BlueMod+S50) to the WL865E4-P Module.

Data Sent: “HELLO WORLD”

Logs 1.) Changing the role of BLE device:

1VV0301570 Rev. 3.0 15 2020-04-01


2.) Initiating a scan on BLE device:

1VV0301570 Rev. 3.0 16 2020-04-01


3.) Establishing connection and data transfer from BLE device to WL865E4-P module:

2.3.2 Use Case 2:Bluemod+S50 as peripheral role and WL865E4-P as central role

Description Demonstrates BlueMod+S50 as a peripheral role which advertises by default. And, WL865E4-P Module acts as a central role which initiates the scan and performs the connection establishment.

Prerequisite Change the role of BlueMod+S50 by issuing Factory reset command.

Precondition NA

Setup Architecture BlueMod+S50 acts as a peripheral device and WL865E4-P as central role which initiates a connection with peripheral device.


WL865E4-PAT+YVER=AT+BI=1AT+BADVE=1AT+BSCANAT+BCONNECT=”PERIPHERAL DEVICE ADDRESS”,”ADDRESS TYPE”

BLUEMOD+S50ATi99AT+BOADAT&F1AT&WAT+RESET

1VV0301570 Rev. 3.0 17 2020-04-01


After initiating the command AT+BCONNECT on WL865E4-P module, connection notification with Connect ID is received in WL865E4-P terminal.

Logs 1.) Central device (WL865E4-P) AT commands:

2.) Establishing connection with BLE module:

1VV0301570 Rev. 3.0 18 2020-04-01


3.) Peripheral device AT commands:

2.3.3 Use Case 3:GATT setup on WL865E4-P module

Description Demonstrates the setup of GATT to read the Attributes & Services using BLE device.

Prerequisite Change the role of BM+S50 as Central and WL865E4-P as Peripheral.

Precondition NA

Setup Architecture WL865E4-P acts as Peripheral (GATT Client) and BM+S50 acts as Central (GATT Server) which makes connection establishment to read the services of WL865E4-P.


WL865E4-PAT+YVEREXT=AT+BI=1AT+BOADAT+BADVE=1AT+BATTRIB=”pserv”,”uuid=12AA”AT+BATTRIB=”char”,”prop=1A”,”uuid=12A1”AT+BATTRIB=”charval”,”perm=0011”,”len=1”,”val=59”AT+BATTRIB=”COMPLETE”

BM+S50ATi99AT+BOADAT&F1AT+LEROLE=1

1VV0301570 Rev. 3.0 19 2020-04-01


AT+BIOCAP=0AT&WAT+RESETAT+LESCANATD<PERIPHERAL DEVICE ADDRESS>,<t2/t3>,GATT

Logs 1. Peripheral (WL865E4-P) AT Commands:

2. Define GATT service:

1VV0301570 Rev. 3.0 20 2020-04-01


3. Central device (BM+50) AT Command

4. Initiate a scan on Central device:

1VV0301570 Rev. 3.0 21 2020-04-01


5. Initiate a connection with WL865E4-P module:

6. Discover GATT services of the peripheral:

1VV0301570 Rev. 3.0 22 2020-04-01


7. Read the values of the peripheral:

2.3.4 Use Case 4:GATT setup with Third-Party Device

Description Demonstrates the setup of GATT by reading the attributes using Third-Party BLE device

Prerequisite Change the role of WL865E4-P as Central which initiates a scan and connects to the Peripheral (Third party device).

Precondition NA

Setup Architecture WL865E4-P as Central (GATT Server) and third-party device Polar Bluetooth Heart Rate Transmitter as Peripheral (GATT Client) which will make a connection establishment to read the services of E4-P.


WL865E4-PAT COMMANDSAT+YVEREXT=AT+YVER=AT+BI=1AT+BOADAT+BIOCAP=4AT+BSCANAT+BCONNECT=”PERIPHERAL DEVICE ADDRESS”,”t2”AT+BSRVD=<CONNECTION HANDLE RECEIVED AFTER BCONNECT COMMAND>AT+BSRVD=<CONNECTION HANDLE>,<UUID SERVICE FROM THE LIST>AT+BREAD=<CONNECTION HANDLE>,<CHARACTERISTIC HANDLE>

1VV0301570 Rev. 3.0 23 2020-04-01


Logs 1. Enable BLE stack on WL865E4-P EVK:

2. Initiate a scan:

1VV0301570 Rev. 3.0 24 2020-04-01


3. Check the display for Third-party device on the scan list:

4. Response to the scan command:

1VV0301570 Rev. 3.0 25 2020-04-01


5. Establish connection:

6. Discover GATT services:

7. Read the values:

1VV0301570 Rev. 3.0 26 2020-04-01


1VV0301570 Rev. 3.0 27 2020-04-01


3 Data Transfer


• TCP (Transmission Control Protocol), page 28

• UDP (User Datagram Protocol), page 30

• HTTP Client (HTTPC), page 32

• MQTT, page 33

3.1 TCP (Transmission Control Protocol)This section describes how to setup the TCP Server/Client with Telit module using the AT command mode.

3.1.1 TCP Client

3.1.1.1 Use Case 1:

Description Demonstrates the transfer of data from Telit node (TCP client) to TCP server, where the Telit node is configured as TCP client and sends data to TCP server.

Prerequisite Installation of Hercules utility on the PC.

Precondition TCP server must be configured to Hercules.

Setup Architecture The setup requires a Telit node (STA), a AP or router and a Hercules utility which act as TCP server.

Procedure Following commands are used to configure the Telit node as a TCP client to send data 'telit' to TCP server (IP address - 192.168.0.96, port - 1234)

AT+WNI=0AT+WNCN=1,”Telit_Guest”,”qwerty123456”AT+SC=2,1,0AT+SCO=0,192.168.0.96,1234 //at+sco=CID, server ip, server portAT+SN=0,,,5,telit //at+sn=CID,,,datalen, data

Logs

1VV0301570 Rev. 3.0 28 2020-04-01


3.1.2 TCP Server

3.1.2.1 Use Case 1:

Description Demonstrates the transfer of data from Telit node (TCP server) to TCP client, where Telit node is configured as TCP server and sends data to TCP client.


Precondition TCP client must be configured to Hercules.

Setup Architecture The setup requires a Telit node (STA), a AP or router and a Hercules utility which act as TCP client.

Procedure Following commands are used to configure the Telit node,

at+wni=0at+wncn=1,"Telit_Guest","qwerty123456"at+sc=2,1,0at+sb=0,0,1234 // at+sb=server CID,portat+sl=0 // after server starts listens - > connect client // at+sl=server CID,0(here second parameter is optional)at+sa=0 // at+sa=server CIDat+srr=1at+sn=1,,,5,telit ////at+sn=CID,,,datalen, data

1VV0301570 Rev. 3.0 29 2020-04-01


Logs

3.2 UDP (User Datagram Protocol)This section describes how to setup UDP Server and UDP client on Telit evaluation board using the AT commands.

3.2.1 UDP Client

3.2.1.1 Use Case 1:

Description Demonstrates the transfer of data from Telit node (UDP client) to UDP server where, Telit node is configured as UDP client and sends data to UDP server.


Precondition UDP server must be configured to Hercules.

Setup Architecture The setup requires a Telit node (UDP client), a AP or router and a Hercules utility which act as UDP client.

1VV0301570 Rev. 3.0 30 2020-04-01


Procedure Following commands are used to configure the Telit node as UDP client to send data 'telit' to UDP server (Hercules). Here server's IP address is 192.168.0.96 and port address is 8355

at+wni=0 // at+wncn=1,"Telit_Guest","qwerty123456" // at+wncn=1,"ssid","password"at+sc=2,2,0 // AT+SC=<Family>,<Type>,[<Protocol>]at+sn=0,192.168.0.96,8355,5,telit // at+sn=CID,,,datalen, data

Logs

3.2.2 UDP Server

3.2.2.1 Use Case 1:

Description Demonstrates the transfer of data from Telit node (UDP server) to UDP client where, Telit node is configured as UDP server and sends data to UDP client.

Prerequisite NA

Precondition UDP client must be configured to Telit node.

Setup Architecture The setup requires two Telit node (UDP Client and a UDP Server) and a AP or router.

Procedure Following commands are used to configure the Telit node as UDP server that is receiving data from UDP client.

1VV0301570 Rev. 3.0 31 2020-04-01


at+wni=0+WNI:1OKat+wncn=1,"ssid"+WNCN:CONNECTED,192.168.16.41,255.255.255.0,192.168.16.1at+sc=2,2,0+SC:CIDat+sb=CID,portOKat+srr=CIDOK//Once the socket receives data from client,following response is received:+SRR:CID,clientip, client port,data length//To display the received data following command has to be issued:at+sr=CID,data length+SR:clientip,client port,data total length, data present length, data

Logs NA

3.3 HTTP Client (HTTPC)

3.3.1 Use Case 1:

Description Demonstrates the configuration of Telit node for HTTP GET, using HTTP GET. The client receives 1kb.html file from server.

Prerequisite NA

Precondition 1kb.html file must be present in the server with IP address is 192.168.2.26.

Setup Architecture The setup requires the HTTP server running in the IP address 192.168.2.26, where the node HTTP client posts a GET request and receive a requested file.

Procedure Following commands are used to configure the node in station mode (in this example, SSID= “Telit_test” is set) then initialize HTTP connection, authenticate with server and then GET http/1kb.html file, close connection. (more details added with each commands).

at+wni=0 // configuration for STA modeAT+WNCN=1,"Telit_test","abcd1234" // credentials for association to APAT+NHTTPCINIT=0,100,1048,1048 // initialization httpAT+NHTTPCCFG=0,1,"Authorization","Basic dGVzdDp0ZXN0MTIz" // server credentials for authorizationAT+NHTTPCCFG=0,3,"1","" // to read header AT+NHTTPCCO=0,"192.168.2.26",80 // server connectionAT+NHTTPCREQ=0,1,"http/1kb.html" // GET request for 1kb fileAT+NHTTPCRDRSP=0,357 //reading headerAT+NHTTPCRDRSP=0,1015 // reading data AT+NHTTPCCL=0 // close connection

1VV0301570 Rev. 3.0 32 2020-04-01


Logs

3.4 MQTT

3.4.1 Use Case 1:

Description Demonstrates the subscribe and publish data feature, from Telit node to Mosquito server using MQTT feature.

Prerequisite MQTT.fx utility is used as an additional node.

Precondition MQTT.fx must be configured.

Setup Architecture The setup requires two nodes (a Telit node and a MQTT.fx) which is publishing and subscribing data to/from Mosquito server.

Procedure Following commands are used to demonstrate data subscribe and publish to Mosquito server. Here mqtt.fx client is used to demonstrate this feature. WL865E4-P is a mqtt client and a mqtt.fx is another mqtt client - both are connected with Mosquito server.

In the below example-one client is publishing data to server while another is subscribing this data and vice versa.

1VV0301570 Rev. 3.0 33 2020-04-01


at+wni=0 // station mode configurationat+wncn=1,"Telit_test" // associating with Telit_testat+nmqttinit=0 // configuration for without SSLat+nmqttconnect=0,"test.mosquitto.org",1883,"test123" AT+NMQTTSUBSCRIBE=0,1,675,"thing/gainspan/property/light"AT+NMQTTRR=0 // read enableat+nmqttr=0,54 // Here 54 is a message ID -- +NMQTTR:0,54,54,0029thing/gainspan/property/light0017test mqtt message // reading by 54 message ID, it reads published message - "test mqtt message" AT+NMQTTPUBLISH=0,1,0,1234,"thing/gainspan/property/light",3,"publish123",AT+NMQTTPUBLISH=0,1,0,1234,"thing/gainspan/property/light",3,"1234",3AT+NMQTTPUBLISH=0,1,0,1234,"thing/gainspan/property/light",3,"789",3 //We are publishing message - '789' // its publish message '789' to server, and another subscriber can read it

Logs

1VV0301570 Rev. 3.0 34 2020-04-01


4 Advanced Services


• Application Features, page 35

4.1 Application Features

4.1.1 Provisioning

4.1.1.1 Use Case 1: Wi-Fi Provisioning with BLE

Description Bluetooth devices have the ability to send and receive data, this service can expose provisioning data to other Bluetooth devices. The term “server device” in this specification refers to the embedded device which has Wi-Fi scan results and implements the provisioning procedure. A “client device” that uses the scan result and selects provisioning AP is referred to as a “Mobile App”.

Prerequisite WL865E4-P Module with latest firmware version, Android phone with Provisioning application installed from Google Play store.

Precondition Installation of BLE Provisioning application-enable location and provide permissions to access the internal files.

Setup Architecture

1. Establish a connection between the central and peripheral device via BLE interface.

2. Once the connection is established, Central (Mobile) device will send the scan request to the peripheral (embedded) device on the “Scan Request “characteristics of Service.

3. On response to the scan request, Peripheral will send the wi-fi scan result in the form of write indication on the “Scan Results” characteristics of Service. It will send the indication till the last scan result and End with the empty frame.

4. Central device will choose the provisioning AP from the scan results and send the write request on the “Provisioning AP” characteristics of service.

5. Once the provisioning verification is done, peripheral sends the success/failure indication to the central device on “Provisioning Status” characteristics of service.

1VV0301570 Rev. 3.0 35 2020-04-01


Procedure WL865E4-P module comes with pre-programmed firmware. Now issue the following commands to stop auto connection, save into profile, and reset the module.

Serial2WiFi APPATC0OKAT&W0OKAT+BI=1OKAT+BIOCAP=0OKAT+WNWEBPROV=2OK

Logs Following are the logs, for the above procedures:

1. Installation through Play store.

2. Enabling access for Provisioning.

1VV0301570 Rev. 3.0 36 2020-04-01


3. Enabling Location Settings.

1VV0301570 Rev. 3.0 37 2020-04-01


4. Provisioning application main page.

1VV0301570 Rev. 3.0 38 2020-04-01


5. Issue of AT Command in tera term for Provisioning.

6. Pairing of the device.

1VV0301570 Rev. 3.0 39 2020-04-01


7. Display of the available SSID.

8. Connecting to a specific SSID.

1VV0301570 Rev. 3.0 40 2020-04-01


9. Provision of IP address using AT commands.

10. Connection status of Provisioning application.

1VV0301570 Rev. 3.0 41 2020-04-01


11. Status of the device after internal reset.

1VV0301570 Rev. 3.0 42 2020-04-01


4.1.2 Firmware Upgrade

4.1.2.1 Use Case 1: Firmware upgrade using OTAFU

Description Demonstrates the OTAFU feature where, Telit node downloads a binary image and upgrade it.

Prerequisite Binary image must be present in the server.

Precondition NA

Setup Architecture The setup requires a Telit node, a AP or router and a server.

Procedure Following commands are used to configure the Telit node as STA which connects with Access Point (example: "Telit_test") and WLAN network interface is initialized.

A HTTP client session is started and connected to a specified server address. GET operation is performed to get the firmware binary (example binary name: “S2W_otafu_7.0.0.36.bin”) from the server and it is loaded to the trial image location. After OTAFU process is completed, the node will restart.

The upgraded firmware is validated (AT+FUVALIDATE=1). Once the validation is completed, the node will restart again. Now the binary version can be verified using the command AT+YVER.

AT+YVERAT+WNI=0AT+WNCN=1,"Telit_test"AT+FUHTTPC="192.168.12.11",80,"S2W_otafu_7.0.0.36.bin",0,1000AT+FUVALIDATE=1

NOTE: There are two locations:- 1). Current location:- If the node is programmed through UART then the current location is the default location of the firmware. 2).Trial location:- For OTAFU, the downloaded image is stored in trial location and after validation (AT+FUVALIDATE=1) the image shifts to the current location and executed. It is mandatory that the trial location is empty before OTAFU.

Logs

1VV0301570 Rev. 3.0 43 2020-04-01


4.1.2.2 Use Case 2: Firmware upgrade using HTTPC

Description Demonstrates the HTTPC feature.

Prerequisite NA

Precondition NA


Procedure Serial2WiFi APPAT+YLCOKSerial2Wireless APPAT+WNI=0+WNI:1OKAT+WNCN=1,"FWUP"+WNCN:CONNECTED,192.168.146.119,255.255.255.0,192.168.146.1OKAT+FUHTTPC="192.168.146.132",80,"S2W_otafu.bin",0,5000OKSerial2Wireless APP - FWUP SUCCESSAT+FUVALIDATE=0OKSerial2Wireless APP

Logs NA

4.1.2.3 Use Case 3: Firmware upgrade using HTTPD

Description Demonstrates the HTTPD feature.

Prerequisite NA

Precondition NA


Procedure Serial2Wireless APPat+WNI=0+WNI:1OKat+wphymodes=1,"B"OKat+wncn=1,"FWUP"+WNCN:CONNECTED,192.168.146.116,255.255.255.0,192.168.146.1OKAT+NHTTPDCFG="FWUP_Server",0,8080,443,0,4,"admin","admin"+NHTTPDCFG:0OKAT+NHTTPDSTARTOKAT+FUHTTPDOK

1VV0301570 Rev. 3.0 44 2020-04-01


Serial2Wireless APP - FWUP SUCCESSAT+FUVALIDATE=0OKSerial2Wireless APP

Logs NA

4.1.2.4 Use Case 4: Firmware upgrade using Web Provisioning

Description Demonstrates the web provisioning feature.

Prerequisite NA

Precondition NA


Procedure Serial2Wireless APPat+WNI=1+WNI:0OKat+wphymodes=0,"B"OKat+WNIPC=0,1,192.168.20.2,255.255.255.0,192.168.20.1OKat+WNAPIPC=0,192.168.20.3,192.168.20.24,86400000OKat+WNCR=0,"Provisoning-Test",2,"NONE","NONE"+WNCR:CREATEDOKat+WNIFCFG+WNIFCFG:0,02:21:7E:24:9E:60,UP,CONNECTED,AP,02:21:7E:24:9E:60,"Provisoning-Test",2,NONE,0,192.168.20.2,255.255.255.0,192.168.20.1,192.168.20.2,0.0.0.0,0.0.0.0+WNIFCFG:1,00:21:7E:24:9E:60,DOWN,NOT CONNECTED,NONE,00:00:00:00:00:00,"",0,NONE,0,0.0.0.0,0.0.0.0,0.0.0.0,0.0.0.0,0.0.0.0,0.0.0.0OKat+WNWEBPROV=1OK+WNWEBPROV:Firmware Upgrade SuccessSerial2Wireless APP - FWUP SUCCESSAT+FUVALIDATE=0OKSerial2Wireless APP

Logs NA

1VV0301570 Rev. 3.0 45 2020-04-01


1VV0301570 Rev. 3.0 46 2020-04-01

Document History

Revision Date Changes

0.0 14-06-2019 First Issue.

1.0 05-09-2019 Removed Preliminary Watermark

2.0 20-11-2019 Addition of BLE use cases

3.0 01-04-2020 Updates to the description of BLE use cases.