Error Messages

The maximum number of references within a chain of cell references is 256 cells, and this error is initiated when the chain of references exceeds 256. A common cause of this error occurs when creating index numbers (e.g. B0=0; B1=B0+1; B2=B1+1; B3=B2+1...B255=B254+1; B256=B255+1; B257=B256+1 --> Error is triggered). In order to prevent this error, hard code a break in the chain of references (e.g. B0=0; B1=B0+1; B2=B1+1; B3=B2+1...B199=B198+1; B200=200 --> hard coded limit, which still leaves an additional reference depth of 56, which might be used by other cells attached to the chain. The chain can then be resumed, B201=B200+1...B255=B254+1; B256=B255+1; B257=B256+1 --> Error is NOT triggered).

Fonts are allowed to have a maximum of 64 character models. Delete unwanted existing models before attempting to add new models.

A host name is required and cannot be blank. Choose a name for the host.

You have attempted to add a host to the In-Sight Host Table that has an invalid IP address. Choose a different IP address. For more information, see Host Table Dialog.

You have attempted to add a host to the In-Sight Host Table that has an IP address already used by an existing host table entry. Choose a different IP address. For more information, see Host Table Dialog.

In-Sight user names must be unique. If you attempt to enter a new user with the same name as an existing user, you will receive Error 5201. For more information, see User Access Settings Dialog.

The Native Mode channel on <host name> has stopped responding to In-Sight Explorer. Reboot the sensor and try the operation again.

You may receive Error 5403 when attempting to log on to a sensor with a valid User Name but an incorrect Password if another user is already logged on to the sensor.

Error 5404 can occur when In-Sight Explorer cannot create a TCP Socket to <host name> over port 1069.  Usually this occurs because a firewall on the machine preventing the TCP socket from being created, or a second Network Interface Card that is configured such that Windows tries to use the second NIC instead of the correct NIC.

Generally, if you can create a telnet or ftp connection to <host name> from windows, you can also create the TCP socket to the sensor through In-Sight Explorer.

From a Windows command prompt, type 'telnet aaa.bbb.ccc.ddd 1069' where aaa.bbb.ccc.ddd is the IP address of <host name>. If telnet is unable to create a socket connection to that port, then In-Sight Explorer cannot either.

There is a Version Stamp Mismatch between the job that you are attempting to load and the In-Sight vision system/emulator that you are attempting to load it onto. This happens when a job is created using one version of In-Sight software or firmware, and is loaded using a different version.

This warning does not indicate a compatibility problem between the job and the vision system. It is meant to alert you to the possibility of such a compatibility problem. If no other error message regarding failing to load the job appears after this warning, the job and the vision system/emulator are compatible and no further action is needed. If such an error message appears, you may have to modify this job file in order to make it fully compatible with the firmware running on the vision system/emulator.

The maximum combined number of functions, arguments, and operators allowed in any given formula is 254. When an argument to a function is a range of cells, each cell within the range is counted as one argument.

For example, the formula Sum(1,2,A3:A6) consists of 1 function (Sum) and 6 arguments (1, 2, A3, A4, A5, A6); this consumes 7 of the allowed 254 for this particular formula.

Error 5701 occurs when you are entering a formula into either a spreadsheet cell or the Formula Bar if some portion of the formula needs to be corrected. Any invalid syntax will be highlighted in red, as shown in the preceding graphic. If no text is shown in red and you are receiving Error 5701, then:

• You may not have completed typing the function's name or supplied all necessary arguments to the function.
• The function may reference more than 254 arguments. The maximum number of arguments allowed in any given formula is 253. When an argument to a function is a range of cells, each cell within the range is counted as one argument. For example, "Sum(C1:C254)" causes this error message because the function references 254 arguments in the range, (C1:C254). For more information, see Error 5700.

When In-Sight Explorer is launched, it attempts to load a startup layout from the options.xml file, which is located in the application's root folder. If a Host Name is defined in the startup layout but cannot be detected on the network, then you will receive this error.

Error 6000 often occurs if the Host Name of the sensor or emulator in question has changed since the startup layout was last saved. Saving a new startup layout can resolve this issue:

1. Log on to any In-Sight sensors to which you would like In-Sight Explorer to automatically log on at startup.
2. Arrange the visual layout of views as desired (tiled or a single view maximized.)
3. On the System Menu, click Save View Layout.

In-Sight Explorer opens UDP port 1069 to communicate with In-Sight sensors on a TCP/IP network. Some PC applications (such as Microsoft Outlook or the Microsoft IIS Admin service) open random UDP ports; this can interfere with the operation of In-Sight Explorer. If you receive the following error:

Error 6001: Unable to open UDP port 1069. In-Sight Explorer will be unable to detect In-Sight sensors on the network. Press OK to continue.

Close all applications and restart In-Sight Explorer. If you still receive the error message after closing all other applications, then reboot the PC and launch In-Sight Explorer again, before launching any other applications. When In-Sight Explorer is installed, a registry entry is created to prevent other Windows applications from using these ports, however the registry entry doesn't take effect until the PC is rebooted.

If an In-Sight sensor or emulator appears within the In-Sight Network tree upon application launch but In-Sight Explorer is unable to communicate with it, you may receive this error. Often this results from a startup layout that contains a host, defined in the Explorer Host Table, that cannot be accessed on the network. For more information, see Explorer Host Table Setup Dialog.

Ensure that the In-Sight sensor or emulator represented by <host name> is powered on and that it can communicate on the network. If it is an Explorer Host Table entry, ensure that the IP address of the host table entry matches the actual IP address of <host name> as defined in the network settings. For more information, see Network Settings Dialog.

