Twitter: @CEDriverWiz
This blog presents a Universal Windows App that connects to an embedded Bluetooth device over the Bluetooth Serial Profile using a genetic Bluetooth USB dongle. This app will run on both a Windows 10 IoT-Core devices such as a Raspberry PI2 and a Windows 10 Desktop. The blog covers in detail the key issues with pairing including where a passkey is required with a RPI2 as well as a Bluetooth primer. Update 1.2: One bug fix (was writing send text twice) and and one code improvement (menu returns DeviceInformation so no need to requery for it.)
The serial pins on the Raspberry PI now have a driver in Windows 10 IoT Core on RPI2!
Publ2shed on Codeplex and GitHub. More details later:Win10 IoT Core Universal Windows App runs on a Raspberry PI 2 (& desktop) that reads some sensors (on an Arduino board) saves to and from Azure Mobile Service
In a previous blog I covered the use of the FTDI D2XX driver on a Windows 10 IoT Core Raspberry PI 2. An issue arose with respect to Startup Tasks. Microsoft have looked into the issue.
Code to display the menu and its interactions.
The commands that the LCD display receives from the Universal Windows app.
An Arduino LCD Display as a Menu.
There are currently 2 reserved GPIO pins on the RPI2 that ordinarily are SOC (I call native) serial. A future Tx and Rx but not at the moment. Serial is achieved on the RPI2 with Win 10 IoT Core via a USB-Serial device connected to a Host USB port on the RPI2. There are though limitations in that the widely used FTDI chipset is not supported by Microsoft, although we have a solution. An alternative is over Bluetooth but there is an issue there.
The following is the complete Debug output for running the Startup Task. Two versions are shown. One with Managed Code Debugging and one with Native Code Debugging. Mixed is not permitted. An exception is thrown when the FTManager is instantiated. This error is not trapped by a Managed Code (c#) try-catch