Thread: Android = Aeroforce

I'm currently using this program on my Droid Incredible. For whatever reason the KR use to spik to odd numbers like 11 and 14 (could be just sitting idle or what not). I have one of those odd adapters and mine is telling me the adapter is bad yet a few of the gauges work. The RPM gauge works but not the transmission temperature. After $30 for the adapter I'm not sure I want to get another one unless its the good kind. It does work to clear codes and what not. I love the idea of this program but the system as a whole doesn't work easily enough.

I love the idea of this program but the system as a whole doesn't work easily enough.

I've gotta disagree. I got the Kiwi adapter with a Droid X and the minute I hooked it up, it started working beautifully (minus the KR bit obviously). I'm not trying to be a dick, but it seems like your bad luck may have stemmed from you being cheap (which I can understand as most times I am as well).

Thanks for the dedication to make this work Ian

x2. You're awesome, man. If this works, I'll be making sure everyone I know has Torque...regardless of whether or not they own a car.

Hi

I've released a few (required for the scanning features) updates to Torque, and am now working on getting the scanner app correct (It's already been quite interesting to see it scanning on my own vehicle!)

I need to make it more user friendly though before I release it, then hopefully you'll be able to drag some useful info out of the vehicles so we can see what's going on. Sorry it's taking so long, but once it's done, it's done and will hopefully be really useful.

It won't get *all* the information like the required units and formula to put the data back together (thats still one of the bits that will need working out) but it will tell us where the extended PID blocks are so we can start working out /what/ they are.

What adapter is one that will work?

Originally Posted by SSJon

Update, Just connected it today and KR now lights up green with the latest update. KR showed 0 at all times but then again my setup shouldn't have KR. Anyone have access to both a scan gauge and this app get a chance to compare readings?

Did you try and tap the knock sensor? I think if you tap on it, it will read KR and you should know if it was working or not. But then again having a working scan gauge to compare to would be the real test.

Got it. Yes, the 14.6 is a bug, I've just fixed it and if you upgrade to version 1.4.66 available on the Android Market right now, KR (and other PIDs) should start working

Have fun!

Ian

Wait until a couple of people who already have the adapters have seen it working - I've only seen it from logfiles at the moment (so it appears to work) but I need someone with 1.4.66 to test where they *know* they have a value other than '0' for knock or can compare against another device

I know I have 4* of knock at WOT near redline with a Tech2 (GM's scantool). Ive never used a scangauge but a buddy at work has an older one he wants to bring in for me to play with.

I just bought a Bracketron window mount for my CLiQ2. Makes my distracted driving much safer.

I updated Torque today and re-added the PID's and took a drive on the Interstate. Torque now shows alot of data for several new PIDs like misfire count, evap and EGR data.

KR now reads 5.1* at WOT anywhere above 5k rpm. One time it did spike to 6.6* when I snapped the thottle shut from about 70% throttle. It felt pretty accurate and definatley a huge improvement.

It feels right but the formula could be a little off still. Its hard to tell without running a tech2 and torque side by side. I wonder if I could splice another DLC in the glovebox for my OBDlink. Any objections?

Any ideas on what I could check or verifiy to make sure were on the right track before I put headers on?

That's brilliant news! Sounds like the PID is now working and pulling valid data from the ECU!

The formula should be correct, though checking would be good - the main point is that KR now appears to be being pulled okay so a simple formula change (if it is indeed required) shouldn't be a problem

Thanks to you, and to ssjon, as well as others for sending debugging info and persevering whilst we get it working!