A custom ODC cable assembly pairs the hardened ODC interface on one end with whatever your equipment actually presents on the other end — a standard indoor connector (LC, SC, FC, ST, E2000), a multi-fiber MPO, or another hardened outdoor family (FullAXS, ODVA, PDLC, NSN Boot, AARC, OptiTap, Q-ODC). One factory-built jumper replaces field splices and adapter chains. ODC® and Q-ODC® are registered trademarks of HUBER+SUHNER; E2000® is a Diamond SA trademark; FullAXS™ is a TE Connectivity trademark; OptiTap® is a Corning trademark. BWNFiber manufactures ODC-compatible assemblies to order.
The two most common builds have their own pages: ODC to LC (the FTTA standard build) and ODC to ODC (all-outdoor links, gender and extensions). Every other combination lands here. New to the ODC interface family? Start with the ODC series overview or the ODC selection guide, then come back with your two port types.
On this page: Combination matrix · Stock ODC assemblies · Specifications · Build process · RFQ checklist · FAQ
The combination matrix
Every hardened end in this matrix is a sealed interface rated IP67/IP68 when mated (per family design). The far-end column tells you what each combination usually connects to — and what to check before ordering.
| Far-end interface | Family | What it usually connects to | Notes |
|---|---|---|---|
| LC | Indoor standard | BBU/DU, ODF, patch fields | See the dedicated ODC to LC page |
| SC | Indoor standard | Legacy transport, ODF, older OLT/ONT ports | UPC or APC; bigger body than LC, check patch-field density |
| FC | Indoor standard | Test equipment, CATV/transport legacy | Threaded metal body resists vibration on racks |
| ST | Indoor standard | Legacy campus/industrial LANs | Bayonet lock; mostly maintenance of installed base |
| E2000 (LSH) | Indoor premium | Carrier transport and high-density builds; common in European carrier networks | E2000 and LSH are the same interface — LSH is the generic name, E2000® the trademark; spring shutter protects the end face; state UPC or APC explicitly |
| MPO/MTP | Multi-fiber indoor | ODF and distribution frames | An ODC-4 to MPO build lands 4 fibers on one MPO at the ODF instead of two duplex LC; state MPO gender (pinned/unpinned), polarity (Type A/B), and the populated-position map. MPO-to-MPO links inside the data hall are out of scope here — the MPO trunk cable installation guide covers those |
| FullAXS | Hardened outdoor | RRU platforms built on the FullAXS system | Sealed LC-based FTTA interface; hybrid jumpers link mixed-interface sites. (A different “hybrid cable” also exists: fiber + 48 VDC power conductors in one jacket for remote radio heads — flag it in the RFQ if that is what you need) |
| ODVA | Hardened outdoor | RRU platforms using ODVA-style ports | Hardened LC/SC/MPO-style system; confirm the exact ODVA variant |
| PDLC | Hardened outdoor | FTTA equipment using PDLC duplex ports | See our PDLC outdoor assemblies |
| NSN Boot | Hardened outdoor | Nokia-era RRU duplex-LC boot ports | See our NSN Boot duplex patch cord |
| AARC | Hardened outdoor | Radio units using the AARC round interface | Confirm gender and keying from the equipment drawing |
| OptiTap | Hardened outdoor | FTTH drops and terminals on the OptiTap system | SC/APC-based; see our OptiTap patch cords |
| Q-ODC | Hardened outdoor | Equipment with push-pull Q-ODC ports | A hybrid ODC↔Q-ODC jumper joins different interfaces — it is a cable, not an adapter; ODC is thread-locked, Q-ODC is push-pull — see ODC vs Q-ODC |
If the far end is not in this table, send a photo — most “unusual” ports turn out to be one of these families with a vendor-specific name.
Nine stock ODC assemblies to check first
Before you spec a custom build, check the nine catalog ODC assemblies below. If one matches your port combination, it ships as a standard product; every combination outside this list runs on the custom build sheet described further down.
Four notes that prevent misorders
1. A hybrid jumper is not an adapter. An ODC-to-FullAXS (or ODC-to-Q-ODC) assembly is one cable with two different factory-terminated ends, linking equipment built on different interface systems. It never implies the two connector families can plug into each other — they cannot. Adapter-based conversions add loss and failure points — each added mated pair can add up to ~0.5 dB (single-mode, typical) — while a hybrid factory build adds none.
2. Hardened-to-hardened builds need both port drawings. When both ends are sealed interfaces, gender, keying, and backshell orientation differ per family. Supply the equipment model or port photo for both ends; the build sheet states each end explicitly.
3. The far end inherits the fiber and polish plan. A combination does not change the optics: bend-insensitive G.657.A1/A2 single-mode by default — chosen because tower and cabinet routing regularly pushes cable against its minimum bend radius; UPC or APC per the link specification, applied consistently across both ends. Mixing polish on one jumper is a build error, not a configuration.
4. Three details separate a fast supplier from a slow one. Ask any candidate for a drawing-level build sheet before production, per-unit IL/RL test records in the box, and trademark-clean wording — a supplier claiming to sell “original ODC” is reselling, not manufacturing. The three answers predict how the rest of the project will run.
Assembly-typical specifications
Spec ranges below are assembly-typical for the platform and for reference only, not a guarantee; the build sheet states the confirmed figures for your configuration.
| Parameter | Value |
|---|---|
| End A | ODC plug or socket, threaded coupling, IP67/IP68 when mated |
| End B | Any interface from the combination matrix above |
| Insertion loss | ≤0.5 dB per mated pair, typical limit (SM) |
| Return loss | ≥50 dB UPC / ≥60 dB APC (SM); ≥35 dB (MM) |
| Fiber | OS2 G.657.A1/A2 standard; OM3/OM4 optional |
| Jacket | ~5.0 mm OD; LSZH where the far end enters racks or cabinets (low smoke, no halogen on combustion), TPU or UV-stabilized PE for fully outdoor runs; armored optional |
| Temperature | −40 °C to +85 °C (assembly-typical) |
| Length | Built to order; reel length and tolerance stated on the build sheet ; per-unit IL/RL test record included |
How a custom ODC build runs
- Configuration — you send the two port types, fiber count, polish, jacket, length, and quantity (checklist below). The three classic misorders — far end treated as an afterthought, polish mixed on one jumper, “hybrid” spec’d as fiber+power when you meant mixed interfaces — are all caught at this step by the same ten lines.
- Build sheet — we return a drawing-level specification: ends, genders, fanout, leg lengths, labels, test limits. You confirm it before production.
- Sample — for new configurations or volume programs, a first-article sample with its test report ships for approval . Run it through your own acceptance checks — IL/RL against your link budget, mating and unmating cycles, an end-face look — before releasing volume.
- Production — volume build to the confirmed sheet, with per-unit IL/RL test records and project labeling.
- Delivery — reels or boxed sets per installation sequence .
The 10-line RFQ checklist
- End A interface + gender (photo or equipment model helps)
- End B interface + gender
- Fiber count (ODC-2 / ODC-4 / other) and port map for 4F
- Polish: UPC or APC, applied to both ends
- Fiber type: G.657.A1/A2 default, or OM3/OM4
- Jacket: TPU / LSZH / PE, armored if needed; gland or conduit size limits
- Length per assembly and tolerance; breakout leg lengths if any
- Environment: temperature, coastal/salt, UV, vibration, rodents
- Test evidence: per-unit IL/RL, end-face inspection standard; for EPC documentation packages, lot traceability on request
- Quantity per configuration, labeling, packaging, destination, schedule — state the destination and project phase up front; packaging, labeling, and the documentation package are built around them
Send the ten lines (even with blanks) and we return a configured quote without a question loop: start your RFQ →
Frequently asked questions
Can you build ODC to SC / FC / ST / E2000 cables?
Yes — all four are standard far-end options on the ODC assembly platform, in UPC or APC, ODC-2 or ODC-4. E2000 and LSH are the same interface under different names.
Can you connect ODC equipment to FullAXS, ODVA, PDLC, or NSN Boot equipment?
Yes, with a hybrid jumper: ODC on one end, the other hardened family on the other end. Both ends are factory-terminated to the respective port drawings — the families themselves never intermate.
Is an ODC to Q-ODC cable possible?
Yes — as a hybrid assembly joining an ODC-port device to a Q-ODC-port device. It is a cable with two different ends, not an adapter, and it does not make the two interfaces compatible. ODC locks by thread, Q-ODC by push-pull; background in ODC vs Q-ODC.
Can ODC break out to MPO?
Yes — an ODC-4 to MPO build lands all 4 fibers on a single MPO at the ODF or distribution frame, one patching position instead of two duplex LC. State MPO gender (pinned/unpinned), polarity (Type A/B), and which positions are populated in the RFQ.
What if my far-end port is not in the combination matrix?
Send a photo of the port or the equipment model. Most “unusual” ports turn out to be one of the families in the matrix under a vendor-specific name; if yours is genuinely outside the list, the build sheet will state the interface explicitly before production.
Can you reproduce an assembly from an old sample or a drawing?
Yes — a physical sample, a supplier drawing, or clear photos with dimensions are enough to build a matching specification. For hardened interfaces, both end faces and the coupling mechanism are measured before the build sheet is issued.
What information do you need to quote a custom combination?
The ten lines in the checklist above. Port photos or equipment models for both ends remove most ambiguity in the first round. On larger programs, buyers usually also ask for a sample build sheet and a redacted per-unit test record up front — both are available on request.
Is there a minimum order for custom combinations?
Custom builds run from first-article samples to volume production . Pricing follows the build sheet: ends, fiber, jacket, length, and quantity.
What fiber and jacket options apply to custom combinations?
The same platform as standard builds: bend-insensitive OS2 G.657.A1/A2 single-mode (OM3/OM4 multimode optional for short in-cabinet runs), ~5.0 mm cable in LSZH for rack and cabinet entry, TPU or UV-stabilized PE for outdoor runs, armored variants available .
Do custom assemblies come with test reports?
Every assembly ships with an individual insertion-loss and return-loss test record; end-face inspection to IEC 61300-3-35 criteria can be added to the build sheet on request .
How long does a custom build take?
Confirmed build sheets go to production immediately; lead time depends on configuration and volume . Samples for new configurations ship first.
Request your combination
Send the two port types (photos welcome), fiber count, polish, jacket, length, and quantity. BWNFiber returns a drawing-level build sheet, a sample plan for new configurations, and pricing — one round, no question loops. Start your RFQ →
