Windows 10 IoT Core release

Pairing with the Bluetooth Smart module from Justin ( [url][/url] ) thru a standard cheap BT dongle on the PI2 with Win-IoT-10240 seems not to be a problem at all. No special action but inserting the dongle and initiating a pairing action on the local pi2 website that comes along with the standard install. Launch the WindowsIotWatcher, right click on the RPI2 that is found and select the web browser here option.

Doesn’t make much sense to connect the Cerbot (that’s where the BLE module is on) with RPI2 but it was just a test if it could pair. It picked up the USB Receiver for the keyboard/mouse for a Logitec K400r as well, working just fine.

That’s nice but I think you will need a BLE or dual mode dongle on the PI2 to communicate with Justins Bluetooth Smart module.

There are other drivers included in the image, but this is the Bluetooth module which the team told me they usually use for testing (despite its “Not suitable” clause in the title.)*Version*=1&*entries*=0

USB Serial info:

(I haven’t checked to see if the newer devices APIs also work with that, but that example should work for you, with some tweaks for Windows 10.)


BTW, if anyone here ever wants to write a driver for some unique hardware, at a level lower than the app layer, here’s some information.

Driver info

Universal Windows Drivers:

Windows Driver Samples (including GPIO)



I used a Conrad labeled BT/BLE dongle just to see if it works, since the refered one used the same CSR8510 chip.

Inserted the Conrad dongle into the PI2 and it is recognized as can be seen in the images of the previous posts. Next step is to make a POC UWP to see if it communicates as well.

My WP 10 phone with build 10152 on Lumia 630 doesn’t work anymore with the Justin BLE module, so I guess I have to rewrite the WP Cerbot Demo App into a UWP app and see if it really works on WP10 and Win-Iot, best would be without any software changes.

@ Pete Brown Thank you for the valueable hints.
@ Peter

Seems that you already have a dual mode or BLE Dongle.
What concerns Windows Phone 10 and bluetooth, perhaps it is better to wait for the final WP 10 version.
I’m just trying to write a NETMF/Gadgeteer driver for the SEEED BLE Dual Bee Module. It supports both, Bluetooth 2.x EDR and BLE.

Ok, can someone confirm my assumption?

I have a Sparkfun XBee USB Explorer, but when I plug it in, the default app does not update to show it as a connected device.

I assume if I can’t see it in the default app, all the sample code in the world will be in vain?

And when UART support is added to W10 IoT Core, will my XBee module become a viable option? If so I’ll likely continue working with my Cerberus / Spider II (To Be Bought) and port it later.

@ Squeebee - Yep, I can confirm that inserting the Sparkfun Xbee Explorer doesn’t animate the RPI2 to any action what so ever, at least not visible in either the RPI2 Startup screen nor the WebUI.

Inserting the same sparkfun xbee explorer into a windows 10 machine a FT232 UART USB Serial Device.

Well, at least the bees talk to each other … in the pic 3 XBees, Spider II and the RPI2/Scream for UART …

Guess, I have to indulge myself in patience …

@ .Peter. - Ooh, what are your bees going to do?

@ .Peter. - Did you see this?

1 Like

@ ianlee74 - Not yet, but give me a sec …


Hot stuff, thanks for the link.

Actually, I have some FTDI stuff and some breadboard XBee adapters maybe I’ll get it working that way until the Fez Cream U-Socket is ‘Online’ …

I reckon the U labeled socket on the cream is still unavailable ?

@ .Peter. - Wait, so this won’t work with the USB explorer?

@ Squeebee - What I did is I took the USB Explorer for XBee from Sparkfun and inserted into my RPI2 and no action visible not on the RPI2 GUI nor on the build in WebUI. when inserting into a Windows 10 laptop it showed as an USB UART Serial. And, as far as I know UART is not living yet on Win-Iot … the other USB dongles I inserted for keyboard and BT/BLE were recognized and visible on the RPI2 GUI.

See for further details in reply #21, #28 and #29 in this thread …

Sorry, what I meant is that the sample code from Hackster won’t work with it? I take it because it is written against FTDI instead of UART?

@ Squeebee - Didn’t find time to test this yet …

Regarding USB serial support, it would seem that the only CP2102-based devices are working right now. The project is using that type of USB serial device. If any other USB-to-UART chip works (FTDI, Prolific), nobody’s writing about it. Naturally, everything I have is either FTDI- or Prolific-based.

A workaround using a Teensy 3.1 is described here: It’s an interesting read, including some .NetMF code.

Perhaps another workaround is to write your own Universal Driver for, say, an Arduino - I’m not really clear on whether that’s doable.


I can confirm that, by using an FTDI FT232RL the RPI2 doesn’t react at all, but a CP2102-based UART popped up immediately as connected device …