B.E.T.S.Y. stands for Battery, Engine & Toyota Scanner for You It is a free, open-source Android app, and this is the first public build I know of that pulls Toyota INF/detail sub-codes directly from the hybrid ECU using a cheap Bluetooth ELM327 dongle. All you need is the dongle and an Android phone. No dealer software, special diagnostic cable or laptop. Mine is a $3.50 AliExpress clone, and it works! BETSY reads the main DTC together with the INF/detail value transmitted by the car. Those sub-codes are often the part you actually need: they narrow a broad trouble code down to where or why the fault occurred. The reader and the explanation catalog are separate. On the confirmed Gen 2 path, BETSY reads all five INF pages and reports the transmitted sub-code. Version 0.0.3 explains 294 exact DTC/sub-code combinations across 78 parent DTCs, every pair in the known Gen 2 inventory. For anything outside it, or where two trouble codes claim the same sub-code, BETSY reports the DTC and raw sub-code and leaves the explanation unresolved rather than guessing. It has been tested on a Gen 2 Prius. Gen 3 support is implemented but has not yet been verified on a real Gen 3, which is what I most want to test next. Gen 4 and newer can come later. Now I need real-world fault data, the more the better. Every capture lets me check the decoder against another car and extend the explanation catalog. If your Gen 2 or Gen 3 Prius has an active or stored fault, please give BETSY a try and share what comes back. P0AA6, P3000, P301x, brake faults, hybrid faults and strange mystery faults are all useful. Even when BETSY does not yet have an explanation, the raw capture is still valuable. A handful of good samples would make a real difference. Download: BETSY v0.0.3 ➡️ Release v0.0.3 · alrighdee/BETSY · GitHub The code, diagnostic logic and ongoing development are public for anyone to inspect, modify or contribute to. The goal is simple: Prius owners should not need expensive proprietary tooling just to ask their own car what is wrong with it. So, if you have a broken Prius, please lend me its faults! ℹ️ If you don't know how to install an .apk on an Android phone, please look here for help: https://www.lifewire.com/install-apk-on-android-4177185
It’s not the dongle. It’s the software. I’m using a four-year-old ELM327 Bluetooth dongle. What I mean is that, as far as I know, smartphone apps such as Dr. Prius and the other consumer tools have not been able to retrieve Toyota INF/detail sub-codes through a standard ELM327. Let alone opensource apps. Now yes, Techstream obviously has been able to do this for years, but that’s a different class of setup. My software can now retrieve those sub-codes on an Android phone using the same old ELM327 Bluetooth dongle. Out of curiosity, which dongle/software combinations are you using? More specifically, which smartphone app is actually retrieving the INF/detail sub-codes?
