All articles
Technology11 min readApril 9, 2026

ROV Fiber Optic Telemetry: Why Bandwidth Matters for Modern Operations

Fiber vs copper telemetry, single-mode vs multi-mode fiber, WDM multiplexing, bandwidth requirements, Focal Technologies, MacArtney NEXUS, and field splicing.

The shift from copper to fibre optic telemetry in work-class ROV umbilicals is not merely a technology preference — it is driven by the bandwidth demands of modern operations. An ROV equipped with HD video cameras, multibeam sonar, inertial navigation, and acoustic positioning simultaneously generates data at rates that copper conductors cannot carry over umbilical lengths measured in kilometres. Understanding the fibre optic telemetry chain from light source to surface receiver makes fault diagnosis faster and more systematic.

Fibre vs Copper: The Bandwidth Comparison

A single copper conductor pair in a typical ROV umbilical can carry approximately 1–10 Mbit/s at umbilical lengths of 1,000 metres or more before signal degradation requires equalisation. A single-mode fibre optic strand in the same umbilical carries 1–10 Gbit/s over the same distance with negligible signal degradation. The difference is three orders of magnitude. For early ROV operations — where telemetry was control commands and analogue video — copper was adequate. For modern operations — where the vehicle simultaneously transmits compressed HD video from multiple cameras, a multibeam sonar data stream, a DVL data stream, a fibre gyro heading and motion package, and acoustic positioning corrections — copper is not physically capable of supporting the aggregate bandwidth without significant compression artefacts or bandwidth allocation conflicts.

Single-Mode vs Multi-Mode Fibre

Single-mode fibre has a core diameter of approximately 9 microns and supports only a single propagation mode of light. This eliminates modal dispersion — the primary bandwidth-limiting mechanism in multi-mode fibre — and allows single-mode fibre to carry signals over distances of tens of kilometres without dispersion-induced degradation. ROV umbilicals universally use single-mode fibre for this reason: umbilical lengths of 2,000–4,000 metres are common in deep water operations, and single-mode fibre handles these distances without repeaters. Multi-mode fibre, with core diameters of 50 or 62.5 microns, is easier to terminate in the field because its larger core is more tolerant of alignment errors during splicing. It is used in some short internal connections within the vehicle frame and tether, where distance is not a constraint, but it is not suitable for the main umbilical run.

Automate your dive logs with ThrusterLog

Stop filling out paper forms. ThrusterLog captures every dive detail, keeps your records audit-ready, and works offline.

Download on the App Store

Wavelength Division Multiplexing

WDM allows multiple independent optical signals to share a single fibre strand by using different wavelengths of light for each channel. Coarse WDM (CWDM) provides 4–18 channels with 20 nm wavelength spacing; Dense WDM (DWDM) provides 40–160 channels with 0.8 nm spacing. ROV telemetry systems use CWDM for most applications — the channel count is sufficient to separate uplink and downlink data streams, video channels, and control data, and CWDM transceivers are more tolerant of temperature variation than DWDM equipment. A typical work-class ROV umbilical carries four to twelve single-mode fibres, and WDM allows each fibre to carry multiple independent data streams, providing both capacity and redundancy — if one fibre is damaged, traffic can be redistributed across remaining fibres.

Bandwidth Requirements by System

  • HD video (H.264/H.265 compressed, 1080p at 30fps): 5–20 Mbit/s per camera stream
  • Multibeam sonar data (Kongsberg M3 or Sonardyne Solstice): 1–10 Mbit/s depending on range and resolution settings
  • DVL (Doppler Velocity Log, e.g., Teledyne RDI Workhorse): under 1 Mbit/s — low-bandwidth but latency-sensitive
  • INS/AHRS (Inertial Navigation and Attitude): under 0.5 Mbit/s but requires consistent delivery without packet loss
  • Acoustic positioning (USBL, e.g., Sonardyne Ranger 2): typically under 1 Mbit/s
  • ROV flight control commands and telemetry: under 1 Mbit/s aggregate
  • Tooling control and sensor data: variable, typically 0.5–5 Mbit/s
  • Total aggregate for a fully instrumented work-class ROV: 50–150 Mbit/s uplink, 5–20 Mbit/s downlink

