ScriptContext in SEA

ScriptContext describes a system for asynchronous drivers in SICS/SEA written in Tcl. Such a driver is a collection of configuration and action scripts. The action scripts are called from the ScriptContext system with in a certain context: a sics hipadaba node and a controller object. The access to the context is implemented with the sct command.

Initialization Script

The scripts should be placed in a file with a path ~/sea/tcl/drivers/<driver-name>.tcl

If different drivers share common code, the common code may be placed in ~/sea/tcl/common/. The individual drivers may then contain only an appropriate source command.

The initialization script must have the name stdConfig::<driver-name>.

Example of an initialization script

In this example no action scripts have to be defined, only scripts from stdsct.tcl are used.

controller std sendterminator=\r timeout=5
controllerDesc? "LakeShore 336 controller"
prop startcmd? "*IDN?"

obj? LS336 -float rd
prop readcmd? "KRDG?A"
prop readfmt? "%g"
kids? "LS336 settings" {
node? set -float wr
prop readcmd? "SETP?1"
prop readfmt? "%g"
prop writecmd? "SETP 1,%g" }

The first command to be called is controller: As terminator for commands CR is used, and a timeout of 5 sec is specified.