Difference between revisions of "Running CODA"
Line 24: | Line 24: | ||
= debug FAQ= | = 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 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. | ||
Line 47: | Line 47: | ||
value = 0 = 0x0 | value = 0 = 0x0 | ||
− | + | == Incorrect number Argument when downloading == | |
− | |||
daLogMsg: Downloading configuration "SIS3610" | daLogMsg: Downloading configuration "SIS3610" | ||
Line 56: | Line 55: | ||
I had incorrectly connected my EB to my ER system | 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...". | ||
[http://www.iac.isu.edu/mediawiki/index.php/Data_Acquisition Back to DAQ] | [http://www.iac.isu.edu/mediawiki/index.php/Data_Acquisition Back to DAQ] |
Revision as of 22:11, 31 October 2007
Startup the processes
Start the following programs in the order below and in different xterm windows
1.)msqld 2.)minicom
- 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
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
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...".