question

AP-2411 avatar image
0 Votes"
AP-2411 asked ·

Invalid values on RawSignalStrengthInDBm on BLE advertisment

Hi!

We're developing a UWP app, which functions as our BLE central, and 'speaks' to many BLE peripheral units. When a connection is formed, the RSSI value for that central-peripheral connection is logged and reported.
We're seeing two flavors of the same problem, The problem is that some portion of the RSSI values we're reading make no sense.
first flavor- RSSI values we get are positive. Examples: 79, 80 etc.
second flavor- RSSI values we get are unreasonably low. Example: -127. This is well below the link budget and doesn't seem like a 'real' RSSI value.

These values are received from Windows.Devices.Bluetooth.Advertisement -> BluetoothLEAdvertisementReceivedEventArgs when receiving events from BluetoothLEAdvertisementWatcher. So they seem to be originating straight from the driver. No manipulation on our side.

Both of these problems are not constant. We'll get reasonable values for a while (-40, -48 etc) and then an anomaly will be recorded, and back to 'normal' values.
We suspect the fault lies with the windows driver, as when we try to switch dongles (different manufacturers with different chipsets), we still see the same strange values pop up every once in a while.
We use Windows.Devices.Bluetooth under UWP (universal windows platform) on Intel NUCs.
Updating windows to the latest version, and updating the BL drivers etc did not solve the problem.

Has anyone experienced these kind of issues before?
Thanks!

windows-uwp
· 10
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

When you try to receive the RSSI values again, would you follow this guidance to provide your Bluetooth log for us to check? In addition, here is an official sample about BLE advertisement, if you test it, will the same issue occur? For more details about RawSignalStrengthInDBm, you can refer to this document.

0 Votes 0 ·

Hi FayWang!

I'm attaching alink to GDrive, since I can not upload the log files as they are too large.

https://drive.google.com/file/d/1U_cjTfx62gXsuLunPV3jPF50v1PlDFCH/view?usp=sharing

You'll find two files- one with a few 'positive value' RSSI reads. The second with a -127 RSSI read which should be towards the end of the run.

Please let me know if you need anything else from me.

Thanks!

0 Votes 0 ·

Hi FayWang!

Just to let you know, We've updated our bios, BlueTooth and other drivers to the latest release from Intel for all our NUCs (I'm referring to the drivers released on August 2020).
We see some improvement in the frequency of 'bad' RSSI values following these updates, but the issue is not completely resolved. If before we saw these values once every 20 readouts, we now see them about one every 50 read outs.

I'm hoping you can point us in the right direction using the log files I've linked.

Thanks!

0 Votes 0 ·

Hi!

Here is a link to the files relevant to 'Driver issues' as described in the link you've sent,
https://drive.google.com/file/d/1AgL8S3PJXTlk0xHcropQNRe7JpI_YF-0/view?usp=sharing
My apologies, I didn't spot that part before.
I've been able to catch the '-127' value of the RSSI read, you can find it in the files I've added. The positive RSSI value still eludes me

Please let me know if I missed anything else.

0 Votes 0 ·

Caught the 'Positive RSSI' issue as well.
See files here
https://drive.google.com/file/d/13HATuDgXWKru6KoQQePJccZAAEwbYgTR/view?usp=sharing

0 Votes 0 ·

I've been able to get an RSSI value of -127 using the official sample watcher. I've not observed positive values thus far.
20593-image.png


0 Votes 0 ·
image.png (47.5 KiB)
Show more comments

0 Answers