hrmm PCMScan doesn't really work for me very well.

ie rpm is all over the place, same with ECT, etc etc...

what am I doing wrong?

 

something to do with the tactrix drivers .. do a delete and reinstall the tactrix drivers ..

I also found that if the PCMScan crash while you're using it (especially when you disconnect OP2.0 from the car while it is still software connected)

I have the same problems .. but it's beginning to be a PITA to keep reinstalling the drivers ..

 

does colby know what the problem is? or that there is even a problem?

 

it seems like its a problem with PCMScan .. not tactrix .. and certain computers ..only a few guys have issues like this ..

 

I tested PCMscan with my Tactrix 2.0 cable and while it will let me clear and view codes, the logging is all crazy with numbers spiking really high every second or so. If you ignore the huge spikes the rest of the data seems like it is correct but there is no way it's useable for logging.

Luckily I only use the EvoScan for logging these days but figured I would mention this wacky behaviour happened to me as well.

 

Interesting, has always worked fine for me. Maybe you guys have the wrong PIDs?

- Bryan

 

i changed my pc and now pcmscan stopped working!! here are the settings i have, should i change anything?