From CAN Bus to Subsea Comms: Transferable Skills
Automotive communication protocols and underwater data transmission have more in common than you'd think. Let's explore how CAN bus expertise maps to subsea communication challenges.
Two Worlds, One Challenge
In automotive software, I spent years working with CAN (Controller Area Network) — the robust, real-time communication protocol that lets dozens of ECUs talk to each other inside every modern vehicle. It handles everything from engine management to dashboard displays, all with deterministic timing and built-in error handling.
Subsea communication systems face the same fundamental challenge: reliably transmitting data in a hostile environment under strict real-time constraints. The medium changes from copper wire to acoustic waves or fiber optics, but the engineering principles remain remarkably similar.
The Parallels
1. Noise and Error Handling
CAN Bus: Operates in electrically noisy environments (engine compartments, near ignition systems). Uses bit-stuffing, CRC checks, and sophisticated error confinement to maintain data integrity.
Subsea Comms: Acoustic underwater communication faces multipath propagation, ambient noise from marine life and shipping, and signal attenuation. Error correction coding and adaptive modulation are critical.
The mindset is identical: assume the channel is hostile, design for failure, verify every message.
2. Bandwidth Constraints
CAN Bus: Classical CAN runs at up to 1 Mbit/s. CAN FD extends this to 8 Mbit/s. Every byte matters — messages are compact by design.
Subsea Acoustic: Bandwidth is often measured in kbit/s. Data compression and efficient encoding aren’t just nice-to-have — they’re essential for operational effectiveness.
Both domains teach you to think carefully about what data actually needs to be transmitted and how to encode it efficiently.
3. Deterministic Timing
CAN Bus: Priority-based arbitration ensures the most critical messages get through first. Worst-case latency analysis is a standard part of system design.
Subsea ROV Control: Pilot commands must reach thrusters with predictable latency. Sensor data must arrive in time for real-time decision-making.
If you can design a schedulable CAN network, you can design a reliable ROV telemetry system.
Where They Diverge
Of course, there are significant differences:
- Propagation speed: Electrical signals travel near light speed on CAN. Sound in water travels at ~1,500 m/s — introducing significant latency at distance.
- Half-duplex constraints: Many acoustic modems can’t transmit and receive simultaneously.
- Environmental variability: Water temperature, salinity, and pressure affect acoustic propagation in ways that have no CAN equivalent.
These differences make subsea communication harder, not different. And that’s exciting — it means there’s real engineering value in bringing automotive rigor to this domain.
What I’m Building
I’m currently working on a project that bridges these worlds: a data logger that implements CAN-like message prioritization for a simulated subsea sensor network. The goal is to demonstrate how automotive arbitration concepts can improve bandwidth utilization in bandwidth-constrained underwater systems.
More on that in a future post. Stay tuned.
The Takeaway
If you’re an automotive embedded engineer thinking about ocean tech, your communication protocol expertise is more relevant than you might realize. The fundamentals — error handling, bandwidth optimization, deterministic scheduling, and noise resilience — are universal.
The ocean just turns the difficulty dial up to 11.