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>.

The first command to be called is one of:

  controller <protocol> <protocol parameters...>
  controller std [sendterminator=...] [timeout=...] [replyterminator=...] [lineseparator=...]
  controller bin <crc-algorithm> <timeout>

Defaults are:

  sendterminator=\n
  timeout=5
  replyterminator=   (means CR/LF or any combination)
  lineseparator=     (means no multiline responses are expected)

The return value is 1 when the controller was created, 0 when it existed already (the return value may be needed if several object share the same controller, and the initialization of the controller properties have to be done only once).

Other protocols than std and bin might be programmed in the core SICS code, in fact there are already a couple of them made by Mark Koennecke. For some needs, it might be easier to enhance the std or bin protocol.