How to Recover the system.

for most common wierd behaviours go to the bottom of these instructions.

Dont Stop any pvss project. The system is now based on at least 2 projects operating together. One of them is used to configure the tell1s and the Velo control board and beetle chips, another one is used to configure the tfc system and the third one is used to configure the the runcontrol. The Runcontrol is not yet quite operational so for the moment I suggest to use the 2 essential ones.

supposing that you restarted the pvss projects for any reason, you should go to the Device editor navigator of each project, run it if it's not running (you can find it on the pvss console for each project) go to FSM tab, do stop all fsm and start all fsm. you can do it even twice just to be sure.

follow also these instructions if the fsms got somehow blocked.

click on the top level with the right click to view the fsm panel that you are interested on.

on ACDC3 project you can start the acdc3Tell1Control (right click -> view)

on the TFC you can start the same way the tfc control. that will give you the tfc panel, you should navigate down always with double clicks on the name of the State machines.

try to reach the partition odinv2_02. look for the recipe ACDC3_Lat133_extTriggers recipe. select it and on the fsm (the coulored button) click configure.

wait until it's configured.

to reconfigure the tell1s click on the toplevel, ACDC tell1 control and do reset if they show ready state, or do configure if they are in not ready state. dont do load Firmwarebe cause that will require a reboot of the crate.

the system should then be configured. start the event builder on the receiving PC.

ssh daq@lbh8lx02 with lhcbdaq as password

do source setupdaq

use the alias takedata to the script takedata.sh to take data.

do it like this:

takedata

the string will be the prefix given to the files.

go to the tfc and start the run. check if the event builder receives events.

it should start writing the files....

Most common weird behaviours:

if no event arrives, there must be something wrong.

check if the tfc is sending triggers. the counters should be updating...

check if all the green lights for the states of auxiliary trigger, odin front end. trigger type broadcast and destination assignments are on.

if not stop the run, click on the tickboxes and make sure it's ok.

if you still doesnt receive any events, try stopping the run, log in to the tfc@odinv202 (should be an expert to do that),

do source setupOdinVelo.sh

reload the recipe on odin and reset and reconfigure the tell1s.

you can try to sudo tethereal -ieth1 to check if ip packets are coming.

if the Odin sends triggers but no events arrive at the pc and no packets come on the sudo tethereal -i eth1, try go to the daq switch and have a look at the leds indicating the net transmission. if the left is off it means that the link is down and the interface is somehow broken. the right one indicates trafic and blinks accordingly to how many events you acquire... so it should blink together with the spill.... if it doesnt blink, check if the tell1 receives triggers, tru to use the tell1 console for that... connect to the ccpc as velo. velo@pctell25 for instance. be a velo expert to go in. type ./startConsole, then try to use d, for detector special and then m for monitoring the adcs on the memory. then look at the raw adcs, check if the values change when triggers are coming. so it means that the tell1 receives triggers.

if that happens and no packets arrive to the pc try reinitializing the ethernet interface of the pc. in the place that you are acquiring data, try to execute the command sudo service network restart

wait and use tethereal again. if the packets come, the events will most likely be able to be built.

you can also try to look at the switch and see if the lights connected to the green cables are flashing with some frequence, when the spill comes. if not that's funny (strange) it may be that the switch got blocked, call me.

check if the tell1s have happy leds on the back of them.

check if the credit card pcs are alive (ping them)

check if the pvss log doesn show something to bad (it often does and that doesn mean much)

i dont know any other funny (not haha) states. try rebooting the crate and restarting the pcs and read this from the top smile (there should be in principle no reason to do that)

Remember that this will kill the temperature readout and also the module configuration.

-- KazuyoshiAkiba - 10 Nov 2006

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2006-11-12 - KazuyoshiAkiba
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback