skc
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| skc [2021/11/25 03:11] – mbrohart | skc [2024/01/30 13:10] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| === Continuous (scheduled) Operation === | === Continuous (scheduled) Operation === | ||
| - | SKC allows an operating schedule, created by the SE command, to be run continuously - | + | SKC allows an operating schedule, |
| - | that is, at the end of the local day a set of summary records is produced (see ED), and the | + | When SKC is ran, it will create a copy of the OP_ST.### to OP_ST.000 as backup as of version 6.2\\ |
| - | schedule waits for the beginning of the next day and the schedule starts again. | + | That OP_ST.000 will then be copied in to the OP_ST.### in during an [[re|RE]] in case of corruption. |
| - | See also Section 8, and the SE and SK commands. | + | |
| + | See also Section 8 of the Brewer Operators Manual, [[sk|SK]] and [[se|SE]] commands. | ||
| - | This routine name stands for schedule, continuous mode. The command is used to input the desired schedule to be used by the instrument for the day.\\ | ||
| - | The schedule is then __continuous__ in that it is restarted the following days. | ||
| ===== Usage ===== | ===== Usage ===== | ||
| Line 16: | Line 14: | ||
| ===== List of schedule used by ECCC ==== | ===== List of schedule used by ECCC ==== | ||
| - | * calsc | ||
| * CAL | * CAL | ||
| + | * calo3 | ||
| + | * calsc | ||
| * calzs | * calzs | ||
| + | * clscnouv | ||
| + | * ecdiag | ||
| + | * eceo | ||
| * eceu | * eceu | ||
| * ecnouv | * ecnouv | ||
| * ecsc | * ecsc | ||
| * idle | * idle | ||
| - | * mb | + | * inside |
| * s60mk2 | * s60mk2 | ||
| + | * s60mk2nv | ||
| * s60mk3 | * s60mk3 | ||
| * spmoon | * spmoon | ||
skc.1637809885.txt.gz · Last modified: 2021/11/25 03:11 by mbrohart