Hi Dialog Team
In DSPS Device Project i made the below changes to measure Extended Sleep Current
In User_ble_bull() , i modified the function call to
user_send_ble_data("DIALOG", 8);
void user_on_disconnect( struct gapc_disconnect_ind const *param )
{
//default_app_on_disconnect(param);
app_easy_gap_advertise_stop();
arch_ble_ext_wakeup_on();
wrbl_env2.sensor_read_time_1 = app_easy_timer( 30000, wake_up_sm ); // 1000 -> 10s
}
void wake_up_sm(void)
{
arch_ble_ext_wakeup_off();
app_easy_gap_undirected_advertise_start();
}
so once DSPS device connected to DSPS Android App(master) , it will receive data ("DIALOG") , once DSPS Android App disconnects DSPS device , device will go to extended sleep , i tested this setup[in Murata dev board , still i am getting 150ua in sleep - via UART booter smart snippets.
what are the chages has to be donein DSPS device project , so i wiil get below 5uamps in sleep...
Thank you.
Hi prasanth,
There are no specific changes that should be done in the fw in order to reach a small power consumption, if you set the device is low power mode and the device is sleeping, the sleeping current should be near the value that you are indicating. I dont have a Murata dev kit to measure the power consumption on that board, but have you measured the power consumption before you connect and check if you see that value before you connect or it is something that occurs after the connection ?
Thanks MT_dialog
Can you explain the function:
wrbl_env2.sensor_read_time_1
please
Hi gert186,
I am sorry, i dont get the question, there is no such variable in the IoT reference design (which i suppose that you are refering to). If you are referencing the variable used on the previous post, its just a variable that stores the timer handle that the app_easy_timer() function returns in order to manipulate the timer.
Thanks MT_dialog