Telit Wireless Solutions BlueMod plus S42/Central Software User's Manual
  1. Manuals
  2. Brands
  3. Telit Wireless Solutions Manuals
  4. Control Unit
  5. BlueMod plus S42/Central
  6. Software user's manual
Telit Wireless Solutions BlueMod plus S42/Central Software User's Manual

Telit Wireless Solutions BlueMod plus S42/Central Software User's Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
BlueMod+S42/Central Software User Guide
1VV0301318 Rev. 3 – 2018-08-31
BlueMod+S42/Central
Software User Guide
1VV0301318 Rev. 3 – 2018-08-31
Reproduction forbidden without written authorization from Telit Communications S.p.A.- All Rights Reserved.
Page 1 of 66

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the BlueMod plus S42/Central and is the answer not in the manual?

Questions and answers

Related Manuals for Telit Wireless Solutions BlueMod plus S42/Central

Summary of Contents for Telit Wireless Solutions BlueMod plus S42/Central

  • Page 1 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Reproduction forbidden without written authorization from Telit Communications S.p.A.- All Rights Reserved. Page 1 of 66...
  • Page 2 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 APPLICABILITY TABLE PRODUCT BlueMod+S42/Central Reproduction forbidden without written authorization from Telit Communications S.p.A.- All Rights Reserved. Page 2 of 66...
  • Page 3 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE Notice While reasonable efforts have been made to assure the accuracy of this document, Telit assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein.
  • Page 4 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Usage and Disclosure Restrictions License Agreements The 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. Copyrighted Materials Software and documentation are copyrighted materials.

  • Page 5: Table Of Contents

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Contents 1. Introduction ........................7 1.1. Scope ........................7 1.2. Audience ........................7 1.3. Contact Information, Support ................... 7 1.4. Text Conventions ..................... 8 1.5. Related Documents ....................8 2. Introduction ........................9 2.1.
  • Page 6 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 6.4.2. Drive from "interface down" to "interface up" State ............. 43 6.5. Example of UICP Usage ..................44 6.5.1. State Change from "interface up" to "interface down" ..........44 6.5.2. State Change from "interface down" to "interface up" ..........45 7.

  • Page 7: Introduction

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Introduction 1.1. Scope This document describes the usage of the BlueMod+S42/Central Bluetooth module. 1.2. Audience This document is intended for Telit customers, especially system integrators, about to implement Bluetooth modules in their application. 1.3.

  • Page 8: Text Conventions

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 1.4. Text Conventions Danger – This information MUST be followed or catastrophic equipment failure or bodily injury may occur. Caution or Warning – Alerts the user to important points about integrating the module, if these points are not followed, the module and end user equipment may fail or malfunction.

  • Page 9: Introduction

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Introduction 2.1. Overview This document describes the usage of the BlueMod+S42/Central Bluetooth module featuring firmware version V3.001 or later. For a detailed description of the commands refer to the BlueMod+S42/Central AT Command Reference.

  • Page 10: Modes And Connections

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Modes and Connections In AT command mode the BlueMod+S42/Central supports 3 parallel central connections or one peripheral Terminal I/O server connection. This means that the BlueMod+S42/Central stops advertising (being connectable) as peripheral as soon a central connection is established. When a peripheral Terminal I/O server connection is active, it is not possible to establish a central connection to be used as GATT client.
  • Page 11 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.1.1.1. Searching for Available Peripheral Devices If the Bluetooth address of the peripheral device is unknown the BlueMod+S42/Central needs to scan for available peripheral devices first. AT+LESCAN=GATT D0A4E9658F65,t3 RSSI:-60 TYPE:CONN NAME:BM+S 8F65 MNF:8F0009B0011000 UUID:FEFB DE338F0D1A22,t3 RSSI:-68 TYPE:CONN...
  • Page 12 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.1.1.2. Create GATT Connection To establish a GATT connection to a peripheral device it is required to initiate a call request to the unique Bluetooth address. ATDF1B9EB41D81E,t3,GATT CONNECT GATT 0x10 The BlueMod+S42/Central reports the created GATT connection with the result message „CONNECT“...
  • Page 13 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 AT+LESRVD=0x10,uFF00 UUID:FF00 0x0011 PROP:0x3E UUID:FF01 0x0014 PROP:0x3E UUID:FF02 0x0017 PROP:0x3E UUID:FF03 0x001A PROP:0x08 UUID:FF04 0x001C PROP:0x04 UUID:FF05 0x001E PROP:0x02 UUID:FF06 0x0020 PROP:0x10 UUID:FF07 0x0023 PROP:0x20 UUID:FF08 0x0026 PROP:0x30 UUID:FF09 0x0029 PROP:0x3E UUID:FF0A 0x002C PROP:0x3E UUID:FF0B 0x002F PROP:0x3E UUID:FF0C 0x0032 PROP:0x3E UUID:FF0D...
  • Page 14 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.1.1.4. Writing Data to a Characteristic To write data to a characteristic it is required that the properties of this characteristic support “write” or “write without response”. There are two different options to write data to the characteristic: •...
  • Page 15 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.1.1.5. Reading Data from a Characteristic To read data from a characteristic it is required that the properties of this characteristic supports “read”, “notify” or “indicate”. To read data bytes from a characteristic of the GATT server on the peripheral side the host controller needs to use the connection handle and characteristic handle from the ATD and AT+LESRVD commands.
  • Page 16 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.1.1.6.1. Enable Notifications: AT+LECCCD=0x10,0x0011,1 The result message “OK” reports that activating notifications to the required connection handle and characteristic handle was successful. When the data of this characteristic on the GATT server changed to “0x36, 0x37” the BlueMod+S42/Central generates an event (“LENOTI”) that reports these changes: LENOTI:0x10,0x0011,3637 The reported “LENOTI”...
  • Page 17 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.1.1.6.4. Disable Indications: AT+LECCCD=0x10,0x0011,0 The result message “OK” reports that deactivating the indications to the required connection handle and characteristic handle was successful. 3.1.1.6.5. Close Connection: When the connection is not needed anymore, it could be disconnected. To close a GATT connection to a peripheral device the host controller needs to use the connection handle.

  • Page 18: Peripheral Role As Terminal I/O Server

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.1.2. Peripheral Role as Terminal I/O Server A Terminal I/O connection to the BlueMod+S42/Central can be created from each Bluetooth Low Energy device that supports the Terminal I/O client role. Telit provide the Terminal I/O client implementation for iOS and Android. To establish a Bluetooth Low Energy connection from a smartphone to the BlueMod+S42/Central the "Terminal IO Utility"...
  • Page 19 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.1.2.1. Incoming Terminal I/O Connection For a Terminal I/O connection it is necessary that the Terminal I/O service and the advertising mode are enabled. This is the default behavior of the BlueMod+S42/Central. The BlueMod+S42/Central signals an incoming Terminal I/O connection with the following event: RING...
  • Page 20 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.1.2.3. Close Terminal I/O Connection The Terminal I/O connection can be closed in the following two different options: • By using the GPIO “HANGUP” (only available if this GPIO is controlled by the host controller) •...

  • Page 21: Multiple Gatt Connections

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.1.3. Multiple GATT Connections This chapter describes the possibility to connect to different GATT peripheral devices at the same time. In complement to chapter 3.1.1 the following example demonstrates GATT connections to 3 different peripheral devices.
  • Page 22 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.1.3.2. Create Multiple GATT Connections Initiate first GATT connection to a peripheral device. ATDF1B9EB41D81E,t3,GATT CONNECT GATT 0x10 The BlueMod+S42/Central reports the created GATT connection with the result message „CONNECT“ include the connection type „GATT“ and a connection handle “0x10”. Initiate second GATT connection to a peripheral device.

  • Page 23: Mux Mode

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.2. MUX Mode To handle connections to peripheral devices and the Terminal I/O connection in parallel the BlueMod+S42/Central supports the multiplexing (MUX) mode. In this mode there is an always accessible AT command channel available. This command channel (channel ID= “FF”) enables the possibility to handle all four links in parallel (three GATT connections to peripheral devices and one Terminal I/O connection).
  • Page 24 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.2.1.1. Enable the Multiplexing Mode As default the BlueMod+S42/Central communicates to the serial interface in the AT command mode. This is the default behavior of the BlueMod+S42/Central. To enable the multiplexing mode during the run time it is required to send the following command: AT+BMUX=1 After this initial command the BlueMod+S42/Central reports the response “OK”...
  • Page 25 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.2.1.3. Discovering Services and Characteristics After the GATT connection gets established the BlueMod+S42/Central is searching for available services. cc ff 0f 41 54 2b 4c 45 53 52 56 44 3d 30 78 31 30 0d cc ff 02 0d 0a AT+LESRVD=0x10 cc ff 05 55 55 49 44 3a...
  • Page 26 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 In addition to the service UUID value it is required to get the characteristic values of the required service UUID “FEFB”. cc ff 15 41 54 2b 4c 45 53 52 56 44 3d 30 78 31 30 2c 75 46 45 46 42 0d AT+LESRVD=0x10,uFEFB cc ff 02 0d 0a...
  • Page 27 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 The list reports all characteristic information of the service UUID: “FEFB” in details: characteristic handle: 0x0011 characteristic properties: PROP:0x04 characteristic UUID: UUID: 00000001000010008000008025000000 characteristic handle: 0x0013 characteristic properties: PROP:0x10 characteristic UUID: UUID: 00000002000010008000008025000000 characteristic handle: 0x0016...
  • Page 28 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 The example will add data channels for two characteristics of the service UUID: “FEFB”. cc ff 1b 41 54 2b 4c 45 41 44 44 43 48 41 4e 3d 30 78 31 30 2c 30 78 31 33 2c 43 4d 44 0d cc ff 02 0d 0a AT+LEADDCHAN=0x10,0x13,CMD...
  • Page 29 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 The following example demonstrates activating “notifications” for the characteristic handle “0x13” in MUX mode: cc ff 16 41 54 2b 4c 45 43 43 43 44 3d 30 78 31 30 2c 30 78 31 33 2c 31 0d AT+LECCCD=0x10,0x13,1 cc ff 06 0d 0a 4f 4b 0d 0a...
  • Page 30 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.2.1.7. Accept Incoming Terminal I/O Connection During the active GATT server connection to maximum three peripheral devices it is possible to handle one Terminal I/O connection in parallel. The following example lists the serial communication of an incoming Terminal I/O connection (i.e.

  • Page 31: Vv0301318 Rev. 3 – 2018

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 3.2.1.9. Close Terminal I/O Connection To disconnect the Terminal I/O connection (i.e. from a mobile phone) the BlueMod+S42/Central close the connection with the use of the connection handle. cc ff 09 41 54 48 3d 30 78 30 31 0d cc ff 0c 0d 0a 4e 4f 20 43 41 52 52 49 45 52 ATH=0x01 cc ff 05 20 30 78 30 31...

  • Page 32: Startup Timing

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Startup Timing The start-up time until the BlueMod+S42/Central is able to accept link requests or serial data depends on: • the firmware version • the source for the slow clock • the usage of the UART Interface Control Protocol (UICP) more details...

  • Page 33: Security

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Security This chapter describes the security mechanisms of the BlueMod+S42/Central to control the access to the local Bluetooth devices characteristics. The pairing process is triggered automatically when an access to a characteristic is requested that requires security. 5.1.

  • Page 34: Security Levels For Terminal I/O

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 given connection only supports LE legacy security key generation procedures this legacy procedures will be used instead. From user point of view this negotiation is mostly transparent and backward compatible. The only exceptions are if LE Secure Connection is mandated (AT+LETIO=4) or the new display yes/no (AT+BIOCAP=1) configuration is used.
  • Page 35 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 AT+BMITM controls the man in the middle (MITM) protection of the device during LE Security. Value Description Man in the middle protection disabled (default) Man in the middle protection enabled LE Security defines the following association models based on the Input/Output (I/O) capabilities of the two devices: •...
  • Page 36 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Responder Display only Display Yes/No Keyboard only No input no output Display and keyboard Initiator Passkey entry Just Works Passkey entry Display only Just Works Just Works (initiator displays, responder inputs) (both automatic (initiator displays, responder inputs) (both automatic confirmation)
  • Page 37 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 The following flow charts will give an example for the different SSP authentication methods “just works” and “passkey entry” within an incoming call request from an iPhone (or other compatible iOS device) using Telit’s Terminal I/O Utility app to the BlueMod+S42/Central (see also the connection example in chapter 3.1.2).

  • Page 38: Connection Example Terminal I/O "Just Works

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Connection Example Terminal I/O “Just Works” 5.4. Reproduction forbidden without written authorization from Telit Communications S.p.A.- All Rights Reserved. Page 38 of 66...

  • Page 39: Connection Example Terminal I/O "Passkey Entry

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Connection Example Terminal I/O “Passkey Entry” 5.5. with I/O capabilities “display only” Reproduction forbidden without written authorization from Telit Communications S.p.A.- All Rights Reserved. Page 39 of 66...

  • Page 40: Uart Interface Control Protocol (Uicp)

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 UART Interface Control Protocol (UICP) 6.1. General Protocol Description Telit UART Interface Control Protocol (UICP) defines a protocol to control the logical state of an UART based interface, thereby peers to switch off local UART devices for power saving (or other) reasons.

  • Page 41: Uicp Protocol States

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 6.4. UICP Protocol States The UICP protocol defines four states: "interface up" - IUR-OUT# active - IUC-IN# don't care (UART flowcontrol) pending pending "interface down" "interface up" - IUR-OUT# inactive - IUR-OUT# active - IUC-IN# active - IUC-IN# inactive "interface down"...

  • Page 42: Drive From "Interface Up" To "Interface Down" State

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 6.4.1. Drive from "interface up" to "interface down" State Once a de-asserted IUR-OUT# signal of the initiator is detected by the acceptor, the acceptor shall confirm that signal by de-asserting its IUC-OUT# signal which is connected to the IUC- IN# signal of the initiator.

  • Page 43: Drive From "Interface Down" To "Interface Up" State

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 6.4.2. Drive from "interface down" to "interface up" State To initiate the state change from "interface down" state to "interface up" state the initiator shall assert the IUR-OUT# signal. The acceptor confirms the IUR-IN# signal with asserting its IUC-OUT# signal which is connected to the IUC-IN# signal of the initiator.

  • Page 44: Example Of Uicp Usage

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 6.5. Example of UICP Usage The following examples show the state change between the BlueMod+S42/Central and the host. The scenario here might be that both devices use the "interface down" state to drive the MCU into some kind of power saving mode that allows to "wake up"...

  • Page 45: State Change From "Interface Down" To "Interface Up

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 6.5.2. State Change from "interface down" to "interface up" Host and BlueMod+S42/Central are in the state “Interface down” and may have the MCU into some kind of power saving state. The host wants to send data to the BlueMod+S42/Central and asserts its IUR-OUT# signal. Parallel to that UICP signaling from host to BlueMod+S42/Central the BlueMod+S42/Central wants to send data to the host and asserts its IUR-OUT# signal as well.

  • Page 46: Nfc Handover

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 NFC Handover 7.1. NFC Mode The NFC mode can be activated or deactivated by using the following AT command: AT+NFCMODE=<value> Value Description NFC interface OFF NFC interface ON Enable the NFC Handover functionality by using the following AT command: 7.2.
  • Page 47 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 After the pairing request ended successfully you will find the new paired device within the Bluetooth settings of your smartphone. For further information regarding NFC Handover please refer to the BlueEva+S42 User Guide. Reproduction forbidden without written authorization from Telit Communications S.p.A.- All Rights Reserved.

  • Page 48: Firmware Upgrade

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Firmware Upgrade The firmware upgrade will be done locally by either • A Telit provided firmware update tool. This is a Windows™ program that contains the firmware and uses a PC with a serial port for the update •...
  • Page 49 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 The program requires a PC with at least one free COM port. The upload is processed via the serial port the device is attached to. Before starting the update by pressing the “Update” button the device shall be reset. •...

  • Page 50: Firmware Update Protocol On The Host System

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 8.1.3. Firmware Update Protocol on the Host System This chapter describes the protocol layer used for firmware update over serial on the BlueMod+S42/Central. The table below contains the maximum possible binary firmware sizes: Firmware variant Maximum possible binary firmware size V3.002...
  • Page 51 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Start packet With the “Start packet” the DFU bootloader is informed about the kind of update and the length of the binary image. The length of the image is an unsigned 32 bit integer in LSB first order. It is length of the file with the “.bin”...
  • Page 52 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Stop packet When the Application image has been transferred to the BlueMod+S42/Central boot loader the image must be activated. The stop packet will inform the boot loader that transferring of the image has completed and the application can be started.

  • Page 53: Firmware Update Over The Air (Ota)

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 8.2. Firmware Update over The Air (OTA) The BlueMod+S42/Central supports firmware over the air update. The firmware update over the air can be performed by using the Nordic nRF ToolBox app available for iOS and Android or by using the Nordic Master Control Panel and the corresponding Nordic Bluetooth hardware.

  • Page 54: Firmware Update Over The Air Using Nordic Nrf Toolbox On Android

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 8.2.1. Firmware Update Over The Air using Nordic nRF Toolbox on Android Make sure the BlueMod+S42/Central has already activated the firmware over the air update. Open the nRF ToolBox app on the smartphone and choose “DFU“. Press the button “SELECT FILE”.
  • Page 55 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Select file type “Distribution packet (ZIP)”. Search via file manager for the firmware package which was previously copied to the smartphone (e.g BMS42_Central_V3_010_FWupdate_OTA.zip in the example below). Reproduction forbidden without written authorization from Telit Communications S.p.A.- All Rights Reserved. Page 55 of 66...
  • Page 56 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Press the button “SELECT DEVICE” and select the “BM+S_DFU” from the list of available devices. Press the “UPLOAD” button to upload the firmware package over the air to the BlueMod+S42/Central. After the file was uploaded successfully the BlueMod+S42/Central will start with the new firmware.

  • Page 57: System Off Mode

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 System OFF Mode The BlueMod+S42/Central supports the possibility to set the module into low power mode during the time the module is not used with the AT+SYSTEMOFF command. The BlueMod+S42/Central will restart on activity at the GPIO input lines UART-RTS#, IUR- IN# or GPIO[4].
  • Page 58 BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Reproduction forbidden without written authorization from Telit Communications S.p.A.- All Rights Reserved. Page 58 of 66...

  • Page 59: Le Connection Parameters

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 LE Connection Parameters This chapter describes the kind of creating a BLE connection from the central device to the peripheral device include the usage of the LE connection parameters. 10.1. Create a Bluetooth Low Energy Connection In a typical Bluetooth Low Energy system, the peripheral device advertises with specific data letting any central device know that it is a connectable device.

  • Page 60: Optimize The Connection Interval From Slave By Using The Slave Latency

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 • Supervision Timeout This is the maximum amount of time between two successful connection events. If this amount of time passes without a successful connection event, the device is to consider the connection lost, and return to an unconnected state.

  • Page 61: Identify The Required Connection Interval

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 10.3. Identify the Required Connection Interval Different applications may require different connection intervals. The advantage of having a very long connection interval is that significant power is saved, since the device can sleep most of the time between connection events.

  • Page 62: Update The Connection Parameters

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 10.4. Update the Connection Parameters In some cases, the central device will request a connection with a peripheral device containing connection parameters that are unfavorable to the peripheral device. In other cases, a peripheral device might have the desire to change parameters in the middle of a connection, based on the peripheral application.

  • Page 63: Central Side Initiates A Gatt Connection

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 10.5.1. Central Side Initiates a GATT Connection Reproduction forbidden without written authorization from Telit Communications S.p.A.- All Rights Reserved. Page 63 of 66...

  • Page 64: Central Side Changed Initial Connection Parameter

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 10.5.2. Central Side Changed Initial Connection Parameter Reproduction forbidden without written authorization from Telit Communications S.p.A.- All Rights Reserved. Page 64 of 66...

  • Page 65: Peripheral Side Create A Connection Parameter Update Request

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 10.5.3. Peripheral Side Create a Connection Parameter Update Request Reproduction forbidden without written authorization from Telit Communications S.p.A.- All Rights Reserved. Page 65 of 66...

  • Page 66: Document History

    BlueMod+S42/Central Software User Guide 1VV0301318 Rev. 3 – 2018-08-31 Document History Revision Date Changes 2016-08-19 First issue 2016-10-05 Added new values 3,4 of AT+LETIO command, Added new chapter LE Secure Connections, Corrected value of AT+BIOCAP in connection example Terminal I/O "Passkey entry" 2018-02-02 Replaced TeraTerm by Telit AT Controller Replaced BlueMod+S42 Updater by IoT Updater...

Table of Contents