08-04-2016 05:37 AM
Hello ccloud
sorry for the delay i tested it today with an cRIO 903x and there it worked
LV 2015 SP1 and RIo 15.5 was in use.
08-10-2016 12:09 PM
This is the code I use to set the cRIO clocks on my local network.
08-15-2016 07:26 AM - edited 08-15-2016 07:26 AM
Thanks CFER_STS. After looking at your code sample I realized my error. I had to create a password for the sbRIO because I am writing files to it. My code was missing the username and password on the initialize session VI. Once I added them it worked properly.
01-06-2020 04:22 AM
Currently Using cRIO9063 with LabVIEW 2014, The cRIO Driver software on target cRIO is ver 14, 15 (mixed) cRIO firmware is 7.0.0
If you run the SetTime VI in the cRIO Linux RealTime, a number of loops will start hanging! This means they stop executing altogether and the cRIO embedded software will appear to freeze!
BUT, when the set time VI was moved to Windows App and I wired the IP Address of the cRIO device, then this hanging issue stopped.
01-07-2020 02:13 PM
Well, that makes sense. The VI is using the localhost system clock as a reference to set the time on a specified remote device. If you try to run it on the system you're trying to set the clock on, it will attempt to use itself as the reference.
If you want to get fancier, you could edit your VI to have the Windows system update its own clock first via ntp or other method before setting the remote clock on the cRIO. That should get you within a few tens of ms.