Testing Controllers with CCD Tool
CCD Tool requires an SBUS interface to the SDSU controllers.
There are two machines available for this, LPSS11 in the WHT detector lab and Lothian at SLO.
Additionally operational DAS machines could be used for offline testing of controllers, using remote login. One must be very careful here since CCD Tool does not use the detector ID code to prevent download to the wrong camera. Be careful that the DAS machine you log into does not have an operational camera attached. The best way to check this is to read the value in utility board address Y:$00 using the RDM command in CCD Tool. The lower two nibbles will give you
the ID code of the currently connected camera, a value of $FF indicates that no camera ID connector is attached.The controller and camera should be connected up as follows : (
jpg image) (PowerPoint)CCD Tool should be run-up from with the
/home/dspdev/ccdtool directory. On some machines it will crash if run from elsewhere. A suitable setup file for CCD Tool (one that identifies the CCD dimensions as well as the location of the download timing and utilty files) can be found at /home/dspdev/ccd/tim/tek2/setupA.setup . This file will configure the controller with TEK2 clock and bias voltages and allow the operation of the controller to be checked with an oscilloscope.Link showing expected voltages from the TEK2 controller
The WHTWFC cannot be tested directly using CCD Tool. uDAS treats the camera correctly as a 2 chip mosaic with each chip contains 2154 columns. CCDTool can be configured to deal with a single chip with two outputs and so emulate the mosaic , but changes are required to the chip dimensions in timwfc.asm. It is recommended that the WHTWFC only be used under uDAS. The controller can still be tested using CCDTool but cannot be used for imaging.
CCDTool is quite unreliable and may occasionally require power cycling of the attached controller and restarting of the program.
|
|
|
|||||