#ERR

A cell that displays #ERR indicates that the cell could not execute its function correctly and is generally due to an invalid input parameter. An #ERR condition can occur for a variety of reasons, some due to normal operation of the vision application, and some due to errors in the spreadsheet logic itself.  A few common occurrences of #ERR are noted below.

1. Basic Mathematical Errors

   Cell A4 = A3 / A2. If the value of cell A2 is equal to 0, then the function in cell A4 will generate a divide-by-zero error.

2. Region Graphic Errors: Region moves off of the image

   If you use a PatFind tool to locate something in the image, and then use the result data to fixture the location of other vision tools, it is possible for the region of a vision tool to be moved to a location causing part of the region to be outside the bounds of the image.  When this occurs, the vision tool will report #ERR instead of returning a valid vision tool result structure.

3. "Get" Functions fail: Vision Tool does not produce results

   If you use a GetRow function in conjunction with an ExtractBlobs tool, there may be conditions where the ExtractBlobs tool fails to locate the expected number of blobs.  If this occurs, the GetRow function will report #ERR if the desired blob could not located in the image.

4. Communication Errors: Cannot send data

   If you create a WriteImageFTP cell or WriteTCPDevice cell, data will automatically be sent from the In-Sight sensor to another computer each time the spreadsheet executes.  If there are problems with client computer such that it cannot receive the data, it is possible for output buffer on the In-Sight sensor to fill-up.  If the output buffer overflows (there's no place the put the data), then these cells will report #ERR.