Diagnostic software recommendations that run on windows or linux
I got a 1996 ram 1500 with a transmission problem (code p0740 for the torque converter clutch solenoid) and it wont hold gears and wont kick down correctly. I did some research and found out the governor pressure solenoid and pressure sensor can possibly throw this code, not the TCCS and i feel like its a problem with the fluid pressure of the transmission. I got a ebay usb to obd2 VAG COM KKL cable and im looking for a piece of windows or linux based diagnostic software that isnt too expensive nor require a box to connect inline between the truck and computer that can read transmission data. I cannot afford a high level scanner like a snap on or autel and i would like to diagnose this problem myself before throwing any parts at it or taking it to a mechanic. Any suggestions? Im familar with linux so if you guys know of any good linux software i would love to try it out.
The pcm sensed an issue and set a code. Even with best scanner it's only going to give you electrical data such as what the pcm is seeing from the pressure sensor. The PO740 is : P0740 Torque Converter Clutch, No RPM Drop @ Lockup. The pcm is not seeing any rpm drop after it energizes the lock up solenoid so it' not going into lock up. You will have to drop the pan to replace it anyway so while you are in there replace the pressure sensor lock up and shift solenoids. Wouldn't hurt to adjust the bands either. That should take care of the issue unless there is something mechanical going on. An easier way to see live data is to get bluetooth scanner that plugs into the OBD port and shows data on your phone. I believe this one shows trans data but verify it before you buy it. Don't know of any laptop software but if others do they will chime in.
Torque Pro is supposed to be pretty good, though I have no experience with it. Trouble is, I don't think there is native support for Windows, or Linux, so, to run on a laptop, you would also need an Android Emulator.......
It is a good app. I got it to read trans temp but it seemed to mimick the coolant temp so unsure if it was a real temp
have you been able to read transmission specific data like converter lockup, commanded gear, etc?
Unsure because I never needed to. I doubt that it could because even my Autel sometimes can't. I could be wrong, so my answer is unsure.
The issue is that any low-cost/free software only reads standard/required OBD2 engine data and presents it in more or less fancy fashion. (AlfaOBD is the notable exception but it only works on later trucks). The PCM may control other systems like the transmission but that is outside the original OBD2 scope. You can't even get the transmission temperature with a generic scan tool.
From what I gather the PCM has data pids for governor solenoid duty cycle, target and actual pressure but what the pid numbers are not known. If you can dig them up I suppose you can add them to most linux software.
From what I gather the PCM has data pids for governor solenoid duty cycle, target and actual pressure but what the pid numbers are not known. If you can dig them up I suppose you can add them to most linux software.
Trending Topics
The issue is that any low-cost/free software only reads standard/required OBD2 engine data and presents it in more or less fancy fashion. (AlfaOBD is the notable exception but it only works on later trucks). The PCM may control other systems like the transmission but that is outside the original OBD2 scope. You can't even get the transmission temperature with a generic scan tool.
From what I gather the PCM has data pids for governor solenoid duty cycle, target and actual pressure but what the pid numbers are not known. If you can dig them up I suppose you can add them to most linux software.
From what I gather the PCM has data pids for governor solenoid duty cycle, target and actual pressure but what the pid numbers are not known. If you can dig them up I suppose you can add them to most linux software.
Can you tell me what you used in torque ? I've been playing with a raw OBD console but only get a response for standard OBD2 PIDs. Any Chrysler specific PIDs just gets a "no data" response so I'm doing something wrong...
I'll see if I can find it again I have it written down somewhere lol













