Complete Zivid Errata

Text with dots under it, like this sentence, hide more information. Hover mouse over to reveal.

Key	Summary:	Description:	Revisions:	Workaround:	Since:	Fixed in:
E-33	GenICam/HALCON point clouds appear darker than in Zivid Studio	Since SDK 2.11, Studio will display color/RGB values in the sRGB color space. This makes the color images look brighter and more correct on monitors, compared to previous versions of Studio, which displayed colors in linear RGB color space. Capturing via GenICam/HALCON will still show colors in linear color space, which will appear darker on the screen.	One+ Large Rev B One+ Large Rev C One+ Medium Rev B One+ Medium Rev C One+ Small Rev B One+ Small Rev C 2 L100 Rev A0 2 M70 Rev B2 2 M70 Rev B3 2+ Rev A0	NA	v2.11.0	v2.14.0
E-32	Capturing a higher resolution point cloud after a lower resolution point cloud fails in Halcon (GenICam only)	The memory buffer in Halcon does not reset after a capture. As a consequence, if you first capture a lower resolution point cloud, the size of the memory buffer will not be large enough for a higher resolution capture, which is why the higher resolution capture fails. Example capture sequence that fails: set_framegrabber_param (AcqHandle, ‘SamplingPixel’, ‘blueSubsample2x2’) grab_data (Image, Region, Contours, AcqHandle, ObjectModel3D) set_framegrabber_param (AcqHandle, ‘SamplingPixel’, ‘all’) grab_data (Image, Region, Contours, AcqHandle, ObjectModel3D)	2 L100 Rev A0 2 M70 Rev B2 2 M70 Rev B3 2+ Rev A0	NA	v2.10.0	v2.14.0
E-30	Exported PLY/PCD/XYZ point clouds appear darker than in Zivid Studio	Since SDK 2.11, Studio will display color/RGB values in the sRGB color space. This makes the color images look brighter and more correct on monitors, compared to previous versions of Studio, which displayed colors in linear RGB color space. Exporting frames as PLY/PCD/XYZ file will store the color values in linear color space, which will appear darker on the screen. This has been the case for all SDK releases.	One+ Large Rev B One+ Large Rev C One+ Medium Rev B One+ Medium Rev C One+ Small Rev B One+ Small Rev C 2 L100 Rev A0 2 M70 Rev B2 2 M70 Rev B3 2+ Rev A0	NA	v2.11.0	v2.14.0
E-29	Zivid 2/2+ can show incorrect image when using Zivid::Experimental::Projection::showImage()	Sometimes when Zivid::Experimental::Projection::showImage() is used the camera may display an incorrect image with its projector.	2 L100 Rev A0 2 M70 Rev B2 2 M70 Rev B3 2+ Rev A0	NA	v2.10.0	v2.11.1
E-28	Zivid 2/2+ may appear unresponsive/offline if PC process is aborted mid capture	If the PC process is aborted non-cleanly in the middle of a capture, then in very rare cases, the Zivid 2 or 2+ camera may become unresponsive and not appear via Zivid SDK, Zivid Studio or ZividListCameras. The camera will also not respond on ping. However, Ethernet activity LEDs on the camera may still blink as normal. This issue can happen if you do long captures and have network congestion (fex using 1G network connection).	2 L100 Rev A0 2 M70 Rev B2 2 M70 Rev B3 2+ Rev A0	NA	NA	v2.12.0
E-27	Crash on Windows when using Zivid 2 or 2+ cameras with Intel GPU	A crash with exception code c0000005 (Access violation) can in rare cases happen when using Zivid 2 or 2+ cameras on Windows OS. This issue can happen when using Intel as compute device. The crash will happen during a capture, and the frequency between crashes can be from a few hours to a few days on affected systems. This issue has not been observed when using Ubuntu.	NA	NA	NA	v2.13.0
E-26	Segmentation fault on Linux	libZividCore.so exported weak symbols from third-party libraries like boost and asio. If a user were also using these libraries as part of their software, crashes such as segmentation faults could occur.	NA	NA	NA	v2.9.0
E-25	Incorrect patterns/stripes in upper parts of the point cloud	When using Nvidia driver 510 and capturing with two or more cameras back-to-back, on occasion incorrect patterns/stripes can be seen in the upper parts of the point cloud. This issue has only been seen on this Nvidia driver version.	NA	We recommend using a different Nvidia driver version if you capture with multiple cameras. Drivers 470, 515 and 525 have been tested and are working well. This issue is not visible if you only use one camera.	NA	NA
E-24	Zivid 2 factory reset button may not work	Some of the Zivid 2 Rev B2/B3 may not have a working factory reset button for resetting the network configuration. The status LED will flash correctly, indicating that the network reset has been done, but the IP of the camera remains the same as before.	2 Rev A0 2 Rev B2 2 Rev B3	https://support.zivid.com/en/latest/support/reset-button-failure.html	NA	NA
E-23	Firmware update on Zivid 2 can in rare cases fail with timeout	Firmware update of Zivid 2 camera can in very rare cases fail with the following error: ”The firmware reported a timeout while updating the camera. Please power cycle the camera, restart the application, and try again.”	2 L100 Rev A0 2 M70 Rev B2 2 M70 Rev B3 2+ Rev A0	The situation can be resolved by power-cycling the camera, restarting the application and doing FW upgrade again.	NA	NA
E-17	”CL_OUT_OF_RESOURCES” or “OpenGL error: GL_INVALID_OPERATION” on Ubuntu 20.04 and Intel GPU	When using Linux 5.8 kernel (released with Ubuntu 20.04.2 when using the newer HWE kernels), with an Intel GPU as rendering device, Zivid Studio, and Visualizer can give errors like “CL_OUT_OF_RESOURCES” and “OpenGL error: GL_INVALID_OPERATION” when displaying the point cloud.	One+ Large Rev B One+ Large Rev C One+ Medium Rev B One+ Medium Rev C One+ Small Rev B One+ Small Rev C 2 Rev A0 2 Rev B2 2 Rev B3	NA	NA	v2.7.0
E-16	Capture time can be higher on Windows compared to Linux for identical hardware.	The difference is larger for low exposure times, and lower for higher exposure times. The relative difference between Windows and Linux on identical hardware is higher when using Zivid 2/2+, compared to using Zivid One+.	One+ Large Rev B One+ Large Rev C One+ Medium Rev B One+ Medium Rev C One+ Small Rev B One+ Small Rev C 2 L100 Rev A0 2 M70 Rev B2 2 M70 Rev B3 2+ Rev A0	None	NA	NA
E-15	Capture time on Windows can occasionally be longer (more than 1 second longer than normal)	Capture time on Windows can occasionally be longer (more than 1 second longer than normal) due to Ethernet packet loss leading to data re-transmits. We recommend to increase “Receive Buffers” and “Transmit Buffers” in the network driver settings in Windows to reduce the occurrence of packet loss.	2 L100 Rev A0 2 M70 Rev B2 2 M70 Rev B3 2+ Rev A0	Increase “Receive Buffers” and “Transmit Buffers” in the network driver settings in Windows to reduce the occurrence of packet loss.	NA	NA
E-14	”CameraImageTimeout” or “Timeout” exception thrown during capture	On very rare occasions a “Command failed: CameraImageTimeout” exception may be thrown during capture.	2 L100 Rev A0 2 M70 Rev B2 2 M70 Rev B3 2+ Rev A0	NA	NA	v2.14.0
E-13	Memory leak when creating Zivid::Application	When the Zivid::Application is created it allocates memory. All of this memory is not free’d when the object is destroyed. The leak can cause out of memory errors if you create many Zivid::Applications in the same process	NA	NA	NA	v2.7.0
E-10	Zivid 2/2+ may hang if the PC process is aborted mid-capture, leading to a reboot after 15 seconds.	Zivid 2/2+ may hang if the PC process is aborted mid-capture when there is also network congestion. Network congestion can typically occur when multiple cameras are connected on a 1G link. Zivid camera will reboot after 15 seconds to recover from this state. In some specific rare occasions, the camera may not reboot on its own. See {{ERRATA-28}} for more information.	2 L100 Rev A0 2 M70 Rev B2 2 M70 Rev B3 2+ Rev A0	NA	v2.4.0	v2.13.0
E-9	OpenCV assertion error on Windows	If you run the SDK in debug mode on Windows, with a Zivid 2 with Calibration model v2.1.0, then you may hit an OpenCV assertion error during capture.	2 Rev A0 2 Rev B2 2 Rev B3	NA	v2.4.0	v2.4.1
E-7	SDK may hang if SIGTERM is received	If SIGTERM is sent to Zivid SDK during operation the SDK may hang.	NA	NA	v2.3.0	v2.5.0