Torque, Android testing

A company called "Xhorse" made the original miniVCI and offered at one time, firmware upgrades. But another Chinese company 'cloned' their OBD interface and copied the software before it would work with more recent Prius. Then "Xhorse" got pissed, shutdown their firmware download site, yet released the ZVW30 compliant version. There may be more 'buzz' about the details but I don't read Chinese. Just I appreciate the irony of two Chinese groups both selling a pirated Techstream having one accuse the other of making a 'clone.' <grins>

I accept your offer. You can send it to:

<contact information shared via private conversation>

Insure it and I'll send e-mail and phone numbers via other means.

Bob Wilson

 

Start thinking about how we'll outline the testing criteria. For example, ECUs and data. We don't need every obscure data point but there are first among equals. We also need to think about operational scenario, the ability to capture metrics for energy studies. We'll also track the configuration and setup overhead.

Bob Wilson

 

That is why I'm a good choice. I know how to induce codes by doing 'things' to the car. But you've hit on three operational scenarios:

1. Diagnostic - we need the codes and critical metrics from HV, engine, battery, and brake ECU. The others are nice to have but lower probability.
2. Driving Aid - metrics used to improve Prius efficiency.
3. Engineering Studies - collected data for detailed analysis with the ability to add GPS based ephemeris.

Many of these over lap but having a good outline before we start improves the quality of these tests.

Bob Wilson