nrfConnect Desktop 2.6.1 - Scanning does not live update advertised fields

[flodis]

Using the "Bluetooth Low Energy" application 2.2.0 extension

Scanning for BLE devices...

Problems in scanning:

1. Each advrtised propertiy is displayed and updated only first time of discovery.
2. Properties no longer advertised remains in the scan display.
3. Hence if a proeprty like "ManufacturerSpecificData" carries sensor data changes are not displayed

In nrfConnect for smartphones live update of advertised fields works fine but fields ino longer advertised remains in the scan result.

Suggested update

Update scanned fields when they change and keep all detected advertised fields, but grey them out if no longer advertised.

The original intention of advertising may not have been to have it flicker with all kinds of fields coming and going but it is a nice feature to be able to cycle through a larger set of data than what fits in one advertise block. A maximum of 31 bytes i think?

Also when debuging, it is better if all advertised fields are considered live and reflect even altering service UUID and device name.   

Or have I got it completely wrong how to broadcast lots of sensor data in fields like "ManufacturerSpecificData" without connecting?

[tesc]

Hi,

Thank you for the suggestions! Better aligning nRF Connect for Desktop with the versions for smartphones is always a good idea, and you also bring up valid points with regards to usability and usefulness.

Regarding how to broadcast a lot of data, yes you can use manufacturer specific data and spread the data over several advertisements. Please note however that there is no guarantee that a single advertisement will be received by a scanner. This means you need to retransmit the data several times, in order to increase the chance of the data being received. You also need to think about the format of each data packet, so that the receiver can put it correctly together and check its validity. Depending on the amount of data you may find that setting up a connection for transferring the data may be preferable.

Regards,
Terje