-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
D430 module not detected by realsense viewer #13264
Comments
Hi @mprat Which version of the Vision Processor D4 Board are you using with your D430 module, please? A D430 without an RGB sensor should be used with the V1 version of the D4 board. The other versions of the D4 board are: V2: used in D435i cameras with the D430 module and an RGB sensor V3: Used in D455 cameras with the D450 module V4: Used in D405 cameras with the D401 module V5: Used in D457 cameras with the D450 module |
@MartyG-RealSense is there a way to check via serial number on the ASIC which version it is? Or is there a marking somewhere that would be visible? I'm pretty sure this is a V1 version of the board, but I can't find any mention of the version anywhere. It's not clear whether doing
|
Another thing I'm noticing is that I would expect based on the datasheet for a D430 module to have a device ID of |
If your D4 board has a sticker on it, the V1 version should have the code number J32139-120 I see that your serial number is listed by rs-enumerate-devices as ffffffffffff. This is a certain sign of a problem. In an example of this issue at #7337 (comment) the RealSense user in that case identified a bent connector on the USB cable as the cause of their particular serial number problem. The PID 0AD6 tends to appear when there is a problem with identifying the camera name, like the Intel RealSense USB2 case (like your camera ID) at the link below. https://support.intelrealsense.com/hc/en-us/community/posts/360033237894/comments/360008292933 In regard to rs-enumerate-devices, the Device Info comes from the D4 board. The supported profiles comes from querying the sensor components, which are the left and right IR sensors on the D430 module in this case. The RGB sensor would also be queried if one was present. The firmware driver identifies the camera and provides the appropriate camera name based on the components that the firmware is able to detect. For example, a D430 with a D4 V2 board would identify as D430i because D4 V2 had an IMU component but there was not an RGB sensor present (so could not be identified as D435i because of the lack of RGB). The profiles listed by rs-enumerate-devices look consistent with what I would expect from a D430 in USB2 mode. 640x480 can be streamed at 30 FPS, but 1280x720 is limited to only 6 FPS maximum. |
Thanks for the quick response - we'll confirm that the D4 board is in fact a V1, and do some checking on the cables and see if that resolves our issue. |
You are very welcome. If the D4 board is a V1, it is worth checking the interposer (the join between the two boards) in particular. If you constructed your own interposer cable then check the wiring, and if it is a pre-made one purchased from the RealSense Store then confirm that both ends of the cable are fully seated in the 50-pin connectors on the boards. On the D4 side of the connection, the interposer cable needs to be in the connector on the upper edge and not the one on the side, which is designed for a tracking module or RGB sensor and not a depth module. |
Hi @mprat Do you have an update about this case that you can provide, please? Thanks! |
This ended up being a cable (or two) that were not properly seeded! Thank you for the quick reply; I'll close the issue since it has been resolved. |
It's great to hear that you found the cause of your problem. Thanks very much for the update! |
Issue Description
Is there any documentation available for bringing up a D430 module using librealsense? When opening
realsense-viewer
, I see "device detected" but then the device does not appear in the sidebar as I am expecting. The error I see is below. Of note, the camera module is connected through a USB 2.0 interface, but my understanding is that this should not affect the ability of the viewer to see the camera. I was able to update the firmware to the latest firmware usingrs-fw-update
no problem, but I cannot find any information on error messages I am seeing below online:The text was updated successfully, but these errors were encountered: