Slow OBDII Port Readings
 

I'm looking for the fastest way to read information from the ECU into an Android app (Torque Pro/Dash Command/Whatever). Right now I have a cheapo $10 bluetooth unit that has severe lag.

I've found out that the 350z uses ISO9141-2 over the OBDII port and is likely the current bottleneck.

Is there a way to use the Consult II protocol to transfer data? Would it be faster? I saw a video of some guys running a Consult I cable and it was instantaneous:

Yes aftermarket ECU would be the ideal solution if they weren't so damn expensive.

I've downloaded a few apps and here are my findings. All apps are connected over bluetooth.

Car Diagnostic Pro
Supports Consult II Protocol, Moderately Fast

Car Gauge Lite/Pro
Supports Consult II Protocol, Moderately Fast

Car Scanner ELM OBD2
Supports Consult II Protocol, Moderately Fast

NDSII Lite
Supports Consult II Protocol, Moderately Fast

Dashcommand
No Consult II Support, Very Slow Over 9141

Torque Lite/Pro
No Consult II Support, Very Slow Over 9141

EconTool for Nissan ELM327
Can't Connect

Try going hardwired.

Unfortunately I'm stuck with Android as an operating system so that limits the software available. I've seen anecdotal data (user cases) that suggests hardwiring over OBDII to Android apps will still produce poor results.

The only time I've seen good results are hardwire (or hardwire to bluetooth adapter) with Windows software or an aftermarket ECU.

Maybe you have seen these already, but here are some ideas:

Wiring AIM products like the MXS via the OBD connector via CAN, lists the pinout functions:
http://www.aim-sportline.com/downloa...II_103_eng.pdf


Nissan Datascan Tool which uses consult iirc:
https://home.exetel.com.au/nds/NDSII/index.php