SU640CSX
4110-0462, Rev. B
Page 89 of 97
© 2016 UTC Aerospace Systems
Date Printed: 1-Dec-2016
This document does not contain any export controlled technical data.
7.
Product Support
Common Problems and Solutions
Problem Possible
Causes
Solution
No data is present at the
digital port, frame grabber
times out
Power is off or low
Verify input power meets requirements described.
Connections to camera
are fully or partially
disconnected.
Verify cameras wiring is properly connected.
Camera is in external
trigger mode, but not
receiving a trigger
Test the camera in internal trigger mode
(
TRIG:MODE 0
) to confirm normal operation. If
internal trigger mode operation is normal, see
“Camera is not responding to trigger input.”
Camera will not respond
to trigger inputs
Trigger source is not
connected
Verify trigger is properly connected. Verify frame
grabber trigger source is properly configured if
using Camera Link CC1.
Trigger signal does not
conform to timing
requirements of the
camera
Verify trigger source meets the timing
requirements described in Section 5.12. Check
camera error status for a trigger or scan error. If
oscilloscope is available, view the trigger input
signal to verify it meets the requirements of the
camera for the selected trigger mode.
Trigger Logic Levels
Incorrect
Verify camera logic levels match logic being sent.
Camera intermittently
responds to triggers,
resulting in missing
frames, or in some cases
timeout errors
Trigger period is too
short, causing following
triggers to be ignored as
they occur during readout
Check camera error status for a trigger or scan error
(>ERROR? ON). Modify trigger to meet timing
requirements for the selected trigger mode and
supported FPA.
Frame grabber software
reports not receiving
enough data before timing
out
Acquisition size
parameters larger than
actual data available
Reduce acquisition window size parameters,
decrementing one pixel or line at a time. Some
frame grabbers require overhead pre- or post-valid
pixels or lines to properly grab the digital data.
