Windows.Devices.Bluetooth ValueChanged event handler frequency

AMM 1

I'm able to test connection with a BLE device and I'm able to receive ValueChanged event to read value received after subscription to a notify service.
This is ok if the ValueChanged event it is fired about 4 times/seconds. But if this frequency increase to about 50 times/seconds, the event stop to fire after 7/8 times.
On the ValueChanged handler I print only a timestamp and I avoid to process data received.

There is a limit on BLE Windows Library?
With a vendor BLE usb key I'm able to receive all data on notify event.

Nico Zhu (Shanghai Wicresoft Co,.Ltd.) 12,861 Reputation points

2020-12-17T12:40:46.143+00:00

There is no such description about ValueChanged limit, but for low energy device, if we rise the trigger rate, it will consume more power. The high trigger rate is not good practice.
AMM 1 Reputation point

2020-12-17T14:39:24.683+00:00

You are right. But it is a desiderata of a client. The new product has a BLE module.
I would like to understand if it is possible to log some informations by Microsoft BLE api, only to understand why stop to fire callback. I'm sure that module continue to send, and at the side of the software I don't receive any crash, only stop to recive.
Nico Zhu (Shanghai Wicresoft Co,.Ltd.) 12,861 Reputation points

2020-12-22T06:44:13.373+00:00

I have discussed with team, may be there is sometime delay.
AMM 1 Reputation point

2020-12-28T07:52:27.83+00:00

But I don't have any delay, after 7/8 messages received in the callback I don't receive any other messages.
Nico Zhu (Shanghai Wicresoft Co,.Ltd.) 12,861 Reputation points

2020-12-31T06:51:07.977+00:00

I mean, we may update the comment delay.

Share via

Windows.Devices.Bluetooth ValueChanged event handler frequency