Instructions for running the PC DAQ in 1008A

SETUP
• Open three windows on phoncs0, via ssh phoncs0, followed by the password.
• Open one window on phoncs1, via ssh phoncs1, followed by the password. This is for running "netmap".
• On each window, type in "setuponcs". Or "setuponcs R3.0.0" to choose version 3.0.0 of the setup script.
• Verify that the Low Voltage is on for the part of the detector you would like to look at.
• On phoncs0, type "gtm GTM.PC.E &" or "gtm GTN.PC.W &" to start the GUI.

GTM LOADING
• Select "LOAD MODE BIT" button, and choose "GTM.PADSTRB2.gtm" for testing, or "GTM.PC_DATA2.gtm" for data.
• On the GTM GUI Check that Clock Source is Internal; otherwise click on "Toggle Clock Source".
• On the GTM GUI Click on GLINK RESET and SCHEDULER RESET.

NETMAPING
• On phoncs1> Type in "netmap /dev/arcX" where X is either
  • 0 for East North PC-1 and East North PC-3.
  • 2 for East South PC-1 and East South PC-3.
  • 4 for West North PC-1, 2 and 3.
  • 5 for West South PC-1, 2, 3.
• The netmap should return with the list of active nodes. These should include 80-87 for PC-1, 88-95 for PC-2, and 96-103 for PC-3.

FEEDING
• On phoncs0> Type "feed.pl"
• On the GUI that springs up on phoncs0, Click on either PC.E or PC.W, depending on which side you are reading out.
• It will think for about 30 secondsm showing "working ... init.fem" or "working ... pattern", until it shows the date and time and it is ready to run.
• Check that it returns "Total number of errors: 0 from 160 files" or something like that.
• If the number of errors is non-zero, then check either the low voltage, or the netmap to see if all nodes are responding.
• Also look at the files in $ARCNET_DATA/pc/acf/pc_init_w/e_all.acf.
• Also look at files in $ARCNET_DATA/pc/pcchip/pc_pattern.acf etc.
• Check that "LOC FORCED ACCEPT", "LEVEL 1 BLOCK" and "SCHEDULER BUSY ENABLE" are all yellow.
• If not, then click on "TOGGLE LEVEL1 BLOCK STATE" or whatever is the appropriate button.

PROCESSING
• On phoncs0> cd /export/software/oncs/online_configuration/rc/hw
• Type ll pc*.
• The DCM reads the file called either pc.w.pcf or pc.e.pcf.
• So create a softlink to this file with: ln -s pc.e.pcf.BASE pc.e.pcf or something like that. You are free to edit or replace the file called pc.e.pcf.BASE to make the readout just what you want, such as turning off a FEM readout.
• Type ll pc*.
• Check that pc.e.pcf --> pc.e.pcf.BASE or whatever you created the softlink to.
• On phoncs0> ./process_pcf_file pc.e.pcf or pc.w.pcf.
• This converts the file to DCM format.
• When finished, it will say "create /..pc_e_daq2a1.dat" or something like that.

LOADING THE DCM
• cd /export/software/oncs/R3.0.0/online/distribution/Dcm/src
• ./dcm PC.E or PC.W
• This brings up a menu which allows you to run interactively, or otherwise.
• Type "0" for interactive.
• Type "301" for read configuration file.
• Return value 0 is good.
• Type "303" next.
• Type "305" to take a run.
• Type "100" for the number of events you want to take.
• Type "/export/bigdisk/phoncs/pc123_april6_test2.dat" or whatever name is most descriptive. DCM will add a ".0" to the file name to make it unique. If ".0" already exists, it will add a ".1" or whatever is required.
• This should produce a change in the "-BUSY STATUS-" indicator.
• Click on "START".
• When the number of LEVEL 1 events equals or exceeds the number you requested, you may click on "STOP".
• For good luck, click on "SCHEDULAR RESET" as well.
• To start another run, type "303", followed by "305" etc.

LOOKING AT THE DATA
• On phoncs0> ddump -n0 -f pc123_april6_test2.dat.0 | more
  in order to look at the events. You may need to fiddle with the window size to make the output look nice. Note: -n0 mean how many events do you want to analyze, 0 == all. -f means take input from a file. NB: You need to specify the .0 on the end of the file name. Pipe the whole thing into more in order to look at it.

RUNNING FROM RUN CONTROL

• In order to run RUN CONTROL, log on to phoncs0> and type
  rc -standalone
  

• followed by "feed.pl"
  
• followed by "ts iocondev2a"
  
• Then click on "DOWNLOAD"
• Watch in iocondev2a window to see if the DCM loads successfully.
  
• Click on "START".
• Click on "PHYSICS".
• Click on "STOP".
• ddump /export/bigdisk/eventdata/rc_...
• Also there is something to do with cratestatus.pl...

DOWNLOADING HEAP MANAGER CODE
• On phoncs0> type $ARCNET_BIN/arcnet_client $ARCNET_DATA/pc/acf/pc1w_hm_fpga.acf

Log in to phoncs0 as phoncs or phnxpc

setuponcs
cd /export/software/oncs/online_configuration/rc/hw/ or $ONLINE_CONFIGURATION

location of GTM files: /export/software/oncs/online_configuration/GTM
We are currently (7/17/01) using
GTM.PC.E.FAST and ...W.FAST, and they can be seen in the .pcf files in ...rc/hw area.

If you edit the GTM file, you will need to remake the file by issuing:
make GTM.PC.E.FAST.gtm

cratestatus.pl shows the status of the GTM and DCM (and GL1) crates.

feed.pl downloads the FEM information via arcnet. It also issues some resets.

Take a look at
http://www.phenix.bnl.gov/WWW/offline/cvsweb/

