Re: Software triggering a PCDig

["M.Stein" <matthias@gom.com>]

On Fri, 31 Mar 2000, Will Lockhart wrote:

> 
> The readout time is absolutely determined by the width of the camera
> array (2048 pixels) and the frequency of CCLK. So EXSYNC governs the
> exposure time and this must be longer than the readout time (plus some 
> overhead). Although the PCDig documentation says that the PRI output
> is used to control exposure time on Dalsa cameras (we are using a
> Dalsa), the camera I have does not have independent exposure control - 
> in other words, the line rate controls the exposure time.
> 
> Will
> 

But if the camera is only readout, when the next frame (line) is being
exposured, than you can drive the camera only in a continuous mode,
because you need more than one frame (line) to get a valid image.
Am I right?

Do you get a valid image, when set to EXSYNC_FREE_RUNNING? Perhaps you
have to outwit driver a little bit (the driver calculates the exsync
cycle time by adding EXSYNC_PERIOD_TIME and *MIDPOINT_DELAY - the naming
is wrong, but config file compatibility is all), setting the 
*MIDPOINT_DELAY to a small value, but not to zero.


					matthias