FORScan forum

PNutts wrote: Tue Dec 26, 2023 9:01 pm Sadly, it does not, but thank you for the reply. This module was never available from Ford in my car's model. It doesn't appear when I choose my car (no profiles). To see it, I must either select a different model that had the module or use a Profile from a different car model that had the module. This is a known process to get the module installed.

Based on my understanding of the documentation and other threads, FORScan doesn't look for the module because it was never an option on my car. The easy button looks like adding it by hand to the Profile and generate a new hash(es) for the file, unless there is something else I can do to get it to appear and be saved in the Profile.

FORScan wrote: Wed Dec 27, 2023 6:54 am FORScan keeps database for every model that contains only modules that were ever installed into this model on the factory. If some car has no factory installed IPMA, but other car of this model has it, FORScan will look for it anyway (that is the difference with FDRS that looks only for modules tied to this car by VIN). However, if IPMA was never installed into this model, in any configuration of it, FORScan will not look for it.

Yes, it is possible to create a Profile editor that will help in some very specific cases (like make a "cut" version of the profile if some module is extracted from the car and connected to the bench, or change module numbers). The problem is that adding a module to the profile will not work if this module is not available in FORScan database to this model. So if IPMA was never installed to Flex by Ford, and FORScan database has no IPMA record for Flex, it will not recognize it even if the module was added to the Profile.

So the only way to make it work is to add the missing module to the database for this model (IPMA for Flex, in your case). Obvious solution is to add missing module to the database. This is why we don't do it:

1. Different models may have different modules. They have different logic, different configuration, set of PIDs, security. For example, if one user will ask to add IPMA from Explorer and another one from Taurus, and these IPMA are different, we will have to add 2 modules somehow and teach FORScan to distinguish between it. Such type of modifications will complicate everything and leading to chaos.

2. A lot of functions in FORScan are tied to model and not to the specific module, so adding full support of some module is not to simple, as it may look like from user's side.

3. FORScan is mass product with a lot of users. Scan for missing module takes about 1 second. It doesn't look much (although there are users that try to retrofit many modules), however, let's think: just because of a single person who retrofitted a module, other thousands of users will have to wait 1 second more on every connect. This is not fair.

The problem can be partially solved using the Profile functionality:

1. FORScan may offer model selection in case of several models are built on the same platform. For example, for 2016-2018 3.5L GTDI Flex you can select between Flex and Lincoln MKT. If you select Lincoln MKT, FORScan will find IPMA as Lincoln has it, in contrast to Flex. As soon as this profile is created, you can use it in case when you need access IPMA. Unfortunately, this option is available not for all models, also the IPMA can be installed of another model. Then there is another way:

2. Use a profile of another car that has this IPMA. It may be difficult for normal user to find appropriate, this is why we try to help in such cases by creating a profile that is most close to the one user needs.

mrkemp1982 wrote: Sat Jun 01, 2024 9:43 pm MY IPC CONFIGURATION DOESNT HAVE ANYZTHING IN IT WHY IS THAT AN WHAT CAN I DO TO FIX IT