next up previous contents
Next: Problems with spectral scans Up: Troubleshooting Previous: Clock interface   Contents

Error: no input for dig32

If you start a scan but no scan lines get done, and you see an error no input for dig 32 rolling by on the terminal window from whence you launched IDL, then you are likely missing the clock pulses. The most likely cause is the cable from the DIG80 to the clock interface. In particular, check the cable at the DIG80 end, where stress on the ribbon cable sometimes pulls it out of the connector a bit.



Tobias Beetz 2001-04-23