Networked eDAQXR units can be connected in a variety of ways. See eDAQXR eXRCPU for information about connection of an eXRCPU to other devices. The eDAQXR currently supports only one networking mode (Mode 1).
Mode 1 Networking
One eDAQXR serves as the networked system host (subsequently referred to as the master node), and all other connected eDAQXR units provide source data to the master node (subsequently referred to as slave nodes). The master node runs the test engine that processes all input channels, Computed channels and DataModes and drives the run time displays. A single SIE file is generated on the master node only.
NOTE
The eDAQXR currently supports only 2 network nodes (i.e., one master and one slave node). The nodes must both use the ETH1 port for the network connection. The ETH2 ports can be used for other device connections (i.e., MX modules or Axis cameras).
The master node is always the node used to start the test. Typically, the SXR file will reside on only one node and this will be the master node when the test is started. For the most part, the user only needs to communicate with the master eDAQXR. However, there is currently the following exception.
All test runs modes (Normal, Cyclic and Remote control) are available in a networked system. If the Remote control run mode is used, the eXRCPU IO switch 1 on the master node must be used.
CPU load balancing: For many applications, the user does not need to be concerned with this issue. However, if the CPU load of any node exceeds 60-70%, the user should consider options for balancing the CPU loads across the nodes, which requires some trial and error experimentation. Following are some guidelines.