• 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

slick2500 said:
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 :(
Click to expand...

What HTC do you have? Its easy to root and install a new custom rom with tons of added goodies and updates
 


Hello

1.4.59 is out with initial support for the KR. You will need to *delete* your existing custom PIDs, and re-add them from the predefined list, then restart Torque

After that, you will need to delete and recreate the relevant KR display on your dashboard to make sure you have the fresh KR pid settings

It may work, there's also a good chance it'll be blank - if that is the case I will need a comms debug log to be sent my way (with 'kr' in the description so I know what it's about) and I'll get on with fixing!

Thanks

Ian

EDIT: Thanks for the KR debug. 1.4.60 is now out and should display something after you have performed the above steps!
 
Last edited:
I kept getting an error message, something about unable to read SD card storage or something with 1.4.60 So I have now flashed to a different stable stock based rom and formatting my SD card just in case that was the issue. I will retry tomorrow, currently the Gauge would show some activity when scrolled over to it, but would always stay on 0.... And I would think it should have at least 1 degree of KR being it is a Top swap car and needs a tune.
 
SSJon said:
What HTC do you have? Its easy to root and install a new custom rom with tons of added goodies and updates
Click to expand...

Droid Eris. I tried a custom rom and sent a debug log and whats his face sent me an e-mail back saying that my bluetooth drivers were messed up and i should go back to the stock rom. So I'm confused.
 
Hi

A couple of you haven't deleted the custom PID list and re-added from the stock list, which will mean that KR wont work for you as you are using the old data (which has changed) in the new versions predefined lists.

You must clear all the extended PIDs first, and delete the display in the realtime dashboard, and then restart Torque (just so we know everything has started fresh, new connection, using the new PIDs) and re-add the KR display

It should then start working!! (at least I hope it does, I don't unfortunately have direct access to a GP to test with)

On the ROM side of thing, 'whatshisface' (me :)) would have said that based on the debug - some of the ROMs use old bluetooth drivers, which are known to be broken and there are some *really* broken bluetooth drivers kicking around out there, however some manufacturers don't update their phones so the ROMs are the only way to get newer drivers. Unfortunately the ROM you were using at the time was (or appeared in the debug) using flawed bluetooth driver.
 
Yeah I tried looking around and could not find any of the modded roms listing that they were using fixed bluetooth drivers, and sorry for calling you whats his face im tired.
 


A couple of you haven't deleted the custom PID list and re-added from the stock list, which will mean that KR wont work for you as you are using the old data (which has changed) in the new versions predefined lists.

You must clear all the extended PIDs first, and delete the display in the realtime dashboard, and then restart Torque (just so we know everything has started fresh, new connection, using the new PIDs) and re-add the KR display
Click to expand...

I updated to the latest version. Then cleared the custom PID list and removed the KR gauge from the dashboard. Restarted and then added the new predefined Pontiac/GM/Opel/Vauxhall PIDs. Restarted once more and added the KR gauge back to the dashboard with no luck. I also tried the alternative and that didn't work either.

Sent you a comms debug labelled "Gp kr new". Hope this helps. Thanks for working with us to figure this out, Ian.
 
So now my adapter doesn't work, everytime there is an update to torque it either stops working or it starts working I don't get it. It worked when I got it, then there was an update to torque and it stops working, then a new update came out and it started working again, and it just seems to be hit or miss, but now torque tells me that my adapter has known issues and doesn't communicate with my ecu. How is it that it worked fine before but now all of the sudden after an update torque tells me that the adapter will not communicate with my ecu and it doesn't?
 
slick2500 said:
So now my adapter doesn't work, everytime there is an update to torque it either stops working or it starts working I don't get it. It worked when I got it, then there was an update to torque and it stops working, then a new update came out and it started working again, and it just seems to be hit or miss, but now torque tells me that my adapter has known issues and doesn't communicate with my ecu. How is it that it worked fine before but now all of the sudden after an update torque tells me that the adapter will not communicate with my ecu and it doesn't?
Click to expand...

I had my adapter stop working after the last update, so I deleted all of the Torque files from the SD card and it was fine. Also your phone was called the Desire in development by HTC, Verison named it the Droid Eris. CM7 is a lot better than CM6 :th_winking:
 


Some of the adapters can be a bit hit-or-miss. 1.4.58/59 was a bad couple of versions which had an issue with headers (the bits I was working on for trying to get your KR working, which is a little difficult without a vehicle to test on:))

1.4.60 should be good though, and an easy way to tell if your adapter has 'issues' is to let it connect and show data for a short time (a couple of minutes) and then go to the adapter information screen. If you are on the latest version, and "Error Count" reading is above 0, then your adapter has issues and may be intermittent in operation. (The entire point of the Adapter Error Count is to help users identify when they have a faulty unit, there are a lot of clone adapters which have issues!)

Here's a list of current faults with the clone adapters:

* Some adapters don't talk reliably between their internal bluetooth module and OBD2 chip, this usually results in unknown command responses (which are picked up by the adapter error rate display in the info screen)

* Sometimes the bluetooth module in the clone adapter can die. It will just go 'deaf' so Torque/the phone won't be able to find it over bluetooth again. Dead adapter (even though the lights light up)

* Some adapters wont work on slightly older Fords because the J1850-PWM protocol on them has a fault (most likely at hardware) but they will work on any other vehicle not using that protocol (CAN, ISO, VPW, etc) perfectly fine.

Those are the main ones that people hit (then unfortunately blame the app, which is a bit fustrating :))

