2000 Ford Ranger No communication...

[gentz]

Well here is another fail for the verus. 2000 Ford Ranger 3.0l vin IFTYR14V8YPB18837 will not communicate. what a let down, genesis picks it right up... Unbelievable. This is become a greater unusable piece of XXXX..... 11.2 and will probably not update any longer......pretty pissed....

[TurboJim]

Well here is another fail for the verus. 2000 Ford Ranger 3.0l vin IFTYR14V8YPB18837 will not communicate. what a let down, genesis picks it right up... Unbelievable. This is become a greater unusable piece of XXXX..... 11.2 and will probably not update any longer......pretty pissed....

Did you try via USB?

Mines been out for 2 weeks tomorrow..... Anxiously awaiting its return. I wonder what a lawyer may have to say about all of this....

[gentz]

The verus is a v1 with the cable.....I have not invested in that garbage wireless .....

[jrorl63]

Well here is another fail for the verus. 2000 Ford Ranger 3.0l vin IFTYR14V8YPB18837 will not communicate. what a let down, genesis picks it right up... Unbelievable. This is become a greater unusable piece of XXXX..... 11.2 and will probably not update any longer......pretty pissed....

Did you try Global OBDII on your VERUS? If that works then I would suspect a bad data cable, adapter or personality key. Sorry to hear of all the problems you've had with your tool.

[USpMD]

Did you try Global OBDII on your VERUS? If that works then I would suspect a bad data cable, adapter or personality key. Sorry to hear of all the problems you've had with your tool.

global OBDII are you freaking kidding me!! this guy spent 10,000 us dollars, plus updates, Global OBDII, you must be a salesman!! for christs sake why didnt you ask him for the light flash codes???

[gentz]

Did you try Global OBDII on your VERUS? If that works then I would suspect a bad data cable, adapter or personality key. Sorry to hear of all the problems you've had with your tool.

cable is good, and key is good. Had just used the verus on another vehicle... Its sad how they never blame the actual crappy atlas software but always either windows, cables or keys. seems simple, replace the cable see if it works, replace key see if it works, nothing solves it, lets re-image and delete all your files. That doesnt work, send it it. tech support re-images, sends it back and back at point zero.. still wont work..... Very pissed. Seems as the verus is turning into a laptop with component test and a scope, a really expensive one!

[TurboJim]

global OBDII are you freaking kidding me!! this guy spent 10,000 us dollars, plus updates, Global OBDII, you must be a salesman!! for christs sake why didnt you ask him for the light flash codes???

No no no....sweeps on an analog voltmeter!! BWAHAHAH!

[TurboJim]

Did you try Global OBDII on your VERUS? If that works then I would suspect a bad data cable, adapter or personality key. Sorry to hear of all the problems you've had with your tool.

And I doubt you're really sorry. I just got word my unit has a bad hard drive. I asked my dealer how the hard drive could cause the buttons to be pressed. I got the dumb look.

2 weeks out and its probably gonna have to go back again. Not cool. This aint no $149 code reader. It costs more than most cars it connects to. Its not acceptable!

But I bet if I stop paying for it they'll jump right on me for it..... thats fair...yea ok.

[crackerclicker]

jrorl's question wasn't out of line. he simply asked if a different communication protocol worked.

[TurboJim]

A 2000 Ford uses K20, as does global. Hardware would be the same. I believe non-CAN Ford, and global both use J1850, so what would the point be?

[Quantum]

I too am having this same issue. No communication error message and occasional firmware mismatch message with firmware reload. Snap on techs have flashed the tool, done a chkdsk with repair and reloaded the firmware more than once. I then take the tool out and connect it to a vehicle and it works great maybe once. I then shuit it dfown and the next time it will give the 1 (0X1) data stream code and not coonnect and giet data or codes. if I screw around with it with shutdowns, etc I may get it to connect occasionally. It appears taht when you click on data, it doesnt even try to communicate, instantly goes into the error mode with the datastream error message.

if you guys get an naswer to this, I wtoo woudl like to enhance my working working experience with this very expensive nonusable tool.

[USpMD]

As I see it, Snap-on has a obligation to its clients to sell a quality product, Now you can’t say these updates 10.4, 11.2 or 11.4 have not had major issues, each one has had its share of built in faults, why Snap-on quality control has not caught them before release is apparently a internal management problem, however after release they continue to allow us to drag on with these built in faults, Why are they not fixing these issues as they arise? I am well aware sometimes something gets missed in software design, Why does it take so long to get an update or patch to correct the issue? Snap-on are you listening????? My dealer IDS version 76 was released last month, it has already had 6 updates and 2 patchs, So Snap-on it is possible to correct your mistakes, 11.4 came out what oct.1st, still no fixes

[Bob's Garage]

11.4 fixes

There is a Service release due out soon. Very soon.

[jrorl63]

I too am having this same issue. No communication error message and occasional firmware mismatch message with firmware reload. Snap on techs have flashed the tool, done a chkdsk with repair and reloaded the firmware more than once. I then take the tool out and connect it to a vehicle and it works great maybe once. I then shuit it dfown and the next time it will give the 1 (0X1) data stream code and not coonnect and giet data or codes. if I screw around with it with shutdowns, etc I may get it to connect occasionally. It appears taht when you click on data, it doesnt even try to communicate, instantly goes into the error mode with the datastream error message.

if you guys get an naswer to this, I wtoo woudl like to enhance my working working experience with this very expensive nonusable tool.

If the issue(s) haven't been software related, it is probably hardware related. If you have a wireless Verus, I would recommend trying a different S3 Scan Module.

[364z]

All I know is this no communication thing is getting out of hand, I have been down the same road, had my unit replaced by a whole new one, they have given me new cables, wireless unit, tech has worked remotely on it and they just can not admit this thing sucks! Also have all the updates. We can not communicate with any 1996 grand am..luckly that is what one of our kids drive..and the tech guy did say there was a note in the file no communication on any 96 ponitac..ohh great! I can not get it to communicate with any ford with the old OBD1 and now today I was trying to hook up to a 98 cavalier and gues what, luckly with the help from tech using a 99 worked.
I get so frustrated that when I have no communication I dont know if its the car or my scanner!!
Do not get me started on how many times it tells me it kind find the wireless unit either that is a whole other topic.
Just glad to see I am not the only one dealing with this!