Can't get evoscan to check for codes.

[Keyan]

My CEL came on today after adjusting my idle.

no matter what settings I set evoscan to, it can't pull any codes.

OBDII gives me a read error
MUTII gives me a speed sensor code #24


but that cant be right because the chrome ecu is OBDII.

Is this a problem with EvoScan? will a universal code puller get the codes?

thanks.

[futurevr4man]

to clear dtc's i use evoscan 2.6

greg said something about 2.9 causing false codes to be thrown

[Chris@Rvengeperformance]

start datalogging first. then stop. then check dtcs with 2.6

[Greg E]

I've sent messages to Hammish about this issue but nothing has come of it.

Looks like we are stuck with using 2.6 to read CELs.

[Keyan]

universal scanners also work, luckily


seems i tripped a p0300 while adjusting my idle. whoops! corrected...