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

power up mesh stack after execution of "mesh_stack_power_down()"

Hello

My setup looks like this.
I am using nrf5_SDK_for_Mesh_v5.0.0 with nRF5_SDK_17.0.2.
I have extended the sensor model example (in  nrf5_SDK_for_Mesh_v5.0.0) and call the function "mesh_stack_power_down()" during operation. After calling this function my system also consumes only 5-6uA which is great. However, I can't manage to power up the mesh stack afterwards so there are no mesh asserts. I tried the function "mesh_stack_start()", but that doesn't really work either. Can you tell me how exactly I have to power up the mesh stack after calling the function "mesh_stack_power_down()" and what exactly I have to consider when powering down and powering up the mesh stack.

Thanks already.

  • Hi,

    The stack is not designed to be restarted without rebooting the device after calling "mesh_stack_power_down()".

  • Hello,

    How else can i reduce the power consumption to the maximum without using the low power feature?
    With "nrf_mesh_disable()" I can reduce the power consumption to about 30uA, but I want to go down to 5-6uA. My module makes measurements during 5-6s and after that it goes into sleep mode where it stays for about 24h. So it is important to have the lowest possible power consumption in sleep. In addition, the mesh should be able to be restarted and switched on again afterwards. Can you help me there?

    Can you tell me how I can reduce the power consumption to 5-6uA and can use the mesh stack again without any problems.

    Thanks already.

  • Hi,

    Can you try to disable scanner by calling scanner_disable() together with nrf_mesh_disable()? Then enable scanner with scanner_enable() and call nrf_mesh_enable() when device wakes up. Disabling scanner may significantly reduce power consumption.

  • Hi,

    I been talking to one of our developers and it seems that Low Power feature is the correct solution for this case. Then, things like IV Update would be correctly handled by the node. Otherwise, the node may get lost in the network. Poll Timeout can be properly tuned so that the node sleeps most of the time.

  • But if I use the low power node feature, then my device has to make a friendship with another node, right? This makes the whole network more complicated and my concept is rejected?
    Or have I misunderstood something?

    Can I use the low power node feature without establishing a friendship with another device? As I said, I just want to achieve the lowest possible power consumption without having to make additional changes like configuring other devices as "friend" for my low power node.
     

    Greetings

Related