Abstract:
This invention provides a trigger for a vision system that can be set using a user interface that allows the straightforward variation of a plurality of exposed trigger parameters. Illustratively, the vision system includes a triggering mode in which the system keeps acquiring an image of a field of view with respect to objects in relative motion. The system runs user-configurable “trigger logic”. When the trigger logic succeeds/passes, the current image or a newly acquired image is then transmitted to the main inspection logic for processing. The trigger logic can be readily configured by a user operating an interface, which can also be used to configure the main inspection process, to trigger the vision system by tools such as presence-absence, edge finding, barcode finding, pattern matching, image thresholding, or any arbitrary combination of tools exposed by the vision system in the interface.

Description:
FIELD OF THE INVENTION 
     This invention relates to vision systems and more particularly to automated trigger functions in a vision system. 
     BACKGROUND OF THE INVENTION 
     Machine vision systems are used in a wide range of manufacturing processes. Among other uses, machine vision is employed to ensure quality and to assist in the constructing various articles and devices. A common use for vision systems in industrial applications is in association with an inspection or assembly location on a moving production line. Images of objects are acquired as they pass under the vision system camera&#39;s field of view. Based upon image data acquired, the vision system can decide whether there is a flaw in the object, determine its alignment for further processes, operate a robot manipulator, identify and sort the object into an appropriate bin, or perform other automated tasks. 
     In a typical implementation, the triggering of image acquisition by the vision system is performed according to an external modality. For example, the drive system for the moving line can include an encoder that triggers after a certain number of pulses that are associated with line movement. Likewise a photoeye/photodetector can be used to sense the presence of an object arriving at the field of view. The camera receives a trigger signal from the photoeye to acquire the image at this time. This approach entails additional hardware and has limited ability to modify the conditions for triggering. Such modifications can be desirable in certain applications—for example, where a photoeye cannot be conveniently mounted near the field of view, or has a disadvantageous view of the object. 
     Some vision systems provide a native image-triggering mode within the camera assembly. However, even when a system has such a native image triggering mode, that mode is typically very rigid such that if a user desires to apply even a slight change to the trigger mode, the system&#39;s software would most likely require a change and/or upgrade. This is because the parameters used to change the image trigger mode are typically not exposed to the user in an interface that he or she can access and control. Even if there are parameters exposed to configure the image trigger mode in available vision systems, those parameters are finite and fixed. The user would not, for example, be able to arbitrarily add a filter to the image trigger. 
     By way of background and definition, a “trigger event” is generally defined as a circumstance in which the system is instructed to acquire an image for inspection. In the case of an external source, such as a photo eye, a trigger event occurs when the object of interest is sufficiently within its view and the photo eye signals a trigger to the camera to acquire the current image and pass it to inspection by the vision system. In the above-described native-image-triggering camera assembly, and as described further below, a trigger event involving an “internal” trigger can entail an acquired image to satisfy various criteria. If the criteria are satisfied, the trigger event passes the acquired image (which generated the event), or another subsequent image to inspection. 
     By way of general example, an image-acquisition-based trigger mode as implemented in prior systems typically operates to capture images continuously (meaning in a continuing sequence for some period of time—that sequence potentially skipping frames or acquiring every available frame), while attempting to satisfy a predetermined “trigger logic” (i.e. the rules and criteria that cause a trigger event). This trigger logic is designed to pass when an object enters sufficiently/fully into the vision system&#39;s field of view. Once the trigger logic passes, the vision system then transmits the acquired image to another logic process to perform the main inspection and return/output the associated inspection results. 
     Other potential disadvantages of internal (within the vision system) and external (using a separate camera or other monitoring device) trigger logic using image acquisition is that the acquisition counts between the vision system and external monitoring devices become inaccurate. This can occur, for example when image acquisitions that trigger the trigger logic are not counted as main inspection triggers and theses two counts fall out of synchronization. Also, there are disadvantages resulting from gating of output inspection results (for example via discrete I/O) when running the trigger logic. Other complications can also arise in using an image-acquisition-based trigger logic (e.g. looping, changing trigger modes, and enabling/disabling trigger and inspection logic). 
     It is therefore desirable to provide a trigger functionality that is readily configurable based on a variety of variable parameters via a user interface. This trigger functionality should avoid common disadvantages of complexity and loss of synchronization with inspection processes. 
     SUMMARY OF THE INVENTION 
     This invention overcomes disadvantages of the prior art by providing a user-configurable trigger for a vision system that can be set using a user interface that allows the straightforward variation of a plurality of exposed trigger parameters. Illustratively, the configuration of triggers is performed in a manner similar to the programming of inspection tasks, using the interface. Illustratively, the vision system includes a triggering mode in which the system keeps acquiring (i.e. continuously acquires) images of a field of view with respect to objects in relative motion. The system runs user-configurable “trigger logic”. When the trigger logic succeeds/passes, the current image or a newly acquired image is then transmitted to the main inspection logic for processing. As a user-configurable trigger logic, it can be readily configured by a user operating an interface, which can also be used to configure the main inspection process, to trigger the vision system by tools such as presence-absence, edge finding, barcode finding, pattern matching, image thresholding, or any arbitrary combination of tools exposed by the vision system in the interface. Notably, the illustrative embodiments provide the user the ability to arbitrarily configure the trigger logic using the tools exposed by the vision system in an effort to afford the user substantial flexibility to customize trigger criteria to a specific vision system task. 
     In an illustrative embodiment, a system and method for using a configurable trigger for a vision system includes a vision system camera that acquires images objects moving relative to a field of view of the camera. A vision system interface is constructed and arranged to allow user access to a plurality of vision system tools to process the acquired images. A trigger configuration function resides within the interface, and is constructed and arranged to allow a user to configure at least some of the plurality vision system tools (defined herein to include any available vision system functions) to define a trigger logic by which an event is triggered. A main inspection configuration function also resides within the interface, and is constructed and arranged to allow a user to configure the vision system tools to define a main inspection logic that operates on at least one of the images in response to the triggered event. The trigger configuration can illustratively employ all the tools available to the main inspection configuration function. These functions can be provided in a user-selectable trigger mode interface that includes user-selectable buttons that expose at least some of the plurality of tools. The trigger mode interface further includes a trigger logic dialog screen that displays a trigger logic criteria based on selected ones of the tools. These criteria can include user or machine-defined threshold values and/or pass/fail criteria. Illustratively, the trigger logic operates on a sequence of the acquired images and, when the triggered event occurs, provides at least one image that triggers the event to the main inspection logic. Alternatively, or in addition, the trigger logic can provide an image (or a plurality of images) acquired subsequent to an image that triggers the event. In an embodiment, the sequence of images can be acquired at a higher frame rate and/or lower resolution (or in regions of interest) compared to the image being provided to main inspection after the event is triggered. In this manner triggers can occur at a higher frequency, with reduced processor overhead. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The invention description below refers to the accompanying drawings, of which: 
         FIG. 1  is a diagram of an exemplary manufacturing arrangement having a moving line with an inspection station including a vision system with a configurable trigger logic according to an illustrative embodiment; 
         FIG. 2  is a block diagram of a uniprocessor vision system in accordance with  FIG. 1  having a single processor that performs a trigger process and an inspection process according to an embodiment; 
         FIG. 3  is a block diagram of a vision system in accordance with  FIG. 1  having multiple processors/processor functions that respectively perform the trigger process and the main inspection process according to another embodiment; 
         FIG. 4  is a flow diagram of an illustrative user-based trigger logic configuration process for use with the vision system in accordance with  FIG. 1 ; 
         FIG. 5  is a diagram of a graphical user interface (GUI) display of a trigger configuration application for use with the vision system of  FIG. 1  in accordance with an illustrative embodiment, showing a main spreadsheet for configuring trigger logic and inspections; 
         FIG. 6  is a diagram of a vision system trigger properties box for use with the interface of  FIG. 5  in which the illustrative image trigger mode with configurable trigger logic is selected; 
         FIG. 7  is an image trigger dialog in the form of a multi-cell spreadsheet for use with the interface of  FIG. 5 ; 
         FIG. 8  is a set event property box for use with the interface of  FIG. 5 , providing a mechanism to signal/set trigger events; 
         FIG. 9  is a menu box for function selection in providing vision system tools and functions to the trigger logic and main inspection for use with the interface of  FIG. 5 ; 
         FIG. 10  is an exemplary display of the image trigger dialog of the interface of  FIG. 5  programmed to employ a bright/dark histogram analysis to base event triggers; 
         FIG. 11  is an exemplary display of the image trigger dialog of the interface of  FIG. 5  programmed to employ an ID/barcode finding function to base event triggers; and 
         FIG. 12  is an exemplary display of the image trigger dialog of the interface of  FIG. 5  programmed to employ pattern recognition/matching relative to training data to base event triggers. 
     
    
    
     DETAILED DESCRIPTION 
       FIG. 1  shows a manufacturing arrangement  100  that includes an exemplary, moving production line  110  that directs a plurality of objects  112  in a direction (arrow  114 ) though the inspection location  120  at which a vision system camera  130  is positioned. An illuminator (not shown) can be provided to the camera and/or at a location remote from the camera so as to illuminate the field of view  132  at the inspection location. The camera  130  in this embodiment includes an appropriate lens  134 , adapted to image the field of view  132  and the object  112  therein with appropriate levels of detail. An appropriate image sensor (not shown) mounted orthogonally to the optical axis within the camera is used to capture the image and convert it to pixel data, typically in grayscale, but optionally in color. The vision system camera  130  can include an on-board vision process/processor (dashed block  136 ), which performs the system&#39;s image acquisition and image processing tasks. 
     An example of a commercially available vision system with on-board image-processing capability if the In-Sight™ product line from Cognex Corporation of Natick, Mass. Such systems and those of competing vendors provide a programmable camera system that employs an interface to set up particular machine vision tools, functions and/or tasks. The interface is interconnected by a link either on a temporary or full-time basis. In an illustrative embodiment, the interface used for set-up, programming and/or monitoring of the camera  130  is provided on a standalone or networked computer (e.g. PC  140 ), running an interface process  142 . The computer  140  is interconnected to the camera  120  via a wired and/or wireless link  144 . Alternatively some or all of the image processing and vision system tasks can be performed within a remote standalone or networked processing system (e.g. PC  140 ), having an appropriate video acquisition peripheral (e.g. a framegrabber, etc.). 
     As used herein, and for completeness, the term vision system “tool”, shall refer to any configurable application or function that allows a particular aspect of an image to be examined to provide a result in relation to the image. A “tool” as defined herein can be taken to include edge detectors, blob analyzers, calipers, contrast tools, light/dark histogram analysis, flaw detectors, ID (barcode, etc.) readers, pattern matchers and search tools, and any other automated vision system function that allows an image to be examined and reported upon. 
     In the illustrative embodiment, the computer  140  includes conventional interface devices, such as a display  144 , mouse  146  and keyboard  148 . This is exemplary of a variety of interface arrangements (e.g. a touch screen), some of which are purpose-built for the particular vision task. Other peripherals and devices, such as robot manipulators and additional vision system cameras can be interconnected with the depicted vision system arrangement  100  according to various embodiments. 
     Reference is now made to  FIG. 2 , which shows a block diagram  200  of a vision system  210  having a single processor  220  for executing a pre-configured trigger and inspection process  230  according to an illustrative embodiment. This processor can be one or more individual processing chips (e.g. a multi-core processor) on a single die. As described below, the trigger process can alternatively be performed across multiple processors either residing within a single vision system camera/platform or distributed over a plurality of networked vision system cameras/platforms and/or in conjunction other processing devices (e.g. a PC). Illustratively, the depicted process  230  initiates in association with startup of the system (step  232 ). The process  230  then acquires an initial image of the scene in step  234 . This image is analyzed by the configured trigger logic in step  236 . If the features within the acquired image do not match the criteria for triggering in decision step  238 , then a trigger event has not been fired, and the process  230  branches back to acquisition step  234 , continuing to search for a trigger event based on the programmed trigger logic. The previous acquired image is eventually discarded from memory—either immediately or within a predetermined number of subsequent acquisitions. As described below, the programming of the trigger logic can be based upon trained image data (from actual acquired image data or synthetic image data) that operates various tools including blob analysis, edge detectors, and the like. These tools operate in a known manner to identify programmed/trained features within the acquired image. When the features are sufficiently identified, then the process  230  can ensure that an object is sufficiently in the field of view to allow a full inspection of that object, potentially using more robust vision system tools. 
     In general, the process  230  performs a high-speed continuous loop (for example at a rate of approximately 200 acquisitions per second), passing each acquired image through the trigger logic. When an acquired image satisfies the trigger logic (decision step  238 ), it (or another newly acquired image in the acquisition sequence) is then passed/transmitted to the main vision system inspection process—or that main vision process is otherwise signaled to access and analyze the stored image (step  240 ). The process  230 , then branches (via procedure branch  242 ) to continue acquiring images for the next trigger event (step  234 ), while the triggered sent/accessed image is processed by the main inspection process in step  244 . The results of the inspection process ( 244 ) are eventually output for use by the overall procedure (step  246 ). For example, the inspection can indicate a good or flawed part, object alignment data, and/or other useful statistics about an object. The various types of outputs and modalities for displaying and employing output information are known to those of skill. For example, information can be displayed on the camera body or a remote indication as a light (red/green) or sound. Alphanumeric data (e.g. barcode data, alignment data, etc.) can be displayed or stored. Any output information and/or images also can be displayed on an interface display screen via a PC, laptop computer, tablet computer, SmartPhone, and the like. Moreover the output information can be used to drive devices, such as robotic manipulators, defective-part “kickers” or chutes or assembly line shutoffs. 
     Note that a trigger event need not be based on a single acquired image that passes the trigger logic. In an embodiment a trigger event can require that a predetermined plurality of images pass the trigger logic. This images can be in a continuous sequence or at some other interval with respect to each other. This can ensure that a single image does not generate a trigger event based where there is a possibility of a false reading. In various embodiments acquired at an accelerated frame rate (see below), can enable the use of multiple images to generate a trigger event. Hence, as defined herein, “one or more” images can be employed to generate a trigger event based upon the trigger logic. 
     It should be noted generally that the quick and robust computational tasks performed in both the trigger process and subsequent main inspection processes are enabled by recent advances in image processing speed brought about by commercially available multi-core processors with high clocking speeds and large online memory capacities. These now-relatively-inexpensive components have made possible the rapid performance of an iterative, high-speed procedures, such as the triggering process described herein. These processes can be performed without compromising the runtime acquisition and manipulation of image data by other functions of the overall vision system. 
     Referring to the diagram  300  of  FIG. 3  showing an alternate embodiment, the system  310  can employ multiple processors  320  and  322  to perform different portions of the overall trigger and inspection process  330  and  350 , respectively. The use of multiple processors  330  and  332  can entail two discrete physical processors on a single die, or on different dies that are interconnected by a communication link. The processors can be part of the same overall device, or can be on different devices (e.g. two interconnected cameras or a camera and a PC). Moreover, the two processors can be “virtual” processor blocks both instantiated within a single-die, physical processor. One example is a multi-thread processor, where each thread is a different processor. 
     The multi-processor system  310  of  FIG. 3  initiates operation of the trigger and inspection processes  330  and  350  at startup (step  332 ). The trigger process  330 , executing on the processor  320 , operates generally in a manner described above. That is, images are acquired continuously at high speed (step  334 ). The trigger logic is applied to each image as it is analyzed by vision system tools (step  336 ). If the trigger logic criteria are not met, then the process  330  loops back to acquisition step  334  to work on the next acquired image (decision step  338 ). Conversely, if the acquired image meets the trigger logic criteria, then a trigger event is fired via decision step  338 . The process  330  sends acquired image data to, and/or signals access of that data by, the main inspection process  340 , while the trigger process  330  branches back top the acquisition step  334  (via branch  342 ) to work on the next acquired image. 
     The main inspection process  350  is carried out in the separate processor  322 , which receives image data from the acquisition process either directly through access of the system&#39;s data memory in response to an appropriate signal (step  340 ) or via a communication link that transfers the data to the second processor and any associated data memory. When received, the image data is processed by the main inspection process  350  using appropriate vision system tools and techniques (step  352 ). The results of the inspection are then output in step  354  as described above. 
     The ability of a user to configure the parameters or criteria of the trigger logic using various vision system tools exposed in a user interface is highly advantageous to providing a good basis for determining when an appropriate image of an object is acquired and can be inspected successfully.  FIG. 4  details a user-based procedure  400  for configuring the trigger logic according to an illustrative embodiment. In step  410  the user enters trigger configuration mode on the interface (a graphical user interface (GUI) described below) to select a given vision system tool, which is exposed as part of a menu of choices. The user then configures the tool&#39;s parameters as appropriate to the particular tool in step  420 . For example, if the tool is an edge finding tool, the user defines locations of expected edges in a runtime image of the object. In step  430 , the configured tool is then added to the trigger logic as part of a list of tools that are applied to each acquired image. In an embodiment, some or all of the vision system tools available in runtime inspection are also available in the image trigger process. Alternatively, the list of tools can be reduced and the tools that run more efficiently can be employed. The tools can operate on the entire image, or on regions of interest within the image. The configuration procedure  400  queries for additional tools (decision step  440 ). If the user desires to apply further tools (e.g. blob analysis, caliper, etc.), the procedure branches back to the selection step  410 . If all tools have been configured and added, then the trigger event is fully configured (step  450 ). Note, as defined herein the “image trigger event” is the process by which the trigger logic forwards the acquired image to the main inspection. This happens when this event is fired (or signaled) in the trigger logic, which is based on the selected criteria of the user. In step  460 , the configured trigger logic is then saved to program memory/data storage associated with the appropriate process of the vision system. 
     Reference is now made to  FIGS. 5-9 , which show various screens of a graphical user interface (GUI) display used to configure trigger logic in an illustrative embodiment. This GUI is based upon an exemplary spreadsheet that allows various vision system functions to be configured. An example of such a spreadsheet is employed in connection with the above-described. In-Sight system. However, a variety of alternate GUI styles and arrangements of data and inputs can be used in alternate embodiments—for example a ladder logic-style interface. As shown in  FIG. 5 , the display  500  provides a main inspection spreadsheet. A trigger mode called “Image” is provided in an illustrative embodiment. This mode provides a mechanism for configuring the image trigger using available vision system tools. 
     Illustratively, the AcquireImage function is a location in the overall spreadsheet interface in which all other functions reference in order to execute when the vision system acquires an image. This function can not be removed from the spreadsheet  510 , and is the location for configuring various acquisition parameters, such as exposure time. The AcquireImage function&#39;s property sheet is the location where the acquisition parameters are manipulated and an illustrative location to provide the configurable image trigger. A graphical version of the training image  530  appears in the main window  520  of the spreadsheet  510 . A set of available vision tools and vision system processes appears in the side pane menu  540 . 
     With further reference to the Trigger properties box  600  of  FIG. 6 . The interface illustratively includes a trigger mode called “Image” (box  550  in  FIG. 5 ) that allows analysis of the image in addition to other selectable triggers (e.g. external triggers such as photoeyes, encoders, etc., manual triggers, and the like) to be employed. See dropdown box  610 . A button labeled “Image Trigger”  620  can be enabled when this mode is selected. When pressed, the Image Trigger button illustratively launches the Image Trigger dialog window (and associated spreadsheet) which can allow the user to configure the trigger logic. This dialog box is shown in further detail in  FIG. 7 . 
     The Image Trigger Dialog window  700  can resemble a typical spreadsheet (the Image Trigger Spreadsheet) with its own AcquireImage function. This AcquireImage function is typically arranged so that it cannot be deleted and is free of input parameters. The AcquireImage function is thus used as an input reference to drive the execution of other functions in the Image Trigger Spreadsheet. 
     In an illustrative embodiment, Image Trigger dialog  700  includes an Event type (provided in box  800  of  FIG. 8 ) that allows for the use of an interface spreadsheet to trigger the event. Illustratively, events in the exemplary vision system interface arrangement can be used to signal the execution of the main spreadsheet logic. In this case, the illustrative event type called “Spreadsheet”  810  in the associated Trigger dropdown box  820  is used to establish the trigger event. This trigger event is used to execute the main inspection process on the object. The user thereby signals a Spreadsheet Event (using a SetEvent function) based on the logic he or she programmed into the Image Trigger dialog  700 . The Spreadsheet Event therefor drives the execution of the main spreadsheet inspection. 
     As described above, the Image Trigger spreadsheet logic is fully configurable in the illustrative embodiment. The user can utilize all of the vision system&#39;s exposed tools or functions to generate events that drive the main inspection spreadsheet. These are provided in the illustrative interface box  900  ( FIG. 9 ), which provides a list of tools and other functions that are exposed by the system and can be inserted into the trigger logic. 
     The following are examples of the configuration of trigger logic using the illustrative interface. Reference is first made to the display  1000  of an Image Trigger dialog  1010  defining an array of spreadsheet cells. In this example, the Image Trigger dialog has been programmed to signal a Spreadsheet Event when a histogram threshold is above a desired value. In Image Trigger mode, the vision system continuously acquires images and sends them to the Image Trigger spreadsheet for processing. In this example the ExtractHistogram function (cell C404) will execute based on its reference to AcqurieImage (cell A400). Then, the HistThresh function (cell D404) will execute and extract the threshold data from the Hist structure. If the histogram threshold is above the value in F407 then the execution will send a Spreadsheet Event (using the SetEvent in cell C411) to the main inspection for processing of the acquired image. The pass/fail logic in cell D409 compares the histogram threshold with the set input value (e.g. 34) in F407. This spreadsheet  1010  represents the full logic that decides whether or not to signal a Spreadsheet Event, and thus forward the image to the main inspection for processing. 
     Reference is now made to a display  1100  having an exemplary barcode-reading Image Trigger dialog  1110 . The dialog is programmed to signal a Spreadsheet Event when there is a valid barcode (ID) in the field of view. By way of example, the ReadIDMax function (cell C402) is returning up to 10 barcode results. The function GetNumResults (cell D414) is returning the number of barcodes the ReadIDMax function has decoded successfully. The pass/fail logic in cell D416 returns 1 if the ReadIDMax has found at least 1 barcode in its field of view. This is a representation of the full logic that drives the Image Trigger spreadsheet to signal a Spreadsheet Event by executing the SetEvent function (cell D417). 
     Reference is now made to the exemplary display  1200  of  FIG. 12 , which shows the Image Trigger spreadsheet  1210  configured for pattern matching of an object. In this example, the Image Trigger dialog is programmed to send a Spreadsheet Event to the main processing spreadsheet based on pattern recognition of an imaged object. The Image Trigger spreadsheet will signal a Spreadsheet Event (cell D411) when it sufficiently matches the pattern which has been trained in cell C403 and is above the desired threshold (cell C408). The pass/fail logic (cell D410) provides a respective I/O value for the Event. In this example, the match of the pattern to the training image is required to score 95/100 to present a pass value. 
     It should be clear that the above-described examples are only a few of the wide range of possible criteria that can be programmed into the trigger logic. Any appropriate combination of tools and vision system functions can be combined to achieve the specific trigger criteria. 
     In an embodiment, the image trigger mode can take advantage of capabilities and functions within the camera and acquisition hardware/software that allow for an increased frame rate and/or reduced image resolution to speed acquisition of an event-triggering image. For example, where the camera and acquisition hardware/software allows for binning of sensor rows (of image pixels) or skipping of alternating rows (and/or columns of pixels), the trigger logic can operate on somewhat lower-resolution images to speed the process. The tools used in the logic can be adapted to be less sensitive to a high resolution image. This allows for more acquisitions and trigger logic analysis to occur within a given time frame. If an event is triggered by the trigger logic using lower-resolution, higher frame rate images, then a next acquired image (as soon as the event is recognized and acted upon by the system) can be acquired at a higher resolution, and transmitted to the main inspection logic. This embodiment thus allows the trigger logic to operate more rapidly, thereby allowing objects to pass through the field of view more quickly. Other techniques for increasing frame rate can be implemented in alternate embodiments with the goal of accelerating the triggering of an event, when the object is sufficiently within the field of view. 
     Illustratively, in programming trigger logic using a reduced frame rate and subsequent, higher resolution image for inspection, the user can configure the appropriate vision tools to identify features that are associated with a leading portion of the object so that a trigger event occurs while the object is just arriving within the field of view. In this manner, the speed of the line can be accelerated while ensuring that the object has not begun to vacate the field of view when the inspection image is actually acquired. 
     Also illustratively, the interface can include a library of pre-programmed trigger logic configuration templates consisting of tools and appropriate settings/thresholds for the tools. These configurations can be used for commonly encountered trigger and inspection tasks to ease use of the interface in conventional implementations of the vision system. For example, a pre-programmed barcode reader trigger configuration can be employed with, for example 1D and 2D barcodes. 
     It should be clear that a system and method for configuration of image-acquisition-based trigger logic enables an efficient, versatile and reliable technique for acquiring inspection images when an object is fully within the field of view. The illustrative embodiments herein avoid loss of synchronization and potential errors that can result from employing a separate image-based-trigger or other position sensing device. More particularly, the illustrative embodiments herein allow for trigger logic to be programmed using the same interface and available tools used in main inspection. A wide variety of such tools are made available, ensuring that the trigger logic can achieve a positive result. 
     The foregoing has been a detailed description of illustrative embodiments of the invention. Various modifications and additions can be made without departing from the spirit and scope of this invention. Each of the various embodiments described above may be combined with other described embodiments in order to provide multiple features. Furthermore, while the foregoing describes a number of separate embodiments of the apparatus and method of the present invention, what has been described herein is merely illustrative of the application of the principles of the present invention. For example, while a moving line with objects that pass under a stationary inspection station is shown, it is expressly contemplated that the station can move over an object or surface or that both the station and objects can be in motion. Thus, taken broadly the objects and the inspection station are in “relative” motion with respect to each other. Also, while the above-described “interface” (also termed a “vision system interface”) is shown as a single application consisting of a plurality of interface screen displays for configuration of both trigger logic and main inspection processes, it is expressly contemplated that the trigger logic or other vision system functions can be configured using a separate application and/or a single or set of interface screens that are accessed and manipulated by a user separately from the inspection interface. The term “interface” should be taken broadly to include a plurality of separate applications or interface screen sets. In addition, while the vision system typically performs trigger logic with respect to objects in relative motion with respect to the field of view, the objects can be substantially stationary with respect to the field of view (for example, stopping in the filed of view). Likewise, the term “screen” as used herein can refer to the image presented to a user which allows one or more functions to be performed and/or information related to the vision system and objects to be displayed. For example a screen can be a GUI window, a drop-down box, a control panel and the like. It should also be clear that the various interface functions and vision system operations described herein controlled by these functions can be programmed using conventional programming techniques known to those of ordinary skill to achieve the above-described, novel trigger mode and functions provided thereby. Accordingly, this description is meant to be taken only by way of example, and not to otherwise limit the scope of this invention.