As part of a series of articles on a set of projects targeted at using a Windows Surface device as the presentation layer for a RPI or Arduino device, this article views the apps as state machines and documents the app states coupling through message passing between them.
Read the rest of entry »
In the previous articles in this series, a UWP app was developed as an array of XAML buttons that acts as the UI for an app running on a remote embedded or IoT device. Once connected the remote app sends a configuration for the UI as a Json string. Connectivity between the UWP and remote apps over Bluetooth and USB Serial has been covered. In this article connectivity over network sockets is covered. The article includes 101 on TCPIP Network Sockets for UWP and Arduino.
This article reworks the previous few articles that use BT Serial and the connectivity so that USB virtual serial is used for communication. It covers in detail USB Serial connectivity between a UWP app and an Arduino devices as well as with a Windows 10 IoT-Core device (eg RPI).
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.)
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
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”
I've blogged about an issue that has arisen with respect to the fact that the phone has not RTM yet and is stuck on build 10160 whereas the desktop Win 10 has RTMed and is build 10240; as is the Windows SDK. This problem is now solved.
Visual Studio 2015 has RTMed also. Win 10 RTM with VS 2015 RTM can't deploy to the current build of the phone (10160).
A Windows 10 UWP 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. . This app is functionally the same as Windows 8.1 version in the previous blog in this series. This blog works through the same material (ie repeats much of it) as the previous blog but from the Universal Windows Platform (UWP) context rather Windows 8.1 Universal App context. The target for the app is Win 10 desktop, Win 10 phone and Raspberry PI2 (running Win 10 IoT). The latter target is a "work-in-progress though".This blog can be read without reference to the previous blog.