Justgot my LSID from Nastf and I'm trying to do a parameter reset. This is a coded PATS system. I am using a cardaq-m and ids suscription. I go to PATS functions, parameter reset, screen says you will be prompted to enter your user id and password, I click yes, then get error code
Earl, I'm running windows 7 pro. I tried a parameter reset a couple of years ago on a 15 focus and it sent me to the LSID sign in, which I wasn't registered at the time. This time it stays within ids, doesn't go to the popup
Ok, just wanted to be sure. If you are getting a "Error code:communication error, backend server failed", this usually points to everything not linking on Ford's end properly.Either with your NASTF credentials or the actual portal login through FJDS. You may need to contact FJDS support to see if they are having an issue on the back end.
I found a post on this network from about 3 months ago, and I think by buying a key code subscription it then allowed fjds to proceed to the internet explorer LSID screen. Just to clarify, when I'm trying parameter reset, it never goes to internet explorer LSID screen. I purchased a key code last night and will try again later this morning. Thanks for all the help.
Tried again this morning after purchasing key subscription, failed. Rechecked IE settings, they were all off, I guess I didn't apply them correctly yesterday. Made changes and restsarted computer, rechecked IE settings, all look good. Retried parameter reset, failed. Anybody used their LSID on FJDS within last couple of days? Trying to figure out if problem is on my end or Ford's?
No, Edward, still wont go through. I just got off the phone with ford tech support, and they literally said, "I dont know"I know that GM can look at your programming event and more or less tell you if its your problem or theirs, but I guess ford cant.
Edward,It never leaves the fjds screen, the info you just sent makes me think I have something wrong in my settings, but I have rechecked several times. Do you happen to have page 15 of the document you uploaded, to see if I'm missing something? Thank you all for your help
Thank you Chris, I had recieved similar info from Edward also. I am pretty confident I have the settings right, but will recheck again and make sure IE is default browser. Has anyone had a successful ford/nastf event in the last couple of days? If so, then its defenitely on my end. Thanks everybody
Thursday last week I used FJDS with NASTF and was able to retrieve a confirmation from the site, but FJDS would not accept it. It was a used PCM on a 2018 Focus. I suspect the issue was related to it being a used module but Im not here to Hijack this thread.
Good evening everyoneSo I've been checking and rechecking settings, no luck, calling ford tech support, they gave me the same info you guys did (thanks again everybody) then I finally got a tech to remotely check, after he was done, tried parameter reset again, backend server failed..He didnt know the exact reason but said its on their end.Anybody else ran into this lately?
Hey guysFord released update this afternoon and guess what...parameter reset went through! I'm glad it went through, but upset that ford would not confirm a problem on their end. I lost my butt on this one, but oh well. Thank you for the help!
Hello. I'm trying to figure out a issu that I have with Ford FDRS software. Basically is not let me to do parameter reset on 2020 Ford Transit. I replace BCM with brand new module did all the setup and that one things left its to do parameter reset. I completely remove software from my laptop and install it from scratch not help, then I start thinking maybe something in the car preventing to do so I try on different fully functional 2020 Transit and the same thing happened. That's tells me it's the software issue. Also found here on DN another person have a same problem as me and he also tested on a few different 2020 Transits.
I tried to communicate with tech support for FDRS but there is no way communicate with them over the phone. Only one way it's go through the fdrs and send concern I'm not even able to do that because system not accepting it. I tried to do three times in every single time I have to redo it and type it all the message again.
I have exactly same issue as Andrey on exactly same vehicle ( 2020 FORD TRANSIT). I can do everything, but not perform PARAMETER reset via FDRS. I have contacted support via FDRS contact page and even attached screen shot . It's been 4 days no answer yet. I'm also member of NASTF.
When I report a issue I apply screenshot. There is the message i received and the version of software (122.5) I'm currently on. Then I report I able finish my job with the version 122.1. So I roll back my software and it worked with shows clearly that software has issues. I'm not able to do the same thing with FDRS because it's not letting me log in when I roll back software.
Hi George, It would be extremely helpful if you could post a NEW SIR with this vehicle so that it can be used with the rest of the records to help support more focus on this issue. These failures indeed should not be happening but we need to bring these issues to the surface and help NASTF make a difference.
Andrey, following up on this one. I have received feedback from a few people that this issue should be resolved and was confirmed to work on a couple of other 2020 Transits using NASTF credentials. The last comment you were receiving an internal error - is this still the case? Don't want to let this one go until we are sure it is OK.
Jason, It's is resolved for this vehicle. Right now we have a prompt to the box for NAFTS credentials prior to selecting Parameter Reset. I will check in a week or two with another 2020 Transit to confirm.Thanks,George.
Local Ford dealer probably can do it now because the main part of the problem is fixed now but the aftermarket side NASTF still not fixed. Before this fix message pops up and says *it has not been possible for the diagnostic tester to get security access to the end immobilizer*That's why local Ford blaming wiring and modules.
Parameter reset for various Ford, Lincoln, Mercury & Mazda vehicles. On ford / Mazda vehicles - if any of the vehicles PATS (Passive Anti-theft System) components such as te dashboard (HEC) or the Power Control module (PCM) are replaced or exchanged a PARAMETER RESET must be performed to re-match the vehicles PATS system.
NOTE: If a new IC is installed, the IC and the PCM require a parameter reset to allow the IC and the PCM to recognize each other. Failure to carry out the parameter reset to the IC and the PCM may result in a no start condition.
NOTE: If the IC or the PCM is being replaced (or both), the parameters must be reset in both modules or the vehicle experiences a PATS no-start ... Refer to Passive Anti-Theft System (PATS) Parameter Reset in this section.
When the parameters in the IC are reset, it clears (erases) the PCM ID from the IC. A PCM parameter reset causes the PCM to send a PCM ID to the IC that is necessary for the system to operate ... If only a PCM parameter reset occurs, the ID stored in the IC does not match the ID being sent by the PCM, and may cause a PATS-related no-start.
Since a new PCM will have a new ID, and you need to reset both PCM (to send the ID) and IC (to accept it), and resetting the IC deletes all stored keys and requires you add them again, I would assume that when tech #2 "reset everything and programmed 2 keys", he did all of that, but it wouldn't hurt to double-check.
EDIT: I had another thought after I typed this out: in your original post, you said you only had one key. Also from the manual: There must be at least 2 keys programmed into the IC in this type of PATS before the vehicle starts.
When I got my van, I also only had one key. Because it was more than 10 years old, Ford (dealer and corporate) was catastrophically unhelpful on how to get new Tibbe keys cut, whether any SKC / Security Code / programming key exists, or how to acquire it. When I hired a mobile locksmith to make me another key, he cloned my existing key's immobilizer chip, rather than programming another. My understanding is that as a result, my two keys only count as one "unique" key for PATS purposes.
If your locksmith was similarly only capable of cloning, it's possible that when he reset everything, you only ended up with one "unique" key in the system, which won't start because it insists on having two "unique" keys programmed.
2011 Ford Transit Connect (FTC) with possible Passive Anti-Theft System (PATS) no-start after battery drained and some rain got in. If two unique keys are needed to reprogram but we only have one, should we completely avoid resetting the Instrument Cluster (IC) or the Powertrain Control Module (PCM), or is there some way to back-up the lost 2nd key info from the IC or PCM to re-write it when resetting both the IC and PCM with the remaining 1st key?
I have a 2015 Ford fiesta SE. I purchase a ECU online which I had to give my VIN# for programming. When I receive ECU in mail install I'm my car,car didn't start so I had locksmith to program my key and it started. But I receive code of the ecm not communicate with the car and the scanner picks up another VIN instead my VIN that should have been program to the ECU I purchase. What would happen if I swap back my original ECU with VIN to my car will I be able to start car or do I have to call keysmith again to have my key reprogram back to original ECU for my car.
The locksmith didn't actually program your keys since keys are stored in the body control module on this model. The programming that needed to be done is called "Parameter reset". This feature matches the synchronization code between the PATS (immobilizer) inside the body control module and the PCM (ecu). Without these two matching the pcm would not allow the start command, fire or fuel.
3a8082e126