FORscan experts - I have questions

[rubydist]

I have some questions for you guys who are experts on using FORscan:

Background: I am thinking of swapping a 2.3 EcoBoost from a late model Ranger into my 09 Ranger. I am in an area where I need to pass emissions tests every 2 years, so I need this to be clean from the regulatory standpoint. I work at a Ford dealer, so have access to all the factory wiring diagrams, etc. through oasis, but I do not work in the shop so I do not have access to any of the Ford service computers.

Questions:
Can I delete or deactivate unused modules? I would be using the 09 airbag system, abs system, etc. so would need to turn off the 21 systems that don't exist in the 09 chassis

Can I update the VIN in the pcm so that connecting to the obd port reads the chassis vin?

Would you recommend pats delete or swapping in the column/wheel from the 21? Why?

What other "gotcha" type issues do you envision?

Is this swap realistic or a pipe dream, given that it has to be emissions friendly?

Thanks for your input.

 

[Ta2dResqr]

I do not know of any way to activate or deactivate whole modules in ForScan. It is more of a reprogrammer. It is used to edit Hexadecimal code. When it says that it supports 1996 and newer vehicles, that doesn't necessarily mean it has a lot of options. More that it can read those modules for codes. Look for spreadsheets that show the options for the vehicle you are using. A quick search for 09 Ranger came up with no spreadsheets. Searching for as built data, only 5 modules come up and only 21 lines. Not much to edit.

 

[rubydist]

The 09 would not be the issue that I anticipate. The concern I have is that I would need to use the engine control module from the 21, and that will expect to see about 20 modules only about 3 of which will really be in use if I stuff that engine into the 09. Everyone that I have found who has done that kind of swap has used a standalone engine control (either Ford Performance, which is only for manual trans, or a 3rd party) and I don't believe I can pass emissions with that approach - therefore I expect I would need to use the 21 engine pcm.

 

[Ta2dResqr]

The 09 would not be the issue that I anticipate. The concern I have is that I would need to use the engine control module from the 21, and that will expect to see about 20 modules only about 3 of which will really be in use if I stuff that engine into the 09. Everyone that I have found who has done that kind of swap has used a standalone engine control (either Ford Performance, which is only for manual trans, or a 3rd party) and I don't believe I can pass emissions with that approach - therefore I expect I would need to use the 21 engine pcm.

The problem is that if you plug it in, it will start searching based on the VIN. If you were able to change the newer PCM to the old VIN (which I doubt will work as they are usually limited to the application, e.g. a 4th gen PCM would accept a 19-22 VIN), it would then search for the 5 modules that apply to that vehicle. If you use the new VIN, it will look for the 21 modules. If they are doing a sniffer test, you should be able to pass. You would have to title it as a custom build though. I do not think factory computers with CAN are a good fit for this application. If you start diving into the modules and the things they will be looking for from non-existent sensors and modules, it will be a deep rabbit hole. You also said you would be trying to use the 09 ABS and AirBag systems. Trying to get modules from a third-gen to communicate with fourth-gen modules is going to be difficult. Maybe check out www.turborangerforums.com? From my experience with ForScan, I am going to say that ForScan, a third-gen platform, a fourth-gen platform, and a factory blend of modules are not going to be easy if at all feasible.

 

[SeanDev]

I have to agree, changing OEM modules is easy with forscan, but modules that didn't belong in the line-up might be a no go. I've used it to get a module replaced and communicate normally to all the others in my F-150. But when it comes to the PCM forscan on my interceptor would not allow me to VIN change the swapped out pcm, only the dealer could do it. It's real important to the PATs module that it knows all modules are who there supposed to be, you run a high risk of "bricking" it.