Difference between revisions of "How to run the RCU - DRORC - Busybox setup"

From ift
Jump to: navigation, search
Line 40: Line 40:
 
You can switch the BC downscaling hex value to a decimal value by right clicking on the value. Rates can also be entered in a more convenient manner than the downscaling factor:
 
You can switch the BC downscaling hex value to a decimal value by right clicking on the value. Rates can also be entered in a more convenient manner than the downscaling factor:
 
<blockquote style="background-color: lightgrey; border: solid thin grey;">
 
<blockquote style="background-color: lightgrey; border: solid thin grey;">
BC downscaling factor is an integer number (32 bits) giving the number of BCs (25ns) between 2 triggers.
+
BC downscaling factor is an integer number (32 bits) giving the number of BCs (25ns) between 2 triggers.<br>
Examples:
+
Examples:<br>
0  -> BC rate (40 Mhz)
+
0  -> BC rate (40 Mhz)<br>
1  -> 40/2 Mhz rate
+
1  -> 40/2 Mhz rate<br>
4000-> generate 1 Start signal per 100 micsecs
+
4000-> generate 1 Start signal per 100 micsecs<br>
...
+
...<br><br>
or use: s (seconds, ms (miliseconds, us (microseconds), for period or:
+
or use: s (seconds, ms (miliseconds, us (microseconds), for period or:<br>
hz (hertz), khz (kilohertz), mhz (megahertz) for rate.
+
hz (hertz), khz (kilohertz), mhz (megahertz) for rate.<br>
3s    -> 3 seconds
+
3s    -> 3 seconds<br>
10 ms -> 10 miliseconds period
+
10 ms -> 10 miliseconds period<br>
3 khz -> 3 khz rate
+
3 khz -> 3 khz rate<br>
 
</blockquote>
 
</blockquote>
  
 +
= Busybox stuff =
 +
From the busybox DCS board, you find some bitfiles to program and setup the Busybox under:
 +
/mnt/kjekspc7/rbo021/busybox_files.
 +
You can program the busybox with the program.sh script:
 +
./program.sh busybox_fpga1.bit busybox_fpga2.bit
  
 +
If you ommit the second bitfile, a dummy bitfile is used and only 1 FPGA programmed.
  
 +
= Datataking with date =
 +
#Start date from the drorc machine as date user with the command: 'startdate'.
 +
#Take the lock by clicking on the white open lock symbol.
 +
#Click on the right arrows until the 'Ready to start' is highlighted, and the button underneath is clickable.
 +
#Click on Start processes. On the LDC display, the green icon should move down to the point 'Waiting start of data',
 +
and the LDC status display should reset its numbers, then show 2 Sub-events recorded. These are the Start of Run Events.
 +
#Then press start.
  
= Busybox stuff =
+
#You then can send triggers from the LTU with the CTP emulator.
  
= Datataking with date =
+
#The procedure is always: Start run, Start sending triggers, Stop sending triggers, Stop run.
 +
If you send triggers while there is no run, the Events remain in the RCU and are not being read out, which makes the run the stuck and the RCU will have to be reset. The Busybox has to be reset between each run anyway with the bbinit.sh script.

Revision as of 08:04, 29 May 2009

How to run the RCU - DRORC - Busybox setup

This shall be a step by step introduction on how to operate the setup and test Busybox firmware. For now this will be a collection of the necessary steps, but in a later stage the configuration part will become more automated.

You need access to the following systems: - DRORC PC - RCU - Busybox - Local trigger unit (LTU)

Setting up the system and getting ready to take data:

More general stuff

  1. Log into the Drorc machine as the date user.
  2. Log into the LTU: "ssh -X ltu@vme1".
  3. Log into the RCU dcs board: "ssh dcs0031".
  4. Log into the Busybox DCS board: "ssh dcs0055".
  5. Start the infoBrowser on the drorc machine with the command "infoBrowser".

Configuring the RCU

On the RCU, execute the script /etc/boot/S40configure.sh. This does several things: - turning on the Front End Cards - Setting the correct L2 Latency - Switching to LTU trigger

Then, as the date user from the drorc machine, execute the alias 'conf-fec'. This configures the RCU and FECs via the DDL for Data readout, but unfortunately also for Software triggers.

Therefor, execute the S40configure.sh script on the dcs0031 once again.

LTU stuff

On the LTU, execute 'vmecrate ltu'. This should pop up two windows on your machine. In the ltu window, click on Configuration-> TTCInit, and then Configuration->LTUInit. Click on 'CTP Emulator' to open the CTP Emulator window. Click on 'click here to choose sequence', and choose the 'L2a.seq'. Don't forget to click 'Load sequence'.

Sending triggers: After you clicked on 'start emulation' you can send triggers in two ways: - Single triggers, for this just click on 'Generate SW Start signal(s)'. - Or triggers with a certain rate. For this, click on 'not selected' and choose BC. You can switch the BC downscaling hex value to a decimal value by right clicking on the value. Rates can also be entered in a more convenient manner than the downscaling factor:

BC downscaling factor is an integer number (32 bits) giving the number of BCs (25ns) between 2 triggers.
Examples:
0 -> BC rate (40 Mhz)
1 -> 40/2 Mhz rate
4000-> generate 1 Start signal per 100 micsecs
...

or use: s (seconds, ms (miliseconds, us (microseconds), for period or:
hz (hertz), khz (kilohertz), mhz (megahertz) for rate.
3s -> 3 seconds
10 ms -> 10 miliseconds period
3 khz -> 3 khz rate

Busybox stuff

From the busybox DCS board, you find some bitfiles to program and setup the Busybox under: /mnt/kjekspc7/rbo021/busybox_files. You can program the busybox with the program.sh script: ./program.sh busybox_fpga1.bit busybox_fpga2.bit

If you ommit the second bitfile, a dummy bitfile is used and only 1 FPGA programmed.

Datataking with date

  1. Start date from the drorc machine as date user with the command: 'startdate'.
  2. Take the lock by clicking on the white open lock symbol.
  3. Click on the right arrows until the 'Ready to start' is highlighted, and the button underneath is clickable.
  4. Click on Start processes. On the LDC display, the green icon should move down to the point 'Waiting start of data',

and the LDC status display should reset its numbers, then show 2 Sub-events recorded. These are the Start of Run Events.

  1. Then press start.
  1. You then can send triggers from the LTU with the CTP emulator.
  1. The procedure is always: Start run, Start sending triggers, Stop sending triggers, Stop run.

If you send triggers while there is no run, the Events remain in the RCU and are not being read out, which makes the run the stuck and the RCU will have to be reset. The Busybox has to be reset between each run anyway with the bbinit.sh script.