One EXRCPU serves as the networked system host and all other connected eXRCPUs provide source data only to the host EXRCPU (master and slave units). As such, only the host EXRCPU runs the test engine, only one SIE file is generated, and the user only needs to (and is normally allowed to) communicate with the host EXRCPU.
The EXRCPU units may be connected through an Ethernet network.
NOTE
If a slave EXRCPU is networked to a master EXRCPU, the Host connector must not be used on the slave unit.
The host eDAQXR web interface runs largely as it does with a stand alone EXRCPU. For the slave eXRCPUs, only a minimal interface shows. After displaying a landing page and minimal loading, the user sees a notification that the EXRCPU is configured as a networked slave. Communication with the slave will be through the interface for the master EXRCPU.
A slave unit may be disconnected from the master unit, so a slave EXRCPU may operate as a stand alone unit. This is required in case there is a connection problem between the units and the user is willing to break the network (this will stop any SIE test that is running).