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?
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?
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?
Yes, the mesh stack uses the timeslot API. The timeslot API uses a timer and this requires the HF clock to be running at all times. This is the reason for the relatively high current consumption.
Thank you.
which does TimeSlot use HFXO or HFINT for HFCLK?
If HFXO is use, can stop in NRF_MESH's TimeSlot-running?
And
Is NRFMESH still high current consumption in the future?
What HFCLK source to use is configurable, but not as straightforward as simply choosing one or the other. You use one of these enums to choose the configuration. The default configuration used in the mesh SDK is NRF_RADIO_HFCLK_CFG_XTAL_GUARANTEED.
nRF Mesh is a work in progress and not fully power optimized yet. We are working on adding features that will improve the current consumption.
Thank you.
I hope them.
Thank you.
I hope them.