| Line 3 was replaced by line 3 |
| - !RUN or DRIVE |
| + !I know how to change this particular parameter in the SEA client, but how do I set it from a batch file in SICS? |
| At line 4 added 5 lines. |
| + Change the value in SEA and look what command is logged in the Input/Output history. |
| + You can use the command as it is in a SICS batch file. |
| + |
| + !Should i use ''run'' or ''drive''? |
| + |
| Line 10 was replaced by lines 15-24 |
| - with ''new_value'' as target. |
| + with ''new_value'' as target, but does not wait for success. The run command has |
| + a caveat though: It keeps monitoring the drivable_object. As soon as you give a |
| + blocking command like drive or scan, it will wait for the temperature to arrive at the |
| + target value. |
| + |
| + If you wish to perform scans while waiting for the sample environment to arrive at a certain state, |
| + the right procedure is to set the drivable_object tolerance to a high value and then run the drivable |
| + object. This will trick SICS into believing that the target value has already been reached. Do not forget |
| + to set the tolerance to a reasonable value gaian if you expect SICS to wait for a SE variable change to |
| + actually happen. |
| Lines 19-20 were replaced by lines 33-34 |
| - \\{{> temperature maxwait}} ''(the maximum time [[sec] to wait until the drive commend quits)'' |
| - \\{{> temperature settle}} ''(the time [[sec] to spend after beeing within tolerance before the drive command quits)'' |
| + \\{{> temperature maxwait}} ''(the maximum time [[sec] to wait until the drive command quits)'' |
| + \\{{> temperature settle}} ''(the time [[sec] to spend within tolerance before the drive command quits)'' |
| At line 22 added 4 lines. |
| + It is not recommended to put a zero value for {{temperature settle}}, as |
| + the drive command will quit when the temperature is for the first time |
| + within tolerance, and the temperature may over- or undershoot. |
| + |
LIN