Are there any resolution limitations imposed by the Arducam Ethernet Cable extension solution?
It may be necessary to reduce the MIPI rate to affect the frame rate,
The chip in the network extension solution only supports 900Mbsp/Lane. If the original MIPI rate is very fast, you need to modify the camera driver PLL configuration part. After the MIPI rate decreases, the frame rate will also decrease.
Doesn’t affect resolution much.
It depends on which camera you are buying.
I just realized that it looks like 1080x1920 60 fps is not supported with the Pis two lane, is that correct?
What is the SerDes chip in the extension solution and how low can the data rate go down?
Will the camera current consumption vary much with frame rate?
I’d like to extend the reach of the four cameras in the Arducam 8MP*4 IMX219 Quadrascopic Camera Bundle Kit. Would this Ethernet cable extension do the trick?
Hi @Dion and @Edward ,
I am using a Hawkeye 64 MP with the ethernet extension kit and haven’t been able to make it work. I get marginal/intermittent results.
My suspicion is that the hawkeye MIPI default rate 912 Mbps/lane exceeds 900 Mbps/lane limit; need lower-rate PLL config.
Is there a modified arducam_64mp driver, or do you have the exact sensor register changes — including any companion PLL/VCO/timing registers beyond the multiplier — to run the 64MP Hawkeye at ≤900 Mbps/lane so it works reliably over the Ethernet extension kit? Reduced frame rate is fine; we only need stills.
Symptoms
- Camera enumerates fine (I²C control OK: “Device found Arducam 64MP”, all modes negotiate).
- Frame capture is unreliable: intermittent Dequeue timer expired / Camera frontend has timed out (no pixel data), and some completed frames are corrupted (magenta/torn bands), most reproducibly in the 1280x720 mode.
- On a short direct ribbon (no kit) the exact same setup is 100% reliable, clean pixels at 1080p and full 64MP.
The website lists the Hawkeye as supposed to be able to work out of the box so let me know if I am missing something.
Thanks!