-
Notifications
You must be signed in to change notification settings - Fork 26
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
ximea.xiapi read camera image sometimes crush #16
Comments
I am in the process of updating the repository to only support the GelSight Mini device. |
yes, I use mini on linux. I have push a ros2 package version: https://github.com/CarlDegio/gelsight_ros2. two nodes use gsdevice so ximea api is used by default. |
I just updated the repository and none of the code uses ximea. If you update and reinstall gelsight, the issue should go away. |
Thank you! I will try it later |
the change seems good. But the crush is still exist. And it just happened randomly and frequently. just like this:
Do you have any suggestions for this, like the frequency to read, or the usb cable. |
At present, I found that it is likely that the usb plug is not in good status. |
If the lights are not staying on all the time, that would indicate a USB problem. |
Yes, I believe I have found the reason. The mini usb on gelsight is not tight. Some contact will lead it offline. |
Please send an email to [email protected] with the serial number of the Mini and a short description of the problem. Thank you, |
@CarlDegio were able to resolve your issue ??? |
Yes, Basically solved. I found that as long as I don't touch it during running (such as fixed), it basically functions normally. But maybe the miniUSB lock strength on the sensor still needs to be strengthened. |
Yes, you are correct, the USB connection needs to be reinforced. We are working on making it better. |
I use showimage and show3d in ros2. Current gsdevice code use:
this sometimes occur:
it seems that the problem is read image from camera failed. Is there any solution? Such as read image by opencv?
The text was updated successfully, but these errors were encountered: