Hardware manual

Troubleshooting Impact Reference Guide
Datalogic Automation Inc. 6-44
Troubleshooting
Issue: Bad Image Event
A Bad Image Event generates a System Log entry with details of the detected error. It also generates a Bad
Image Event Trigger (see “Trigger Event Types” on page 3-35).
Things to check
• Buffer Overrun – This results from triggering the camera so fast that images are acquired more
quickly than the task can process them. That is, the task processing time is consistently longer than the
time between camera triggers. This situation will eventually cause the camera to run out of image buf-
fers.
 Slow down the triggering rate
 Decrease task execution time by optimizing the inspection
• Trigger Overrun – This results from triggering the camera to acquire an image while it is still in the
process of acquiring the previous image. This can be the result of a “bouncy” or noisy trigger signal.
 Use a cleaner trigger signal source
 Adjust the Input Debounce time. See “Input Debounce” on page 2-8.
• Bad cabling or interference – If the DSL cable is bad or there is Electromagnetic Interference (EMI)
coupling with the DSL cable, multiple camera triggers can be generated or the acquired image can
become corrupted.
 Replace the DSL cable
 Remove the EMI source
 Be sure all electrical grounds are securely connected
• Noisy power – A noisy power supply to the camera could generate extra triggers or degrade the DSL
connection.
 Replace the power supply
 Be sure all electrical grounds are securely connected
Issue: System Overrun
A System Log entry "System overrun: out of image buffers" is displayed.
Things to check
• This results from images occupying multiple image buffers and not releasing them.
 The inspection task may contain image processing tools that do not process the current image. If
the task branches around image processing tools, the tools that processed the previous image, but
do not process the current image, will continue to reference the previous image and keep its buffer
occupied. If this happens for many tools, i.e. holding references to several previous images because
there are tools that have not run for several triggers, several buffers can remain occupied.
Issue: The Image Display in VPM does not refresh
When the system is online and receiving triggers, the image display will freeze and the current images are
not displayed.
Things to check
• This results from triggering the camera so fast that images are acquired more quickly than they can be
displayed. That is, the task processing time is consistently longer than the time between camera trig-
gers.