IDS testman errors
Am I the only one still getting Testman errors when using IDS V115.04?
Trying to update the PCM on this 09 F-150 where it updates the PCM first then does the TCM. Upon choosing programming it programmed the PCM fine then when it started the TCM it stops and gives me a Testman error. I tried rebooting multiple times tried various methods , tried deleting the session and starting again with same testman error. Tried a different laptop with my hardrive that has my IDS license on. Tried leaving key on while starting another session tried cycling key.. etc etc.
called the 1-888 rotunda phone number where the first guy I talked to said there is no problems with their software and suggested it was a vehicle problem. Finally talked with another support personal (Ben) where he actually acknowledged that this is a problem and was willing to try and help. he had me send in a file which he will forward to engineers to try and resolve the issue.
These testman issues seem to have come from version v114 + (on 2010 vehicle and older)
I was getting these issues at v114 and when v115.02A came out it was suppose to get rid of them... which I loaded v115.02A and updated my vcm2 and the testman error was gone and worked for a a variety of vehicles since then until today.
I tried updating today to v115.04 and tried using the cleaning utility and reinstalling IDS with the same testman error. This is quite frustrating and costing time and money with no immediate resolution. Not to mention I have 2 more ford reprogrammings to do today.
I feel Ford should allow us users to reinstall v113 and allow programming functions until they sort out these issues.
Yes I had the same issue you had with 115.3 went over to my other laptop with 115.4 and it went through. 115.4 is on windows 10 and 115.3 is on windows7. Not sure if that is the difference.
Windows 10 pro only my friend. Tech support will not talk to you unless you are on that.
Kevin, When you went from 114 to 115.02A, did you uninstall 114 and then run the IDS Cleanup utility from motorcraftservice.com/diagnostic/Sup…; Then reboot the PC and install 115.01 and update to 115.04?
When I initially had this issue it was back at v114 and at that time I uninstalled v114 ran utility and Re-installed to v115.02A which resolved the issue when I first seen the testman errors. Again it was fine until today when I went to program a 09 F-150 pcm/tcm. I just used the same laptop and vcm2 to perform a PMI on a 07 F-450 used PCM replacement where it programs the PCM,FICM,TCM and it…
Kevin, Maybe when everyone comes back from the mass vacation event at Motorcraft this will finally get resolved. :) I had asked Donny in a previous post when things went sideways with V114.XX what we learned from all of this and what were the steps taken so it didn't happen again. It was never answered.
John..this issue has been a pain in the ass! Another reason I hate Ford!
Honestly they should offer technicians with this issue some free subscription time. Very costly in terms of time lost. I wonder if Donny (Nastf) has any more info on this issue???
2008 F250 smart junction box replacement went through without issues. Seems to be a hit and miss issue depending on make/model/year.
Edwin, Always great when you chime in. Go Stingrays! You have a Long Island kid on that team on defense who is tearing it up. I will be thinking of you soon when I am shoveling snow. LOL. It has no doubt. My issue here is Ford IDS has always been bulletproof. Now, it makes me nervous all the time. But, the real issue here is how Ford/Motorcraft/Rotunda has handled this whole situation…
Good to hear from you John hey road trip down south Stingray tickets are on me! I've had two issues one shop I had to bail on cuz I couldn't get it to work the other shop I ended up downloading on another PC the Ford module programming software and using a j box I don't know about you if you've ever used a Ford module programming software it takes forever and a day to get it loaded hopefully…
I was doing a Ford the other day that wanted to reprogram 4 modules. The first 2went fine, then got the testman error, luckily after the 2nd was complete. I had to do a hard shutdown and restart of the computer, and then was able to do the next 2 modules no problem.
Kevin, I had one yesterday as well
Hi Sean Can you tell me if your using Windows 7 or 10? I am trying to see if there is some correlation to which version of Windows is giving the testman errors. I still can’t believe the first tech support guy I talked with today tried to tell me it was a problem with the vehicle and NOT the software.
Kevin Windows 7. Had the testman error on programming and twice now I've had it during data logger use
115.05 is now released. I have had problems with ids since 114..... hopefully they will get it together and fix the issue
116.01 is due out 12/4/19, hope for the best
Hi Chris: The first incremental update will probably be next year. There is no way on God's green earth that I would install that one unless I had no choice. The highlight of my day is not being an unpaid beta tester. Guido
I didn’t read all the posts, but I feel your pain. I have been through the test man wars. Had to wait out ford for two weeks once on an f350. This is THERE problem. But they wont admit it. I keep a old version or two around just to get around this. Always use Window 10 Pro. They will not even talk to you if you don’t. Try a second PC. Unlikely that will help, but worth a try. We have Autologic…