I have a TSN setup with a cRIO-9045 and cRIO-9040 and after 1 day they get out of sync. Is there a (preferably out of the box and easy) way to double check the synchronisation? On both cRIO-9045 and 9040 there is an NTP daemon running which is synchronizing to the same host machine. Is the combination TSN and NTP surely not conflicting?
Please review the following Table:
|Min. Software Stack with the TSN 17.0 Driver||Min. Software Stack with the TSN 17.5 Driver||Min. Software Stack with the TSN 18.0 Driver||Min. Software Stack with the TSN 18.1 Driver|
|LabVIEW 2017||LabVIEW 2017 SP1||LabVIEW 2018||LabVIEW 2018|
|LabVIEW Real-Time Module 2017||LabVIEW Real-Time Module 2017||LabVIEW Real-Time Module 2018||LabVIEW Real-Time Module 2018|
|LabVIEW FPGA Module 2017||LabVIEW FPGA Module 2017 SP1||LabVIEW FPGA Module 2018||LabVIEW FPGA Module 2018|
|CompactRIO Device Drivers May 2017 (17.0)||CompactRIO Device Drivers December 2017 (17.6)||CompactRIO Device Drivers May 2018 (18.0)||CompactRIO Device Drivers June 2018 (18.1)|
|TSN 17.0||TSN 17.5||TSN 18.0||TSN 18.1|
|LabVIEW 2017 FPGA Xilinx Compilation Tool for Vivado 2015.4 (optional)||LabVIEW 2017 FPGA SP1 Xilinx Compilation Tool for Vivado 2015.4 (optional)||LabVIEW 2018 FPGA Xilinx Compilation Tool for Vivado 2017.2 (optional)||LabVIEW 2018 FPGA Xilinx Compilation Tool for Vivado 2017.2 (optional)|
|DAQmx 17.1*||DAQmx 17.6 is included with the CompactRIO Device Drivers 17.6 and later||DAQmx is included with the CompactRIO Device Drivers||DAQmx is included with the CompactRIO Device Drivers|
*Only needed if you need to control a TSN cDAQ from a cRIO (sync).
For cRIO-904x series, the minimum required software is the Software stack 2018, Therefore as you are using cRIO 904x, you need to use at least LabVIEW 2018.
Find the links to download this software in the NI TSN thread: Installing Software and Hardware Setup for NI TSN Devices
Hi guys, I was digging further in this problem here. And it seems that NTP and the NI-Timesync are unable to work together (as I read in some NI official document). This is very problematic for me as I really need both. The two CompactRIOs need to be perfectly in sync with TSN for the acquisition. The master timebase needs to be the timebase of the company's NTP. Is there a way to tell NI-TimeSync that he needs to use the NTP clock as master timebase and then have all the others follow this NTP clock?
FIY. I couldn't find anything wrong with the software stack. (see screenshots in attachment)
I also posted this question in the specific TSN group.
Thanks bhovhann for the link!