We are pleased to present below all posts archived in 'March 2015'. If you still can't find what you are looking for, try using the search box.
A solution is now at hand with respect to interrupts being lost when they are close to a system timer tick interrupt, with TI AM335X CPU. THE LATEST UPDATE NOW HAS THIS SOLUTION.
Read the rest of entry »
A new Compact 2013 release is available on MSDN that will bring your build environment up to date as per February 2015.
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.