2009 F150 Connection/Programming.

[booyah45828]

Working on my 2009 f150 5.4 King Ranch. I've been getting a p060a and narrowed it down to what I think is a faulty pcm. I have a used pcm with the same part number as the original, and I'm trying to program as-built data into this. I've got a paid license into forscan, and have a Nexiq Usblink2(primarily HD j1939 shop) that I've been using in the past with this.

I can connect, run tests, view codes/data with this, and even programmed the abs module on it using the usblink2. So it works and can communicate, but I can't program as-built data or upgrade firmware in the pcm with this, forscan stops after clicking write and says "error applying feps programming signal". I've monitored voltage on pin 13 and I do not have 18v present at anytime during the process, so I assume the usblink2 isn't capable of doing such a thing, and that's where my error lies. I'm not surprised by this. I understand it's limitations being designed for and around the HD world, and that obd2 and j2534-2 stuff isn't exactly supported. But I've read on another forum that applying battery voltage to pin 13 in a certain sequence can get around this, but my attempts at it have resulted in the same "error applying feps programming signal". Not sure if forscan can look past that, or if the software sees that the usblink2 can't create the feps voltage and doesn't even try to program. Or maybe I'm not applying the voltage right, or maybe those others guys were wrong and it can't be done.

I've got a Vgate vLinker FS ordered(it's cheap enough to try), but I want to make sure that's where my issue is, and that I don't have something else going on here.

[tractmec]

Working on my 2009 f150 5.4 King Ranch. I've been getting a p060a and narrowed it down to what I think is a faulty pcm. I have a used pcm with the same part number as the original, and I'm trying to program as-built data into this. I've got a paid license into forscan, and have a Nexiq Usblink2(primarily HD j1939 shop) that I've been using in the past with this.

I can connect, run tests, view codes/data with this, and even programmed the abs module on it using the usblink2. So it works and can communicate, but I can't program as-built data or upgrade firmware in the pcm with this, forscan stops after clicking write and says "error applying feps programming signal". I've monitored voltage on pin 13 and I do not have 18v present at anytime during the process, so I assume the usblink2 isn't capable of doing such a thing, and that's where my error lies. I'm not surprised by this. I understand it's limitations being designed for and around the HD world, and that obd2 and j2534-2 stuff isn't exactly supported. But I've read on another forum that applying battery voltage to pin 13 in a certain sequence can get around this, but my attempts at it have resulted in the same "error applying feps programming signal". Not sure if forscan can look past that, or if the software sees that the usblink2 can't create the feps voltage and doesn't even try to program. Or maybe I'm not applying the voltage right, or maybe those others guys were wrong and it can't be done.

I've got a Vgate vLinker FS ordered(it's cheap enough to try), but I want to make sure that's where my issue is, and that I don't have something else going on here.

I will assume you have done all of the external checks That can cause this P060A DTC(PCM Power and Ground PCM relay etc.)

I would say the FEPS signal missing is the main problem you are having in this particular instance!
In looking at the specs for this Nexiq adapter it would seem to be incapable of providing that FEPS signal(as Far as I know only FORD uses it and only up to ~2010- 2012) and moreover it does also not appear to support the J2534-2 Pass Thru standard so there would also not be any MSCAN support(again only Ford appears to use)!

Programming on these early PCM modules(Changing VIN Number Gear ratio tire size VIN ID Block Asbuilt etc) requires a Complete Calibration file(Firmware Update) Erase and rewrite with the proposed changes!(Calibration files and the vehicles original AsBuilt File must be present in the FORScan Calibration Files folder and it can be a challenge in some instances to find them)

There must be 18 volts applied to DLC pin 13 or the PCM will not open to be flashed! I have no idea where you found that supposed work around but Having bricked a PCM in the past(Actually present as it is still non functional at the moment, extreme cold weather preventing outside work)! I would not be fooling around with anything like that! These things can go bad even using FORD software and hardware(also experienced this)!

