Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

How to determine BLE connection quality while connected

We are developing a medical device that connects via BLE and sends non critical data to phone/tablet/computer which draws a moving graph.

We'd like a way to determine how much any interference is affecting our data transfer before we start losing significant data. So just looking at missing packets (Frame Error Rate) is kinda too late. We really want to know something like, how many retries did it require to get the packet across so we can show signal bars like a cellphone. Maybe this would be for 3 and 2 bars, and 1 and 0 bars would be missing packets?

currently we are looking at packet delay and frame error rate, i.e. how many packets were not received.

RSSI doesn't seem to be a very good indicator as you can have a good RSSI but still have packet loss due to interference.

Packet Delay : The peripheral sends a packet every 100ms when BLE is connected

Packet delay is how long after the expected 100ms did the packet arrive

Frame Error Rate: For Frame error rate we are looking for lost packets

we are using the wire shark sniffer during algorithm development to look for lost packets ( log to a file, parse the file )

I'm concerned, is Wireshark is reliable enough to catch every packet? I'd rather the software did this...

So the actual question is: what is the best way to determine if interference is causing packet transmission issues?

Lastly, I always thought BLE transmissions were guaranteed, but it looks like it can drop packets without dropping the connection?

Thanks!

Keith Vasilakes

Parents Reply Children
No Data
Related