Difference between revisions of "Running CODA"

From New IAC Wiki
Jump to navigation Jump to search
Line 34: Line 34:
 
== Creating run Configurations==
 
== Creating run Configurations==
 
The following describes how to make a run configuration file
 
The following describes how to make a run configuration file
 +
 +
 +
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
  
  

Revision as of 23:29, 20 March 2009

Startup the processes

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

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

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

3.)et_start

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

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


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


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

Prestart

Run

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.

Back to DAQ