• State Not Answered
  • Replies 5 replies
  • Subscribers 62 subscribers
  • Views 2947 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 102242
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SD120 central device RSSI problem

Tiit Rätsep

Hi,

We are developing a pair of devices - one central and one peripheral at the moment and we would like to be able to read the value of RSSI on both of them on demand. The way I want to go ahead with that right now is enable the RSSI events for a while, filter the results and then turn it off again (we will later have upto 8 devices on the central and there would be too many events with RSSI enabled). The problem is that turning on RSSI events causes the Softdevice to crash ("[APPL]: ASSERT: src\host_hci.c, 131, error 0xdeadbeef").

Right now we can read the RSSI from ADV packets but we stop these when we make a connection. We can, maybe (not tried yet), keep sending ADV packets even in connected state but that would complicate our scanning logic and we would rather not do that.

Is RSSI even supported in SD120? On the peripheral we are using SD110. We will try the newest version of SD120 but don't have high hopes for that. Can you advise us on what we could be doing wrong.

Parents
  • 0

    Hi,

    Thanks for the answer. So since that feature is unsupported (at the moment hopefully) we worked around it by reading the RSSI on the peripheral and notifying this to the central. We would very much like to get the RSSI on both devices but we can live with this solution for the moment.

    When connected the central should be able to get the RSSI from the packets sustaining the connection or have I misunderstood something. The value of RSSI should (at hardware level) come from some register not the packet itself, right? If so can we expect central RSSI reading capability in future releases of SD120?

Reply
  • 0

    Hi,

    Thanks for the answer. So since that feature is unsupported (at the moment hopefully) we worked around it by reading the RSSI on the peripheral and notifying this to the central. We would very much like to get the RSSI on both devices but we can live with this solution for the moment.

    When connected the central should be able to get the RSSI from the packets sustaining the connection or have I misunderstood something. The value of RSSI should (at hardware level) come from some register not the packet itself, right? If so can we expect central RSSI reading capability in future releases of SD120?

Children
No Data
Related