Dtrack2 software has errors when clicking “start” because one of the “slave” computers are not connecting.
A sudden and extended (over an hour) power outage was experienced on campus, which took the CAVE equipment offline. After restarting the Dtrack2 server and both of the “slave” PCs, Dtrack2 still was not successfully able to start the tracking system.
It might start, but only half of the cameras would appear functional. Or maybe it would fail to start and pop up with a “fatal error” message along with the IP address of the computer that is not connecting.
The system might display an IP address of the server having the problem, either 192.168.5.163 or 192.168.5.164 (the controller server IP is 192.168.5.162).
If the problem is with the IPs ending in 163 or 164, those are the “slave” computers that are on the mini-rack behind the center screen in the CAVE.
They have labels on the back of those servers, either ATC-718 or ATC-719.
Check to see if the network connector has blinking lights on either of them. If one does not, then take the cable from the blinking one and plug into the other one to check if the network card is functional. If it is functional, then the problem is probably a network switch. One of the two ART servers is connected to a network switch on the small rack.
If the switch on the rack is not lit up, then pull the power cord wait about 10 seconds and then plug it in again. That fixed the issue today.
Checking for ping also works, but the computer has to be connected to the 192.168.5.XXX subnet. The ART computers can be pinged from the head node.