AnsweredAssumed Answered


Question asked by Michael Brudevold on Feb 27, 2017
Latest reply on Feb 27, 2017 by josem.reyes.chaidez

I am making a call to Gap_ReadRssi shortly after the connection is established and I am getting RSSI readings of 0.  I expected to see a value of 127 (gGapRssiNotAvailable_d) or something correct (likely -50 or less).  Is this a known issue in version 1.0.2 of the connectivity software (running on a MKW31Z)?


Also, how soon after a connection can I expect RSSI readings to become valid?  And are they updated every connection event?  Any chance there can be an API to automatically produce gConnEvtRssiRead_c events when RSSI is updated?