Which Example should i use for BLE mesh which support the OTA?

[shubham gupta]

Hi Everone..

I want to know for my project Which Example should i use for BLE mesh which support the OTA

I have nRF52832 DK, and several other custom board  which is based on nrf52840.  I have working on BLE mesh sdk version 5.0

I want to make BLE mesh in that node, relay node, Border node for communicate with server.

Node_1(Adc_reading) (boolean_ value) (SPI) --------> relay_Node---->Border_Node------->(Through UART)-----> send data to Server(Cloud).

Please give me tutorial and what would be the flow for this using nRF52832 BLE mesh. It will use making smart socket project.

Thanks in Advance.

[Hung Bui]

Hi Shubham, 

I'm afraid I don't fully understand what you want to do. 

Could you please describe your application ? 
Which device is connected to cloud and how do you want to communicate via UART. What do you mean by "use UART instead to client" ? 

Do you mean the NUS service ? UART over the UART wire or UART over BLE ? 
Have you managed to test the SDK UART coexistence example ? On the phone you need to type either 1 or 2 or 3 or 4 and send that to the nRF52 (the client node) it will turn the light of the server node on/off. 

[shubham gupta]

Hi Hung Bui...

sorry if i made u confuse...

actually i m quite new to nrf...

my question is --- In nrf mesh I Used the Example of light swith example. Here 1 nrf Kit i used as a client(switch) AND 2 nrf kits i used to as a Server(light). If i press the buttton on client(switch) the led will blink on servers(lights) which is perfect.

 What do you mean by "use UART instead to client" ?

Answer---  Here i mean to say that instead of pressing the button on nrf kit which is client... can't we give the command through the KEYBOARD. by using UART.

And i didn't try the NUS service yet.

[shubham gupta]

Hi.....

i m stuck between follow the steps which are present in the nordic semiconductor infocenter>SDK UART COEXISTING EXAMPLE>

in 4th step i am unable to understand how to 

• Replace the light switch client with examples/ble_peripheral/ble_app_proximity_coexist/pca10040/s132/ses/Output/Release/Exe/ble_app_proximity_pca10040_s132.hex.

is it means that replace  light switch client's hex.file with Exe/ble_app_proximity_pca10040_s132.hex. file?

And I want to use nrf mesh mobile app to provisioning swith and light (gateway and node)

what i all need to do that is--

client (gateway)----->(Through UART)-----> send data to Server(node).

for doing that should i have to combine any  two example codes...?

plese suggest with examples.

thank you.

[Hung Bui]

Hi, 

The sentence means that you follow the instruction the same as in the light switch client instruction. But instead of flashing the light switch client, you flash the ble_app_uart_pca10040_s132.hex (basically you flash the application that you just built). It's a bug in the documentation that it mentioned about proximity it should be the coexist UART app. 

So basically you just compile and flash the coexist UART app. And you provision it using a provisioner (not the phone) and then after that you can control the server the same way as you control the server using the light switch client. 

If you want to provision the coexist UART application with a phone you need to add PB-GATT to it. I have made an example for that here.

[shubham gupta]

HI,

Thanks for your friendly support....

i downloaded your code which you give to me "ble_app_uart_coexist_GATT"

i pasted it on "C:\nRF5_SDK_17.0.2\nRF5_SDK_17.0.2_d674dde\examples\ble_peripheral " on that path..

first it show "log_beckend.rtt error" but after included the libarary it sloved...

but now it show

can you help me to sort it out.?

thanks in advace.

[Hung Bui]

Hi, 
The example is from SDK v4.0 and to be used with SDK v16 so there is some slightly changed needed. I would suggest to have a look and check for the change that I made (you can use diff or use a compare tool in Notepad++ for example) and apply the same change to SDK v17 and the example in SDK v5.0.

All in all, I would suggest to get familiar with the co-exist example without any modification first before you move to anything else. 

[shubham gupta]

Hi,

As per your suggestion i go through the co-exist example only. its working fine.

thank you so much friend.

But,

could you do me a favour...?

could you please send me the code "ble_app_uart_coexist_GATT".

which support the nrf SDk 17.0.2 with nrf MESH 5.0

besacuse i am unable to do changes in your code which you send me last time.

if u do it for me i'll be very thankful to you..

thanks.

[Hung Bui]

Hi, 
Please find the application for SDK v5.0 
Please make sure you have defined the SDK_ROOT and MESH_ROOT in SES correctly, pointed to the right SDK. 
What I edit is marked with "//GATT_EDIT********************"
7536.ble_app_uart_coexist_GATT_SDK5.0.zip

[shubham gupta]

hi,

i got your code...  "ble_app_uart_coexist_GATT".

its working with nrf sdk v17.0 and mesh v5.0

its build without any issue... thank you so much..

but,

by this also i am unable to provision with mobile app "Nrf Mesh"

while scanning in app it is showing only the server kit name with ( nrf5x light) BUT not showing the "Nordic Uart" Do you know why...?

AND

i also go through the ble_app_uart_coexist example also...

i used a another nrf kit to do provision (i do not use mpbile here)

but when i open tera term to give input it is not working...

i checked the correct COM port and baudrate also.. but it is not taking any input through keyboard.. and showing nothing..

please help to solve it.

please suggest.. is it a better idea if i use j-link RTT viewer instead of tera term (Uart)

what is better thing between these two.

thanks.

[Hung Bui]

Please add

 #define MESH_FEATURE_PB_GATT_ENABLED (1)

#define MESH_FEATURE_GATT_PROXY_ENABLED (1)

into nrf_mesh_config_app.h that was missing in my code. 

Also please do a chip erase before testing to avoid the chip already being provisioned before you test.

If you want to provision from a COM Port you need to follow this guide.