User Tools
hardware:mark5.conditioning
This wiki is not maintained! Do not use this when setting up AuScope experiments!
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hardware:mark5.conditioning [2012/08/03 14:43] Moblas people |
hardware:mark5.conditioning [2012/09/05 05:22] (current) Moblas people |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| Conditioning performs a read/write cycle over the set of disks and identifies and isolates bad sectors. | Conditioning performs a read/write cycle over the set of disks and identifies and isolates bad sectors. | ||
| - | To Condition a module: | + | **__To Condition a module:__** |
| - | Place the module in Bank A leaving Bank B empty or unlocked. | + | Place the module in Bank A **(Leave Bank B empty or unlocked)**. |
| On a terminal window on the ops1xx pc enter: <code> | On a terminal window on the ops1xx pc enter: <code> | ||
| Line 10: | Line 10: | ||
| to log onto the Mark5B where xx = yg, ke or hb. Then ensure Dimino is not running by typing:<code> | to log onto the Mark5B where xx = yg, ke or hb. Then ensure Dimino is not running by typing:<code> | ||
| Enddim </code> | Enddim </code> | ||
| - | Start the conditioning program with or without logging: | + | Start the conditioning program:<code> |
| - | - Without logging: <code> | + | ./condition "logfile" </code> where "logfile" is the output log file for SSErase - usually use the modules vsn for the logfile name. eg: **//./condition HOB+0061//**. The logfile will be placed in ./scripts/. |
| - | SSErase -m0 -c1 </code> | + | |
| - | - With a log file: <code> | + | |
| - | ./condition "logfile" </code> where "logfile" is the output log file for SSErase - usually use the modules vsn for the logfile name. eg: ./condition HOB+0061. The logfile will be placed in ./scripts/. | + | |
| The program will mention this is going to take a long time (see [[hardware:mark5.conditioning.times | Conditioning times]] ) | The program will mention this is going to take a long time (see [[hardware:mark5.conditioning.times | Conditioning times]] ) | ||
| - | and ask you if you are sure you want to do this - answer "y". | + | and ask you if you are sure you want to do this but it won't wait for an answer - it will start automatically. |
| + | After many seconds, you should see the program output its first line of info. | ||
| + | When the routine completes , it will say how many seconds it took - **note this, to write on the side of the module**. Ensure the time taken is close to normal for that size module - if it is radically different - try conditioning the module again. | ||
| + | |||
| + | If the script gets in a real tangle, you can usually ctrl-c it and then reset the Mark5 with: <code> SSReset </code> and try again. | ||
| + | |||
| + | It is a good idea to do some [[hardware:mark5.conditioning.postconchecks | post conditioning checks]] | ||
| + | |||
| + | Mark5B manual is here : http://www.haystack.mit.edu/tech/vlbi/mark5/docs/Mark%205B%20users%20manual.pdf | ||
/home/www/auscope/opswiki/data/attic/hardware/mark5.conditioning.1344005003.txt.gz · Last modified: 2012/08/03 14:43 by Moblas people
Page Tools
