Image Logging FAQs

Q: Why does the Image Logging step log the wrong image?

If you set the Image Logging step to Log Images Only When Inspection Status Fails, the Image Logging step must be placed after a Set Inspection Status step in the inspection. Otherwise, the value of the Inspection Status will not be set for the current image when the Image Logging step executes and the image may not be logged.

Q: What are the disadvantages of using lossless compression for image files?

Lossless compression allows for smaller image file sizes, but takes longer to save the image because of complex calculations that take time to process. If the amount of time it takes to save the image is important for your application, disable lossless compression.

Q: Why are the Limit Number of Logged Images and Max Number of Logged Images controls not available?

The controls are grayed out when the value specified for the File Name is a constant and the Append Timestamp control is not enabled. In this case, since the name of the logged image file will be the same for each logged image, it is not possible to log more than one image because each new image overwrites the existing image file. To log more than one image, either enable the Append Timestamp control or set the File Name to use a dynamic result from a previous step in the inspection.

Q: What are the advantages/disadvantages of background FTP data logging?

When information is logged in the background, the logging step has a shorter execution time because the step sends the information to a background task and allows the inspection to continue executing without having to wait for the FTP write operation to complete. A possible disadvantage to background logging is that you can lose information if the background logging task is unable to keep up with the inspection.