|When using the Keck Lab, please leave it as you found it. Specifically,
if you change the settings of any cameras or PCs, please return them to their
original configuration when you are finished. The Keck Lab was not
designed to be reconfigured easily, so removing the cameras from the original
mounts is not recommended. In the past, doing so has resulted in taking
many hours before getting the system working properly again.
All changes to the Keck Lab should be mailed to firstname.lastname@example.org.
Using the tools described on the rest of the page, data acquisition typically consists of the following steps in some similar order:
See the Frequently Asked Questions for resolutions to common problems encountered during data acquisition. If your problem is not listed, then send mail to email@example.com.
The Keck Controller provides a versatile interface for using the cameras in the Keck Lab. It supports the following operations:
To focus a set of cameras:
During operation, the Trigger button reflects the status of the sync signal. When the sync signal is being generated, the button is depressed. The sync signal is automatically controlled by the other operations of the Keck Controller. However, should the need arise, the Trigger button also acts as a manual switch to manually control the generation of sync signals.
The Keck Controller uses the Keck Server, a custom DCOM server running remotely on each Keck PC, to perform the camera operations. The controller makes connections with each of the camera PCs, and sends and retrieves messages and images. The ICamera interface used for the Keck Server is:
In the future, the Keck Server can be customized to perform other tasks (such as locating LED points).
Images can also be captured by executing lc3 remotely on each Keck camera PC to capture images to memory and save them to disk.
lc3 has the following command-line:
c:\bin\lc3 cams num_frames dcf_file save_name
- the cameras used to capture (any combination of the four cameras 0-3)
- number of frames to capture
- the Matrox DCF file to use (es310_60.dcf for frame rate higher than 30, and es310_30.dcf for frame rate 30 and below)
- save location for the captured images, given by the path and sequence name (d:\test\cap would be saved as d:\test\cap.#.####.tif)
- The directory specified need to be created beforehand on each Keck PC used or the operation will fail.
Typically, lc3 is executed in batch to capture from multiple rigs. The batch file lc3_all.bat shows how to use lc3. The general procedure for capturing video is:
The Kodak ES-310 camera parameters are set using the RS-422 bus, which is connected to the keck16 controller via a Blackbox RS485 controller. A HyperTerminal configuration "ES-310" is available on the desktop of keck16. Use HyperTerminal to change camera settings such as exposure (EXE).
Use the LOG command before communicating to any camera (which are numbered 1-64). The document ES310_UM.PDF describes all camera features and parameters, and Patrick's Calibration Notes describes the commonly used parameters.
The PC keck16 has a Quantum 35 GB Digital Linear Tape drive installed, which is used to save and retrieve data from the Keck computers. Use the Backup program to save and retrieve data. The drive transfers data at 5MB/s, so a writing a complete tape takes about 2 hours.
The color cameras in the Keck Lab captures images using Bayer color filter mask as shown below. See the specification for more details.
The ImgTool application performs color interpolation and converts the captured "grayscale" TIF images to true color BMP images.
Select "Auto" to automatically determine whether an image is color or grayscale by using image contrast. Select "Color" to convert to color BMPs. Select "Grayscale" to convert to grayscale BMPs. Check "Remove TIF" to have the original TIF files removed after conversion. Finally, click the "Convert to BMP" button and select all of the TIF images to be converted, and ImgTool will do the rest.
After installing MIL 6.0, you need to install the latest drivers, which are located in "\\degas\archive\cameras\kodak\es310\latest drivers". Once this is done, the ReservedHostSpaceForLcBuffers in genesis.ini should be set to 0x70000. Each computer (keck00-keck15) has 1GB of RAM, and is setup so that the upper 896MB is available for capturing to memory (Windows NT 4.0 uses 128MB). Alternative NT hardware configurations would allow different memory configurations.
The uninstall feature for MIL 6.0 does not remove the genesis and mtxdma drivers. To change the memory configuration, these need to be removed manually using the instsrv (part of the NT Resource Kit, and located on c:\bin in keck00). To remove these drivers, type:
To install the drivers (with 128MB for NT, 896MB for capture), from the c:\genesis\drivers\nt4.0\i386 directory, type:
Note that you need to also update the c:\winnt\system32\genlib.dll file.
There are batch files available in c:\bin\drivers on Keck16 to check and update the drivers:
To make setup of the PCs as easy as possible, we use disk cloning software (DriveImage Pro) to clone keck00 to keck01-keck15.