| Lines 5-9 were replaced by lines 5-7 |
| - 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. |
| + of initialization and action scripts. The action scripts |
| + are called from the ScriptContext system within a certain |
| + context: a sics hipadaba node and a controller object. |
| Line 11 was replaced by line 9 |
| - !Initialization Script |
| + !Tutorial |
| Lines 13-14 were replaced by line 11 |
| - The scripts should be placed in a |
| - file with a path {{~/sea/tcl/drivers/<driver-name>.tcl}} |
| + * [A simple driver example] |
| Lines 16-38 were replaced by line 13 |
| - 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'' |
| - |
| - {{{ |
| - 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" |
| + !Reference |
| Lines 40-41 were replaced by lines 15-16 |
| - } |
| - }}} |
| + * [initialization commands|StdSctInitCmds] |
| + * [standard action scripts] |
| Removed lines 43-44 |
| - In this example no action scripts have to be defined, |
| - only scripts from stdsct.tcl are used. |
| Removed line 46 |
| - ''Explanation, line by line'' |
| Line 48 was replaced by line 20 |
| - {{controller std sendterminator=\r timeout=5}} |
| + ---- |
| Lines 50-51 were replaced by line 22 |
| - The controller object is defined, specifying the characteristics |
| - of the protocol. |
| + to be done |
| Lines 53-70 were replaced by lines 24-26 |
| - {{controllerDesc "LakeShore 336 controller"}} |
| - |
| - A description of the controller object. |
| - |
| - {{prop startcmd "*IDN?"}} |
| - |
| - The command prop creates a property to the last defined |
| - node, which is in this case the controller node. |
| - The property startcmd defines a command which is sent |
| - after initialization. Ideally this is a command requesting |
| - the instrument type, software version number and possibly |
| - a serial number. |
| - After an interruption of the connection, this command is sent |
| - again in order to check that the device is still the same. |
| - |
| - {{obj LS336 -float rd}} |
| - |
| - This creates the object |
| + 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. |