2000 Ford Ranger No communication...
Collapse
X
-
I usually don’t use the Verus on Fords, But yesterday I did a quick test on a 09 Ford F150 TPMS, Yep you guessed it, It would not communicate with if, Pulled out the IDS, worked like a charm, How long till that service release is out???"I wanna help the helpless, but I could careless about the clueless". Dennis MillerComment
-
The service release will be out when we shell out another 1200 clams...ohh but guess what, it wont be there either as we will have just added the capability to scan "Lamborgini" ( smart car ---like if we see any of those it should of been suzuki or other makes that are more on the rode).....I just cant believe it smart car scan capabilities....WOW....man get the shiz straight and add vehicles that we always use or atleast that we see on the road more of.....and FIX the darn issues that were supposed to have been working since 10.4....Diagnostic Specialist, diagnostic tool specialist. You name It I have it or have used it! MasterTech since 1998.Comment
-
Comment
-
Read the manual for communication faults as it suggests. Hook up external power to the obd 1 and a usb on newer can fordsComment
-
Diagnostic Specialist, diagnostic tool specialist. You name It I have it or have used it! MasterTech since 1998.Comment
-
-
Comment
-
What is wrong with suggesting to start with the basics? Do you reimage your unit everytime you have a software conflict? I realize i missed the fact that he has a gen 1 with a cable but the fact remains that he and others are having issues on several vehicles. Picking fights with someone trying to help only insults your own intelligence.Comment
-
not able to scan any fords
lately Ive been noticing that my 1st gen wired Verus with 11.4 will not scan any fords.Allways get comm error (404x) message.3 today,03 windstar,suspecting fem module problem-no communication with any module.96 f-150 missfire,no communication with pcm.00 f-250 tranny issues,no communication.Call tec support and they tell me to update the bin files,so I do,same problem.call them back and reimage,same problem.neighbour shop brings me his cable and k20 key,same problem.After getting off the phone with tec support they tell me it could be hardware related.The brick and $90 mac code reader did communicate with all these vehicles and pull codes,was supprised to see the brick even did the fem on the 03 windstar.
I do have a fleet of 22 f series pick ups that are city road trucks and I need to communicate with fords.I remember when I got rid of my very usefull modis to buy a verus back aroud 9.4 that it did scan fords very well.
Ok so where does that leave me,what are my options.
1-send in the verus to see if it is hardware related.(not likely)
2-buy an IDS,I dont have a problem with the initial cost but if I understand correctly it about 1k a year for software that expires or it wont work after that,is this correct.
3-look to buy a genesis,launch or some generic scanner that does fords well-open to suggestions on that one.
4-send all my fords away and wait for snap on to release a service release that may resolve this.(ok sure)
5-shop on e-bay for a used modis
6-spen 4k on the new snap on solus ultra,is it flawless for fords or also glitchy.
Overall I like the verus but I need ford functionallity and any suggestions would be appreciatedComment
-
-
1999 ford ranger 2wd 3.0v engine...no communication with engine control module....communicates fine with body computers...brand new out of the box solus ultra...bundle 13.2 version 1.3.0.10904 usComment
-
S. BrelandComment
Comment