Up: Troubleshooting Previous:Run Control: disconnecting

Run Control: Other Comments

  1. The Run Control process is independent of MiniDAQ and Slow Controls. As such, it can be killed and re-started without stopping a run in progress.
  2. Run Control is built on a layer of applications, all of which have time-outs. If network traffic is heavy, some steps (e.g. initializing and configuring) may succeed once and fail later, for no apparent reason. (This was observed already with MiniDAQ's ability to access the table server.)
  3. Run Control, as a Java application, is color-table intensive, presenting possible conflicts with other applications.

Written: November 27, 1996 by Eugene Yee and Nathan Stone
Modified: January 27, 1997 by Eugene Yee
Last modified: July 8, 1997 by R.Bossingham

Page maintenance:

Roy Bossingham, LBNL