• State Verified Answer
  • Replies 11 replies
  • Subscribers 20 subscribers
  • Views 636 views
  • Users 0 members are here
Options
Related

Unexpected BLE connection problem

NVelev

I'm working on an app that uses data from a remote pressure sensor and I believe I got stuck because of a rather unexpected problem. My Garmin Edge 1030 device is not being able to discover the sensor during BLE scan.

As a background, I want to state that I've successfully used connections to several other BLE enabled external devices in other CIQ apps on the same Edge 1030 device. So it is not that I'm missing out how to do it in principle.

The problem now is that the list of results that are returned to the BleDelegate after initiating a BLE scan on the Edge 1030 device just don't contain the sensor I'm playing with. 
All sorts of other devices can be seen there, but never this one.
Without discovering it via the built-in scan I cannot connect to it because the "pairDevice()" function accepts as a parameter a ScanResult object and a ScanResult object cannot be instantiated manually. It has to be created by the BLE scan..
 
Can anyone come up with a suggestion about why the sensor is not "visible" for the BLE scan that the Edge 1030  performs, while in the same time it is readily visible when I do a scan on my Android phone? 
Thank you in advance!
Nikolay
  • 0 in reply to jim_m_58

    Of course your're right about that and it is clearly stated in the API documentation:

    getServices() as BluetoothLowEnergy.Iterator

    Retrieves an Iterator over the services provided by the device.

    This will only provide Services that have been registered using registerProfile()

    However the service has already been properly registered with its UUID and respective characteristics in the same way as I've done it for other applications, where executing getServices() on a search result did return non-empty results.

    Also, as I've mentioned, after I pair directly I can use this service and read the values, which wouldn't be possible unless the service has been registered before that..

    Apparently there is some form of incompatibility with this particular device.