I reach out to you on behalf of our company, and our development team responsible for software applications that control a (so-called) active-implantable medical device for stimulation of the nervous system.
In our new software development project for an upcoming therapy, we are communicating an Android device, with a Windows-10 system over Bluetooth 4. Our medical system context requires us to use BLE (BT4) for all communication. In our setup, we define the Android device as being the Central, and the Windows system as being the Peripheral. This is conform the BLE standard, where the peripheral can only communicate with 1 Central.
Our developed software applications for Android and Windows successfully configure both sides and communication works.
In our test setup, we are using an Intel NUC as the Windows-10 system, which supports the Bluetooth Peripheral Role (reports TRUE). See attachment 1 from Windows device manager:
The Intel Wireless Bluetooth device hardware ID states: VID=8087 (Intel) PID=0A2B (no idea which variant and can't find this on Intel website)
For different customers, we want to deploy different Windows 10-based hardware (computers).
For example, we have also deployed the latest Surface Pro 4 (2017). However, our Windows application throws an exception that the Intel Wireless Bluetooth does not support Low Energy Peripheral Role and as such, we cannot set up communication over BLE between our devices. If we check the same Windows Device Manager dialog we see:
Bluetooth Radio supports Low Energy Peripheral Role
So, we understand the cause.
The hardware ID of this Surface Pro states VID=8087 (Intel) but PID=0A2A (still, no idea what device this is, but it's different than the one in the Nuc!)
We see the same with other systems, some HPs, Dells, even some Mini PCs. It's a roulette game whereby only after buying hardware, we discover if the system supports Peripheral or not.
Also because Intel seems to list all these different devices as "Intel Wireless Bluetooth" and "Bluetooth 4.0". Even though the capabilities vary.
Please note that the test and development team have ensured the comparison was done with equal windows version and equal releases of the Intel driver software (tested different 19 and 20 releases)
- Are we correct to conclude that the issue lies on the hardware variant (Bluetooth Radio)? Some 'variants' of the Intel Wireless Bluetooth support peripheral and some do not.
- Where can we find datasheet or technical specifications about what device 0A2B and 0A2A exactly are and what their differences are? A link is appreciated highly.
- Most importantly: how can we know before purchasing systems by volume, if a Windows-10 system features the Intel Bluetooth Chipset that supports peripheral role.
Your help is greatly appreciated to the progress of our work,