-
Notifications
You must be signed in to change notification settings - Fork 0
Home
BETSY is a free, open-source Android app that reads hybrid battery data, diagnostic trouble codes and Toyota INF/detail sub-codes through an ELM327-compatible adapter. The goal is to give Prius owners useful diagnostic information without requiring dealer software, a special diagnostic cable or a laptop.
- Prius 2004–2009 (Gen 2): confirmed on a stock US-market 2009 car.
- Prius 2010–2015 (Gen 3): implemented, but not yet verified on a real Gen 3.
- Prius 2001–2003 and 2016 onward: recognised but not supported by the current build.
Other Toyota or Lexus hybrids using the same protocol may work, but they have not been validated.
An Android phone running Android 8.0 or newer and an ELM327-compatible Bluetooth or Wi-Fi adapter. Development and on-car testing used an inexpensive Bluetooth clone.
Yes, on the confirmed Gen 2 path. BETSY reads all five diagnostic detail pages from the hybrid-control ECU and reports the transmitted three-digit INF value.
Version 0.0.3 includes plain-language explanations for 294 exact DTC/INF combinations across 78 parent trouble codes, which is every pair in the known Gen 2 inventory.
That inventory is what this project has confirmed, not everything a car can emit, so it is expected to grow. Five of the 294 were themselves found outside the original list. Real-car captures are the main way new pairs turn up.
BETSY still displays the main DTC and the raw INF value. It leaves the explanation unresolved rather than borrowing a meaning from another code or guessing.
Full coverage of the known inventory does not remove this. Two cases still produce no explanation:
- A pair outside the known inventory. The catalog covers what has been confirmed, and a car can report something that is not in it yet.
- A genuinely ambiguous pair. A few sub-code numbers belong to more than one trouble code and mean different things under each. When both of those trouble codes are stored, the evidence cannot say which one owns the sub-code, so BETSY shows none of the candidate meanings. Picking one would be a coin flip presented as a diagnosis, and the wrong side of it points at the wrong repair.
The scan is still useful in both cases: the raw sub-code is what a garage asks for, and sharing the capture is how a verified explanation gets added in a future build.
Yes. It matches each INF value only against documented parent DTC/INF pairs reported by the hybrid controller. Equivalent mappings can share an explanation; genuinely ambiguous combinations remain unresolved.
No. The current build is read-only. It does not clear trouble codes, run actuator tests or write to an ECU. Code clearing may be considered in a future build, but it is deliberately not implemented now because clearing a fault can destroy useful diagnostic and freeze-frame data.
A shared capture can include the app version, detected vehicle layout, adapter model, diagnostic trouble codes, raw diagnostic responses and a short diagnostic log. BETSY removes vehicle-identifying information before submission and does not include the VIN, location, or a phone/account identifier.
The app shows the consent details before anything is submitted.
Download the latest APK from the BETSY releases page. Android will warn about installing an app from outside the Play Store; that is expected for a sideloaded build.
Try BETSY on a Gen 2 or Gen 3 Prius with an active or stored fault and share the resulting capture. Unknown and unusual faults are especially valuable because the raw data can extend both vehicle support and the explanation catalog.
For bugs, questions or contributions, open an issue.