Difference between revisions of "Running CODA"

From New IAC Wiki
Jump to navigation Jump to search
Line 2: Line 2:
 
Start the following programs in the order below  and in different xterm windows
 
Start the following programs in the order below  and in different xterm windows
  
(need to do: source CODA/2.5/coda.setup)
+
(need to do: source CODA/setup)
  
 
1.)msqld<br>
 
1.)msqld<br>

Revision as of 21:11, 28 July 2011

Startup the processes

Start the following programs in the order below and in different xterm windows

(need to do: source CODA/setup)

1.)msqld
2.)minicom (telnet roc1)

cntrl-A P E to setup communication speeds
reboot to be sure ROC is alive

3.)et_start -v -s 70000 -n 200

you may need to delete the old memory file /tmp/et_sys_DAQ
error message
~ >et_start
et_netinfo: error in gethostbyaddr
et_udpreceive: bind error
et SEVERE: et_listen_thread: problem opening socket

The above error message happened when I took the DAQ system to the IAC. The solution is to add the new IP addresss for the DAQ machine to the /etc/hosts file

For example

192.168.40.150  daq1.physics.isu.edu    daq1


The following fixed the above message

add the line

10.1.1.1        daq1.physics.isu.edu    daq1

to /etc/hosts file

According to Dave Abbott:

In looking at the ET code it seems that the ET system is checking all active network ports on a particular host and it gets a list of valid IP addresses (in your case 10.1.1.1 and 130.50.3.210). However it then attempts to get a hostname associated for each IP address (using gethostbyaddr). In your case 130.50.3.210 returns "daq1" but 10.1.1.1 returns <null> hence the error. In principle the hostname is not required for anything in particular, but the ET system does not start up because of this.


4.)rcServer

5.) coda_eb -i -s DAQ -n eb1 -t CDEB

6.)coda_er -i -s DAQ -n LDS_ER -t ROC

7.) runcontrol

Select run configuration

Creating run Configurations

The following describes how to make a run configuration file


use cedit to save a configuration to the data base (best to copy an old configuration)

Then

1.) lauch dbedit application

>dbedit


2.) select "localhost"

3.)click on "localhost" tab

4.) select "LDS" data base

5.) now start copying other tables into a new tabl

a.) SIS3610 copy to table SIS3610gem b.) SIS3610_option copy to table SIS3610gem_option c.) SIS3610_pos copy to table SIS3610gem_pos


6.) go to new copy and change location of executable code to a new directory (row 1 column "code")


The tables won't reload if you jsut stop runcontro. restarting the msql server didn't work

how to get the new runconfiguration to show up in runcontrol?

Th library for the ADC needs to be downlaoded by hand into the ROC. On the ROC terminal window type

ld < v792Lib.o

Download configuration to ROC

  1. Click COnfigure in the Runcontrol GUI
  2. select V775_TDC from the pull down menu
  3. click the download button in the runcontrol GUI
 You should see message appears on several of the open windows.  
You should see information in the ROC window.  If you see error 
messages check that you loaded the libraries with the commands

-> ld <v792Lib.o
-> ld < v775Lib.o

Prestart

Clicking the "Prestart" button in the GUI will begin initializing modules for the run

You should not see any error messages in the terminal windows.

Run

Click "Go" in the runcontrol GUI will start a data acquisition

debug FAQ

Using local network card

I decided to connect the ROC directly to the second 1 Gigabit ethernet card on the host in order to avoid setting up a firewall which makes our sys admin guys happy and allows CODA to work.

I had to tell the ROC to alias the new host names in the boot script


so in the file CODA/bootscripts/roc1.boot

I added the line

hostAdd "daq1","10.1.1.1"

You can do this on the roc as well and then on the ROC you can check the lookup tables using the command

-> hostShow                                                                     
hostname         inet address       aliases                                     
--------         ------------       -------                                     
localhost        127.0.0.1                                                      
roc1             10.1.1.2                                                       
localdaq         10.1.1.1          daq1                                         
value = 0 = 0x0                                                                 

Incorrect number Argument when downloading

daLogMsg: Downloading configuration "SIS3610"
Incorrect number of Arguments passed for ROL = 1
daLogMsg:  Incorrect number of Arguments passed for ROL = 1


I had incorrectly connected my EB to my ER system

ROC won't load VxWorks Kernel

If you have anout output to stdout from a .cshrc or .tcshrc login script then the ROC will have trouble loading the kernel.

I ran into this one when I deciced to "source CODA/setup" in order to define my CODA environmental variables when I log in. The setup script did a "echo" and this caused the ROC to stop loading the kernel. When I was watching via minicom all I saw was the word "Loading...".


coda_eb constructor faile

~ >coda_eb -i -s DAQ -n eb1 -t CDEB constructor failed : Couldn't setup listening socket on any port: Cannot assign requested addressNS_ServerInit (dp_MakeRPCServererror : Couldn't setup listening socket on any port: Cannot assign requested address ) Segmentation fault


coda_eb couldn't resolve the name server address

change /etc/hosts file so it has the right IP number for daq1.


et_start Segmentation fault

Solution: Try removing the file /tmp/et_sys_DAQ.

Cannot open broadcast Handle

Download run failed (UDP?) =

Attached TCP/IP interface to geisc0.                                            
Warning: no netmask specified.                                                  
Attaching network interface lo0... done.                                        
Loading...                                                                      
Error loading file: errno = 0x3c.                                               
Can't load boot file!!                                                          
 

The above was because the computer name was not correct

changed

host name            : localdaq

to

host name            : daq1 


now

-> hostShow                                 
hostname         inet address       aliases                                     
--------         ------------       -------                                     
localhost        127.0.0.1                                                      
roc1             10.1.1.2                                                       
daq1             10.1.1.1          daq1.physics.isu.edu                         
value = 0 = 0x0          

-> roc1 create UDP socket rc UDP host is daq1.physics.isu.edu port is 2052


Turn off Firewall

As super users execute:

/sbin/service iptables stop


Setting up IAC network

as root run the script

/root/IAC_network.sh


Back to DAQ Data_Acquisition