This section describes limitations in VisionPro 3D-Locate.

The VisionPro 3D-Locate API requires image coordinates to be specified in the Raw2D coordinate space. This is the 2D coordinate space of the acquired images used for camera calibration.

The VisionPro 3D-Locate API requires all 3D coordinate spaces to be 3D right-handed spaces.

This section describes limitations of 3D vision tools in VisionPro 9.7.

Virtual machines implement adapters for 3D acceleration that are not always compatible with the VisionPro 3D Display, which takes advantage of native 3D acceleration to provide the fastest response times. Cognex does not officially support the VisionPro 3D Display on virtual machines.

This section describes limitations with GenTL acquisition in VisionPro 9.7.

Be aware of the following limitations using GenTL acquisition:

• If you call Disconnect(true) on a GenTL frame grabber, Cognex cannot guarantee you will be able to use that frame grabber again in the executing process. Do not call Disconnect() until you are ready to exit your application, and then call Disconnect(false).
• If you physically disconnect a USB3 camera cable while your application is running you will not be able to use that camera again in the executing process, even if you later reconnect the camera.
• If you add a USB3 camera to your system after your application has started, VisionPro cannot recognize that camera and it cannot be used for acquisition. This release does not support dynamic discovery of cameras using the Refresh method of the CogFrameGrabbers class.
• Persistent Camera Enumeration functionality is not implemented for GenTL cameras.
• You cannot control the order in which cameras appear when enumerated by VisionPro.
• All pre-existing (non-DSMax) GenTL .vpp files will not load properly in this release. Old .vpp files were saved with the "Cognex NullFormat" video format, which is now illegal for non-DSMax GenTL cameras. So the attempt to restore the old acq fifo will fail. This is not a fatal error, but it means that you get a non-functioning "ghost" fifo instead of a fifo that can be used for acquisition. You must recreate your fifo to get your application working again.

This section describes limitations of the Cognex Communication Card in VisionPro 9.7.

Be aware that VisionPro does not support using multiple Cognex Communication Cards in the same PC.

This section describes limitations of the DS1000 series sensor in VisionPro 9.7.

All z-height information displayed for the right half of Range With Grey Images acquired by a DS1000 series sensor should be ignored. The right half of such images contains intensity data, not height data.

This section describes limitations of the DS900 series sensor in VisionPro 9.7.

All z-height information displayed for the right half of Range With Grey Images acquired by a DS900 series sensor should be ignored. The right half of such images contains intensity data, not height data.

This section describes limitations of QuickBuild in VisionPro 9.7.

Adding items into Posted Items using the Property Browser supports adding Properties but not Methods. Even though Methods are shown in the Property Browser (i.e. CogBlobTool.Region.CogPolygon.GetVertexX) and the browser allows the item to be added, no value will be returned when user result is available (see UserResultAvailable event handler).

This section describes limitations of the OCV tool in VisionPro 9.7.

Clicking the "?" button in the OCV tool edit control will display a message that VisionPro is unable to locate the online help and that re-installing the product might resolve the issue. The OCV tool edit control, however, does not support access to the online documentation supported by most other tool edit controls. Re-installing VisionPro will not resolve the issue.