Wait for the vLinker FS, try that and report back!
Also make sure that you are using FORScan 2.4.11Beta(earlier versions had many Problems) and make sure to have a Vehicle profile saved as the recovery in 2.4.xx uses a previous profile to establish a connection to the vehicle in case of a non functional PCM!

If you experience problems (Service interrupted errors ect.) Contact FORScan at the email address just above the Heading "Providing FORScan Debug Information" at the following Link using the instructions listed: https://forscan.org/contactus.html#debug_info(testing versions are available for problems using these instructions as this is in Beta testing status still)

[booyah45828]

I will assume you have done all of the external checks That can cause this P060A DTC(PCM Power and Ground PCM relay etc.)

Yes, all power+ground checks out. No ac voltage from alternator, and nothing goofy from coils/injectors either. It originally had a missing noise capacitor on the ignition coil + circuit that caused erratic throttle body operation. That was found/fixed over a year ago, and it's been working fine until now. Runs fine for hours in the shop, starts to miss, run rough/erratic after driving for a few minutes, which gives the p060a code. After key cycle, that code clears and not even a p1000 will be present.

I would say the FEPS signal missing is the main problem you are having in this particular instance!
In looking at the specs for this Nexiq adapter it would seem to be incapable of providing that FEPS signal(as Far as I know only FORD uses it and only up to ~2010- 2012) and moreover it does also not appear to support the J2534-2 Pass Thru standard so there would also not be any MSCAN support(again only Ford appears to use)!

I think so too, and the little I understand about feps, I know it's for sure not applying it. I'm not surprised by this, as it's a HD focused adapter anyways.

Programming on these early PCM modules(Changing VIN Number Gear ratio tire size VIN ID Block Asbuilt etc) requires a Complete Calibration file(Firmware Update) Erase and rewrite with the proposed changes!(Calibration files and the vehicles original AsBuilt File must be present in the FORScan Calibration Files folder and it can be a challenge in some instances to find them)

I didn't know this. If that's what it needs then so be it. I have the former ecm yet, and it still boots, so I assume I can pull whatever data I'll need from it.

There must be 18 volts applied to DLC pin 13 or the PCM will not open to be flashed! I have no idea where you found that supposed work around but Having bricked a PCM in the past(Actually present as it is still non functional at the moment, extreme cold weather preventing outside work)! I would not be fooling around with anything like that! These things can go bad even using FORD software and hardware(also experienced this)!

A little concerning reading this. I've always treated programming like that in the past, but reading all of the successes on here is giving me some false confidence. At the end of the day, it's undriveable as is, so bricking an ecm isn't the end of the world.

Wait for the vLinker FS, try that and report back!
Also make sure that you are using FORScan 2.4.11Beta(earlier versions had many Problems) and make sure to have a Vehicle profile saved as the recovery in 2.4.xx uses a previous profile to establish a connection to the vehicle in case of a non functional PCM!

If you experience problems (Service interrupted errors ect.) Contact FORScan at the email address just above the Heading "Providing FORScan Debug Information" at the following Link using the instructions listed: https://forscan.org/contactus.html#debug_info(testing versions are available for problems using these instructions as this is in Beta testing status still)

vlinker showed up today. Trying it out now, wish me luck

[booyah45828]

If it's wanted, I can link the other forum's post regarding the FEPS only needing 12v instead of 18v like specified, but if that's not the case there's no point in sharing false info.

[booyah45828]

vlinkerfs worked flawlessly. Had to download drivers, and then upgrade it to the latest version at first, and then update forscan to v2.4.11(had 2.4.10) like tractmec suggested, and all went well. Reprogrammed/upgraded firmware to latest, loaded AB from previous file, relearned pats, and all is well.

So in conclusion, nexiq usblink2 can not program anything with feps. No idea on non-feps vehicles, and now that I have the vlinker I doubt I'll ever find out.