MIPI FFC cable length limits for split camera modules

Splitting the sensor head from its carrier board frees space in a compact vision station, and the first question that decides the mechanical design is always the same: how long can the ribbon be? A MIPI CSI-2 camera module connects through a flat flexible cable, and the honest planning number is a few tens of centimetres, not a metre. This guide gives you the quantity that sets the limit — the per-lane data rate — a length table to plan against, a worked example with the arithmetic shown, and the two clean ways out when your split is longer than any ribbon can carry.

The length to plan on

A ground-guarded, impedance-matched ribbon reliably carries a CSI-2 link 20-30 cm at low to medium lane rates, 15 cm around 1 Gbps per lane, and 10 cm or less at the 2.5 Gbps per lane fast modules run. Longer than 30 cm, no ribbon passes a proper qualification with margin. No data sheet prints a maximum length, so treat these bands as the design envelope and settle the number at the bench with the exact parts. When the mechanical split needs more, the decision is already made: a serializer pair, or an interface built for cable.

Why the standard prints no cable length

CSI-2 specifies the electrical link at its ends: a transmitter swing of about 200 mV differential, lane timing, and the eye the receiver must recover. A driver is qualified into a defined test channel, not into your cable. Your channel is the module connector, the ribbon, both carrier connectors and the board stubs, and every centimetre of it spends the budget.

That is why bench results cluster the way they do. The pattern repeats across platforms: a link passes at 5 cm, then fails at 10 or 20 cm when the only change is the cable. The silicon is fine either way; the channel has stopped delivering an open eye. Where those failures surface in software is covered by the CSI-2 capture pipeline, sensor to host.

What closes the eye

Three mechanisms, all of them worse as the bit rate rises:

• Loss. A flat conductor is a small, lossy transmission line. Attenuation climbs with frequency, so the same ribbon looks electrically longer at 1 Gbps than at 200 Mbps.
• Crosstalk. Adjacent pairs couple into each other, and the coupling lands directly in the eye. Ground conductors interleaved between the pairs cut it hard; that is what a ground-guard construction buys.
• Reflections. Every impedance dip sends energy back toward the transmitter. The pair is designed around 100 Ω differential, and a generic ribbon plus a generic connector wanders off that target at every joint.

Skew adds a fourth term: the two conductors of a pair, and the pairs relative to each other, must arrive within a fraction of a bit period. Ribbon conductors are cut to equal lengths, but connector pads and vias add uncontrolled stubs. The board side of the channel has its own limits — the trace length and signal integrity guide covers those — and the lane rate feeding this whole budget comes from the camera's timing, worked through in the lane bandwidth explainer.

The length budget by lane rate

Compute your per-lane rate first, then read the length the table allows:

Hold one band of margin when the housing runs hot, the loom passes motor cables, or the frame rate may rise later. These bands are what designs routinely pass with proper cable and matched connectors; they are a planning envelope, and the bench qualification below is what settles the number for your assembly.

Worked example: a 1 MP mono module, raw10, 60 fps, four lanes

Take a typical split-head module: a 1 MP mono sensor of 1280×800 pixels, read out at 60 fps, packed as raw10 (10 bits per pixel) and sent over four data lanes. These are illustrative inputs for the class of module this kind of stereo-style split is built around, not a data-sheet row for any specific part.

The rule, in words: multiply width by height by bits per pixel by frame rate to get the payload rate; add about 15% for packet headers and footers; divide by the lane count. Blanking is excluded, so the real line rate runs a little higher still.

Arithmetic:

• 1280 × 800 = 1,024,000 pixels per frame
• 1,024,000 × 10 bits = 10,240,000 bits per frame
• 10,240,000 × 60 fps = 614,400,000 bits/s ≈ 614 Mbps payload
• 614 Mbps × 1.15 ≈ 707 Mbps on the wire
• 707 Mbps ÷ 4 lanes ≈ 177 Mbps per lane

At about 177 Mbps per lane the link sits in the top band: a ground-guarded, impedance-matched FFC carries it at 20-30 cm, so plan the split at 30 cm maximum and fix the cable drawing from the start. Double the frame rate to 120 fps and the lane rate doubles to about 353 Mbps — same band, same plan. Swap in a 5 MP module (2592 × 1944) at the same 60 fps and the arithmetic gives 3,023 Mbps payload, about 3,477 Mbps on the wire, about 869 Mbps per lane: the middle band, so the plan drops to 15 cm. The rate, not the centimetres, is what you are engineering — and past 30 cm, no band helps.

Specifying the ribbon and the connectors

Order the cable by construction, not by length alone:

