Ford FJDS 114.06 Issues / software crashing!
I know we have been talking about Ford programming software issues lately... I foolishly updated to 114.06 today before going to do a mobile job. Transmission had been replaced and needed software installed. I was doing PCM update and software crashed before finishing as a result the TCM was unresponsive/NO comm. I tried several attempts and ideas before completely uninstalling the FJDS and reinstalling version 114.01 - I was then able to properly complete the PCM/TCM programming. 😁
What JBox are you using? I’ve done several progrmming jobs this morning on 114.06? But I am using IDS and a VCM 2
I had same issue with a Drew Tech Cardaq 2plus good to hear earlier version of 114 worked.
It's not a Jbox only issue. Still seeing Testman errors with the VCM2.
Bill, Did you start the programming from the top again? Another words, reconnect the original pcm to suck out the info? I'm having the same issue as you and may need to revert back.
Bob, my situation was not a replacement PCM but a new transmission installed. So I needed to do PCM/TCM sequence the program seemed to work untill the TCM and then failed would lock up and I could not exit. I tried several times rebooting and also tried module replacement instead of reprogram with no success. At that point I did a vehicle scan had NO comm with TCM 😤 i uninstalled FJDS…
FWIW the 6R TCM's are the only Ford module that I know of that will show no comms until programmed.
I have been seeing issues with the sequential PCM/TCM programmings. Several attempts may allow for completion (close software and reboot, resume sessionand pmi module again) Seems there is something changed in FJDS 114's core files causing issues.
I tried a couple times already so I'm going to give Bill's solution a try. I still have the full original 114.0 install file. I'll let you know how it goes.
With all the 114.xx issues does anyone have the 113.01 install file?
unless you have some way to fool it 113.xx won't program anymore. I got a box saying "programming is suspended until you update to a newer version", I was using 113.4
Michael, I do not know if you intended the reply to me or not. Yes, I am fully aware of 113.06A timing out this week. The only "legitimate" way to program is with 114.XX version now and hope it works.
I was responding to Kabel who was looking for a 113.01 install file
Fjd, but it looks like everyone is saying that it timed out, I just hope my next Ford isn’t as big of an issue as the last one with 114.01
I'm using IDS/VCM2, my crashing problems started with 114.0, had to go back to 113.4. That finally timed out this week, I reinstalled 114.0 & the problem returned. I went to the website & downloaded 114.06 & that fixed the problem
I talked with Rotunda this week. They admitted to having issues with 114.XX with PMI and reprogramming mostly on 2010 and earlier vehicles. I held out with 113.06A until it timed out. Now, I have no safety net. The representative told me they had many tickets in with Ford engineering on issues with 114.XX Even 114.05. Version 114.06 came out within the last 48 hours lets hope it corrects…
"Programming is easy until it isn't." Truer words were never spoken.
I was trying to program a reman module in an 2008 F150 today. I tried a couple times with 114.06 and no go. I uninstalled and loaded 114.0. Tried a couple times and no go. Went back to 114.06 and finally got it to program. Keys took a couple tries also but it's now running. Now my NEW problem. I have code P1639 "vehicle id block corrupted or not programmed". I cannot clear this code. I can read…
I had the same code today on a escape. I was able to clear it and it did not return. Just popped up out of nowhere. I had reset the kam with a snapon tool. Wasn't using ids though. The car was here with a dirty throttle body, poor idle. No mil, Cleaned and reset kam, then the light came on.
Check the programmable parameters. Tire size, axle ratio, ect... I've had this code set because of wrong or missing data.
I was doing some research and this looks like it could be the answer. I downloaded the as-built data file and will try it tomorrow.
To fix the P1639 you will need to perform PCM PMI. P1635 is the typical DTC for tire size and axle ratio.
Chris, I have been trying to do that with no success. I even tried the blank path programming process where you leave the key off during the id process and enter the tear tag number. The programming completes, I'm instructed to turn the key off, I get the 15 sec count down screen, then it says turn back key on and when I click the tick mark, THEN I get the testman failure and the program…
Almost definitely a Ford software issue. even with patched the 114 version seems to be problematic. I wonder if one of the cracked IDS, like VCX nano uses, would be able to resolve this as they are not running the latest software. I am all for licensed and legal versions of software, but this might be an instance to look into other resources.
Bob - I don't think it's your equipment... Sounds similar to my issue yesterday as the program would crash when after clicking the tick mark and then I could not complete the TCM setup/program. Too bad the 114 earlier version didn't help you guess I got lucky..
Well I spent a good part of the day today on AE Tools tech support trying to get my problem solved. The bad news is that we were not successful. The vehicle starts and runs but we cannot get rid of code P1639. The problem is that the software errors out before completing the programming of the configurable parameters such as axle ratio and tire size. The parameters are not being written to the…
So I spent all day Friday with tech support trying to get rid of P1639. The PCM is programmed and the vehicle runs. We tried over and over to configure the axle ratio and tire size but it didn't appear to be working. I came in this morning and looked through scan data and this is what I see. The Axle ratio and tire size (663 is the correct number) are there but the code still won't clear! As…
Its not the PCM at fault. If the PMI process is not performed by IDS or FJDS without error the pcm will not be fully configured. Testing programming of new modules with FORScan sometimes results in the module not being configured completely, correcting these errors usually requires PMI in IDS. FORScan only codes the AsBuilt to the module. There are things that get written 'behind the scenes" of…
Hi Chris: I've had situations where the customer had to chase down the module that he should've never let go of just so a proper PMI could be done. (One didn't have the correct axle ratio as an option until....) I've also had some situations where As Built could be forced from the website so that the programming could then be done. Then we get the ones where the part line has been consolidated…
If the as built page shows 'Blank PCM Data Available in File ' then you can program without having to swap modules. Just do a key off with the asbuilt files downloaded to the calibrations folder. This issue is related to the software not performing the configuration portion of the pcm programming after writing the calibration. The software seems to be most problematic to the rear wheel drive 6…
Hi Chris: That makes sense. My beast was a Mustang. Guido
Doesn't Ford have a TSB regarding this problem? Or is it a GSM?
What O.S. are you running? I'm running 114.05 and I just finished installing 114.06 on a customer's laptop. We both have successfully programmed several modules between us. We both use Win7Pro. One other customer called me over the weekend running Win10Ent (Enterprise) and he cannot program without the same error message as you Bill Kenel. I've walked him through all the steps I know to make…
Jamie for what its worth the PC i was using was a windows 7 pro.... I also did/completed several programming sessions using 114.01 to 114.05 and had NO issues-- once i update to 114.06 the trouble began 🤢
Thanks Bill. Someone else messaged me that it's not a Win10xx problem as well.
From Ford's website this morning: "Aug 1 2019 IDS RMI Related Crashes The issue with some IDS users experiencing Testman Error, Blue Screen, or IDS crash during PMI on certain vehicles with IDS version R114.01, R114.02, and R114.03 has now been resolved. Previous action of uninstalling and going back to R113 level is no longer required. Corrections have been made in the latest R114.04…
Pfft, you funny Jaime. He's playing here all week, folks. Please don't forget to tip your bartender. Guido