1
Bluetooth Framework / Re: Necessity to Pair LE Devices in current Win10
« Last post by Mike Petrichenko on January 30, 2020, 01:13:34 PM »You are welcome!
Recent Posts
2
Bluetooth Framework / Re: Necessity to Pair LE Devices in current Win10
« Last post by sommerat on January 30, 2020, 12:54:56 PM »Hi Mike,
You were right, there were several Events missing that are necessary for this type of BLE communication (Terminal IO protocol):
Thanks for the direction where to search for the solution!
You were right, there were several Events missing that are necessary for this type of BLE communication (Terminal IO protocol):
Code: [Select]
OnProtectionLevelRequest
Code: [Select]
OnIoCapabilityRequest
with out values set toCode: [Select]
Mitm = wclBluetoothMitmProtection.mitmProtectionRequiredBonding;
IoCapability = wclBluetoothIoCapability.iocapDisplayYesNo;
and finally theCode: [Select]
OnConfirm
Thanks for the direction where to search for the solution!
3
Bluetooth Framework / Re: Necessity to Pair LE Devices in current Win10
« Last post by Mike Petrichenko on January 29, 2020, 08:48:51 PM »I think it is because you forget to handle wclBluetoothManagerConfirm event of wclBluetoothRadio object. It is used for "Just works" pairing.
4
Bluetooth Framework / Re: Necessity to Pair LE Devices in current Win10
« Last post by sommerat on January 29, 2020, 06:13:42 PM »It seems to be working with the BluetoothManager demo.
I will compare the pairing process in the demo to the one in our application to find the differences.
Thanks for the help so far. I will post the solution.
I will compare the pairing process in the demo to the one in our application to find the differences.
Thanks for the help so far. I will post the solution.
5
Bluetooth Framework / Re: Necessity to Pair LE Devices in current Win10
« Last post by Mike Petrichenko on January 29, 2020, 02:26:20 PM »Ok, that is good.
Now please, try BluetoothManager demo application. Unpair your device first. In the demo app in discovering type select BLE. Then discover your device, select it and click Pair. What is the result?
Now please, try BluetoothManager demo application. Unpair your device first. In the demo app in discovering type select BLE. Then discover your device, select it and click Pair. What is the result?
6
Bluetooth Framework / Re: Necessity to Pair LE Devices in current Win10
« Last post by sommerat on January 29, 2020, 01:51:01 PM »it is BLE
7
Bluetooth Framework / Re: Necessity to Pair LE Devices in current Win10
« Last post by Mike Petrichenko on January 29, 2020, 01:09:24 PM »Also please check how your device detected during discovering in BluetoothManager: is it BLE, Mixed or Classic?
8
Bluetooth Framework / Re: Necessity to Pair LE Devices in current Win10
« Last post by Mike Petrichenko on January 29, 2020, 12:39:00 PM »Try BluetoothManager demo application. Unpair your device first. In the demo app in discovering type select BLE. Then discover your device, select it and click Pair. What is the result?
9
Bluetooth Framework / Re: Necessity to Pair LE Devices in current Win10
« Last post by sommerat on January 29, 2020, 09:56:29 AM »Hi again,
With unpaired/unbonded BLE device:
Beacons Demo shows some frames from our BLE device in Monitoring; the Name, the Service UUID, a short uuid, ....
Re-Testing Discovery today it found the BLE device too - must have been bad karma the other day.
Still unpaired/unbonded:
Connect works, gettings services and getting characteristics from the specific service works.
Subscribe to an IsIndicatable characteristic returns no error.
But the WriteClientConfiguration returns a WCL_E_BLUETOOTH_LE_INSUFFICIENT_AUTHENTICATION
Writing to a IsWritable characteristic also returns 0x00051004
When the device is paired in Windows - there is no PIN no Passphrase no nothing - the above code works like a charm.
For your other question regarding pairing:
I am using the same procedure as for classic devices except for one difference.
Registering all Events in the Manager and call RemotePair. Connect the wclRfCommClient and wait for the Events to authenticate the device and check the Error in OnAuthenticationCompleted.
For BLE I need to wait prior to Connect the wclGattClient because the Connect aborts the process; but the Error in OnAuthenticationCompleted is mostly WCL_E_BLUETOOTH_LE_AUTH_REJECTED_BY_HANDLER
With unpaired/unbonded BLE device:
Beacons Demo shows some frames from our BLE device in Monitoring; the Name, the Service UUID, a short uuid, ....
Re-Testing Discovery today it found the BLE device too - must have been bad karma the other day.
Still unpaired/unbonded:
Connect works, gettings services and getting characteristics from the specific service works.
Subscribe to an IsIndicatable characteristic returns no error.
But the WriteClientConfiguration returns a WCL_E_BLUETOOTH_LE_INSUFFICIENT_AUTHENTICATION
Writing to a IsWritable characteristic also returns 0x00051004
Code: [Select]
if (m_creditTx.IsIndicatable)
{
success = m_client.Subscribe(m_creditTx);
success = m_client.WriteClientConfiguration(m_creditTx, true, wclGattOperationFlag.goNone, wclGattProtectionLevel.plNone);
if (success != wclErrors.WCL_E_SUCCESS)
{
throw new Exception();
}
}When the device is paired in Windows - there is no PIN no Passphrase no nothing - the above code works like a charm.
For your other question regarding pairing:
I am using the same procedure as for classic devices except for one difference.
Registering all Events in the Manager and call RemotePair. Connect the wclRfCommClient and wait for the Events to authenticate the device and check the Error in OnAuthenticationCompleted.
For BLE I need to wait prior to Connect the wclGattClient because the Connect aborts the process; but the Error in OnAuthenticationCompleted is mostly WCL_E_BLUETOOTH_LE_AUTH_REJECTED_BY_HANDLER
10
Bluetooth Framework / Re: Necessity to Pair LE Devices in current Win10
« Last post by Mike Petrichenko on January 27, 2020, 10:13:00 PM »By the way how do you test pairing?