DatabaseToyotaNHW11

Toyota NHW11 (2001-2003 Prius) vehicle-specific database

This database declares the information available from control units in the 2001-2003, or Classic, Prius. See [VehicleDatabaseFormat] for details.

• View / Download

Reported issues

#2
Vincent's DTC XGauges aren't in NHW11 database
#3
Vincent's multiline XGauge notes could be exported as multiline

History and credits

• As early as mid-2003, Graham Davies of ECROS Technology pieces together enough NHW11-specific information to produce the first version of his Prius Mini-Scanner.
• The 2004 Prius adopts CAN, a newer communication bus and protocol, leading naturally to completely different parameter address databases for the newer cars. The MiniScanner does not work on the newer cars, and newer tools that offer Prius-specific data at all concentrate on the new model, not on the Classic, which sold in numbers too small to be a compelling market. Another small, inexpensive tool, Linear Logic's ScanGauge, appears, but without vehicle-specific capabilities, and doesn't seem to work very well on a Classic even as a generic reader. The MiniScanner, or "Graham scanner" as it comes to be called, remains the only inexpensive scanning tool capable of reading NHW11-specific data.
• Between August and October of 2007, ECROS Technology is left unable to produce more MiniScanners when the microcontroller used in the scanner is discontinued. Still the only way for Classic Prius owners to get car-specific data, existing Graham scanners become items to collect and rent.
• In September of 2007, the ScanGaugeII adds the XGauge feature, allowing it to be programmed for vehicle-specific data using the four front-panel buttons. And a lot of patience. But little vehicle-specific data is available. And it still seems to mess things up on a Classic.
• In April 2008, ChapmanF contacts Graham Davies to inquire whether the vehicle database built into the MiniScanner could be made available to support experimentation with other inexpensive OBD-II scanning hardware. At the time, ECROS Technology is still exploring whether enough demand exists to resume MiniScanner production by porting its firmware to another microcontroller.
• In January 2010, w2co begins a thread on whether the ScanGaugeII can be useful in the NHW11. It is still limited by the apparent flakiness it causes when connected to an NHW11, and by the lack of available vehicle-specific data with which to program its XGauge feature.
• In April of 2010, vincent1449p posts one XGauge that works on the NHW11. And, a week later, posts over 70 more. But the ScanGaugeII still makes the car flaky.
• In May and June of 2010, rickw discovers that Linear Logic will send a different cable to use in the NHW11, curing the flakiness. It turns out that the ScanGaugeII includes CAN among the communication protocols it tries to use, but the two connector pins used for CAN have other functions in the pre-CAN NHW11: they are used for brake, steering, and airbag diagnosis, which is why strange things happen when the ScanGaugeII tries to use them for CAN.

The replacement cable with those two pins unconnected, available from Linear Logic at no charge, solves the problem completely and makes the ScanGaugeII a reliable scanner for the Classic.

• In August 2010, vincent1449p posts XGauges for the important HV ECU INF codes.
• September 2010, vincent1449p posts how to read all DTCs (not just emissions-related ones) with a raw ISO14230 command issued from the ScanGaugeII, later posting how to achieve the same effect with an XGauge.
• October 2010, ChapmanF searches for scanner options to diagnose a disconcerting hum, discovers all of the progress that has been made putting together vehicle data in XGauge format, and thinks the time would be perfect to merge this work with the MiniScanner tables to form a merged open-source NHW11 vehicle-specific database.
• 7 November 2010, Graham Davies agrees (e-mail to ChapmanF).
• 10 November 2010, the first versions of the NHW11 database and XGauge converter are born.