I have the red brick with both the old cartridges (to 99) and almost the latest programmable one, could be 8.something. All I'm missing is the CAN adapter. I drive older Ford cars, and it is fine for my needs right now. I also use Forscan, which is a near dealer level FREE scan tool that works with the cheap OBD adapters. The author is always adding applications.
Brick kit cost me $250, probably paid for itself 10X over. I use it also to bleed fluid every 3-4 years in older cars, and I have no problems.
Anyway there is one application - the 95-02 Continental - I'm having a hard time reading ABS data. Tried it on two cars, and one car had an abs pcm change so that makes three. I was able to do it with FORSCAN(can't read the wheelspeed pids on this application, but that may change), by forcing it in test mode and then swapping the brick when in data mode. Otherwise brick will stay blank or for the old cartridge say not connected. No data read.
It seems that in all versions of the software (old and new cartridge-legacy and softmode) they don't put it into test mode before reading the data. I tried starting the bleed process, disconnecting and reinserting the connector but it times out. Theoretically two mt2500s on a splitter would work.
I know this is old stuff but I'm surprised Snap on would have such an issue. They are supposed to be perfect for what these things used to cost. I sold my original years ago but I paid an ungodly amount for it in the mid 90s. That is one thing I dislike about this field and why I'm out.
Wish there was a way to trigger the tests manually like on forscan. Wonder if the Verus would fail too, may call up an old colleague to test.
Brick kit cost me $250, probably paid for itself 10X over. I use it also to bleed fluid every 3-4 years in older cars, and I have no problems.
Anyway there is one application - the 95-02 Continental - I'm having a hard time reading ABS data. Tried it on two cars, and one car had an abs pcm change so that makes three. I was able to do it with FORSCAN(can't read the wheelspeed pids on this application, but that may change), by forcing it in test mode and then swapping the brick when in data mode. Otherwise brick will stay blank or for the old cartridge say not connected. No data read.
It seems that in all versions of the software (old and new cartridge-legacy and softmode) they don't put it into test mode before reading the data. I tried starting the bleed process, disconnecting and reinserting the connector but it times out. Theoretically two mt2500s on a splitter would work.
I know this is old stuff but I'm surprised Snap on would have such an issue. They are supposed to be perfect for what these things used to cost. I sold my original years ago but I paid an ungodly amount for it in the mid 90s. That is one thing I dislike about this field and why I'm out.
Wish there was a way to trigger the tests manually like on forscan. Wonder if the Verus would fail too, may call up an old colleague to test.
Comment