• Ground guard. Ground conductors interleaved between the differential pairs for the whole length of the cable.
• Controlled impedance. 100 Ω differential, stated in the cable drawing. Impedance-controlled FFC is a standard catalogue item; a generic camera-module ribbon is not one.
• Matched connectors at both ends. Use a ground-terminal connector family made for shielded, impedance-matched FFC, so the 100 Ω target holds through each joint. The connector matters as much as the cable.
• One continuous run. No adapters, no couplers, no mid-run splices; every extra joint is a new discontinuity.
• Same pitch and keying both ends, with the latch treated as a wear part — the ribbon cable latch and length limits guide gives the replacement rules.

Routing is part of the channel too. Keep the ribbon away from motor and power cables, cross anything unavoidable at right angles, and treat plain FFC as a static part: a head on a moving joint needs a flex-rated cable or a different interface. Extension assemblies sold for CSI cameras exist, and the CSI extension cable compatibility checks are the list to run before trusting one.

A different module on the same carrier

Swapping in another module works only if the carrier's side of the channel still matches:

• Connector and pinout. Same FFC pitch, same pin count, and the carrier's pin map assigned to the same lanes. A mismatch here is a re-layout, not a cable choice.
• Lane count and rate. The carrier routes as many lane pairs as the new module drives, and the host link rate must be set for the new module's timing.
• Control side. The control bus and the host's sensor driver must support the new sensor; register maps differ between sensor families.
• Channel budget. Recompute the per-lane rate with the new module's resolution and frame rate, then re-read the table above; the old cable may no longer qualify.

The match-the-host compatibility list is the systematic version of these checks.

Qualify before you freeze the layout

The bands in the table are earned by the exact assembly: same module, same cable drawing, same connector parts, run at the full frame rate. Qualify at the hottest ambient the housing sees, not at bench temperature — a link with two centimetres of margin at 25 °C can close inside a warm enclosure.

Judge the link by errors, not by pictures. Occasional CRC errors and dropped bursts are the early warning; visible symptoms — smeared or shifted rows, a lane that drops frames, sudden noise on a mono image — mean the eye is mostly closed already. The isolation order in sensor detected but frames time out separates interface faults from configuration ones, and the swap test in identical USB camera timeout is the fastest way to pin a failure on the cable itself.

Handle bare modules at an ESD-safe station; the low-voltage lanes and the sensor die have little tolerance for a static discharge.

Past 30 cm: two ways out

A serializer pair. A small chip beside the sensor serializes the CSI-2 stream onto a coax or twisted pair, and a matching chip at the carrier recovers it, with control data riding back the other way. Links like this run for metres inside real products. It is a module-design decision made before the sensor board is laid out, not a cable added afterwards.

A cable-native interface. GigE and USB3 board-level cameras put the sensor behind an interface designed for cable. GigE reaches 100 m on one Ethernet segment; USB3 covers about 3 m passively. When the split is machine-scale, this is the cheaper answer by a wide margin, because every cable, connector and length in the catalogue is already qualified for it.

The board-level cameras category and the camera finder are where these parts live.

Values as printed in each product's data sheet; open a part for its drawing and full specifications.

In that table, the MV-CB016-10GM-M-W is a 1.6 MP mono board camera with a global shutter, an M12 mount and a GigE port; the LS-BCM-0061 is the miniature option at 1.3 MP on a 1/2.7" sensor, also GigE; the LS-BCM-0003 moves 3.1 MP over USB3 at 120 fps with a global shutter.

Where the head still speaks CSI-2 and only the distance is the problem, a CSI-over-Ethernet extension kit keeps the existing module — the CSI Ethernet extension kit guide covers the no-driver path, and USB cable length limits for 3D cameras runs the same budget arithmetic for the USB side.

For the cables themselves, both interfaces have high-flex, drag-chain-rated parts: the LS-CBL-0199 GigE cable comes in 3 m with screw locks, and the LS-CBL-0219 matches it in 3 m high-flex USB3 build.

For a fixed GigE run beyond the bench, RJ45 camera data cables come in 15 m, like the LS-CBL-0117.

The camera cables category holds every family.

When the ribbon answer is wrong anyway

Three cases where shortening the cable is not the fix. A head on a moving axis or through a hinge has no plain-FFC answer at any length: flex-rated cable if the run stays short, a cable-native interface if it does not. A housing that runs hot or washes down moves the whole envelope: qualify there, and if the margin is gone, serialize. And when the fix is a new camera instead of a new cable, the bench work that proves it is in the board camera evaluation checklist.

Next step. Work out your lane rate with the formula above, read your length from the table, and pick the ribbon by construction: ground guard, 100 Ω, matched connectors. If the split will not fit, the accessories finder lists the data-cable families and the camera step of the configurator builds the camera side from your field of view and frame rate. The physical-layer planning guides live on the systems topic page.