Here are some interesting directories...
$ARCNET_BIN/arcnet_client
$ARCNET_DATA/pc/acf/pcw_hm_fpga_bcast.acf
/export/software/oncs/log/arcnet
$SCRIPTS_SRC/feed.pl (cvs commit feed.pl)

In order to run RUNCONTROL in standalone mode:
rc -standalone
or the normal RUNCONTROL
rc

This is where the data files end up
/common/buffer2/eventdata
or ..junkdata, or calibdata or ...

In order to create a new Pcchip file, log in to any linux machine,
cd cvs/online/monitoring/pad/pcchip/pcchip
and play with the gui...

High Voltage (phoncs5)

Location of DCM crates and GTM crates:
West carriage
DCM:iocondev1d
GTM:iocondev10 slot 12

East carriage
DCM:iocondev2a
GTM:iocondev11 slot5

Arcnet Nodes

PC1.W.S.0   /dev/arc5 PC1.W.S.1   /dev/arc5 PC1.W.S.2   /dev/arc5 PC1.W.S.3   /dev/arc5 PC1.W.S.4   /dev/arc5 PC1.W.S.5   /dev/arc5 PC1.W.S.6   /dev/arc5 PC1.W.S.7   /dev/arc5	80 81 82 83 84 85 86 87	4001 4002 4003 4004 4005 4006 4007 4008	PC1.W.N.0   /dev/arc4 PC1.W.N.1   /dev/arc4 PC1.W.N.2   /dev/arc4 PC1.W.N.3   /dev/arc4 PC1.W.N.4   /dev/arc4 PC1.W.N.5   /dev/arc4 PC1.W.N.6   /dev/arc4 PC1.W.N.7   /dev/arc4	80 81 82 83 84 85 86 87	4009 4010 4011 4012 4013 4014 4015 4016
PC2.W.S.0   /dev/arc5 PC2.W.S.1   /dev/arc5 PC2.W.S.2   /dev/arc5 PC2.W.S.3   /dev/arc5 PC2.W.S.4   /dev/arc5 PC2.W.S.5   /dev/arc5 PC2.W.S.6   /dev/arc5 PC2.W.S.7   /dev/arc5	88 89 90 91 92 93 94 95	4033 4034 4035 4036 4037 4038 4039 4040	PC2.W.N.0   /dev/arc4 PC2.W.N.1   /dev/arc4 PC2.W.N.2   /dev/arc4 PC2.W.N.3   /dev/arc4 PC2.W.N.4   /dev/arc4 PC2.W.N.5   /dev/arc4 PC2.W.N.6   /dev/arc4 PC2.W.N.7   /dev/arc4	88 89 90 91 92 93 94 95	4041 4042 4043 4044 4045 4046 4047 4048
PC3.W.S.0   /dev/arc5 PC3.W.S.1   /dev/arc5 PC3.W.S.2   /dev/arc5 PC3.W.S.3   /dev/arc5 PC3.W.S.4   /dev/arc5 PC3.W.S.5   /dev/arc5 PC3.W.S.6   /dev/arc5 PC3.W.S.7   /dev/arc5	96 97 98 99 100 101 102 103	4065 4066 4067 4068 4069 4070 4071 4072	PC3.W.N.0   /dev/arc4 PC3.W.N.1   /dev/arc4 PC3.W.N.2   /dev/arc4 PC3.W.N.3   /dev/arc4 PC3.W.N.4   /dev/arc4 PC3.W.N.5   /dev/arc4 PC3.W.N.6   /dev/arc4 PC3.W.N.7   /dev/arc4	96 97 98 99 100 101 102 103	4073 4074 4075 4076 4077 4078 4079 4080
PC1.E.S.0   /dev/arc2 PC1.E.S.1   /dev/arc2 PC1.E.S.2   /dev/arc2 PC1.E.S.3   /dev/arc2 PC1.E.S.4   /dev/arc2 PC1.E.S.5   /dev/arc2 PC1.E.S.6   /dev/arc2 PC1.E.S.7   /dev/arc2	80 81 82 83 84 85 86 87	4017 4018 4019 4020 4021 4022 4023 4024	PC1.E.N.0   /dev/arc0 PC1.E.N.1   /dev/arc0 PC1.E.N.2   /dev/arc0 PC1.E.N.3   /dev/arc0 PC1.E.N.4   /dev/arc0 PC1.E.N.5   /dev/arc0 PC1.E.N.6   /dev/arc0 PC1.E.N.7   /dev/arc0	80 81 82 83 84 85 86 87	4025 4026 4027 4028 4029 4030 4031 4032
PC3.E.S.0   /dev/arc2 PC3.E.S.1   /dev/arc2 PC3.E.S.2   /dev/arc2 PC3.E.S.3   /dev/arc2 PC3.E.S.4   /dev/arc2 PC3.E.S.5   /dev/arc2 PC3.E.S.6   /dev/arc2 PC3.E.S.7   /dev/arc2	96 97 98 99 100 101 102 103	4081 4082 4083 4084 4085 4086 4087 4088	PC3.E.N.0   /dev/arc0 PC3.E.N.1   /dev/arc0 PC3.E.N.2   /dev/arc0 PC3.E.N.3   /dev/arc0 PC3.E.N.4   /dev/arc0 PC3.E.N.5   /dev/arc0 PC3.E.N.6   /dev/arc0 PC3.E.N.7   /dev/arc0	96 97 98 99 100 101 102 103	4089 4090 4091 4092 4093 4094 4095 4096

Michael Sivertz ... sivertz@bnl.gov ... Last modified: Tuesday, 17-Jul-2001 11:19:04 EDT