- March 24, 2020 at 3:14 am #21479AnonymousInactive
I think this is probably the best place to post this, but please let me know if I should move it to another forum topic:
I am trying to get the arducam autofocus (AF) camera module to work with the Nvidia Xavier developer board. I have 2x B0182 arducam Raspberry Pi V2 8mp motorized focus drop in camera replacements. I am using these cameras along with the Leopard imaging LI-JXAV-MIPI-ADPT-4CAM which breaks out 4 csi connectors on the Nvidia Xavier. I can access the AF cameras just fine, capture and stream video via commands using “argus_camera” or “gst-launch-1.0 nvarguscamerasrc” on the xavier but the focus motors don’t show up anywhere on any of the i2c-busses. Note that the motors don’t show up for either of the camera modules I have (either both motors are broken or the B0182 doesn’t work with the Xavier/Leopard imaging combo).
I also tried getting these to work on a Raspberry Pi B3 with no success, but after reading the product page a little more carefully, I don’t think this version (B0182) is meant to work with the Pi B3/3+: “Note: The camera can be used on compute module CM3, CM3+, and NOT compatible with Raspberry Pi 3B/B+”
As the Xavier i2c bus configuration is slightly different than the Jetson Nano’s, I ran an i2cdetect command on each of the i2c busses I can see to try to hunt down where the motors turn up. This returned the addresses below, which I don’t think contains the motor addresses anywhere (UU are the reserved addresses on each bus). Busses 3, 5 and 6 took too long to scan and are assumed to be used internally/blocked. Bus 30-33 are expansions provided by the Leopard Imaging board – you can see the RPi camera V2 encryption chip address, 0x64, show up on bus 30 where the AF camera is connected. So I would expect to see 0x0c show up on bus 30 for the AF motor control as well.
Bus 0: 0x50 0x56
Bus 1: 0x74, UU: 0x08, 0x40, 0x41
Bus 2: 0x54, UU: 0x10, 0x70
Bus 4: 0x20, 0x40, 0x50 UU: 0x3C, 0x4C, 0x68
Bus 7: UU: 0x1A
Bus 8: 0x74 (40-pin header bus)
Bus 30: 0x54 0x64, UU: 0x10, 0x70
Bus 31: 0x54, UU: 0x10, 0x70
Bus 32: 0x54, UU: 0x10, 0x70
Bus 33: 0x54, UU: 0x10, 0x70
Any insight on if the B0182 should work on the Nano (which I’d then expect to work on the Xavier as well) or if I just happened to get 2 faulty motor modules would be much appreciated. Similarly any help debugged would also be appreciated.
- March 25, 2020 at 5:42 pm #21506
- April 8, 2020 at 8:58 pm #21712AnonymousInactive
Thanks for your advice Wong, I took a while because I was pursuing a few different ways trying to get this to work:
Following your advice, I tried a few combinations of opening a camera pipeline and communicating with the motor, but nothing worked. I tried both opening a gstreamer pipeline in the same process, and in a separate process, trying both i2cdetect (which never recognised any hardware at that address) and just blindly sending i2c commands to that address, all of which failed.
In trying to figure out if it is the Xavier, the autofocus motors, or the motorized camera configuration I have, I went and borrowed a 5 MP motorized focus camera and tried that with the Xavier, which was successful. Though I didn’t have the drivers to connect to the OV5647 sensor and see the motor in action, I could still send commands to the autofocus motor and hear it move. This led me to believe that either I got two faulty camera modules, or the specific camera set up (B0182) – which is designed to be a drop in replacement as a way to circumvent the crypto chip on the Raspberry Pi cam V2 – doesn’t work with the Xavier (or possibly Jetsons in general?).
Along these lines I ordered a B0181, which comes with the entire breakout board and is designed to only works on the Nvidia jetsons, and it worked fine on the Xavier – all the demos work as expected.
Do you think that I received two faulty motorized focus units (B0182), or that the B0182 doesn’t work on the Nvidia platform (seeing how the B0181 worked without issue)?
- April 14, 2020 at 9:22 am #21843
Sorry, my account above was deleted multiple times by a bug in your verification emails.
To bump this – should I expect the B0182 to work with the Nvidia platform, or did I just receive 2 units with faulty motors? It would be cheaper to replace my current cameras with B0182 (as opposed to buying the B0181), but based on my experience I don’t know if I should actually trust them.
- May 11, 2020 at 1:35 am #22460
- May 11, 2020 at 6:17 pm #22483
No worries about the delay, it’s understandable with the state of things. Below is a picture of the two B0182s that I originally purchased with one mounted on a v2.1 board. Let me know if this picture captures what you were looking for or if you’d like another angle or two, I can email more to you.
- May 12, 2020 at 7:17 pm #22542
Hi @abattiston ,
Through the picture you provided, we can confirm that a resistor on the module has a welding error. You now have two options:
1. You can re-weld yourself
2. We give you a replacement
If you want to solder by yourself, here is the correct welding diagram:
If you want to replacement, please let me know and our after-sales staff will contact you.
- May 13, 2020 at 10:52 am #22594
I don’t think I’m skilled enough to do that small of a solder job, please put me in touch with your after sales team.
- May 13, 2020 at 6:26 pm #22601
- May 27, 2020 at 1:47 am #23133eikishParticipant
@abattiston how are you physically connecting the cameras to the LI-JXAV-MIPI-ADPT-4CAM board? It seems from the online picture that the connector is completely different than the standard camera flex cable? I’m curious because I’m looking at buying that board myself to use with Xavier and Arducams…
- May 27, 2020 at 5:13 pm #23153
- May 28, 2020 at 6:01 pm #23222
Have you solved your problems?
- June 2, 2020 at 1:08 pm #23478
No not yet. I’ve replied out to sales on May 24th with my address and previous order number but haven’t heard back since then.
- June 3, 2020 at 7:17 am #23512
Sorry to hear that. Can you post it again? Maybe the mail was abnormally lost
- July 5, 2020 at 11:27 pm #24865
- You must be logged in to reply to this topic.