Windows 10 IoT
This blog is a Tutorial on how to implement Win 10 IoT Universal Apps that make use of Raspberry PI 2 (RPI2) General Purpose Input Output (GPIO) pins. This covers:
The interrupt (event driven) version addresses the InvokeRequired pattern in the XAML context. (Controls can't be updated directly from another thread).
The complete solutions are available (in source) on Codeplex at:
"Windows 10 IoT Samples": https://IoTSampler.Codeplex.com
Read the rest of entry »
I was an early adopter of Win 10 IoT with Raspberry PI 2 (RPI2) as well as Windows Remote Arduino. Whilst I was able to use my Windows 8.1 phone to control an Arduino device as per the latter technology, I did have some problems with some fine detail with the RPI2 technology. I have now had a second stab at Win 10 IoT with RPI2 with success. This blog discusses these issues.
Various scenarios were presented for Windows 10 IoT at Build 2015. In all cases, the object is to have a Windows 10 device, whether desktop, mobile or embedded/IoT, talking to custom hardware and to the cloud. The “reference” design for hardware from a Makers’ perspective is Arduino. Let’s examine the scenarios.
Windows 10 IoT is the third (lower) layer of Windows 10. All three are built from the same codebase, part of Microsoft’s one Windows mantra. Whilst the desktop will have significantly more features than the IOT layer, the IoT layer will embedded features such as General Purpose IO (GPIO) which the desktop doesn’t. The Phone layer will support cellular networks for phone calls whereas the other two only support this for internet access. Apart from the common code, a binding feature of all three is Universal Apps.