Jeffa

I'm dusting off my Netduino 2 Plus... In a previous project that I authored, I used a syntax of

static AnalogInput a0 = new AnalogInput((Cpu.AnalogChannel)Cpu.AnalogChannel.ANALOG_0, 3.3, 0.0, 10);

I had to reLoad it from gitHub to realize / remember it was a version sdk4.3 project.

I'm working in a 4.2 project now* duplicating the code for another project. Currently my Netduino 2 Plus is configured as

static AnalogInput a0 = new AnalogInput(AnalogChannels.ANALOG_PIN_A0);

For a couple days now I've been reading about ISO 8601 Date and Time representations. This Wikipedia article has some good information. 

As of about version 4 .net has standardized on ISO 8601 for representation of DateTime when serializing. See this article by Scott Hanselman

In an application I have code that writes DateTime.UtcNow which is apparently creating an incorrectly formatted serialization of DateTime. The only allowable alpha Timezone is 'Z' for zulu. Others are expressed as numeric offsets.

Note these two Json serializations. The first from a .net windows phone application (correct), the second from my ndp2 (incorrect) project. Both reporting to Azure.

 [{"id":1,"DataLoggerName":"Ben Walkin","Time":"2013-02-19T18:39:51.733Z",[{"id":1,"DataLoggerName":"JHANetDuino","Time":"2013-02-19T16:46:55.205K",

I hope to work around this problem by learning how to set a Timezone in .netmf. However using DateTime.UtcNow should not reflect the local time. Correct?

I documented some of my travails in this stackoverflow question. And earlier in these forums in this article.

I'm attempting to create table data in Azure with mobile services. Got it working. It looks to me that my ndp2 is producing and persisting valid ISO 8601 DateTime to azure However the json.net JsonConvert.DeserializeObjectAsync in my Metro application barfs on the DataTime Deserialize. Please see this Stackoverflow quesion would appreicate it if you have experience with javascript and .net json.net.

            // Initializes the time client            SNTP_Client TimeClient = new SNTP_Client(new IntegratedSocket("time-a.nist.gov", 123));            // ExtendedTimeZone.SetTimeZone(TimeZoneId.Arizona); // not supported            TimeClient.Synchronize();

        public static void AzureUpdateThread()        {            while (true)            {                string strTime = DateTime.Now.ToString("yyyy-MM-ddTHH:mm:ss");                DateTime dateTimeMinusMilliSeconds = DateTime.Parse(strTime); // Apparently no DateTime.Parse                HistoricalTemperatureDataForAzure htdForAzure = new HistoricalTemperatureDataForAzure()                {                    DataLoggerName = DataLoggerName,                    // Time = DateTime.Now,                    // Time = DateTime.UtcNow,                    Time = dateTimeMinusMilliSeconds,                    Temperature0 = temperature0,                    Temperature1 = 0                };                var json = MobileService.GetTable("HistoricalTemperatureData").Insert(htdForAzure);                Thread.Sleep(5 * 60 * 1000);            }

I am noticing what appears to be some inconsistent behavior between my Netduino Plus 1 and my new Netduino Plus 2.

Most of the weekend I have been working on a Socket implementation to serve XML from a Netduino. It's been deploying and running for the most part flawlessly and consistently the entire weekend with many modifications and deploys to a single Netduino plus 1. The code is available on my gitHub account: here

I decided to continue development and add Azure mobile services. I ran out of room to deploy on the Netduino 1 Plus (Note that I haven't merged the Azure code up to gitHub). I had just purchased a new Netduino Plus 2. Attached and deployed fine, but right away it just seemed inconsistent in starting up. If I just fired it up it hung or otherwise failed while setting the clock from NTP, or listening with the Socket. If I set a break point on Main() and stepped through, it would run dependent on how I stepped into or over breakpoints. However without setting breakpoints it rarely if ever ran as expected and had run on the Netduino Plus 1 before growing the code to large to fit. 

Any ideas or comments? Below I include output from MfDeploy for both 'duinos. I am running SDK 4.3 (RTM) and Netduino SDK v4.30 (February 2013) in vs2012Ultimate.