Difference between revisions of "MainPage:Nuclear:NPS:PWO:CODA"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
# In the same terminal, type < sudo ./coda_user_setup_databases >; you will be prompted to type in the password (bolded)- it is: '''linux!''' ... some windows will pop up- wait 10 seconds. | # In the same terminal, type < sudo ./coda_user_setup_databases >; you will be prompted to type in the password (bolded)- it is: '''linux!''' ... some windows will pop up- wait 10 seconds. | ||
# Then type < sudo ./coda_user_setup_codamaster > in the same terminal. | # Then type < sudo ./coda_user_setup_codamaster > in the same terminal. | ||
| − | # Several windows will pop up, one of interest is the "working config" window which asks you to select a configuration name. Select | + | # Several windows will pop up, one of interest is the "working config" window which asks you to select a configuration name. Select the configuration name '''vme_camac''' |
#Click on '''Config''' on the top left of the window that popped up with "vme1 and EB1, kill, etc", and select "Enable Buttons". | #Click on '''Config''' on the top left of the window that popped up with "vme1 and EB1, kill, etc", and select "Enable Buttons". | ||
#Click on '''Event builder''' and '''Run Control''' buttons. | #Click on '''Event builder''' and '''Run Control''' buttons. | ||
| Line 21: | Line 21: | ||
If there is a successful '''VME1''' and '''EB1''' connection, the messages will say that the connection is successful. If there are warning signs or there is a consistent "configuring" or "activating" on the status bar, then there is a problem. Go to the Troubleshoot section below. | If there is a successful '''VME1''' and '''EB1''' connection, the messages will say that the connection is successful. If there are warning signs or there is a consistent "configuring" or "activating" on the status bar, then there is a problem. Go to the Troubleshoot section below. | ||
| − | |||
| − | |||
| − | |||
=== Killing coda === | === Killing coda === | ||
| Line 32: | Line 29: | ||
#Rebooting minicom: go to a new terminal and to the home DAQ directory. Type: < sudo minicom > and then < reboot >. This will relay a lot of messages on the terminal, one of them including "VX WORKS" which (hopefully) ensures that minicom is rebooted. | #Rebooting minicom: go to a new terminal and to the home DAQ directory. Type: < sudo minicom > and then < reboot >. This will relay a lot of messages on the terminal, one of them including "VX WORKS" which (hopefully) ensures that minicom is rebooted. | ||
#Now you can start coda: type < cd coda > in a new directory. | #Now you can start coda: type < cd coda > in a new directory. | ||
| − | # And now type < sudo ./coda_user_setup_codamaster > and follow the same instructions '''after''' #'''4''' | + | # And now type < sudo ./coda_user_setup_codamaster > and follow the same instructions '''after''' #'''4''' in the above section '''Starting/Restarting CODA'''. |
| − | |||
# Possible [http://hallaweb.jlab.org/equipment/daq/coda_hints.html website] that may help. | # Possible [http://hallaweb.jlab.org/equipment/daq/coda_hints.html website] that may help. | ||
| Line 39: | Line 35: | ||
== FAQ == | == FAQ == | ||
# Why does coda sometimes crash? | # Why does coda sometimes crash? | ||
| − | #* There could be several reasons: so far we have experienced a corrupted connection between VME1 and EB1 | + | #* There could be several reasons: so far we have experienced a corrupted connection between VME1 and EB1. |
#What is VME1 and EB1? | #What is VME1 and EB1? | ||
#* VME1 is the connection between the DAQ setup and the computer, and EB1 is the "event builder" which is the interface used to take events (idk?). | #* VME1 is the connection between the DAQ setup and the computer, and EB1 is the "event builder" which is the interface used to take events (idk?). | ||
# Who can help us if there is a bigger internal issue? | # Who can help us if there is a bigger internal issue? | ||
#* Steve Wood: email - saw@jlab.org | #* Steve Wood: email - saw@jlab.org | ||
Revision as of 19:21, 10 December 2016
| ⇐ Back to Neutral Particle Spectrometer |
| ⇐ Back to the Main_Page |
Introduction
The Data Acquisition (DAQ) setup at CUA utilizes "CODA" which is a software and hardware that enables data taking in nuclear physics experiments. We use CODA for many experiments at CUA (light yield, PMT testing, etc.). You can read more about it here.
How to use CODA
Starting/Restarting coda
- Restart the DAQ computer if you are having problems.
- On the DAQ computer, type < cd coda > in a terminal to go to the directory where coda is located.
- In the same terminal, type < sudo ./coda_user_setup_databases >; you will be prompted to type in the password (bolded)- it is: linux! ... some windows will pop up- wait 10 seconds.
- Then type < sudo ./coda_user_setup_codamaster > in the same terminal.
- Several windows will pop up, one of interest is the "working config" window which asks you to select a configuration name. Select the configuration name vme_camac
- Click on Config on the top left of the window that popped up with "vme1 and EB1, kill, etc", and select "Enable Buttons".
- Click on Event builder and Run Control buttons.
- On the run control GUI, click Platform and then Connect on the top left side of the window.
- It should say "connecting" you can now click the configure button right below "platform". Should say configuring, and then configured on the status bar. You can now start the run.
If there is a successful VME1 and EB1 connection, the messages will say that the connection is successful. If there are warning signs or there is a consistent "configuring" or "activating" on the status bar, then there is a problem. Go to the Troubleshoot section below.
Killing coda
- Just restart the computer if "ctrl+c" or closing out of all the windows doesn't work.
Troubleshoot
- If warning signs of VME1 and EB1 connection and the status saying "configuring" or "activating" are persistent, then there is a problem and we have to reboot coda. If the problem persists for another time, close out of coda again/restart the computer. We have to reboot minicom.
- Rebooting minicom: go to a new terminal and to the home DAQ directory. Type: < sudo minicom > and then < reboot >. This will relay a lot of messages on the terminal, one of them including "VX WORKS" which (hopefully) ensures that minicom is rebooted.
- Now you can start coda: type < cd coda > in a new directory.
- And now type < sudo ./coda_user_setup_codamaster > and follow the same instructions after #4 in the above section Starting/Restarting CODA.
- Possible website that may help.
FAQ
- Why does coda sometimes crash?
- There could be several reasons: so far we have experienced a corrupted connection between VME1 and EB1.
- What is VME1 and EB1?
- VME1 is the connection between the DAQ setup and the computer, and EB1 is the "event builder" which is the interface used to take events (idk?).
- Who can help us if there is a bigger internal issue?
- Steve Wood: email - saw@jlab.org