2020/01/06 (Thursday)

Status	Tower from Run 71 has been removed.
0930	SPA computing is being absorbed by CSE. Because of this we need to change the static IP addresses of our devices. IT is handling this behind the scenes for our linux and Windows machines. For the DCRCs, Nick and Chad (IT) made these changes last week and today. The procedure to change the addresses is described here. Except for DCRC2, all the boards were able to be updated via USB on the windows machine. DCRC2 for some reason was unable to initiate this connection. It was changed by first connecting via telnet using the old address, changing the boards IP address in the telnet session, then IT updated the new IP address on their routing tables, and then the board was reset.

Status

Tower from Run 71 has been removed.

0930

SPA computing is being absorbed by CSE. Because of this we need to change the static IP addresses of our devices. IT is handling this behind the scenes for our linux and Windows machines. For the DCRCs, Nick and Chad (IT) made these changes last week and today. The procedure to change the addresses is described here. Except for DCRC2, all the boards were able to be updated via USB on the windows machine. DCRC2 for some reason was unable to initiate this connection. It was changed by first connecting via telnet using the old address, changing the boards IP address in the telnet session, then IT updated the new IP address on their routing tables, and then the board was reset.

The DCRC IP changes need to be propagated to MIDAS. Searching for the old addresses in a recent odb file shows they appear in the following places:

/Equipment/Tower01/Settings/DCRC1/DcrcIPAddress
/Equipment/Tower02/Settings/DCRC1/DcrcIPAddress
/Equipment/Tower03/Settings/DCRC1/DcrcIPAddress
/iZIPRevC01/DCRCInfo/DCRC0/DcrcIPAddress

We think that only the first is relevant for our purposes. The Tower 2,3 settings were probably just copied and the final location seems to be associated with a different odb structure than we use, possibly related to an older (or newer) dcrc driver version.

0940	Updated the IP addresses at /Equipment/Tower01/Settings/DCRC/DcrcIPAddress* Plug in DCRC1 to a miniBoB and start it up. Enable only DCRC1 in the odb and try to start the DAQ programs. They don't crash. Try to start the pulse viewer, but get the following error:

TMidasControl::connect: Connecting to experiment "cdms_UMN" on host "cdms2.spa.umn.edu:7071"
TMidasControl::connect: Cannot connect to MIDAS, status 503.
==================================
Cannot connect to MIDAS! Check server....
EXITING!
==================================

0947	Take test series of 1 min of randoms triggers. Programs don't crash but nothing new shows up in midasraw. Could be that lazylogger is dead, we haven't restarted the DAQ in a while. Restart MIDAS. Now lazylogger copies the file over and I can see it with BatViewer. Seems the issue is just with SQUIDTuningGUI connecting to MIDAS.
1000	Ah, solved it. The SQUIDTuningGUI issue was just a problem for Nick since his default python is v3.x instead of v2.x. This causes problems for all the DAQ stuff if you don't switch over to v2.x in the terminal used.

Next Day