Error 6003 can also occur if the Internet Information Services (IIS) Admin service is started in the Windows control panel; if running, try stopping this service and restarting In-Sight Explorer. The IIS Admin service may be restarted afterIn-Sight Explorer has been launched.

Following the steps to resolve Error 6001 may also fix Error 6003, as these can appear together.

In-Sight Explorer could not write <file name> to disk. Ensure that the drive exists and that it has sufficient free space to write the report file. If <file name> points to a network drive, ensure that the drive is connected and that you have write access to it.

In-Sight Explorer was unable to Link to the destination host. The host could be down, or you may have chosen not to complete the link when prompted.

In-Sight Explorer was not able to retrieve file directory information from <host name>. Your user account may not have sufficient privileges to view the files contained in this folder. Ensure that the Local FTP Port on <host name> matches the Explorer FTP Port specified in the Options dialog.

For more information, see FTP Settings Dialog and Explorer Host Table Setup Dialog.

Connection Refused: connect

In-Sight Explorer cannot communicate with the sensor that is currently selected in the In-Sight Network tree. Refresh the In-Sight Network by selecting Refresh from the View Menu. If the sensor is still inaccessible, power-cycle the sensor and retry the operation.

Invalid password, not logged in.

The current user does not have access to display the files on <host name>. Log on as a different user with sufficient access to see the files contained on this sensor and retry the operation.

Error 6010 occurs with a secondary error descriptor:

File not found

<file name> may be invalid with respect to the In-Sight file system. Ensure that the file name does not contain any symbols or special characters (such as $). Attempt to rename the file and retry the operation.

On the System Menu, click Options. Ensure that the Backup Directory is a valid folder name and that this folder is accessible through Windows Explorer.

• Transfer Incomplete - No Space: This error can occur when a file name is too long for the In-Sight file system, or the file size is too large to fit on the destination sensor. Check the backup directory, located in:  <ISE dir>\Backups\<host name>, where <ISE dir> is the folder in which In-Sight Explorer was installed, and <host name> is the name of the destination In-Sight sensor. Ensure that the length of 'file name' is 15 characters or less (not including the extension). If the destination sensor contains many files, try deleting other files and attempt the restore operation again. Alternatively, copy the file manually using the In-Sight Files pane or Windows Explorer. For more information, see In-Sight Files.
• Restore Operation on emulator prompts error: While attempting to restore an emulator, this error will occur if any files (image1A.bmp, image1B.bmp, image2A.bmp, etc) are read-only; remove the read-only attribute and then attempt the restore operation again. For more information, see Restore Dialog.

In-Sight Explorer was not able to locate the backup folder for <host name>. Backup folders are stored in the following path:

<InSight2>\Backups

where <InSight2> is the folder in which In-Sight Explorer was installed. Backups are stored as subfolders with a name equal to the Host Name of the sensor. Ensure that this folder was not moved, renamed, or deleted. See Error 6046 for more information on how backup directories are named.

Certain files within the In-Sight file system are critical to the operation of the sensor, and thus cannot be deleted. The following files cannot be removed from an In-Sight sensor or emulator:

• proc.set
• image.bmp
• image.jpg
• screen.bmp
• screen.jpg

In-Sight Explorer was unable to delete <file name> from the In-Sight system. Ensure that the file is not read-only.

The file may have been deleted remotely. Refresh the In-Sight files pane by selecting a file and pressing F5.

In-Sight Explorer could not copy <file name> to the destination In-Sight sensor. The following messages may appear with Error 6018:

• Transfer Incomplete - No Heap: If you were copying a file to an In-Sight sensor, the sensor may not have enough free flash memory to complete the file transfer. Try removing some files and copy the file again.
• Write permission denied: The file you attempted to overwrite has read-only permissions. Remove the permission and attempt the copy again.
• File not found: The file you attempted to copy no longer exists on the source sensor. Refresh the In-Sight Files pane (F5) and ensure that the file exists on the source sensor.
• Problems with drag-and-drop file operations:
  • Issue #1: On an English operating system, dragging and dropping file names that contain Korean or Chinese characters from Windows Explorer to the In-Sight Files pane will result in Error 6018.
  • Issue #2: On a Korean operating system, it is only possible to drag and drop file names that contain Korean or English characters from Windows Explorer to the In-Sight Files pane, all other characters will result in Error 6018.
  • Issue #3: On a Chinese operating system, it is only possible to drag and drop file names that contain Chinese or English characters from Windows Explorer to the In-Sight Files pane, all other characters will result in Error 6018.
• Workarounds:
  • Use the Open Job dialog (File > Open Job) to load the file
  • Use English characters in the file names

Certain files, such as proc.set, contain vital network settings and cannot be simply copied to another sensor.

The Offline Programming Key you have entered into the Options dialog is invalid. Contact your Sales Engineer or Cognex Technical Support to obtain a valid key. For more information, see Technical Support.

In-Sight Explorer could not establish a connection to <host name>.

Error 7003 may appear with a secondary descriptor:

User <user name> from <host name> is already remotely connected to this system

To complete the operation, click Yes when prompted to Proceed with log on.

The IP address you have specified could not be assigned to the In-Sight sensor. If you received this error message in the Add Sensor/Device to Network dialog, check to see if the In-Sight sensor is configured for IP Address Lock; the IP address of a sensor cannot be changed when IP address lock is set to true. Issuing SL0 to the sensor through a telnet session will remove the IP address lock.

The Add Sensor/Device to Network dialog could not establish communication with the In-Sight sensor. Ensure that the sensor has power and an active network connection. See Error 5404 for more troubleshooting tips.

See the note that follows Error 7731 in the dialog for more troubleshooting information.

In addition, ensure that the device is connected on the same physical subnet as the PC, and that it is powered on. Check all Ethernet cabling to the device.

If all else fails, connect the device directly to your PC and power-cycle the device.