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

gemini330 ros2 depth cloud point result_frame->dataSize() not stable #93

Open
tarikbeijing opened this issue Feb 25, 2025 · 0 comments
Open

Comments

@tarikbeijing
Copy link

it is about this void :
void OBCameraNode::publishDepthPointCloud(const std::shared_ptrob::FrameSet &frame_set) {

i see that the result frame when i display it crop regularly. i have follow back the data
i see coming from camera
auto point_size = result_frame->dataSize() / sizeof(OBPoint);

dadasize 12288000
dadasize 12288000
dadasize 12288000
dadasize 11059200<<<<<----
dadasize 12288000
dadasize 12288000
dadasize 11059200<<<<<<---

later when i look the valid count
point_cloud_msg->width = valid_count;

i have also the same effect

valid_count2 : 909707
valid_count2 : 913847
valid_count2 : 911681
valid_count2 : 737903<<<<<----
valid_count2 : 909707
valid_count2 : 913847
valid_count2 : 913647

when i display the result it look like that the max opening angle regulary is not the same

it disturbing a lot the result.

in the opposite the color_depth frame dont have that problem

i used 2 different gemini 330, both has this problem, i use the last firmware and ros2 driver, lunux ubuntu 22.04

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant