Inexpensive Code Reader
Torque displays them in grey (or ghosted) characters - presumably giving rise to them being called 'Grey codes'. I'm sure Forscan reads/displays them as well although I have not used Forscan as much or seen them in my usual application of it.
I run Torque pretty much constantly in my truck, and seems basically like "Grey codes" are stored in a separate data bucket of events (or a flag) that require re-occurrence on multiple drive cycles to set CEL. Kinda like 'pending' codes. They (as well as hard codes) will go away if their cause is removed. They are the reason I have adopted the procedure of NOT clearing codes, but try things and monitor codes periodically and see if they go away after a few drive cycles. (Clearing them to see if they come back results in P1000 that sometimes takes more drive cycles.) This procedure wouldn't work for a mechanic shop, but as a individual, I prefer it.
I run Torque pretty much constantly in my truck, and seems basically like "Grey codes" are stored in a separate data bucket of events (or a flag) that require re-occurrence on multiple drive cycles to set CEL. Kinda like 'pending' codes. They (as well as hard codes) will go away if their cause is removed. They are the reason I have adopted the procedure of NOT clearing codes, but try things and monitor codes periodically and see if they go away after a few drive cycles. (Clearing them to see if they come back results in P1000 that sometimes takes more drive cycles.) This procedure wouldn't work for a mechanic shop, but as a individual, I prefer it.
With Forscan you can not only read and erase codes from ALL modules you can also program new keys, etc.....
Torque is great for a quick scan and clear, pcm pids and that's the extent of it's abilities.
.
Torque is great for a quick scan and clear, pcm pids and that's the extent of it's abilities.
.
Last edited by RLXXI; Jun 2, 2019 at 11:11 PM.



