01-25-2010 09:44 AM
We something strange in the way the absolute time responds on a cRIO target.
When powering up the cRIO the timestamp seems to be malformed resulting in date/time strings like "19013672-80u04m00s" (could be a bug in scan to string with option %<>T).
Nevertheless the originating stamp is not in the range "1904 - now", this doesn't happen with a soft reboot.
How is the cRIO absolute time handled?
Is a set absolute timeable to survive a short or long power cycle?
03-05-2010 02:23 AM
Hi André,
What cRIO controller do you have? And what software version?
Maybe this KB helps.
Regards,
Bas
03-05-2010 03:35 AM
Thanks for the response.
Our systems use the 9014 controller, not the ones indicated in the KB article.
04-07-2010 09:32 AM
Hi André,
Do you have your code? I can't reproduce it here. I also have a 9014.
I tried it with the RT set Date and Time vi. And with a format date time string.
And what time format string do you use?
Bas