Plug a Bluetooth OBD dongle into your car, open wavestripe.app on your phone or laptop, sign in. DTC scans with AI-explained faults, live HV data, ~35 ✅-tier safe maintenance routines. No app store, no installer, no cables to the laptop.
Same engine the workshops use, wrapped in a hosted UI you reach from any URL. No tooling to install, no cables to a laptop, no warranty-voiding writes.
Reads every active and stored fault across every Fisker ECU. AI explains it in plain English with severity, likely root cause and a repair estimate.
~97 SAE J1979 PIDs streamed live. HV SoC, cell-voltage spread, pack and motor temps, isolation resistance, DC-DC voltage, 12 V aux.
~35 ✅-tier safe routines: EPB apply/release, TPMS relearn, ADAS calibrations, comfort training. Confirm modal + supervisor verdict before any byte hits the bus.
Drill into any past scan for a per-VIN view — last-scan summary, odometer, 12 V voltage, Fisker DID sweep (identity + battery + drive + keys), and one-click jump back into Scan / Live / PDF.
One-page diagnostic report — vehicle metadata, adapter info, DTCs, AI summary, safety verdict, OEM calibration IDs. Generated locally, send to any workshop.
Append-only history of every routine, scan and supervisor verdict. Per-VIN filter, severity pills, server-stored — proof of what wavestripe sent the car. 30 days Free, 365 days Pro.
The diagnostic engine ships with feature flags baked in. The browser never sees a code path that can mint a writeVIN write. Defense-in-depth: the server independently enforces the same blocklist on every signing request — a forged client config can't bypass policy.
Start with a full 1-hour Pro trial — no card required. Then Monthly $6 or Annual $59.99 (≈17% off). Billed in US dollars via Stripe regardless of country; your card issuer converts at the rate they publish at the time of each charge.
The trial gives you full Pro access for 60 minutes once you pair your OBD adapter. After that, you'll need a subscription to keep using AI, knowledge base and diagnostics.
For owners with a small fleet — and for independents doing the workshop work. Same USD price worldwide.
Owners ask us the same dozen questions about diagnosing the Fisker Ocean — about which OBD-II adapter actually works, about reading HV battery health, about clearing fault codes, and about whether wavestripe is safe to use on a car with ovloop firmware. The answers, in one place.
The Fisker Ocean is a UDS-only vehicle. Generic OBD-II readers using broadcast queries will not return DTCs — the gateway only responds to per-ECU UDS requests with the correct ATSH header for each ECU (ECC, BCM, BMS, ICC, IBOOSTER, etc.). wavestripe.app handles this transparently: it sends the right header for each Fisker Ocean ECU, retries on NRC‑78, and renders the results with plain-English AI explanations. Any modern BLE OBD-II adapter (vLinker FD+, OBDLink CX, MX+) works.
Fisker Ocean ECUs do not respond to the legacy broadcast queries that older OBD readers send. Fisker's gateway requires per-ECU UDS requests on each ECU's physical CAN ID with the correct ATSH header. wavestripe.app implements the Fisker UDS path natively — that is why a $20 generic reader returns "NO DATA" while wavestripe.app pulls full DTC lists from every ECU.
Yes. wavestripe.app polls the BMS for SoC, SoH-equivalent metrics, per-cell voltage spread, pack temperature, isolation resistance, and 12 V auxiliary voltage. The Live tab streams these in real time, and the Overview tab caches the last-known values so you can spot a degrading module — cell-imbalance ≥80 mV is the canonical early-warning threshold — without waiting for a P0A82 DTC.
Any BLE-capable ELM327-compatible adapter works. We test daily with the vLinker FD+ and the OBDLink CX (both real BLE, not BT-Classic). The web app filters the chooser to namePrefix: "vLinker" by default; you can show all adapters in Settings. Avoid the cheapest no-name "OBDII BLE" clones — their CAN error-frame handling is unreliable on Fisker's gateway. Avoid Wi-Fi adapters on iOS (Safari blocks raw TCP); BLE works on Android and on every desktop Chromium browser.
Not yet. Apple's WebKit (required for every iOS browser, including Chrome and Brave) does not expose the Web Bluetooth API, so the diagnostic engine can't reach the OBD dongle from Safari. We're building a thin PWA wrapper that adds a native BLE bridge so the same engine code runs unchanged on iOS — join the iOS waitlist below. Today wavestripe.app works on Android Chrome / Edge / Brave and on every desktop Chromium browser (Windows, macOS, Linux, ChromeOS).
Yes — wavestripe.app exposes a ✅-safe-tier "Clear DTCs" action per ECU. Before clearing, the AI will recommend running a full DTC scan so you have a record of what was set and why. Clearing without fixing root cause means the codes return on the next drive cycle. The Service tab also has soft-reset and hard-reset per ECU for cases where the ECU is in a stuck state but no actionable fault is stored.
Reading DTCs, reading live data, and clearing DTCs are universally permitted owner-side operations under US Magnuson–Moss and EU Block Exemption rules — they are exactly what any independent workshop will run. wavestripe.app additionally blocks every ⚠️ and ☠️ tier write (writeVIN / writeSEC_OC / writeRole / FCM calibration) at four independent gates: client config, server config, supervisor verdict, and the embedded ECDSA verifier. The button to mint a writeVIN does not exist in the UI. Maintenance routines like EPB apply/release and TPMS relearn are equivalent to what an OEM service computer does and are owner-safe.
Yes. ovloop is a community OTA / telematics / phone-as-key firmware that replaces some Fisker-Inc-side functionality after Fisker's bankruptcy. The diagnostic surface is unchanged on ovloop vehicles, so wavestripe.app reads DTCs, live data and ECU info exactly the same way. The AI explainer is firmware-aware: it downgrades certain stock-firmware-only warnings (e.g. expected SecOC counter codes) to historical-only when it detects an ovloop VCF, so you do not get spurious "critical" verdicts for normal ovloop behaviour.
P0AA6 is the SAE J2012 generic code for "Hybrid Battery Voltage System Isolation Fault." On the Fisker Ocean the BMS sets it when the isolation-resistance monitor reads below the threshold (~500 Ω/V) between the HV pack and chassis. Likely causes: condensation in the pack after a wash, a chafed HV cable in the front compartment, a failing PTC heater, or a degraded HV connector. wavestripe.app reads the isolation-resistance live value on the BMS — if the value is hovering at the threshold rather than crashing to zero, you usually have a moisture problem that resolves after the pack dries; a hard short produces a near-zero reading and needs urgent attention before the next drive.
The Fisker Ocean's 12 V battery is sustained by the DC-DC converter whenever the car is awake, so a healthy 12 V should read ≈13.4–13.8 V with the car on and ≈12.4–12.8 V resting. wavestripe.app's Live tab shows the 12 V rail in real time and the Overview tab caches the last value. Below 12.0 V resting indicates an aged 12 V battery; below 11.5 V you will see comfort-electronics dropouts (windows, door modules, ADAS) and intermittent CAN errors. Replace with an AGM of the original cold-cranking-amp rating; flooded lead-acid is not recommended.
Yes. The Service tab has a ✅-safe EPB Apply / Release routine that drives the rear caliper motors fully open so you can compress the piston for new pads, then re-applies. The routine asks for confirmation, and writes the supervisor verdict to the audit log. This is the same routine the OEM service computer runs.
wavestripe.app is operated by Codestripes LLC, registered in Buffalo, Wyoming, USA. The product is not affiliated with Fisker Inc. or Fisker Group Inc. — it is an independent diagnostic tool built by Fisker Ocean owners for Fisker Ocean owners. Contact us via the contact form.
Start your 60-minute Pro trial — no card required. Pair your Fisker Ocean BLE OBD adapter and you are reading fault codes in under a minute.
Apple's WebKit doesn't expose Web Bluetooth or raw TCP, so the diagnostic engine can't reach the OBD dongle from Safari.
PHASE 2 · PWA WRAPPER