All pages

Every document in this site, in reading order. The same list is published as sitemap.xml for crawlers, and the sidebar links back here from every page.

Guide

• Homedocs/index.md

  A command-line OBD-II and UDS diagnostics toolkit for a 2021 Chrysler Pacifica, talking to a vLinker FS USB adapter. Built on python-OBD, managed with uv, scriptable end to end.

• Getting starteddocs/getting-started.md

  Ten minutes from a cold clone to reading your van's codes. Everything below runs from the repository root.

• Command referencedocs/usage.md

  Every command accepts the global flags below, and every command that reads data supports --json — before or after the subcommand, both work. Configuration commands (ports, history, show, vehicles, tui) take no adapter flags.

Reference

• Technical referencedocs/technical.md

  How the toolkit is put together, which parts of the protocol stack it owns, and which vehicle facts are baked in. If you plan to change the protocol layer, read this first — several of the behaviours below are deliberate and shouldn't be "simplified" away.

• Vehicle support (RU family)docs/vehicle-support.md

  pacifica-obd is hardwired to one vehicle: a 2021 Chrysler Pacifica (RU), gas. This document asks how far the existing transport + UDS approach stretches across the rest of the Pacifica RU family (2017–2027, gas and PHEV, Voyager, Grand Caravan), what is genuinely different on those vans, and what has to become data…

• Project READMEREADME.md

  An OBD-II diagnostics toolkit for a 2021 Chrysler Pacifica talking to a vLinker FS (FTDI FT230X) USB adapter, built on python-OBD and managed with uv.

Deep dives

• AI assistant setupdocs/ai-setup.md

  The browser assistant on #/assistant is a read-only diagnostics copilot. It can read this tool's stored data and, only when you allow it, the vehicle bus. It never writes. You bring your own key (or run a local model); nothing is sent anywhere until you configure a provider.

• Chrysler Security Gatewaydocs/chrysler-sgw.md

  Notes for going beyond generic OBD‑II on a 2021 Chrysler Pacifica (RU platform). This is background/reference; pacifica-obd itself stays on the safe, generic OBD‑II side.

• Enhanced (manufacturer-aware) diagnosticsdocs/enhanced-diagnostics.md

  This document maps out what it would take to grow pacifica-obd from generic OBD‑II into manufacturer-aware FCA/Stellantis diagnostics — the class of things proprietary manufacturer-aware tools do. It is an investigation + plan, not a claim that all of it is safe or easy.

• FCA modulesdocs/fca-modules.md

  How Chrysler/FCA PowerNet control modules are addressed and modelled for a 2021 Chrysler Pacifica (RU), and a concrete plan to grow pacifica-obd from generic OBD-II + UDS identification reads into read-then-guarded-write support for body/chassis modules.

• FCA seed/key selectordocs/fca-seedkey-selector.md

  Scope: this document explains how AlfaOBD decides which security-access algorithm to run for a given module, reproduces the mapping we could recover from the vendor artefacts, and shows how to turn your own copy of AlfaOBD into a Python provider for pacifica-obd security --provider.

• FCA built-in seed→keydocs/fca-keys.md

  pacificaobd.fcakeys ships the FCA/Stellantis PowerNet seed→key algorithms and the selector that picks one, so pacifica-obd security can compute a 0x27 key without any external provider file on the modules this project supports.

More documents

• Bundled Pacifica datasetdocs/pacifica-data.md

  pacifica-obd ships its own Pacifica (RU-platform) dataset so the toolkit is self-contained: no external ECU database, no configuration path and no network access are required at runtime. The data lives in one resource,

• Web UI + bring-your-own-key AI layer — designdocs/web-ui.md

  Status: stages 1 and 2 built. Stage 1 is the read-only web UI (§1–§4, §6); stage 2 adds the guarded write surface (§3.7/§3.8), the 0x27 held-seed policy (§9.2) and the bring-your-own-key AI layer (§5), built to the owner decisions in §9. Stage 3 adds the Raw console (§3.14) and the HV battery screen (§3.6).