IEEE 1588 External Switch Requirements
To take advantage of the network synchronization features of the cRIO-905
x
controllers,
ensure that your network infrastructure meets certain requirements depending on which
IEEE 1588 profile is implemented for your application:
•
IEEE 802.1AS-2011 support—Automatically enables timebase synchronization and
enables the use of time-based triggers and timestamping between devices across the
network. Synchronization performance will meet NI product specifications.
•
IEEE 1588-2008 support—Enables timebase synchronization and enables the use of time-
based triggers and timestamping between devices across the network. Synchronization
performance will vary and may not meet NI product specifications. As a default
configuration for IEEE 1588-2008, NI supports the IEEE 1588 Delay Request-Response
profile, using the UDP over IP transport (layer 3-4).
Battery
The cRIO-905
x
contains a lithium cell battery that stores the system clock information when
the cRIO-905
x
is powered off. There is only a slight drain on the battery when power is
applied to the cRIO-905
x
power connector. The rate at which the battery drains when power is
disconnected depends on the ambient storage temperature. For longer battery life, store the
cRIO-905
x
at a cooler temperature and apply power to the power connector. Refer to the
for the expected battery lifetime.
The battery is not user-replaceable. If you need to replace the battery, contact NI. Refer to the
controller specifications on
for information about battery disposal.
File System
LabVIEW mounts USB devices and microSD cards to the
media/sdx1
directory and creates
symbolic links
/u
,
/v
,
/w
, or
/x
to the media mount point, starting with
/u
if it is available.
To prevent any file corruption to external storage devices, verify that any file IO operations
with the specific drive finish before removing the device. Refer to the
LabVIEW Help
for more
information.
The file system of the cRIO-905
x
follows conventions established for UNIX-style operating
systems. Other LabVIEW Real-Time targets follow Microsoft Windows-style conventions. In
order to facilitate the porting of applications from those targets, this target supports the
Windows-style
/C
home directory. This path is bound to the UNIX-style directory
/home/
lvuser
.
Various LabVIEW Real-Time system files which would be accessible from
C:
(or
/C
) on
other LabVIEW Real-Time targets are found in different locations on this target.
UNIX-style file systems support the concept of a symbolic link, which allows access to a file
using an alternative file path. For example, it is possible to link
/C/ni-rt/system
, where
dynamic libraries are deployed on other LabVIEW Real-Time targets, to
/usr/local/lib
,
where they are stored on the cRIO-905
x
, if the application requires this.
For more information, visit
and enter the Info Code
RT_Paths
.
18
|
ni.com
|
NI cRIO-905x User Manual
