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

From ift
Jump to: navigation, search
m
Line 13: Line 13:
  
 
# Log into the Drorc machine as the date user.
 
# Log into the Drorc machine as the date user.
# Configure the RCU with the conf-rcu alias. This sets up the RCU and configures the Front End Cards (FECs).
+
# Log into the LTU: "ssh -X ltu@vme1".
# Execute the /etc/boot/S40... script on the RCU-DCS. This changes the trigger from a software trigger to the DCS trigger intput.
+
# Log into the RCU dcs board: "ssh dcs0031".
 +
# Log into the Busybox DCS board: "ssh dcs0055".
 
# Start the infoBrowser on the drorc machine with the command "infoBrowser".
 
# Start the infoBrowser on the drorc machine with the command "infoBrowser".
# Start date with the command "startdate".
 
# Log into the LTU: "ssh -X ltu@vme1".
 
  
This is the general setup and configuration done. Continue with the the setup of the LTU.
+
= 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.
  
= RCU stuff =
+
Therefor, execute the S40configure.sh script on the dcs0031 once again.
  
 
= LTU stuff =
 
= 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:
 +
<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.
 +
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
 +
</blockquote>
 +
 +
 +
  
 
= Busybox stuff =
 
= Busybox stuff =
  
 
= Datataking with date =
 
= Datataking with date =

Revision as of 07:52, 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

Datataking with date