From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
10-03-2013 03:49 PM
I'm migrating a project over to LV 2013 and rely on the custom time reference project to update my real time system clock on a cRIO-9025. Does the released code work with Timesync 1.3 and LabVIEW 2013? What are the steps to get the custom time reference code running under 2013?
04-08-2015 03:45 PM
Hello,
Sorry this post has been left languishing. Getting the Sync-Labs time reference working alongside the 1588-2008 time reference with NI-TimeSync 1.3 will be a little tricky. The reason is as follows, when you install a new version of NI-TimeSync (1.3+) on a system with a Sync-Labs release (1.2.X), the result is that it uninstalls the LabVIEW support for your time references. Also, the Sync-Labs release only installs API support up to LabVIEW 2011. You should still be able to install your custom time reference to a VxWorks/PharLAP Real-Time target, but the APIs to control and monitor them will not be available.
Here is how I would recommend you get these two releases to work together.
Now you should be able to install both the custom and the 1588 time reference to your target and you should have API support on LV for the custom time reference.
Note: The custom time reference VI will not have been compiled for your version of LabVIEW, so you will more than likely be prompted to resave that VI.
Sincerely,
Mark