mar345 Program Manual | 3 6 |
______________________________________________________________________________________
6. Troubleshooting
Both the computer and the scanner can produce fatal errors and warnings. All messages are numbered. Messages with message numbers < 1000 come directly from the scanner controller and are potentially serious. Message numbers >= 1000 are generated by program mar345 and may be a consequence of a controller error or some other kind of malfunctioning or warning.
If you don’t know how to fix a scanner problem, contact marresearch. We will usually ask you right away to send us the mar.spy file and the mar.log file where the error occured (see chapter 2.3) since they contain almost all information we need.
The following error messages >= 1000 are produced by program mar345:
_______________________________________________________________________
No. Description
_______________________________________________________________________
1000 | Message: | "Error sending command to mar controller" |
| Reason: | Network connection to scanner interrupted. |
| Action: | Reboot scanner. Check cables. Try "ping mar345". |
1001 | Message: | "SERVO system cannot be INITIALIZED" |
| Reason: | Severe hardware problem. |
| Action: | Call. |
1010 | Message: | "Waiting for X−rays..." |
| Reason: | The X−ray intensity as read from the ion. chamber has |
|
| dropped below the critical level (see configuration file: |
|
| INTENSITY MIN xxx). The next exposure starts only |
| Action: | after the X−rays are back. |
| Check generator, monochromator or collimator. | |
1020 | Message: | "Not enough disk space left on device. Aborting data collection" |
| Reason: | Disk full. |
| Action: | Clean up disk. |
1030 | Message: | "The Image Plate has been exposed to X−rays" |
| Reason: | A running exposure has been aborted. |
| Action: | Erase plate and continue. |
1040 | Message: | "X images have been successfully retaken" |
| Reason: | Some images had to be retaken due to hardware problems, |
| Action: | possibly shutter. |
| Carefully check log file for learning more about the reasons. |
_______________________________________________________________________
