Erratas

For a table of all erratas for all models and accessories see Complete Zivid Errata.

Erratas per camera

Key

Summary:

Revisions:

E-29

Zivid 2/2+ can show incorrect image when using Zivid::Experimental::Projection::showImage()

Workaround: Stopping and re-starting the image projection fixes this issue when it arises.

  • Rev A0

E-28

Zivid 2/2+ may appear unresponsive/offline if PC process is aborted mid capture

Workaround: Manually power cycle the camera. If you are capturing a very long capture sequence, doing a shorter capture (fewer HDR acquisitions) can help.

  • Rev A0

E-23

Firmware update on Zivid 2 can in rare cases fail with timeout

Workaround: The situation can be resolved by power-cycling the camera, restarting the application and doing FW upgrade again.

  • Rev A0

E-16

Capture time can be higher on Windows compared to Linux for identical hardware.

Workaround: None

  • Rev A0

E-15

Capture time on Windows can occasionally be longer (more than 1 second longer than normal)

Workaround: Increase “Receive Buffers” and “Transmit Buffers” in the network driver settings in Windows to reduce the occurrence of packet loss.

  • Rev A0

E-14

”CameraImageTimeout” or “Timeout” exception thrown during capture

Workaround: This will resolve itself on the next capture.

  • Rev A0

E-10

Zivid 2/2+ may hang if the PC process is aborted mid-capture, leading to a reboot after 15 seconds.

Workaround: Avoid network congestion, and/or wait for the camera to reboot.

  • Rev A0

Key

Summary:

Revisions:

E-29

Zivid 2/2+ can show incorrect image when using Zivid::Experimental::Projection::showImage()

Workaround: Stopping and re-starting the image projection fixes this issue when it arises.

  • L100 Rev A0

  • M70 Rev B2

  • M70 Rev B3

  • Rev A0

E-28

Zivid 2/2+ may appear unresponsive/offline if PC process is aborted mid capture

Workaround: Manually power cycle the camera. If you are capturing a very long capture sequence, doing a shorter capture (fewer HDR acquisitions) can help.

  • L100 Rev A0

  • M70 Rev B2

  • M70 Rev B3

  • Rev A0

E-24

Zivid 2 factory reset button may not work

Workaround: https://support.zivid.com/en/latest/support/reset-button-failure.html

  • Rev A0

  • Rev B2

  • Rev B3

E-23

Firmware update on Zivid 2 can in rare cases fail with timeout

Workaround: The situation can be resolved by power-cycling the camera, restarting the application and doing FW upgrade again.

  • L100 Rev A0

  • M70 Rev B2

  • M70 Rev B3

  • Rev A0

E-16

Capture time can be higher on Windows compared to Linux for identical hardware.

Workaround: None

  • L100 Rev A0

  • M70 Rev B2

  • M70 Rev B3

  • Rev A0

E-15

Capture time on Windows can occasionally be longer (more than 1 second longer than normal)

Workaround: Increase “Receive Buffers” and “Transmit Buffers” in the network driver settings in Windows to reduce the occurrence of packet loss.

  • L100 Rev A0

  • M70 Rev B2

  • M70 Rev B3

  • Rev A0

E-14

”CameraImageTimeout” or “Timeout” exception thrown during capture

Workaround: This will resolve itself on the next capture.

  • L100 Rev A0

  • M70 Rev B2

  • M70 Rev B3

  • Rev A0

E-10

Zivid 2/2+ may hang if the PC process is aborted mid-capture, leading to a reboot after 15 seconds.

Workaround: Avoid network congestion, and/or wait for the camera to reboot.

  • L100 Rev A0

  • M70 Rev B2

  • M70 Rev B3

  • Rev A0

Fixed issues

Key

Summary:

Revisions:

Fixed in:

E-17

”CL_OUT_OF_RESOURCES” or “OpenGL error: GL_INVALID_OPERATION” on Ubuntu 20.04 and Intel GPU

  • Rev A0

  • Rev B2

  • Rev B3

v2.7.0

E-9

OpenCV assertion error on Windows

  • Rev A0

  • Rev B2

  • Rev B3

v2.4.1

Key

Summary:

Revisions:

E-16

Capture time can be higher on Windows compared to Linux for identical hardware.

Workaround: None

  • Rev B

  • Rev C

Fixed issues

Key

Summary:

Revisions:

Fixed in:

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

  • Rev B

  • Rev C

v2.6.0

E-19

Failed to check if block 0 in the EEPROM master table is occupied

  • Rev B

  • Rev C

v2.3.0

E-17

”CL_OUT_OF_RESOURCES” or “OpenGL error: GL_INVALID_OPERATION” on Ubuntu 20.04 and Intel GPU

  • Rev B

  • Rev C

v2.7.0

E-8

Red status indicator LED may flash even when there is no error.

  • Rev C

v2.4.0