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).
Read the rest of entry »
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.
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”.
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.
At Build 2015 in San Francisco this week, there has been a large range of announcements wrt Windows 10. The topic of interest here is "Windows 10 IoT Core Insider Preview" as a public release of this for this for the Raspberry Pi 2 was much anticipated. That is now available. The IoT sessions indicate that it is now available not only for that but for a number other contexts
A detailed description of the CEJSON JSON Parser.
Version 1 AzMS Tables use an auto-incremented integer field as the primary key which is more compact than the GUID string used in version 2 AzMS tables.. The Azure Portal generates Version 2 tables which can be inefficient for resource limited embedded devices. This blog covers how to generate version 1 AzMS tables.
C:\JSONParser.Compact2013>JSONParser POST Temperature 78
In the previous blog in this series, using Flash for non-volatile program data was covered. One aspect of this was the F( ) macro that enables Serial.print/println strings to be accessed from Flash where the program is stored. That is, they do not consume RAM space allowing for more volatile programming space. This blog compares using and not using the F( ) macro. In the Telemetry sketch this allows for nearly double the number of name-value pairs