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-19	Failed to check if block 0 in the EEPROM master table is occupied	If the SDK or Studio is looking for cameras while the camera is booting, there is a small chance that an exception will be thrown with the message {{Failed to check if block 0 in the EEPROM master table is occupied}}.	One+ Rev B …and more	NA	NA	v2.3.0
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.	Two Rev B2 One+ Rev B …and more	To avoid this issue, use Linux kernel 5.4, which is the LTS (stable) base Linux kernel for Ubuntu 20.04.	NA	NA
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 Two, compared to using Zivid One+.	Two Rev B2 One+ Rev B …and more	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.	Two Rev B2	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” exception thrown during capture	On very rare occasions a “Command failed: CameraImageTimeout” exception may be thrown during capture.	Two Rev B2	This will resolve itself on the next capture.	NA	NA
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	Do not create many Zivid::Applications in a single process. Make one Application and use it for the lifetime of the process.	NA	NA
E-10	Zivid Two may hang if the PC process is aborted mid-capture, leading to a reboot after 15 seconds.	Zivid Two 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 Two will reboot after 15 seconds to recover from this state.	Two Rev B2	Avoid network congestion, and/or wait for the camera to reboot.	v2.4.0	NA
E-9	OpenCV assertion error on Windows	If you run the SDK in debug mode on Windows, with a Zivid Two with Calibration model v2.1.0, then you may hit an OpenCV assertion error during capture.	Two Rev B2	NA	v2.4.0	v2.4.1
E-8	Red status indicator LED may flash even when there is no error.	The red status indicator LED may flash even when there is no error to report.	One+ Rev C	NA	v2.3.0	v2.4.0
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
E-1	Power-up fails below 2°C	There is a chance that the camera may fail to power up below 2°C.	Two Rev B2	Make sure that the camera is powered up when it is above 2°C.	NA	NA