As I discussed in a previous blog article, the Raspberry PI3 Bluetooth driver for Windows 10-IoT-Core becomes errant and misses updates when the update rate is high. This is a known issue with the RPI. This problem does not exist other Windows 10 systems including the Dragonboard running IOT-Core. This article again discusses the problem and presents a workaround that does work. Includes how to disable/enable a driver using devcon.
Read the rest of entry »
Solved: How to use one line per item in a UWP XAML ListView
Several months ago I published a UWP app on GitHub that interacted with a Texas Instruments CC2650STK SensorTag using the Bluetooth Low Energy (BLE) API. It was based upon a previous Microsoft sample UWP app for interacting with an earlier TI SensorTag. Whilst the new app ran well on the Windows 10 Desktop and Windows 10 Phone, it was found to be erratic on the Raspberry Pi3 running Windows 10 IoT-Core.. working well some times but errant other times. Windows 10 Creators Edition added a key feature to BLE, namely the ability to connect to a device that is advertising without being paired. This blog examines the erratic nature of the RPi3 with BLE and investigates whether this is solved with the Creators Edition. In so do a comparison is made between between BLE Paired and Unpaired connectivity in the UWP app development context..
This Sketch scans a phone keypad using the Keypad library and detects key pressed, released and held events. The events generate a string that is sent serially denoting the event and key.
A library on Codeplex. Been a long time coming: Arduino sketches and UWP class libraries and apps, focused upon scanning a phone keypad as input (Bluetooth serial) to a UWP app running on a phone, desktop or IoT-Core device.
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.)
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.
Whilst the Raspberry Pi 2 has extensibility through GPIO, I2C, SPI and Single wire, the main interface for adding off-the-shelf peripherals is via USB. Unlike the desktop, there is though only a limited set of USB peripherals that can be used on the RPI2 running Windows 10 IoT in the first release. This series of articles looks at what is available and what the overarching issues are. The first Article is “Connected Devices”
A Windows 8.1 Universal app can be built upon the Remote-Wiring library such that the app can interact with an Arduino device running Firmata. An app similar to the Windows Remote Arduino “Blinky” example, but with feature additions, is developed. It performs GPIO (output AND input) as well as some analog IO. The app runs on a Win 8.1 desktop, phone and RT Surface. The UI has some extra XAML “bells and whistles”.