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-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 Two factory reset button may not work	Some of the Zivid Two 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.	Two L100 Rev A0 …and more	https://support.zivid.com/en/latest/support/reset-button-failure.html	NA	NA
E-23	Firmware update on Zivid Two can in rare cases fail with timeout	Firmware update of Zivid Two 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.”	Two L100 Rev A0 …and more	The situation can be resolved by power-cycling the camera, restarting the application and doing FW upgrade again.	NA	NA
E-22	Zivid One+ camera can end up with a damaged projector if powered on for weeks before the first capture is triggered from the application	Failing to perform DLP projector mirror parking on a device can lead to the mirrors becoming stuck. The idle-state timer that parks the mirrors is started on every capture, but if the camera boots and sits idle for a long time this may never happen.	One+ Rev B …and more	NA	NA	v2.6.0
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 L100 Rev A0 …and more One+ Large Rev B …and more	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 Two, compared to using Zivid One+.	Two L100 Rev A0 …and more One+ Large 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 L100 Rev A0 …and more	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 L100 Rev A0 …and more	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	NA	NA	v2.7.0
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 L100 Rev A0 …and more	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 L100 Rev A0 …and more	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