When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I have a thread going about black smoke during mild acceleration. The only thing I didn't list in that thread was a mistake I made with Torque Pro because i didn't think it was related. I remembered recently that right before my troubles started i loaded several PIDS on torque pro and started the truck. As soon as i hit real time info the truck coughed and died. I could hear Tugly screaming in my head "I TOLD YOU TO TEST THEM BEFORE YOU RAN THE TRUCK " but it was too late. I immediately deleted the custom PIDS and restarted the truck. It cranked and ran fine so I didn't think any thing of it. Now I'm wondering if i induced a problem. What do you think?
Torque Pro seems to me to be strictly unidirectional, ie only capable of receiving data from requested PIDs. If the requested PID is poorly written or otherwise uninterpreted, incorrect or no data will be returned.
I have seen no instance of a command from Torque Pro that could have any effect on the PCM even if requesting a reply that may not be available.
This failure can be easily avoided by testing the command to see if the PID is valid on the PCM in question.
Apps that are bidirectional MAY be capable of screwing with the PCM, but not likely to be able to disrupt the ROM. Tuners being the exception as these are bidirectional and specifically intended to modify ROM in the PCM.
Although I don't believe Torque Pro can corrupt your PCM, I can kill my dads 2001 Ex when I connect my tablet to his truck. My PIDs work great on my 2002, but something kills the 01 every time.
I believe the requests from Torque can freak out the PCM, but I also believe it is momentary and non destructive after removing the offending PID.
I thought the same thing about the app being a read only but if that's the case then how can it cause the truck to shut down. I know I'm not the only one who has had this happen hence the warnings about testing first
Although I don't believe Torque Pro can corrupt your PCM, I can kill my dads 2001 Ex when I connect my tablet to his truck. My PIDs work great on my 2002, but something kills the 01 every time.
I believe the requests from Torque can freak out the PCM, but I also believe it is momentary and non destructive after removing the offending PID.
Was typing while you were. Hopefully your right about it being temporary. Have considered having PCM reflashed to eliminate it as a possibility
Issuing a non valid command CAN confuse the PCM and cause a temporary glitch. The ROM (tune) will not be affected. Quit issuing the non valid command and the PCM's ROM will default to normal operation.
Torque Pro is not capable of writing to the PCM's ROM (READ ONLY MEMORY)!
Issuing a non valid command CAN confuse the PCM and cause a temporary glitch. The ROM (tune) will not be affected. Quit issuing the non valid command and the PCM's ROM will default to normal operation.
Torque Pro is not capable of writing to the PCM's ROM (READ ONLY MEMORY)!
Thanks. Makes sense. I have a decent grasp on mechanical and electrical but am an idiot where computers are concerned.
Although I don't believe Torque Pro can corrupt your PCM, I can kill my dads 2001 Ex when I connect my tablet to his truck. My PIDs work great on my 2002, but something kills the 01 every time.
I believe the requests from Torque can freak out the PCM, but I also believe it is momentary and non destructive after removing the offending PID.
You need a fresh vehicle profile for every vehicle, and build the gauge set each time. I have a Prius and a Powerstroke. Imagine what would happen if I just jumped back and forth between the two with the same PIDs.
Originally Posted by AllaboutMPG
Was typing while you were. Hopefully your right about it being temporary. Have considered having PCM reflashed to eliminate it as a possibility
As mentioned, no need to reflash. However - Torque Pro can send commands to the PCM, this will be used later when we figure out how to tell the PCM to conduct tests. There is a command, and TP can send it, but I don't know the code (yet). I also don't know the "as you were" code to restore everything to pre-test mode. For now, I went into settings and told TP I don't want to send any commands.