Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frame corruption #287

Open
2 tasks done
mhubii opened this issue Dec 19, 2024 · 6 comments
Open
2 tasks done

Frame corruption #287

mhubii opened this issue Dec 19, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@mhubii
Copy link

mhubii commented Dec 19, 2024

Preliminary Checks

  • This issue is not a duplicate. Before opening a new issue, please search existing issues.
  • This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description

I've been noticing a strange frame corruption recently, see below (topic: zed_node/left/image_rect_color):

frame_corruption.webm

Also see screenshots below

frame_corrupted

frame

I haven't had these issues using the zed2i in the past, so this issue could be related to the ROS driver.

Steps to Reproduce

ros2 launch zed_wrapper zed_camera.launch.py camera_model:=zed2i

Expected Result

Frames

Actual Result

Corrupted frames.

ZED Camera model

ZED2i

Environment

OS: Ubuntu 22.04
ZED SDK Version: 4.2.2
CUDA: 12.1
Release: humble-v4.1.4

Anything else?

No response

@mhubii mhubii added the bug Something isn't working label Dec 19, 2024
@mhubii
Copy link
Author

mhubii commented Dec 19, 2024

closing this issue because it is quite difficult to pinpoint it to this driver.

@mhubii mhubii closed this as completed Dec 19, 2024
@gianlucapargaetzi
Copy link

gianlucapargaetzi commented Dec 20, 2024

No solution for this? I have the same issues on a Zed Mini.

@mhubii
Copy link
Author

mhubii commented Jan 4, 2025

hi @gianlucapargaetzi, no, no solution. Happy to hear someone else is facing the issue. Re-opening it in the hopes there might be a fix. Again, it is hard to pinpoint this issue to the ZED camera, but I don't get this type of issue with the Realsense for example.

@mhubii mhubii reopened this Jan 4, 2025
@Myzhar
Copy link
Member

Myzhar commented Jan 4, 2025

Frame corruption is caused by the USB3 communication.
It does not happen with RealSense because it does not provide data at the same high resolution/frequency, so it uses less bandwidth.
Normally you can consider different causes for this type of issue.

Hardware:

  • USB3 cable too long or bad cable extenders
  • not original USB3 cable
  • cable screws not strongly strengthened
  • USB3 cable too close to motors or power cables
  • USB3 hubs
  • USB3 channel shared with other devices

Software:

  • host device overloaded: the CPU cannot retrieve data from the USB3 buffer fast enough and it overflows causing data overwrite with consequent frame corruption

Can you recognize one of the conditions from this list?

@mhubii
Copy link
Author

mhubii commented Jan 5, 2025

Been using original hardware but can try to re-run the camera in isolation to test against CPU load hypothesis. Thank you for the hints and explanations.

@tomasz-lewicki
Copy link
Contributor

@Myzhar I have been seeing intermittent frame corruption issue with ZEDM as well on Ubuntu 22.04 + SDK 4.2.2 + CUDA 12.2/CUDA 12.6.

I've tried everything from the list above, I'm using the shortest ZED-branded USB cable I have. I unplugged all other USB devices. I've tried to pin it on CPU/GPU load. But I'm observing it on a pretty-high end system running only /usr/local/bin/ZED_Explorer at ~35% load on one CPU core.

image

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

4 participants