A list of known issues in VisionPro 9.7 along with workarounds when available.
Categories:
This section describes open issues concerning 8700 series frame grabbers in VisionPro 9.7.
After upgrading from a CFG-8714e to a CFG-8724 the computer continues to identify it as a CFG-8714e and reports the serial number as "Invalid serial number".
Workaround:
Completely power down your computer and reboot. A warm reboot after installing this VisionPro release does not allow the CFG-8724 to function correctly.
Cognex also recommends you disable the Windows 10 Fast Startup feature when changing frame grabbers.
This section describes open issues concerning the Cognex Communication Card in VisionPro 9.7.
Calling CogPrio.DisableEvents() at the same time as an event response is pulsing an output line may prevent the output line from completing the pulse. After which, the output line may become unresponsive forcing the application to be restarted.
This section describes issues concerning image display.
Windows 10 operations that result in the loss of the viewing surface may cause VPro to crash if the 2D Display is active on the screen. Examples are locking the system using CTRL-ALT-DEL or when a display goes into sleep mode.
The Cog3DDisplayV2 's API provides different rendering mode settings. The non-default DisplayMode.Vertices can cause a crash if the graphics hardware/driver is not DirectX 11 compliant. This issue has been seen on Vision Controllers that have the Intel HD3000 graphic hardware as the available driver supports DirectX 10.5.
This section describes open issues concerning the DS1000 series sensor in VisionPro 9.7.
Some settings for Peak Detection Mode might result in the wrong peak being selected when used with HighDynamicRange. Cognex recommends that HighDynamicRange be used only when Peak Detection Mode is set to Max.
When changing the IP address on a DS1000 series sensor, if the firmware is incompatible with the release you will receive an erroneous error. This error should be ignored. Note that you will need to upgrade the firmware before the sensor can be used with the VisionPro release, but before you can upgrade the firmware you must set a valid IP address, and thus will see this spurious error.
If Line Finding Mode is set to Binary and Peak Detection Mode is set to Closest, the proper position of the laser line might not be detected if its thickness is equal to Binary Peak Width. The problem does not appear when the laser line is greater than the value of Binary Peak Width.
If you configure a DS1100 to use Semi-Trigger acquisition and Intensity (or IntensityWithGraphics) mode, and you then queue more than a single acquisition start, a single triggered acquisition will occur and the acquisition system will fail to acquire on subsequent triggers.
Workaround:
You can prevent this error from happening by not queuing multiple starts when in Semi-Trigger Intensity mode. Be aware that calling StartAcquire( ) while an acquisition is in progress is the same as queuing more than a single acquisition start.
If you configure a DS1100 to use Manual or Semi-Trigger acquisition, and acquire images greater than 10922 lines, calling ICogAcqFifo::StartAcquire( ) more than once before calling ICogAcqFifo::CompleteAcquire( ) will cause acquisitions to hang after the first or second image.
Workaround:
You can prevent this error from happening by not having more than one outstanding acquisition at any time. In QuickBuild, set Number of Software Acquisitions Pre-queued to 1 (the default setting) in the Configure Job Properties dialog box.
If you configure a DS1100 to use a test encoder, the following properties are inoperative, even though their controls are enabled:
- Single Channel Encoder
- Positive Acquire Direction
- Encoder Resolution
VisionPro does not generate a value for the maximum line rate when using a DS1100 sensor.
Workaround:
- Configure the exposure, high dynamic range, and ZDetection settings.
- Acquire a peak or range image regardless of whether the encoder overruns.
- Read the CPCyleTimeUSec feature from the camera.
- Maximum line speed (lines per second) is approximately 1,000,000 / CPCycleTimeUSec.
- Go back to step 1 and adjust parameters until step 4 produces a number suitable for the application.
This section describes open issues concerning the DS900 series sensor in VisionPro 9.7.
When field calibration is used with a DS900 sensor and "Remove Skew from Image" is disabled, the x, y, and z scales on the Calibration tab are ignored and default values will be used for both x and z scales. The y scale will depend on the encoder settings.
The maximum line rate for the DS900 series sensor is 1200 Hz. Attempting to acquire at a line rate greater than the measuring field supports can cause one of the following issues:
- For measuring fields that support 1200 Hz, slightly exceeding 1200 Hz may cause dropped lines or hangs instead of overrun errors.
- For measuring fields that are limited to less than 1200 Hz, slightly exceeding the specified line rate will report overrun errors.
- At very high line rates, hangs may be observed regardless of the measuring field.
Workaround:
The DS900 sensor cannot be configured for a line rate higher than 1200 Hz. Correcting the setting should restore normal operation.
When using an encoder to control the rate of acquisition of a DS900, small changes in direction (as may happen due to vibration in the motion) may trigger encoder overrun errors or repeated acquisitions of the same line. For best results, the encoder should always indicate a steady direction of motion. If this cannot be achieved, enabling IgnoreTooFastEncoder may allow the DS900 to ignore the unwanted motion and still produce accetpable images, at the cost of not being able to detect when the encoder is truly running too fast.
The DS900 series may produce acquisition errors which include "AUTO_ABORTED" in the exception message. This can happen when very short range images are acquired at a very high line rate. It is recommended to acquire range images that are at least 10 lines high to avoid this problem.
This section describes open issues concerning GigE Vision acquisition in VisionPro 9.7.
GigE Configurator defaults to an IP address of 169.254.x.x for GigE network adapter when no GigE Vision cameras are attached.
Workaround:
Plug in a GigE Vision camera and refresh the utility to retrieve the static IP address. Alternatively:
1. Open Windows Control Panel.
2. Select the network connections.
3. Select the adapter.
4. Right-click and select Properties.
5. Double-click Internet Protocol Version 4 (TCP/IPv4)
6. Set the static IP address for the adapter.
A CFG-8704e, a quad-port GigE Vision network adapter, or any network interface card that uses the 82574 Ethernet Controller can go in standy mode where the network port is inactive.
Workaround:
Download the latest Intel driver from the Intel downloads page:
https://downloadcenter.intel.com/SearchResult.aspx?lang=&ProductID=3023&ProdId=3023
The eBus Universal Pro Driver may not be functional on all GigE Vision network interface cards after installation. The GigE Vision Configuration Tool will display Not Installed for the name of the performance driver, and the eBus Universal Pro Driver checkbox will be unchecked.
Workaround:
1. Open the Local Area Connection Properties control for your GigE Vision adapter.
2. Select the eBus Universal Pro Driver if it is present and click Uninstall.
3. Close the Local Area Connection Properties control.
4. Check the eBus Universal Pro Driver in the GigE Vision Configuration Tool to install the driver.
Attempting to modify GigE Vision features for a GigE Vision camera during acquisition can cause QuickBuild to become unresponsive.
The GigE tab and the Custom Properties tab of the QuickBuild Image Source control cannot reliably read and write integer values containing a comma.
Workaround:
Do not specify integer values using commas. For example, use "1234" and not "1,234".
This section describes open issues concerning installation of VisionPro.
The VisionPro installer can fail to install the .NET 4.7.2 prerequisite if the Windows 10 OS is not fully updated.
Workaround:
Perform all Windows 10 updates on the PC and relaunch the VisionPro installer.
After installing the latest VisionPro release but before rebooting the PC, the GigE Vision Configuration Utility might crash.
Workaround:
Reboot the PC.
This section describes miscellaneous issues in VisionPro 9.7.
Some virus scanning utilities can incorrectly flag/quarantine VisionPro dynamic-link library (DLL) files. Cognex verifies that all binaries are virus-free prior to being released.
Workaround:
Add the DLL files to the whitelist of your particular virus scanning software.
This section describes issues concerning Model Maker in VisionPro 9.7.
An existing Visual Studio project containing a CogSynthModelEditorV2 edit control might report a problem opening Cognex.VisionPro.Core.dll. The problem is limited to 64-bit OS machines.
Workaround:
1. Open the file MyForm.designer.cs in the IDE text editor and remove the following line:
this.cogSynthModelEditorV21.Subject = ((Cognex.VisionPro.ICogShapeModelCollection)(resources.GetObject("cogSynthModelEditorV21.Subject")));
2. Open the file MyForm.resx in the resource editor editor and remove the following row from the table:
cogSynthModelEditorV21.Subject
3. Save all files and rebuild the project.
This section describes open issues concerning QuickBuild in VisionPro 9.7.
When vision tools having a variable number of inputs are reset to their default state through their tool edit controls, any links to those inputs must be recreated. Sometimes the links will be drawn before the link is recreated, but inspecting the input point values will reveal that the link is not working. To recreate the links, first create the objects corresponding to the inputs, then drag from source node to destination node.
This section describes open issues concerning hardware security in VisionPro 9.7.
VisionPro running on a PC using Microsoft Windows 8.1 reports no licenses are enabled when using an existing security key. Checking the licenses with the Cogtool utility reports "unsupported firmware".
Workaround:
1. Remove the security key.
2. Uninstall Cognex Drivers.
3. Reinstall Cognex Drivers from the VisionPro installation media.
4. Install the security key.
This section describes miscellaneous open vision tool issues in VisionPro 9.7.
The CogIPOneImageConvolveNxM operator may produce incorrect results if used with a kernel having more than 256 elements. For square kernels that means 17x17 or larger kernels can give incorrect results.
Workaround:
Cognex recommends using either the CogIPOneImageSampleConvolve operator or the CogIPOneImageSubSampler operator instead.
This section describes open issues concerning the PMRedLine tool in VisionPro 9.7.
VisionPro fails to correctly calculate the value of CogPMRedLineResult.ContrastFraction in existing applications when migrating to this release.
Workaround:
Retrain the pattern for any PMRedLine tool you use in applications created using an earlier VisionPro release, and save your changes.