800G On One Module, Split Across Two Independent MPO-12 Cables
Overview
800G-OSFP800-502 module packs two complete 400G DR4 engines, each on its own MPO-12/APC port, so a site already cabled for 40G or 100G DR4 can reach 800G without adopting less common MPO-16 hardware. EDGE supplies the module and the MPO-MPO-OS2-12B-LSZH trunks it needs, one per engine, straight point to point. Each trunk has to be Type B (crossed), not Type A - both ends use the same module, so the fiber positions need to reverse for transmit to land on receive. 800G-OSFP800-502 is a finned-top/IHS transceiver, meaning it can be used in switch OSFP ports, that support IHS.
Budget calculation
800G-OSFP800-502 carries a 3 dB channel budget per engine, and at the rated 500 m reach, fiber attenuation and connector loss together use about 0.7 dB, leaving roughly 2.3 dB of margin. Both trunks carry the same numbers, since both engines are identical.
Bill of materials
Every product in the diagram above, with the quantity each one appears. Open a row for full specifications, pricing and ordering.
- 2x800G-OSFP800-502OSFP800 800G 2xDR4 Module (Tx/Rx: 1304.5-1317.5nm, 106.25Gbps (PAM4) per lane, up to 850 Gbps, Max. 500m over SMF, 3 dB, Temp. 0-70C, dual MPO-12/APC Connectors, Closed Top)
- 1xMPO-MPO-OS2-12BMPO Female to MPO Female, 12 fiber, Type B (reversed), OS2 9/125μm, APC, LSZH Trunk cable, Length 0.5-100 meters
Frequently Asked Questions
Can a single MPO-16 trunk replace the two MPO-12 trunks this module uses?
No. 800G-OSFP800-502 presents two separate MPO-12/APC ports, one per 400G DR4 engine, not one MPO-16 port. There is no single MPO-16 receptacle on this module for an MPO-16 trunk to mate with, so each engine still needs its own point-to-point MPO-12 trunk.
Why does each trunk have to be Type B instead of Type A?
Both ends of each trunk connect directly to an identical 800G-OSFP800-502 module, with no cassette or patch panel in between to flip the fiber positions. A Type A (straight-through) trunk keeps the same fiber position at both ends, so a module's transmit fiber would land on the far module's transmit fiber instead of its receive fiber. Type B reverses the fiber positions inside the cable itself, so each engine's transmit lanes land on the far engine's receive lanes. This is also why Type B/Method B is the standard recommendation for direct parallel-optics links.
What happens if a Type A trunk is connected by mistake?
With two identical modules and no crossover in the cable, transmit lanes face transmit lanes and receive lanes face receive lanes instead of crossing. The link will not establish — expect no signal detected (loss of signal) at either end rather than a degraded or unstable connection. Verify the trunk's printed polarity marking, or test it, before connecting if there is any doubt.
Can existing 40G or 100G parallel single-mode MPO-12 cabling be reused for this module's two engines?
Often yes for the fiber plant itself: 40G and 100G parallel single-mode optics in the PSM4/DR4 class already use the same 8-fiber-active MPO-12/SMF layout this module's engines use. The detail to confirm before reusing a trunk is polarity — those existing links need to be re-verified as Type B (or re-terminated to Type B) if the original deployment used Type A, since this module's point-to-point configuration specifically requires Type B. (Note: this only applies to single-mode PSM4/DR4-class cabling — 40GBASE-SR4 multimode MPO-12 plant is a different fiber type and isn't reusable here.)