Update: Settings for DCRC RevE is available at this link

Each board must be set up individually in order to tune the detector and take data.

1. Plug the DCRC board into the ebox. Be aware of which board you’ve plugged into which stripline. As you plug in the board, make sure not to touch any components on the board. Make sure the screws that plug the board into the ebox are as tight as possible.
2. Put the copper shield on the board. Make sure the screws are in as tight as possible. There is an additional skinnier copper shield that goes directly over the power supply. Cover the power supply and the gap that surrounds it with this shield. Tape this shield onto the DCRC with copper tape and make sure that it is in firm contact with the power supply.
3. Open a PuTTY session for the correct DCRC board. (Or if using MIDAS open a telnet session in a terminal like so: telnet [ADDRESS] 5000. )Note when you open the putty session the address for the board can be found in the current DCRC settings table below.
4. Start the clock on the board:
   • wr 15 0
   • wr 15 20
5. Make sure the board is powered properly. One indication is that the mixing chamber temperature will rise a little. Also, you can see if it’s being powered by reading information from the board:
   • rd 30
6. If the response is 0800, you’re in business. Do this for all three boards.
7. DCRC31 has an extra step. You will notice that if you do the above, the baseline remains high for the charge channels. This can be rectified by the following command (It should do this automatically, but for some reason this board doesn't):
   • wr 33 2000

Once you've done the above, you're good to go.

Updated revE IP for SN18: Oct 16, 2024

Updated revE values: 7/11/2023

Current as of 1/3/2020

G/W IP Addr: 128.101.21.174

SUBNET MASK: 255.255.255.240

To set up the timing link for simultaneous data acquisition, we daisy chain the boards. We designate one DCRC to be the master, and link them together with ethernet cables (the ethernet cable on the master plugs into the “FAR” socket, the socket closest to the corner of the board).

1. Give each board the following command:
   • wr 3c 0
2. Then, the slave boards should receive the following command:
   • wr 15 10
3. The traces will stop. On the master board, enter the following to establish the timing link:
   • wr 15 1
   • wr 15 21

There is a document by the DAQ computer that lists the putty commands to control the DCRC boards. This is useful for when you wish to write to the DCRC boards directly without using the readout or control vi’s.

1. (Defunct)Go to IP address 131.225.53.100 on browser. Password is [redacted].
2. (Defunct)Check that everything is disabled
3. Power on your DCRC board of choice by plugging the power souce data & power out into the board and the power source power in to a PoE switch port.
4. Use a USB cable to plug card into Windows computer.
5. Open PuTTY session (through start menu or PuTTY tab on bottom left of screen), and select COM 6 DCRC from the saved sessions list.
6. Type sock and check that board is connected.
7. Type set to see current IP setup.
8. Type set 1 131.225.53.89 (or chosen IP address) to change local IP address.
9. Type set 2 131.225.53.89 (or chosen IP address) to change global IP address.
10. Type save and then reset. Disconnect and reconnect the board (unplug and replug it).
11. Open PuTTY session again and select COM 6.
12. Type sock and check that board is connected.
13. Type set to see current IP setup. It should have changed.

Note, these settings can also be accessed through the standard telnet menu. However, this requires coordination with IT since they set which mac address is associated with which IP. This is how we had to set DCRC2's addresses on 1/3/2020 since it wasn't connecting via the COM port properly.

written 2016 May 13

• Plug in PoE ethernet cable into DCRC.
  • You will see four lights on opposite side, underneath ethernet port.
  • Three will blink for transmitting/receiving data.
  • The fourth is separated by a small gap from the other three. This is the connection light, and will light up solid when a connection has been established.
• Connect to the DCRCs via telnet.
  • When using MIDAS, which connects using ports 5001, 5002, connect to the boards on port 5000 with telnet.
• Execute the following commands on each board:
  • wr 15 0
  • wr 15 20
  • rd 30
• RevC.1 DCRCs will automatically turn on the FET heater when starting up in order to bring the FET to a working temperature. Once this has been achieved, they automatically turn off the heater.
  • rd 30 will return 0900 when the FET heater is still on.
  • Wait until rd 30 returns 0800 to indicate that the FET is on, but the FET heater has turned off.
• RevC DCRCs will *not* turn on the FET heater automatically.
  • You must execute wr 30 0900 manually, then wait until the charge channels on the DCRC become un-saturated.
  • Then you can turn off the FET heater by executing wr 30 0800.
• The DCRCs are now set up and ready to be connected to by the MIDAS frontends.
• Telnet session is also used to establish timing link, using procedure on this same page. Other DCRC communications handled through MIDAS.

• Stop MIDAS frontends (dcrc_driver, towerfe, triggerfe)
• In telnet session for each DCRC type quit to close that connection
• DCRCs are no longer communicating on any port. Unplug PoE ethernet cable to unpower.