Last update: February 5, 2003 by Nazim Khan

What to do if Labview Is Unresponsive on Plasmon:

If labview freezes up, kill it by selecting "end process" on the Windows Task Manager.  To restart all the labview vi's, follow the steps below.  The shortcuts to the 5 vi's that you need to start are located at the top of the plasmon desktop.  If you need more info about a specific vi, click the appropriate link below.

1. Double click the HV Control v3.1 vi, and then hit the white arrow in the upper left hand corner of the VI.  Wait a ~10 minutes while it loads the voltages from the mainframe.  The settings should then be the same as before labview started acting up and turned on sensors in the STATUS grid will then turn green. READ NOTE BELOW.
2. Double click the Camac Controls vi and then hit the white arrow in the upper left hand corner of the VI.  After waiting a minute or so the settings should be the same as before labview started acting up.
3. Double click the PaddleCrateMonV8 vi.  Click the run continuously button .
4. Double click the PCMAlarmSender_V6.2 vi.  Now choose PCMAlarmSender.vi on the menu that pops up by selecting it and hitting OK.  Then push the run continuously button .
5. Double click the AlarmSender vi.  Select AlarmSender.vi from the menu that pops up.  Click on the little white arrow to start the vi.

Notes:

• The Big Blue Button "Retrieving Data From Mainframe" will disappear only when the loading of values is finished and all turned on sensors show up green in the STATUS grid. Even after the Big Blue Button disappears, due to the slow speed of labview,  the vi will still be locked out and it will take a further ~1min before the lock out is turned off. Please be patient: When "Main" and "Null" is visible in the text boxes below the "CONTROLS" panel then mouse clicks will definitely be effective.
• It's okay to continue taking data while you're restarting the vi's.  HOWEVER, if one or more of the HV channels tripped while you were restarting, then you must invalidate all the sequences taken since labview froze.
• Please note in the logbook what was going on when labview crashed (e.g., beam conditions, tripped HV channels, nothing at all, etc.).  This will help us diagnose the problem.

If you still have problems getting labview to work, call a Tof or Trigger expert.

Go to the TOF documentation for the online version of this document.