• State Verified Answer
  • Replies 3 replies
  • Subscribers 74 subscribers
  • Views 949 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 213048
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

MESH BLE with custom HW proof of concept

JoseSecmotic

Hi everyone,

I'm trying to evaluate the BLE mesh SDK, using the example of the light_switch.

I have the SDK15 and the the SDK_mesh v2 and I am able to compile everything just fine. The provisioner also registers the client as expected.

The problem that I am facing is that both provisioner and client are DK boards, but the servers I have are also nrf52832, but custom hardware.

I'm trying to do a proof of concept in which the client, after pressing one button, turns on the client's LED (in the address 29 in my case).

What I have done is modifying the BSP_BUTTON_LED in the pca10400.h for the address of my interest, but this had no success.

Could you give me some guidance on how to achieve this? I think I am pretty close but I am getting lost

Another question that I am facing, is that the devices are mobile, so.. when should the provisioner provision the different servers or clients? I think that it will not be very useful if everytime that I get a disconnection on a device it has to be provisioned again.

Thanks in advance and best regards

Parents
  • 0

    Sorry, when I said:
    "I'm trying to do a proof of concept in which the client, after pressing one button, turns on the client's LED (in the address 29 in my case)."
    I meant that, after pressing one button, turns on the SERVER's LED, which is the custom hardware

  • +1 in reply to JoseSecmotic

    If you turn on persistent storage on all of the nodes, the nodes will still remain a part of the mesh network if the connection is lost or a power loss occurs. See this video for a good intro.

    What custom HW are you currently using? Is it a module? Also, which mesh sdk are you using? v2.0.1, v2.1.1?

    It should work to just use the led functionality like it is done in the button_event_handler() function in the light switch server for example. The hal_led_pin_set() function is called, which changes the value of the NRF_GPIO register. The LED_PIN_NUMBER DEFINE is set to BSP_LED_0, which is again defined as LED_1. LED_1 is defined as pin 17 (see pin assignment doc for more info). Also, these two cases could be useful: case 1, case 2.

Reply
  • +1 in reply to JoseSecmotic

    If you turn on persistent storage on all of the nodes, the nodes will still remain a part of the mesh network if the connection is lost or a power loss occurs. See this video for a good intro.

    What custom HW are you currently using? Is it a module? Also, which mesh sdk are you using? v2.0.1, v2.1.1?

    It should work to just use the led functionality like it is done in the button_event_handler() function in the light switch server for example. The hal_led_pin_set() function is called, which changes the value of the NRF_GPIO register. The LED_PIN_NUMBER DEFINE is set to BSP_LED_0, which is again defined as LED_1. LED_1 is defined as pin 17 (see pin assignment doc for more info). Also, these two cases could be useful: case 1, case 2.

Children
Related
Terms of service