Application Development related
AppInstall can be used to install Appx packages on an IoT-Core device This blog covers an updated version of the toolkit for use on the latest Winsider IoT-Core builds.
Read the rest of entry »
In the previous two blogs I discussed using the Web Portal running on a Windows 10 Phone to remotely or in-phone install and Universal Windows Platform app. In this blog I discuss options for install UWP app packages on Windows 10 IoT devices. This is a work in progress as I have not had success some of these methodologies.
An issue has arisen with the last two Fast Track Windows 10 Mobile OS versions this week. You can’t deploy apps from Visual Studio to phones with those versions. Jump off Fast Track for now to Slow Track or “slower”. If you have one of these versions on your phone there isn’t a simple way to unwind. The problem as I see it is one of connectivity and sounds a bit like the issue we had last November with IoT-Core.
In this exercise we will use Android Studio to create a single screen Android UI app that will access the sensor class to get the number of established sensors on a device. Don’t worry if you don’t have any sensors, It’s just that its more interesting than doing yet another “Hello World”. My system didn’t have any sensors enabled.
Universal Windows(10) Apps settings is easy. Its simple to specify as part of the build, save them to storage, get them back and modify .. I mean dead easy!
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
In the quest to reduce RAM usage with a RAM challenged Arduino device, this blog covers using permanent storage (Flash and EEPROM).
In Part 9 of this series, it was shown how to create a Version 1 table such that the id field is an auto-incremented integer which saves storage space on a small device. Version 1 tables don't automatically save a creation and modification date. This blog covers how to do it with a Script.
The default id field for a Azure Mobile Services Table, that the table is indexed on, is a string. By default the string that is auto-generated is a 36 character GUID string. This can be 3 or more times rest of the data sent as a HTTP Response to a default HTTP GET for each record from the Telemetry table . This blog discusses this issue and canvasses some options to resolve this overkill.
This blog covers the major revision of the Telemetry to remove old, now unnecessary code, fix some bugs, further improve error responses, and a stored data structure that makes the parsed JSon data available after the HTTP Response processing is complete.