2 years, 8 months ago.

How to develop x86 desktop BLE app in Windows 10??


I have NXP MBED boards (around three of them), then various TI BT chips. Then I have Intel x86 embedded PC, then I have laptop Acer Aspire R13 with BLE (Intel chipset).

How the hell can I write a desktop application with BLE API? I cannot find anything on the internet. Everyone is doing just ios,android apps. I just read Windows 10 has some new universal driver bluetooth api. Then Google is spoiled with Windows 10 IoT version, so it's hard to find anything about desktop Windows 10 and BLE support.

I don't want to connect 4 various BLE dongles in USB if I have BLE in my laptop already. I'm gonna use Wifi Bee or ESP8266 instead. This is real hell!

I don't care about technology or programming language. I'm looking for ANY solution that would be able to scan nRF services and listen to notifications like my Android phone with nRF master control panel. And I guess my LG G4 is not using NXP/nRF. So how is that possible that Android app has implemented working BLE stack for nRF, whereas PC version requires some freaking dongle? If this is the only way, BLE is dead then.

Comment on this question

3 Answers

2 years, 8 months ago.

Hi Lukas , You can add from nuget "feet32" dll this can help you working with your Bluetooth , writing code is very similer using Net.Sockets. Another way you can use System.IO.Ports and in your bluetooth driver setting in the COM tab add income / outgoing

2 years, 8 months ago.

look at maybe it is useful.

2 years, 8 months ago.

I just did a demo using Node and the noble module, source code can be found here : . This is a webapp, but it could easily be wrapped up / used as a base to create a desktop app.

I would also reccomend looking at Electron ( as it tends to have loads of really good plugins and be cross platform aswell.

This tends to work best on Linux / Mac but it is possible to do BLE on Windows. You will need to follow the install instructions for NodeJS and noble for windows.

Best of Luck!


To post an answer, please log in.