Hi everyone, hoping to get some help here. I purchased two of the Sync Dual-Camera Bundle Kits for Jetson Orin. The device is being recognized over I2C but the camera feed is just a blank green image — no actual picture, just solid green.
While I was troubleshooting, I accidentally damaged one of the side camera ports on the adapter board — it’s physically broken now. Before I go further, I wanted to ask: can the empty center port on the adapter board be used as an alternative to the broken side port? I noticed it’s unpopulated but maybe it carries the same signals?
Thanks for the photos. Unfortunately, the center port on that adapter board is a reserved interface — it does not carry the necessary signals for stereo camera operation. It cannot be used as a substitute for the damaged side port.
The green screen issue can’t really be diagnosed until the physical connection is restored, since a broken connector means the camera isn’t properly linked to the board. You’d need to get that adapter board repaired or replaced before we can dig into the green image problem further. If you reach out through the official support channel, they can help with repair or replacement options for the adapter board.
Quick update — I’ve now tested with two brand-new AR0245 CSI stereo camera kits for the Jetson Orin, so the damaged adapter board from before is out of the equation. But the blank green image issue is still there. Across both brand-new kits.
Here’s what I’ve confirmed so far:
The sensor probes correctly over I2C — the device is detected.
But the sensor doesn’t seem to be initializing properly. No image data, just green.
I’ve double-checked that the camera driver is connected to the 4-lane CSI port on the Jetson.
Followed all the setup instructions exactly.
Same behavior on every unit. I’m starting to think this isn’t a sensor defect — it’s something else.
Also, I was trying to buy a spare adapter board and extra ribbon cables (both the camera-side and adapter-side cables) individually on the website but couldn’t find them listed. Are they available separately?
On the adapter board and cables — could you clarify which specific cables you’re looking for? I’m attaching a marked screenshot, just confirm if those are the ones you need and I’ll point you in the right direction.
On the green image — the 4-lane CSI connection is critical, and this is the most common thing that trips people up. Can you post a photo of your actual hardware connections on the Jetson Orin? I want to visually verify that the camera is connected to the correct 4-lane CSI interface and not accidentally going into a 2-lane port. A mismatch there would absolutely cause the sensor to show up on I2C but fail to stream frames — exactly what you’re describing.
Alright, I went ahead and ordered two more complete camera kits just to absolutely rule out any sensor defects. That’s four units total now, all brand new.
Same behavior across ALL of them:
Sensors consistently probe fine over I2C, always detected.
But the ribbon cable connections are extremely sensitive to any slight movement. If the ribbon gets bumped even a little, frame capture just dies and never recovers — even though the sensor is still detected on I2C. A full power cycle is needed to get anything back.
This really feels like a CSI synchronization or signal integrity problem, not a sensor defect. Four kits can’t all be bad in the exact same way.
My next step: I’m going to try using those short ribbon extension cables (3-4 inches) that were mentioned earlier, combined with a brand new camera adapter board. If that doesn’t fix it, I’ll probably have to return the recent purchases.
Thanks for the detailed update. That’s a lot of useful data — four units behaving identically and the movement sensitivity definitely point away from sensor defects and toward something at the signal level.
This kind of issue (CSI sync dropping on movement, I2C staying alive) is tricky to debug over forum posts alone. I’ve sent you details via private message for setting up a remote assistance session so we can look at this live on your Jetson Orin. Please check your messages when you get a chance. We’re on UTC+8 timezone — the booking link in the PM will show availability in your local time.
Just a follow-up after digging into this more on our side:
We agree the connection loss with slight movement is almost certainly a signal integrity issue related to the extension ribbon cables. The plan to test with shorter FPC cables (3-4 inches) along with a fresh adapter board is the right move — that’s what we’d try next as well.
We’re currently checking inventory for 3-4 inch FPC cables on our end and will update once we have sourcing sorted out.
One more thing — we’d like to replicate your mechanical setup internally for testing. Are you using a 3D-printed enclosure, and if so, is it the standard STEP file from our website or a custom design? If it’s modified, could you share the STEP file? The enclosure geometry can sometimes affect how the ribbons are routed and stressed, so we want to match your setup as closely as possible.
