|
Q - What do I do when I lose my Camera Driver
Files?
A
- a) Download the relevent files from this site on the relevent
camera page
A - b) Contach heat Inc and request an new Camera Driver CD
|
|
Q - Is it possible to query the integration
time from the camera?
A
- Most units ship at a set integration time and this will not vary
from unit to unit. There is not an easy way to query integration
time outside of the factory.
|
|
Q - Is it possible to set the integration time?
A
- There is not an easy way to set integration time outside of the
factory.
|
|
Q - Is it possible to read the shutter temperature?
A
- Yes - The shutter temperature can be read by sending: shut:temp?
|
|
Q - Is it possible to command the frame rate
other than with the BitFLow camerafile?
A
- Frame rate is not a variable in the M series setup. The external
output is 60Hz progressive. The ability to make minor precision
phase changes to pixel rate due to digital genlocking is not a change
of frame rate but more a phase lock loop adjustment to ensure pixel
lock and spatial correspondence.
|
|
Q - Is it possible to command the camera to
output a different bit depth (something other than through the BitFlow
card)?
A
- The bitflow has no direct impact on the bit depth other than via
the serial port embedded in CL. The modes are 0,1,2,3. That is the
only way to control the bit depth and the command is sent directly
to the M series. The M series serial port can be accessed directly
as an RS485 serial command string. If a customer wishes to control
the camera via a separate port there is extensively no difference
but it is not a supported mode of operation as HEAT Inc has any
control of the customers implementation.
|
|
Q - Camera integration - M Series : Is there
any way we can manually control when the camera integrates? Are
their any flags in the telemetry that indicates the start and end
of integration? We need to synchronize other instrument processes
with the start of integration
A
- The M series integration time could be controlled by adjusting
some of the FPGA registers. The integration is done one detector
row at a time. For a VideiIR 640M FPA there are 480 integration
cycles each 1/30th of a second frame time. For a VideiIR 320M FPA
there are 240 integration cycles each 1/60th of a second frame time.
It would be possible to determine what the timing relationships
are between the LVDS horizontal sync and the start and stop of integration
of a VideiIR 320M. The VideiIR 6400M would be harder because of
the 30 to 60 Hz conversion. This would require Factory personal
interaction as any integration time modification is usually factory
adjustment only
|
|
Q - Output format - M Series : What is inserted
in the extra pixels and frames coming out of the VideoIR 320M? Are
the pixels an average of the nearest neighbors or determined some
other way?
A
- The extra pixels may be interpolated or replicated. This choice
is determined by a configurable setup parameter. Most M series cameras
are configured for bi-linear interpolation. In bi-linear interpolation,
the interpolated pixels are the average of the 2 nearest or the
4 nearest pixels.
|
|
Q -
A
-
|
|
Q -
A
-
|
|
Q -
A
-
|
|
Q -
A
-
|
|
Q -
A
-
|
|
Q -
A
-
|
|
Q -
A
-
|
|
Q -
A
-
|
|
Q -
A
-
|
|
Q -
A
-
|
|
Q -
A
-
|
|
Q -
A
-
|
