This is not question of DA14531, I hope to search for help to post here.
Maybe someone has faced this question before, maybe they have found the solution.
I made 10 clients configured with BLE module,and the server developed with Delphi.
My hardware configure:
1) Windows 10 on surface Model 1769;
2) Marvell AVASTAR Bluetooth Radio Adapter / Microsoft Bluetooth LE Enumerator in surface;
3) ARM Cortex M0+ + DA14531 module.
In server side, I use TBluetoothLE to connect with DA14531.
It can find all 10 clients, but can only connect with 8 of them, other 2 clients can't be connected,
The error raised: Access not allowed or no service available.
I don't know which layer limit it:
-Marvell AVASTAR Bluetooth Radio Adapter
-Microsoft Bluetooth LE Enumerator
-Delphi.TBluetoothLE
There is no property / method to change connection count for TBluetoothLE.
And I did not find info on changing connection count for Win10.
Any suggestion?
Update: Sometimes all 10 clients connected,and sometimes not all.
Getting harder.
Hi Xiao,
Thank you for posting your questions online.
DA14531 as a peripheral, with no conflicts with each other.
Could you check the MAC address, please set them differently. Otherwise, please contact HOST device helpdesk for help.
Or try another PC for testing
BR,
JH_Renesas
I have tried many ways, Basically I can say the host device makes the limitation.
Usually the first 8 clients can be connected soon, but it gets very long or impossible from 9th clients.
For those can't connected, they maybe will connect too if you restart the host application,that means there is no problem with BLE module.
Why the 9th and followed client can be connect sometimes?
I think maybe some client in those 8 disconnect occasionally,and that gave the chance for clients not connected yet.
I have found 1 question in Internat,but no reply. can we bypass this limitation?
Hi Xiao,Thank you for the reply.I checked on this on the Microsoft Website:How many BLE bonding/connection are supported by windows? - Microsoft Q&AIt seems that there is a limitation by Win10. This is not something related with our BLE devices. You should reach out directly to Microsoft for more information on this.Best Regards,OV_Renesas