Anyone having SNTP / RTC issue on Spinneret today?
Rforbes
Posts: 281
Hey all,
Yesterday the sntp protocol on my spinneret worked fine. Today, I keep getting 31/12/2013 for the date (Dec 31, 2013)
I'm trying to troubleshoot it and I'm pretty sure it's the sntp object that isn't calculating it correctly. But if anyone else is getting the correct date after using SNTP then I guess that's not the issue (using the same object of course.)
Yesterday the sntp protocol on my spinneret worked fine. Today, I keep getting 31/12/2013 for the date (Dec 31, 2013)
I'm trying to troubleshoot it and I'm pretty sure it's the sntp object that isn't calculating it correctly. But if anyone else is getting the correct date after using SNTP then I guess that's not the issue (using the same object of course.)
Comments
Somehow, between the last time I saved and shutdown the propeller tool just now, I got the HTTPServer object file corrupted or something, shown above. wth??
Also- earlier today, I was able to get something outta pst. Shown below:
It's interesting that you got "13/229/2013" from the rtc.readTime though.... My date is 31/12/2013 but if I use pst as I've shown above:
The pst.Dec(byte[@MM_DD_YYYY][X]) showed the values 7, 221, 229 and 13. I don't remember which order now, and I also get nothing but 0's now. I haven't changed the code since earlier, at all.
(I'm still trying to figure out how HumanTime does everything, so in the mean time I wrote a sample that works. It's clunky and nothing to be proud of, but it does work. I'm going to see if I can adapt it for use in the sntp object soon.)
In case anyone needs to get the sntp functionality on the spinneret working quickly, here's my sample. It might help you figure out a much better way to do it.