• The site migration is complete! Hopefully everything transferred properly from the multiple decades old software we were using before. If you notice any issues please let me know, thanks! Also, I'm still working on things like chatbox, etc so hopefully those will be working in the next week or two.

Android = Aeroforce

11a6 did turn green in the selection list while I was driving, but read 0 the whole time. After I shut the car off, I never did see it come back up and I drove for another 30 mins.
 


A bit off topic, but if one already has the bluetooth adapter and needs a more reliable way to scan for KR (and only KR since the adapter reads everything else fine), is there a gauge that would work that is cheaper than an Aeroforce?

In theory, a kr gauge for $70 and the bluetooth adapter + Torque would still be cheaper than an Aeroforce (and more user friendly).
 
Last edited:
You would not be able to use both at once. A scan gauge plugs into the same OBD II port as the bluetooth adapter.
 
I'm sure you could find an OBD splitter, but I don't think the OBD port has enough power to use both at once, unless you tapped into an accessory wire or fuse. At least that's the impression I got from reading around.
 
My car shows zero data at all times and the little box never turns green. 2000 Chev Monte Carlo SS, with all PIDs and formulas for KR.

I scanned a '04 GTP today and had some weird results. At idle it reads anywhere from 4.5-12.5 KR on the graph, but the digital display stayed stuck on what ever the graph showed when you page over to it and the little box never turns green. Again this is with all PIDs and formulas.
 
I have pretty much given up. I think the dude who made the program needs to get with Aeroforce or someone to figure it out.
 


I didnt read the whole thread but I have the setup as well on my 97 gtp. Everything works great, I was able to diagnose my MAF issue with it. But im not sure if the kr is reading right cause it reads zero, but i havent really got on it yet (because of my maf isssue) and it was stock before i pulled it apart so it could be reading right I guess. I did download the pid's and stuff to make it work. I know Ian (guy who made torque) really wants to get it working on the w bodies if it isnt yet.....
 
Ian is the guy who wrote the program. I have contacted him many times on his forum. I started a W-body thread on there also. If you guys want to get on there and try to send him some messages, here is the link:

Forums — Torque

Type: "W-body" into the search and you will see the thread I started. It seems that he needs more logs of the errors and what is happening when the app is run to read KR.
 
Hello, I'm still here and keen to get KR working.

Please note, when you're putting PIDs into the equation editor you *want* to prefix them with '22'

So, KR (11a6) is:

2211a6

in the PID box at the top of the extended PID editor. This should help.

Also, I'm not *entirely* sure 11a6 is the correct PID for KR, though if you change the PID in the extended editor, delete (if already on the screen) and re-add the display for the PID on the 'realtime information' screen, connect with the engine at idle for a few moments (so it can pull some data) then use the 'Send comms debug log' menu option, I'll have a look.

Please make sure you put something in the description field (like GP KR, etc or an email if you want me to get back to you) otherwise I won't know what it's about :-)

Thanks

Ian
 


Now that more people have, and are using these adapters, what have users found to be the best (reliable while still decently cheap) bluetoothe OBD2 adapter? I dont want to spend a ton on one, but I also want to get one that will work. It may be written in here somewhere but I didnt want to scan 14 pages

Also, has anyone tried hitting the Knock sensor to check for KR? -- Disreguard this section
 
Last edited:
I paid like 25 shipped on ebay for my adapter....works great, as soon as the s/c is back on, I am going to do what Ian said a few posts ago and do whatever I can to get this to work...
 
piemmm said:
Hello, I'm still here and keen to get KR working.

Please note, when you're putting PIDs into the equation editor you *want* to prefix them with '22'

So, KR (11a6) is:

2211a6

in the PID box at the top of the extended PID editor. This should help.

Also, I'm not *entirely* sure 11a6 is the correct PID for KR, though if you change the PID in the extended editor, delete (if already on the screen) and re-add the display for the PID on the 'realtime information' screen, connect with the engine at idle for a few moments (so it can pull some data) then use the 'Send comms debug log' menu option, I'll have a look.

Please make sure you put something in the description field (like GP KR, etc or an email if you want me to get back to you) otherwise I won't know what it's about :-)

Thanks

Ian
Click to expand...

This is good news, and I plan to help as much as I can to get KR working for the good of all the W-body community.
 
Hi

If that's the case then it should be a simple issue of making sure that it's 2211A6 in the PID editor in Torque.

If that is the correct PID, and it's not working, then it might require, in the vehicle profile, the "Use alternate OBD2 header" tickbox to be set (make sure you quit and restart torque after doing this to make sure you start a new connection)

The alternate header may cause all the normal dials to stop working, but the KR may *start* to work - and not knowing if KR needs the engine running or not to produce values other than 0)

Either way, if you're using 2211A6 and have the display on screen for a few seconds, a 'comms debug' (accessible from the menu on the realtime info screen) would be very helpful! (just make sure you put what it's about in the description)

Regards,

Ian
 


I tried the "Use alternate OBD2 header" option today and that didn't work. Sent a comms debug titled "GP KR". Hopefully that helps
 
piemmm said:
Hi

If that's the case then it should be a simple issue of making sure that it's 2211A6 in the PID editor in Torque.

If that is the correct PID, and it's not working, then it might require, in the vehicle profile, the "Use alternate OBD2 header" tickbox to be set (make sure you quit and restart torque after doing this to make sure you start a new connection)

The alternate header may cause all the normal dials to stop working, but the KR may *start* to work - and not knowing if KR needs the engine running or not to produce values other than 0)

Either way, if you're using 2211A6 and have the display on screen for a few seconds, a 'comms debug' (accessible from the menu on the realtime info screen) would be very helpful! (just make sure you put what it's about in the description)

Regards,

Ian
Click to expand...

The Alt OBD header did not connect to my car so no data for anything. I sent a few comms debug logs for both the provided set of extended PIDs including KR, and the alt formula one.
 
Hi

Got the comms debugs, thanks!

I can see what's wrong now, 2211A6 is the correct pid to send, but the ECU (from the logs you sent) is basically replying with a 7F (No) instead of giving me the data.

Good news is that I can (probably) fix that. Leave me with it and I might have something by the end of the weekend - I need to rewrite some code

Ian
 
Mien stopped working it says that phones bluetooth driver contains a bug and that I should get a Rom update from HTC or Verizon, there is no updated Rom :(
 
You must log in or register to reply here.
Back
Top