Fault codes

Fisker Ocean fault codes

How the codes are built, the ones confirmed on Ocean cars, and what to do about them.

This is not a full code table. It lists only codes confirmed on real Ocean cars, and it is not a substitute for a qualified EV technician. When you scan in Ocean Live, the app also describes standard codes, and you can import your own description lists.

How a code is built

A code like B208896 has three parts: a letter for the system, four characters for the base code, and two for the failure type. Some scan tools show only the first five characters, or put a dash before the failure type (B2088-96).

  • B: the system, here body
  • 2088: the base code, which says what part or signal it is about
  • 96: the failure type, here component internal failure

On the Ocean, B208896 means: overhead console touch controller not responding.

The first letter

LetterSystem
PPowertrain
CChassis
BBody
UNetwork

Common failure types (the last two characters)

EndingUsually means
11Short to ground
12Short to battery
13Open circuit
16Voltage below threshold
17Voltage above threshold
1CVoltage out of range
31No signal
54Missing calibration
55Not configured
62Signal compare failure
81Invalid serial data
86Invalid signal
87Missing message
88Bus off
96Component internal failure
F1Safety/integrity check

Active, pending, stored

Ocean Live marks each code Active now (the fault is present now), Pending, Stored (it happened before) or Warning lamp (the module asked for a warning light).

Codes confirmed on Ocean cars

These codes have been seen and confirmed on real Ocean cars. Search by code (paste one, with or without a dash) or by a word.

CodeMeaning
U15AD87Lost communication with the power steering module
U1613F1End-to-end message check failed (a message failed its integrity check)
U199701Lost communication with HV coolant heater H (cabin heating may not work)
U199702Lost communication with HV coolant heater B (HV battery heater may not work)
U201162 U201262Communication verification failure
B20FE16Trailer module supply voltage below threshold (trailer lamps may not light fully)
B208896Overhead console touch controller not responding
B178854Module not coded (configuration missing)
C21A531Front camera: no signal on its Ethernet link (timeout)
C21A586Front camera: invalid signal on its Ethernet link
U114281 U1142F1Climate control value invalid / signal outdatedCommon on cars running the O-Loop / ovloop 2.2.3+ software, where it is usually a side effect of the update.
U114381 U1143F1Stability control (ABS) value invalid / signal outdatedCommon on cars running the O-Loop / ovloop 2.2.3+ software, where it is usually a side effect of the update.
U114581 U1145F1Cockpit controller value invalid / signal outdatedCommon on cars running the O-Loop / ovloop 2.2.3+ software, where it is usually a side effect of the update.

Many U-codes (lost communication, signal outdated, integrity check failed) appear after a module was asleep, the 12V dipped, or software was updated, and often clear and stay clear. Codes that come back right after clearing, or that come with a warning on the car's screen, point to a real problem.

The modules Ocean Live scans

Scan all modules reads stored codes from 39 modules. Their short names, as the app shows them:

  • BMS: HV battery
  • BCM: body control
  • VCU: vehicle control
  • MCU_F / MCU_R: front / rear motor
  • PDU: power distribution
  • PIU: power integration unit
  • WTC and BTC: HV coolant heaters A and B
  • ECC: climate
  • RAC: rear climate
  • ESP: stability control
  • IBOOSTER: brake booster
  • EPS and EPS2: power steering and backup
  • ACU: airbags
  • PKC: keys and NFC
  • ICC: cockpit and screens
  • GW: gateway
  • TBOX_EU / TBOX_US: telematics
  • HYDRA: driver assist
  • FCM: front camera
  • MRR: front radar
  • CMRR_FL/FR/RL/RR: corner radars
  • OHC: overhead console
  • CIM: steering column
  • MFSS: steering wheel switches
  • DSMC / PSM: driver / passenger seat
  • PWC_L / PWC_R: wireless phone chargers
  • PLGM: power liftgate
  • TRM: trailer module
  • AMP: audio amplifier
  • VSP: pedestrian warning speaker

What to do about a code

  1. Scan: open Faults→Scan all modules. It takes about a minute. Tap Active now to see active codes first. New marks codes that weren't there in the last scan. Some lists may be incomplete; scanning again usually fills them in.
  2. Tap a code to see what it affects, possible causes and how it's fixed, when known.
  3. Tap Share report to keep a text report, or to send it to a shop. Do this before clearing anything.
  4. Not sure? Tap the round ? at the top and ask "Any questions?". It can see the codes from your last scan (unless you turn off "Include my car's readings").

Clearing codes and restarting a module

Clear codes (one module or every module) and Restart are the only things in Ocean Live that change anything in the car. Before you use them:

  • The car is on and in Park, your foot is on the brake, the charging cable is unplugged and the climate is off.
  • The app checks that the car is still and almost no power flows, and stops if that changes. Messages like "The car is moving. Park it first." mean a safety check stopped it.
  • Restart is not offered for the brakes, steering, airbags, drive motors, gateway or battery management.
  • Clearing erases the history a workshop would use, so share the report first. Clearing doesn't fix anything: codes for faults still present come back straight away. A restart is not a repair.

Airbag (ACU), brake (ESP, IBOOSTER), steering (EPS) and high-voltage (BMS, PDU, PIU, MCU) faults should go to a qualified EV shop. An insulation (isolation) fault is a safety issue: don't open anything.

This page is made from the Ocean owner guide that "Any questions?" answers from. More on using the app: Help.