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

nrfmesh high current comsunption on IDLE

On nrf52832 and nRF5 Mesh1.0.0

When running idle state(not RX/TX), current comsumption is over 400uA.

And every 100ms, CPU is wake up.(small working.)

What happen?

Parents
  • I use FreeRTOS and BSP's(LED and button).

    So, RTC1/GPIO/GPIOTE.

    And

    Another problem, (every 100ms wakeup)
    
    I try nrf5_SDK_for_Mesh_v1.0.0_src/examples/beaconing.
    
    Modified,
    1. main.c: beacon interval change to 5000ms.
    2. nrf_mesh.c:nrf_mesh_enable() scanner_enable() is comment out.(not scan)
    
    When run the program on my nrf52832 board,
    Every 100ms, NRF_RADIO_CALLBACK_SIGNAL_TYPE_TIMER0 event occured.
    Timeslot request and ranges from 100 us to 100 ms.
    So that, nrf mesh is wakeup every 100ms, Whether scanner enable or disable.
    And increase a little current comsumption.
    Is this really?
Reply
  • I use FreeRTOS and BSP's(LED and button).

    So, RTC1/GPIO/GPIOTE.

    And

    Another problem, (every 100ms wakeup)
    
    I try nrf5_SDK_for_Mesh_v1.0.0_src/examples/beaconing.
    
    Modified,
    1. main.c: beacon interval change to 5000ms.
    2. nrf_mesh.c:nrf_mesh_enable() scanner_enable() is comment out.(not scan)
    
    When run the program on my nrf52832 board,
    Every 100ms, NRF_RADIO_CALLBACK_SIGNAL_TYPE_TIMER0 event occured.
    Timeslot request and ranges from 100 us to 100 ms.
    So that, nrf mesh is wakeup every 100ms, Whether scanner enable or disable.
    And increase a little current comsumption.
    Is this really?
Children
Related