Hey there. Have had a ELM327 bluetooth dongle that has worked on my E38 BMW and Mazda Protege. Just bought a 2000 Sierra 5.3 a week ago.

Having intermittent O2 sensor codes (CEL comes on, goes off, etc), and my ELM327 is not able to recognize the ECU in my Sierra.

Is there a particular setting within TorquePro to toggle it to log up?

Just wanting to do some data logs to see whats up before I run out and buy HP tuners in the next month.

 

Is there power getting to the ELM327? Are the lights flashing on it? If they are not, check the cigarette lighter fuse to see if it is blown.

 

Power gets to it......and the bluetooth is docked with my android phone.

Damn thing just stalls trying to connect to the CAN/BUS iso coding. (Sorry not sure which version it displays, I'd have to check again).

 

Well, it shouldn't be talking on CAN, your truck doesn't have it. Check your settings and make sure you're communicating on SAE J1850 VPW.

A BMW could be either ISO 9141 or CAN 15765. Maybe you got a setting somewhere that instructs it not to hunt protocol and just use CAN?

 

Well, just used my buddy's ELM tool...worked right away. So the "shorty" Elm clearly doesn't have the SAEJ1850 VPW in it.

Bummer is that i think my issue is probably with the 4l60e.

It feels "jumpy", like timing is being pulled, then all of a sudden it gets into the powerband in 2nd above 4000rpm and just flares up to 5000rpm like the T/C is having issues.


Can TorquePro log trans temp at all? We didn't have time to try.