Focal Technologies, MacArtney NEXUS, and Schilling Fibre Systems

The telemetry system integrator landscape for work-class ROVs is relatively small. Focal Technologies (Dartmouth, Nova Scotia) produces the FOCUS telemetry system used on a number of North American work-class ROVs, providing WDM multiplexing, Ethernet data distribution, and video compression in an integrated package. MacArtney's NEXUS system is widely used in European and global fleets — it provides a modular fibre telemetry architecture that accommodates different vehicle configurations and has a well-established service network. Schilling Robotics (now TechnipFMC) integrates proprietary fibre telemetry into the UHD work-class platform, with the telemetry system designed as an integral part of the vehicle architecture rather than a third-party addition. The operational implication for pilots is that fault diagnosis requires knowledge of which system is fitted — alarm presentation, fibre health monitoring, and redundancy switching are all system-specific.

Field Termination and Splicing

Fibre optic field termination is one of the more demanding maintenance tasks on ROV systems and requires tools and technique that are distinct from electrical work. Mechanical splicing — using a precision alignment sleeve to butt two cleaved fibre ends — provides acceptable insertion loss (typically 0.1–0.5 dB per splice) and can be completed without power equipment, making it viable for vessel field repairs. Fusion splicing uses an electric arc to melt and join two fibre ends, producing insertion losses below 0.05 dB and a mechanically strong joint — but requires a fusion splicer, a clean environment, and a skilled operator. Single-mode fibre is less forgiving of poor cleave quality than multi-mode: a cleave angle error of more than 1 degree produces measurable insertion loss in single-mode that would be insignificant in multi-mode. On vessels, the primary challenge is maintaining the clean, dry working conditions that fibre termination requires — wind, salt spray, and vibration all degrade termination quality.

Troubleshooting Signal Loss

  • Identify the symptom precisely: complete loss, intermittent loss, degraded throughput, or specific channel loss
  • Check optical power level at the surface receiver using an optical power meter — compare against baseline commissioning figures
  • Measure optical power at the vehicle end using the ROV-mounted optical tap point if available
  • Calculate insertion loss across umbilical: total loss should not exceed fibre attenuation coefficient (approximately 0.35 dB/km for single-mode at 1310 nm) multiplied by umbilical length, plus connector losses
  • Inspect all above-water connectors and bulkhead fittings — contamination on connector end-faces is the most common cause of high insertion loss
  • Clean connector end-faces using IEC 61300-3-35 compliant cleaning tools — never use compressed air alone
  • Check for bend radius violations in umbilical storage drum — single-mode fibre requires minimum bend radius of approximately 30 mm for static and 60 mm for dynamic applications
  • If loss is umbilical-section specific, use OTDR (Optical Time Domain Reflectometer) to locate the fault position along the fibre
  • Document all insertion loss measurements in ThrusterLog against the umbilical serial number — trending loss increase over multiple campaigns indicates developing fibre damage before catastrophic failure

Why Bandwidth Discipline Matters Operationally

A fibre optic telemetry system with 1 Gbit/s physical capacity does not deliver 1 Gbit/s to the pilot — the network stack, compression overhead, protocol encapsulation, and management traffic all reduce usable bandwidth. On a fully instrumented work-class ROV, bandwidth allocation conflicts between the sonar system demanding maximum data rate and the HD video system requesting high bitrate are genuine operational issues. Pilots who understand the bandwidth hierarchy — which systems have priority in the telemetry management layer — can adapt their operational approach when the system is degraded. Running a sonar at reduced range resolution to free bandwidth for video quality during precision intervention is a legitimate and informed trade-off. Running it unknowingly because the system is throttling automatically is not.

Ready to streamline your ROV operations?

ThrusterLog is available free on the App Store.

Download on the App Store