Finding RSSI value after connection continously

RE: Finding RSSI value after connection continously

Simonr — Thu, 04 Apr 2019 06:33:05 GMT

Hi Sumanth

Yes, increasing the interval of an operation/adding operations will increase the current consumption somewhat (not by a huge amount). However to reduce the current consumption on your nRF chip, this post describes just about every way to do so. If possible I would look at enabling the DCDC converter, as that usually helps alot in current consumption reduction.

Best regards,

Simon

RE: Finding RSSI value after connection continously

P Sumanth — Wed, 03 Apr 2019 12:34:48 GMT

Thanks Simonr i am able to get RSSI for every updated value, Now I have to read up to 5 RSSI values on interval basis, i,e for every 300 ms i have to read RSSI upto 5 values and get an average, This should be repeated continuously, Do it consume more power, if yes how can i reduce it?

Regards

sumanth

RE: Finding RSSI value after connection continously

Simonr — Wed, 03 Apr 2019 12:25:01 GMT

Hi Sumanth

You have to call sd_ble_gap_rssi_start() initially so that the SoftDevice will start to report the RSSI. Depending on the parameters, you will get an event (BLE_GAP_EVT_RSSI_CHANGED) every time the RSSI change. Then you should be able to use the sd_ble_gap_rssi_get() event when the RSSI_CHANGED event occurs. Something similar to this should do.

// On the connection event

uint32_t err_code;  
m_conn_handle  = p_ble_evt->evt.gap_evt.conn_handle;  
err_code = sd_ble_gap_rssi_start(m_conn_handle, 10, 0);   
APP_ERROR_CHECK(err_code); 


//On the RSSI_CHANGED event

uint32_t err_code;  
int8_t rssi;  
err_code = sd_ble_gap_rssi_get(m_conn_handle, &rssi);  
APP_ERROR_CHECK(err_code);

Then you should be able to log the RSSI values.

Best regards,

Simon