I've had some KR debugs back, thank you.
A little progress has been made on this and the ECU is responding to the PID instead of ignoring the request, though it is responding with an 'invalid subcommand' (on a '98 GP's) which means that 2211A6 is unsupported on that year, or that KR is on another PID for that age of vehicle.

Do you know of anyone which had KR working on any other scanner type for this year of GP as I'm not sure if the PID (at least for this year of GP) is correct. Still haven't had a KR debug from anyone with a newer GP yet though which should be interesting!

Thanks,

Ian
 
Do you know of anyone which had KR working on any other scanner type for this year of GP as I'm not sure if the PID (at least for this year of GP) is correct. Still haven't had a KR debug from anyone with a newer GP yet though which should be interesting!
Click to expand...

The Aeroforce scan gauges many of us use work for all models of Grand Prixs from 1997-2007. Individual years don't have different PID sets as far as I know. I would expect the newer GPs to have the same problem.
 
piemmm said:
Some of the adapters can be a bit hit-or-miss. 1.4.58/59 was a bad couple of versions which had an issue with headers (the bits I was working on for trying to get your KR working, which is a little difficult without a vehicle to test on:))

1.4.60 should be good though, and an easy way to tell if your adapter has 'issues' is to let it connect and show data for a short time (a couple of minutes) and then go to the adapter information screen. If you are on the latest version, and "Error Count" reading is above 0, then your adapter has issues and may be intermittent in operation. (The entire point of the Adapter Error Count is to help users identify when they have a faulty unit, there are a lot of clone adapters which have issues!)

Here's a list of current faults with the clone adapters:

* Some adapters don't talk reliably between their internal bluetooth module and OBD2 chip, this usually results in unknown command responses (which are picked up by the adapter error rate display in the info screen)

* Sometimes the bluetooth module in the clone adapter can die. It will just go 'deaf' so Torque/the phone won't be able to find it over bluetooth again. Dead adapter (even though the lights light up)

* Some adapters wont work on slightly older Fords because the J1850-PWM protocol on them has a fault (most likely at hardware) but they will work on any other vehicle not using that protocol (CAN, ISO, VPW, etc) perfectly fine.

Those are the main ones that people hit (then unfortunately blame the app, which is a bit fustrating :))

I've had some KR debugs back, thank you.
A little progress has been made on this and the ECU is responding to the PID instead of ignoring the request, though it is responding with an 'invalid subcommand' (on a '98 GP's) which means that 2211A6 is unsupported on that year, or that KR is on another PID for that age of vehicle.

Do you know of anyone which had KR working on any other scanner type for this year of GP as I'm not sure if the PID (at least for this year of GP) is correct. Still haven't had a KR debug from anyone with a newer GP yet though which should be interesting!

Thanks,

Ian
Click to expand...


Ian,

I have an '05 GP and wouldn't mind helping. So set the comm debug up, then I'll label it like.... 04+ GP KR. What else do I need to do? And for how long, just a few minutes? If I don't remember to do it tomorrow I'll do it this weekend.
 


piemmm said:
subcommand' (on a '98 GP's) which means that 2211A6 is unsupported on that year, or that KR is on another PID for that age of vehicle.
Click to expand...

fyi, with my computer based scanner I use the same plug-in to scan my '98 and my '05 (both sc'd 3.8 liter engines) so I'm thinking that the PID is the same for both.
 
Hi

The ability to read the KR pid isn't down to the adapter, it's simply down to finding the right PID and integration equation for Chryslser/Pontiac ECUs.

I think I'm going to have to write a MODE22 scanner to do this, as from the efforts from you guys(thanks!) have pointed to the fact that we don't have the correct PIDs for that ECU type. If I write a scanner, I can scan the entire mode22 segment and hopefully somewhere along that, the correct set of PIDs will be found and then we stand a lot better chance of working out where KR is

I'll probably do this as a plugin, might take a week to finish as I'll need to update Torque with the required bits as well to facilitate this

Thanks

Ian
 
You must log in or register to reply here.
Back
Top