Image sets overview

An alternate way of acquiring images for your project is to configure and use a series of preestablished images from file (an image set). By default, the images from the image set are queued (buffered) until the Camera step is executed in the flowchart. After the Camera step, the next image (from the image set) is available to your project.

The ImageSet page of the Platform Configuration dialog allows you to add, rename, or delete the image sets used by your project. Each image set has a SetN page that directly controls the sequence of images to be used. These options include, but are not limited to, the source location and naming scheme of the images. An image set is typically created prior to project deployment and remains constant.

The file thumbnails in the Camera Images pane allow you to view, exclude, or select the next image to be used at design-time. For more information, see the Camera Images pane section in the Panes and editors reference chapter.

A design-time alternative to an image set is the PhysicalCameraSetN set of images. This is a group of up to 25 images acquired by your camera. The images are stored in memory, and are replaced in a round-robin fashion as more images are grabbed. Typically, this alternative is only used when trying to troubleshoot a project with a camera component. If the images of the PhysicalCameraSetN set are of use beyond the initial troubleshooting period, they should be saved as an image set.

When entering a diagnostic or training mode, and in software triggered mode (that is, using a Trigger step in your project), you can enable the Reuse current image option to keep using the previous image.

If deploying your project so that it uses image sets instead of images acquired from a camera, you might want to remove any automatically added camera components from the project, so that you avoid getting warnings if the runtime platform has no camera attached.