2 replies to this topic

[Bendage]

So tonight I was racking my brain on the easiest way to send a datetime val as a string through serial to my Netduino. The problem is that the Netduino code in my app is so big I didn't want to write a bunch of substring parsing code to parse the datetime string to set the controller clock.

I noticed the Ticks constructor on the New DateTime object in the Micro Framework so I figured I'd just convert DateTime.Now.Ticks.ToString on the PC and send it through. What happened was the tick count exceeded the Micro Framework DateTime.MaxValue. Hmmmm!

Looking through it more MF starts their DateTime at 1/1/1601 12:00 AM while Framework 4.0 is 1/1/1 12:00 AM

Here is the solution if anyone is interested

// PC Send
string time = (DateTime.Now.Ticks - new DateTime(1601, 1, 1).Ticks).ToString();


// Send time string via serial....

// Netduino Instantiate
Microsoft.SPOT.Hardware.Utility.SetLocalTime(new DateTime(Int64.Parse(time));

Bam! You got your clock set with no parsing.

[emg]

Yep. Works via Ethernet too. I send logging data from the Netduino back to a PC and use UDP sockets to create a poor mans NTP server where the PC can force a time setting on the Netduino or the Netduino can request a time update.

[emg]

Also remember if you sending the time from the netduino back to the PC to add 1600 years to the ticks value for the correct date. See here: DateTime ticks inconsistent between .NET MF 4.2 and full .NET 4.0?