Known Issues
The following Known Issues have been identified in this release:
| Issue # | Known Issue |
|---|---|
| IS280-10117 | There is a large variation in job execution time. For example, if In-Sight Easy Builder reports an average execution time of 200 ms, the trigger is no faster than 280ms. The trigger rate for the vision system has to be 1.5x the total job execution time. For example, if the job takes 100 ms to complete, the trigger rate can not be less than 150 ms. Going below this rate results in less predictable job/tool execution timing. You can find this time in the Inspection step when viewing all tools. |
| IS280-10296 | There is a 1-second time frame during firmware update when the power loss happens. To avoid this, do not disconnect power during firmware update. |
| IS280-628 | Date/timestamps from the vision system is set to the time of manufacture, not to the current date/time. |
| IS280-10672 | Record/Playback performance declines with large (100+) numbers of images. As the image count grows to hundreds, scrolling images becomes slow. |
| IS280-892 | Having the editor connected to a vision system while online affects job performance. Make sure that an editor is not connected to an online vision systemunless it is in a state where the job performance is not critical. |
| IS280-10101 |
Problem: Pixel count tool undercounts edge pixels if the region of interest is a rotated rectangle. Workaround: Use a Polygon ROI when adding a Pixel count tool to the job. |
| IS280-10985 | If you link a tool to the Communication application step property and then you delete, the links to that tool in the Communication application step gets removed. If you perform an undo of that deletion then the tool is present again, but the links to the tool are not reestablished in the Communication application step. The only exception are the links on the right side of the screen such as context panel where the "enabled" link is restored. |
| IS280-11109 | If you set up the Math tool to pull data from a PLC and try to reference those cells in the Communication/Input application setup, the values do not update upon trigger. Data shows up correctly in the Math tool, but not the output value. |
| N/A |
If using OPCUA with the network settings set to DHCP instead of static IP, occasional loss of connection happens. To avoid this, use a static IP address. |
| ISPROD-2160 | Emoji or Unicode password characters are not supported, but occasionally allowed. |
| ISPROD-1330 | When you fixture a pattern tool to another pattern tool, the tool location moves properly with the fixture. However, the angle does not. More specifically, the angle range appears to reference the main image and not the fixture. |
| ISPROD-4705 | A BMP saved from one In-Sight 2800 camera is unable to open on another In-Sight 2800 camera |
| ISPROD-4663 | Enabling and disabling HDR makes the next acquisition an out-of-focus image. Acquiring again shows an in-focus image. |
| ISPROD-4653 | When loading a job with a valid ID though In-Sight Vision Suite, the job ID does not get updated correctly and is set to 65535(0xFFFFFF). This does not happen when the job is loaded using Job Load by ID with Profinet. |
| ISPROD-4320 | SVGs and images with Graphics are clipped incorrectly if browser scaling is enabled. |
| ISPROD-2399 | Self-trigger stops triggering if all acquisition buffers are in use. |
| ISPROD-1355 | Self-trigger mode does not overlap acquisition when the job execution exceeds the trigger interval. Instead, the next acquisition is simply delayed until the job execution is complete. This means that for long-running jobs, the self-trigger interval is determined by whichever is longer. |