Complete

CIQQA-789

All data would have to be sent through the ADV IND packets, and read from those same packets.

Bluetooth Low Energy - Scan Response issue

Hi everyone,

I'm currently developing an app for Garmin Edge 830 using Bluetooth to read some data from a e-Bike sensor (developed by me and my Team and used regularly with other displays and every smartphone).

I started my project from Nordic Thingy 52 demo, but I have found an issue that makes impossible to find some BLE devices. 

My sensor (which acts as an Advertising Peripheral in BLE communication) stacks some Beacon Data in the ADV IND packet, while Services Uuid, device name, appearance etc... are all in the Scan Response data packet. 

I noticed that in onScanResults callback in BLE Delegate, I am able to see only the data contained in the ADV IND Packet, but not the data contained in the Scan Resp Packet. The result is that I can't read the data contained in this packet (in my case Device Name and Service Uuids), so i am not able to connect to my device.

The only workaround I found for this issue is to change my e-Bike sensor BLE firmware to send all data in the ADV IND Packet instead of using the Scan Response Data, but this would make me change a communication infrastructure that has been used for years. 

Is this issue a bug? Or is it an expected behaviour (that is Garmin BLE stack ignores the data contained in the Scan Response Packet)?

Thank you very much and greetings,

Giovanni.

Former Member
Former Member
Parents
  • It is possible to use the Manufacturer Specific data record, the Garmin sees it. I have a device which delivers it's MAC address this way. But the whole ADV IND scan record seems to be truncated to 20 bytes. So it's important in which order a device sends it's data in the ADV IND record, because only the first 20 bytes can be seen and, thus, used.

Comment
  • It is possible to use the Manufacturer Specific data record, the Garmin sees it. I have a device which delivers it's MAC address this way. But the whole ADV IND scan record seems to be truncated to 20 bytes. So it's important in which order a device sends it's data in the ADV IND record, because only the first 20 bytes can be seen and, thus, used.

Children
No Data