This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

BLE Mesh Project with BLE_NUS

Hello,

I'm using the sample project from this post.

Following the steps and using nRF52DK, one for server and one for client. I've modified the server count from 3 to 1 in client project .

#define SERVER_COUNT (<<1>>)

The provisioning is success, the server side will get the response and show

RX: [aop: 0x00C3]

on the J-Link RTT Viewer when I press button 3,but there is no response in server side when I press button0.

I don't have any idea how to solve this problem, could you give me some hints? Thanks.

P.S. The following image is the log of client side. image description

[Updated on 2017/10/18]

Based on Hung Bui's comment, I tried to get the unicast address by dsm_local_unicast_addresses_get() function. I get the same unicast address "1" when I press button 0 or 3.

image description

Still can NOT solve the problem...

Parents
  • Hi Sara,

    This is showing the server subscribed successfully to the group address (0xCAFE) but for some reason the unicast address was not matched. You need to check which unicast address the server has after provisioning. You can use dsm_local_unicast_addresses_get() to get the unicast address.

    Then you compare it to the broadcast address of the client when you press button 0.

    If you have a look at the mesh_msg_handle() function in access.c you can print out more information about the packet including source address, destination address.

Reply
  • Hi Sara,

    This is showing the server subscribed successfully to the group address (0xCAFE) but for some reason the unicast address was not matched. You need to check which unicast address the server has after provisioning. You can use dsm_local_unicast_addresses_get() to get the unicast address.

    Then you compare it to the broadcast address of the client when you press button 0.

    If you have a look at the mesh_msg_handle() function in access.c you can print out more information about the packet including source address, destination address.

Children
No Data
Related