Dialog Semiconductor DA1468 series User manual

Company Confidential
User Manual
DA1468x Mesh SDK
UM-B-098
Abstract
This document provides basic guidelines for developers and kit users to get familiar with the
DA1468x Mesh SDK and to modify or create a BLE Mesh application based on it.

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
2 of 47
© 2019 Dialog Semiconductor
Contents
Abstract................................................................................................................................................ 1
Contents............................................................................................................................................... 2
Figures.................................................................................................................................................. 3
1 Terms and Definitions................................................................................................................... 5
2 References..................................................................................................................................... 5
3 Introduction.................................................................................................................................... 7
4 Features and Highlights ............................................................................................................... 7
5 Getting Started: Running the Demo Application ....................................................................... 8
5.1 Description ............................................................................................................................ 8
5.2 Connecting Hardware and Powering On .............................................................................. 9
5.3 Button and LED Usage ......................................................................................................... 9
5.3.1 Buttons and Switches............................................................................................ 9
5.3.2 LEDs...................................................................................................................... 9
5.4 Mesh SDK Demo Examples Bring up................................................................................. 10
5.4.1 Mobile Application Instructions............................................................................ 10
5.5 Various SDK Example Demonstrations.............................................................................. 19
5.5.1 Generic ON/OFF Model Demonstration.............................................................. 19
5.5.2 Generic Level Model Demonstration................................................................... 19
5.5.3 Light HSL Model Demonstration.......................................................................... 19
5.5.4 Generic ON/OFF Model with Multiple Elements Demonstration......................... 19
5.5.5 Vendor Specific Model Demonstration ................................................................ 20
5.5.6 Provisioner Example Demonstration ................................................................... 20
5.5.7 Proxy Example Demonstration............................................................................ 20
5.5.8 Relay Example Demonstration............................................................................ 21
5.5.9 Friend and Low Power Node Example Demonstration ....................................... 21
5.5.10 SW Upgrade Over The Air (SUOTA) Support..................................................... 22
5.5.11 Microbus Devices Example Demonstration......................................................... 22
6 Development Environment Setup.............................................................................................. 24
6.1 Installing the Environment................................................................................................... 24
6.2 Importing and Building the BLE Mesh Project .................................................................... 24
6.2.1 Build project for DA14681.................................................................................... 25
6.3 Flashing New Software into the SDK.................................................................................. 25
6.4 Modify the Bluetooth Address and Mesh Device UUID ...................................................... 27
6.5 Specify the Role of a Device............................................................................................... 27
6.6 Debugging the Application.................................................................................................. 27
6.7 Obtaining Logging Information............................................................................................ 29
6.7.1 UART Logging Window ....................................................................................... 29
6.8 Developing on Linux Host OS............................................................................................. 29
6.9 Developing on MacOS........................................................................................................ 30
6.10 Understanding Serial Terminal Options.............................................................................. 30
6.10.1 Reset the Accessory............................................................................................ 31

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
3 of 47
© 2019 Dialog Semiconductor
6.10.2 Reset to Factory Default State ............................................................................ 32
6.10.3 Enabling or Disabling Mesh Features (Proxy/Relay/Friendship)......................... 32
6.10.4 Security Keys Dump Function ............................................................................. 32
6.10.5 Monitor FreeRTOS Heap Usage and Task Stack Usage.................................... 33
6.10.6 Change Log Level................................................................................................ 33
6.10.7 Change Default TTL Value Used when Sending Messages ............................... 33
6.10.8 Change Maximum BLE RF Range to around Two Meters.................................. 33
6.10.9 Commands Related to Friendship and Low Power Node ................................... 34
6.10.10 Modify the Subscription Address List of a Server Model..................................... 34
6.10.11 Modify the Publish Address of a Client Model..................................................... 35
6.10.12 Change Client Model State using the UART Console......................................... 35
6.10.13 Change Provisioning Bearer................................................................................ 36
6.10.14 Scan for Unprovisioned Devices ......................................................................... 36
6.10.15 Start Provision for Selected Device..................................................................... 36
6.10.16 Start Configuration for Selected Node................................................................. 36
6.11 Using the SEGGER SystemView........................................................................................ 37
7 Software Architecture................................................................................................................. 40
7.1 BLE Mesh Specification...................................................................................................... 40
7.2 DA14683 Mesh SW Architecture ........................................................................................ 40
7.2.1 Overview.............................................................................................................. 40
7.2.2 Mesh DK SW Architecture................................................................................... 41
7.2.2.1 Folder and File Structure................................................................. 42
7.2.2.2 The user_<onoff/level/hsl>_<server/client>_example Files .. 42
7.2.2.3 The appl_proxy.c File .................................................................... 43
7.2.2.4 The appl_provision.c file.............................................................. 43
7.2.2.5 The appl_conf.c file ....................................................................... 43
7.2.2.6 The demo_hw.c file........................................................................... 43
7.2.2.7 The appl_storage.c file.................................................................. 43
7.2.2.8 The mesh_console.c file.................................................................. 44
Revision History ................................................................................................................................ 45
Figures
Figure 1: DA14683 USB Development Kit ............................................................................................ 8
Figure 2: DA1468x PRO Development Kit, Motherboard and Daughterboard ..................................... 8
Figure 3: DA1468x Basic Development Kit ........................................................................................... 9
Figure 4: Start Dialog's BLE Mesh App............................................................................................... 11
Figure 5: Create A Group in the Mesh Tab ......................................................................................... 11
Figure 6: Name the Group................................................................................................................... 12
Figure 7: Power the Board Programmed as a Light............................................................................ 12
Figure 8: Provision a new device ........................................................................................................ 13
Figure 9: Complete the provisioning process...................................................................................... 13
Figure 10: Nodes screen..................................................................................................................... 14
Figure 11: Settings, publish and subscribe configuration screens...................................................... 14
Figure 12: Select the Nodes Tab......................................................................................................... 15
Figure 13: Light Node screen.............................................................................................................. 15

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
4 of 47
© 2019 Dialog Semiconductor
Figure 14: Configuration Tab............................................................................................................... 16
Figure 15: Nodes screen containing both switch and light node......................................................... 16
Figure 16: Toggle Light Bulb States by SW1...................................................................................... 17
Figure 17: The group screen............................................................................................................... 17
Figure 18: Red LED on Light Bulb Board Turned on .......................................................................... 18
Figure 19: Microbus 7-Segment Display and Slider Modules............................................................. 23
Figure 20: Build Configurations of ble_mesh Project in SmartSnippets™ Studio ............................... 24
Figure 21: Build Log of ble_mesh Project in SmartSnippets™ Studio................................................. 25
Figure 22: Writing the generated Image into the flash ........................................................................ 26
Figure 23: Writing the generated Image into the flash: Log Output .................................................... 26
Figure 24: Debug Configurations ........................................................................................................ 27
Figure 25: Eclipse Debug Perspective ................................................................................................ 28
Figure 26: UART Logging Window...................................................................................................... 29
Figure 27: Verifying the Correct J-Link Version................................................................................... 37
Figure 28: SEGGER SystemView Capture Settings........................................................................... 38
Figure 29: SEGGER SystemView Trace Capture............................................................................... 39
Figure 30: SystemView Trace - Task Switching.................................................................................. 41
Figure 31: Mesh DK SW Architecture ................................................................................................. 41
Figure 32: SW Stack and File Location............................................................................................... 42

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
5 of 47
© 2019 Dialog Semiconductor
1 Terms and Definitions
ADV Advertising
ATT ATTribute Protocol
BLE Bluetooth Low Energy
CPU Central Processing Unit
DIS Device Information Service
DK Development Kit
FW Firmware
GATT Generic ATTribute Profile
GDB GNU Debugger
HSL Hue Saturation Level
HW Hardware
iOS iPhone Operating System (Apple)
IDE Integrated Development Environment
LED Light Emitting Diode
LPN Low Power Node
LTK Long Term Key
MACOS Macintosh Operating System (Apple)
PCB Printed Circuit Board
PTS Profile Tuning Suite
RF Radio Frequency
SDK Software Development Kit
SIG (Bluetooth) Special Interest Group
SRP Secure Remote Password (protocol)
SUOTA Software Upgrade Over the Air
SW Software
SWD Serial Wire Debug
TLL Time-to-Live
USB Universal Serial Bus
UUID Universally Unique Identifier
2 References
[1] Mesh_Model_Specification v1.0.pdf
[2] Mesh Device Properties v1.0.pdf
[3] Mesh_v1.0.pdf
[4] Mesh Technology Overview.pdf
[5] WGS17_Group Updates Main Deck.pdf
[6] Dialog-BLE-Mesh-Training.ppt
[7] UM-B-060, DA1468x/DA1510x Development kit Pro Hardware, User Manual, Dialog
Semiconductor
[8] UM-B-057, SmartSnippets™ Studio User Guide, User Manual, Dialog Semiconductor
[9] UM-B-066, DA1468x Development Kit Basic, User Manual, Dialog Semiconductor

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
6 of 47
© 2019 Dialog Semiconductor
[10] UM-B-047, DA1468x Getting Started with the Development Kit, User Manual, Dialog
Semiconductor
[11] UM-B-056, DA1468x Software Developer's Guide, User Manual, Dialog Semiconductor
[12] AN-B-037, DA1468x Power Measurements, Application Note, Dialog Semiconductor
[13] UM-B-094, DA14683 USB Kit, User Manual, Dialog Semiconductor
[14] UM-B-044, DA1468x Software platform reference, User Manual, Dialog Semiconductor

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
7 of 47
© 2019 Dialog Semiconductor
3 Introduction
This document provides basic guidelines for developers and kit users to get familiar with the
DA1468x Mesh SDK and to modify or create a BLE Mesh application based on it.
The reference implementation is tested against the latest profile tuning suite (PTS) tool from the
Bluetooth Special Interest Group (SIG) and is under certification for BLE Mesh v1.0 specification.
Users are expected to have some basic understanding about the BLE Mesh protocol
(http://blog.bluetooth.com/introducing-bluetooth-mesh-networking).
4 Features and Highlights
■Supports Bluetooth BLE Mesh v1.0 specification [1]
□Provisioning over generic attribute profile (GATT) and advertising (ADV) bearer
□Support for all Mesh SIG defined models except sensor and time model
□Support for Vendor Specific Mesh models
□Support for Relay, Proxy, Friend, and Low Power Node features
■Qualified Bluetooth subsystem (QDID)
□Tested as part of UnPlugFest UPF53, (Jan 2016), UPF54 (June 2016), UPF55 (Oct 2016),
UPF56 (Jan 2017), UPF57 (June 2016), UPF58 (Oct 2017), UPF59 (Jan 2018), UPF60 (May
2018), UPF61 and UPF62
■Single-chip solution with hardware (HW) acceleration for all Mesh security operations
■Bluetooth low energy (BLE) 4.2 wireless connectivity
■Easy scalable software (SW) architecture to integrate other smart home protocols in a single
design
■User application memory resources:
□Application size only limited by size of external Flash memory
□~64 kB RAM remaining after existing reference app/BLE stack/Mesh library usage
■Compatible with DA1468x Basic, Pro, and USB HW development boards
■Debug features: Segger J-Link debugger/RTT/Systemview and print to console
■Sample iOS and Android applications demonstrating many of the BLE Mesh features

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
8 of 47
© 2019 Dialog Semiconductor
5 Getting Started: Running the Demo Application
5.1 Description
The DA1468x Mesh SDK is compatible with both Pro, Basic and USB DK HW. The HW boards are
described at reference documents [7], [13], and [9]. For all Mesh reference applications, the same
HW can be used. The DK can be reprogrammed to run a single instance of an application. In order to
switch between different applications, these HW boards can be upgraded over JTAG using the
development process explained in section 6.2.1.
NOTE
The preferred DK HW to start using the Mesh SDK with is the DA14683 USB development kit. It has a much
smaller form factor, is more affordable, and is easier to create and test large Mesh networks with multiple
nodes.
Figure 1: DA14683 USB Development Kit
Figure 2: DA1468x PRO Development Kit, Motherboard and Daughterboard

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
9 of 47
© 2019 Dialog Semiconductor
Figure 3: DA1468x Basic Development Kit
5.2 Connecting Hardware and Powering On
The DK HW boards are pre-assembled and does no need extra rework. There is no need to change
any jumper positions to get a functional demo application running.
The DK HW boards are shipped unprogrammed. So to flash the demo image, please first follow the
instructions in sections 6.1, 6.2,and 6.2.1. The boards will then be in factory reset state and their
node database will be empty (start from un-provisioned state).
The boards are powered via USB. Connect the provided USB cable to laptops, desktops, or power
adapters to power the accessories.
The boards should then enter the unprovisioned Beacon advertising mode and be ready to interact
with any Mesh enabled provisioner. The default provisioning bearer is GATT.
5.3 Button and LED Usage
The buttons and LEDs that are used in the reference implementation are listed in section 5.3.1 and
5.3.2. This guide assumes that the DA14683 USB DKs are used:
5.3.1 Buttons and Switches
●RESET: resets the DA14683 HW.
●SW1 short press: toggles Mesh model state (represents the behavior of manually switching ON
or OFF a fan, a lock, a light bulb, or others).
●SW1long press (~5 sec): reset the device to factory state (start from un-provisioned state).
●SW2: it is only used in the multiple-element example to represent operation of the second
element
5.3.2 LEDs
●D10: it represents Mesh model state (for example, ON: lightbulb is turned on; OFF: lightbulb is
turned off)
●D8: it represents the provisioning and configuration state:

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
10 of 47
© 2019 Dialog Semiconductor
○Fast blinking: Device is unprovisioned and waits to be provisioned
○Slow blinking: Device is provisioned (belongs to a network) but not configured yet (no publish
or subscription address is assigned yet)
○Turned off: Device is both provisioned and configured and can interact with other devices in
the network
○Its intensity level represents the state of the level server model in the corresponding example
○Its color represents the hue saturation level (HSL) settings of the HSL server model in the
corresponding example
●D9: it is only used in the multiple-element example to represent operation of the second element
5.4 Mesh SDK Demo Examples Bring up
The device can be tested against any iOS or Android smartphone applications which support the
Mesh protocol.
Make sure that Dialog's Mesh application, which can be found under
DA14683_MESH_vXXX\projects\host_apps\ethermind-mobile directory, is used.
Dialog's USB DK should be programmed with the default ble_mesh application found in the directory
DA14683_MESH_vXXX\projects\dk_apps\demos\ble_mesh. The default application code enables
provisioning over GATT and expects the devices to be provisioned over GATT.
At least two different nodes need to be programmed. Both should have a unique node ID and
different roles (for example, one is a lightbulb and the other is a switch). One of them should get
configured as the server of the model and the other one as the client. The available model examples
in this release are:
●Generic ON/OFF
●Generic level
●Generic ON/OFF with multiple elements
●Light HSL
●Vendor specific
For every node after factory reset, a random BLE address and Mesh universally unique identifier
(UUID) is assigned to the node. Users do not need to try to assign UUIDS to the nodes like when
using the previously released SDKs, for example, programming NVPARAM partition.
NOTE
This release contains support for all the SIG models defined in the Mesh specification v1.0. The examples
can be used as a guideline to how models can be initialized and used.
The provisioner example in the release is not meant to be tested with the mobile app. This example
demonstrates provisioning over the ADV bearer with the other examples in the SDK, while the mobile app
demonstrates provisioning over the GATT bearer. For more information regarding the provisioner example
refer to section 5.5.6.
5.4.1 Mobile Application Instructions
The section describes how the mobile app can be used to provision and configure a new device to
the network. Any of the SDK examples can be used but new users are recommended to start with
the Generic ON/OFF example, which provides a simple demo of how to turn ON/OFF a LED in the
server (for example, a lightbulb) side by using a button from the client (for example, a switch) side.
Note 1 The mobile application can provision and configure all the examples in the SDK, but its current version
can only remotely control the generic ON/OFF example.

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
11 of 47
© 2019 Dialog Semiconductor
1. Download Dialog's BLE Mesh Application from either Apple's App Store or Google Play Store
and start the App (Figure 4).
Figure 4: Start Dialog's BLE Mesh App
2. Select the "CREATE NEW NETWORK" Option. Type the name of the new network, optionally
select an icon for it. The rest options can be left unchanged.
3. Create a group by pressing the "Add New Group" button. In Mesh, a group usually represents
an area in which many Mesh nodes belong and should be controlled and respond together for
example a kitchen, living room, bedroom. (Figure 5)
Figure 5: Create A Group in the Mesh Tab
4. Enter a name for the group and press the "CONFIRM" button (Figure 6)

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
12 of 47
© 2019 Dialog Semiconductor
Figure 6: Name the Group
5. Power the board programmed as a light and make sure it is un-provisioned (factory reset) by
pressing the SW1 for at least 5 sec. (Figure 7)
Figure 7: Power the Board Programmed as a Light
6. Provision a new device by selecting in the side menu the "Unprovisioned devices" tab. (Figure
8)

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
13 of 47
© 2019 Dialog Semiconductor
Figure 8: Provision a new device
7. Select the device to be provisioned and type the required password to complete the
authentication process. Note that this is device specific, depends on the device configuration and
it can be optional. The default password that is used in the SDK is "f00l", ie the word "fool" after
replacing the "o" with zero. Once the provisioning process is completed press "GO TO
OVERVIEW" (Figure 9)
Figure 9: Complete the provisioning process
8. Now the Nodes tab contains the new node that was just added. The default names for the
elements and the nodes are used. These can be changed through the settings as shown below.
(Figure 10)
Node settings

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
14 of 47
© 2019 Dialog Semiconductor
Figure 10: Nodes screen
9. Each element name along with publish/subscribe settings can be modified as shown below. For
publish settings, one address can be assigned along with publish period, transmit interval and
count. For the subscription list settings, multiple groups can be selected. (Figure 11)
Figure 11: Settings, publish and subscribe configuration screens
10. The node settings screen can be used to set a friendly name for the node (eg Bedroom
Lightbulb), set which mesh features are enabled (er proxy, beacon, friend, relay), or un-provision
the node by clicking on the trashcan icon. (Figure 12)
Element settings

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
15 of 47
© 2019 Dialog Semiconductor
Figure 12: Select the Nodes Tab
11. The configured node is shown at the below figure. Note that if an element contains a model
server element (eg Generic ONOFF server), the application can control its state by sending a
ON/OFF message directly to its unicast address (Figure 13).
Figure 13: Light Node screen
12. Another node can be added by repeating steps 5-11. The following figure displays the screens
after a switch node is added. Note that the switch is a Generic ON/OFF client, it does not contain
a state therefore unlike the lightbulb case, the application does not contain a control element
switch any state (Figure 14)

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
16 of 47
© 2019 Dialog Semiconductor
Figure 14: Configuration Tab
13. The nodes screen now should contain the two different nodes. The vendor and the first element
address of each node is also displayed (Figure 15).
Figure 15: Nodes screen containing both switch and light node
14. At this point, since both nodes are subscribed to the same group, the user can toggle the state of
light bulbs by using SW1 on the switch board (Figure 16)

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
17 of 47
© 2019 Dialog Semiconductor
Figure 16: Toggle Light Bulb States by SW1
15. The group screen contains all the created groups for this network. For each group, for every node
element that is subscribed, there is the corresponding control element. For example, for the
Generic ON/OFF model servers there is an ON/OFF switch, for the Generic Level model servers
there is a slider. In this specific example, the corresponding ONOFF switch will control all the
lightbulbs which are subscribed to this group. Note that the group address is used as the
destination address in the corresponding messages. (Figure 17).
Figure 17: The group screen
16. The red LED on all light bulb boards is turned on (Figure 18).

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
18 of 47
© 2019 Dialog Semiconductor
Figure 18: Red LED on Light Bulb Board Turned on

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
19 of 47
© 2019 Dialog Semiconductor
5.5 Various SDK Example Demonstrations
5.5.1 Generic ON/OFF Model Demonstration
The instructions described in section 5.4.1 should result in a complete demo set up between a server
(the lightbulb) and a client (the switch). After the setup, pressing the switch SW1 should toggle the
lightbulb D10 LED.
It is possible to extend the network with more nodes of the same model. For example, by following
the same instructions multiple lightbulbs can be added to the same group and be toggled at the same
time by a single switch. A different demo can be setup by creating two different groups in the mobile
application (refer to step 2to 6in section 5.4.1), for example, "Office" and "Kitchen". Then two
different switches can be configured to control two different groups of lights at the same network.
5.5.2 Generic Level Model Demonstration
The same instructions as in section 5.4.1 can be applied to provision and configure two client/server
nodes with the generic level model enabled. Compared to the generic ON/OFF model, the only
difference in this example is that the mobile application does not support the control of the level
server from the smartphone (see Note 1). Users can still use the SW1 button from the client side to
control the intensity of the D8 LED of the level server. Alternatively, controlling the intensity of D8 can
be done by the UART console (refer to section 6.10.12).
Similar to the generic ON/OFF model, multiple groups of nodes can be created. For example,
multiple clients can control multiple server nodes at the same or different groups.
5.5.3 Light HSL Model Demonstration
The same instructions as in section 5.4.1 can be applied to provision and configure two client/server
nodes with the light HSL model enabled. Compared to the generic ON/OFF model, the only
difference in this example is that the mobile application does not support the control of the HSL
server state values from the smartphone (see Note 1). Users can still use the SW1 button from the
client side to control the color of the D8 LED of the HSL server by cycling through a set of predefined
colors. Alternatively, controlling the color of D8 can be done by the UART console (refer to section
6.10.12)
Similar to the generic ON/OFF model, multiple groups of nodes can be created. For example,
multiple clients can control multiple server nodes at the same or different groups.
5.5.4 Generic ON/OFF Model with Multiple Elements Demonstration
The same instructions as in section 5.4.1 can be applied to provision and configure two client/server
nodes with the "generic ON/OFF multiple elements" enabled. Compared to the generic ON/OFF
model, the only difference in this example is that the mobile application does not support the
configuration and control of the second element (see Note 1). This has to be done manually using
the UART console.
At the client side, users need to enter:
publish set 1 49454
At the server side, users need to enter:
subscribe add 1 49454
Now toggling the switch SW2 from the client side should toggle the D9 LED which represents the
second element from server side.
Note that another demo setup could be to add the same address in the first element of the server.
subscribe add 0 49454

UM-B-098
DA1468x Mesh SDK
Company Confidential
User Manual
Revision 1.2
1-April-2019
CFR0012
20 of 47
© 2019 Dialog Semiconductor
Now LED D9 responds to both SW1/SW2 toggling, but D10 only to SW2.
For more information regarding these commands, refer to sections 6.10.10 and 6.10.11.
5.5.5 Vendor Specific Model Demonstration
The example "vendor specific model" defines a custom model that represents two states in the same
model. The first is an ON/OFF state and the second is a level state. Compared to the generic
ON/OFF model and generic level model, the vendor specific model defines two different states in a
single model. Moreover, this setup is also different from defining two separate elements, one as a
generic ON/OFF element and the other one as a generic level element, in the same model.
The same instructions as in section 5.4.1 can be applied to provision and configure two client/server
nodes with the vendor specific model enabled. Compared to the generic ON/OFF model, the only
difference in this example is that the mobile application does not support the control of the ON/OFF
and level server from the smartphone (see Note 1). Users can still use the SW1 and SW2 switches
from the client side to control the ON/OFF state of D9 and intensity of the D8 LED at the level server.
5.5.6 Provisioner Example Demonstration
The target of this example is to demonstrate the provisioning and configuration of a new node to the
network by using a different node that has the role of a provisioner and a configuration client. In this
demo smartphones are not needed at all. A provisioner node and a smartphone create two
completely different networks (network/device keys), therefore the nodes that are provisioned with
one network cannot communicate with the other.
Another big difference between a provisioner node and a smartphone is that a provisioner node does
the provisioning over the ADV bearer while a smartphone does the provisioning over the GATT layer.
All the examples in the code are configured to do provisioning over the GATT layer by default.
Therefore, in order to test the provisioner example, users have to change the bearer to ADV bearer
by executing:
Shell> bearer adv
NOTE
Due to a known bug in the SDK which is supposed to be fixed at the next release, only one node at a time
can be provisioned and configured successfully. Before adding a new node to the network, users need to
reset both the provisioner and the new node to factory reset state. After a new node is added, it can
communicate with the other nodes.
5.5.7 Proxy Example Demonstration
The proxy feature in a node enables it to connect with a smartphone over GATT and enables
smartphone Apps capable of being connected to Mesh to communicate and control Mesh nodes in
the network.
The proxy functionality can be enabled in two ways:
●through the mobile application during provisioning and configuring a node. Refer to step 13 of
section 5.4.1
●by manually enabling the feature at the UART console of a node. Refer to section 6.10.3
After enabling the proxy feature, follow the steps Error! Reference source not found. to 14
described in section 5.4.1.
NOTE
The mobile applications with the version up to V0.0.3 only support the control over the ON/OFF example.