Vehicle profiles in FORScan

Any issues related to FORScan application
Locked
FORScan
Site Admin
Posts: 2609
Joined: Fri Jun 13, 2014 2:21 am

Vehicle profiles in FORScan

Post by FORScan » Sun Mar 31, 2019 4:57 am

This old functionality still causes confusion, especially for new users, so we have decided to create an article about it.

Vehicle profile is a file FORScan creates to store information about a vehicle. On the first connect FORScan does a lot of work: it peforms full scan of the vehicle network loooking for network configuration, available modules and their numbers, parameters (PIDS) etc. This process may take several minutes (depends on multiple factors such as adapter's and bus peformance, number of available modules and so on). FORScan then does save this information to the vehicle profile file. On second and subsequent connects to this vehicle FORScan will take this information from the profile and not perform the time consuming scan again, so connection time and performance improve drastically. Second important function of the profile is that it keeps original module information. If module or vehicle is bricked or damaged, the profile can be used to connect to the vehicle.

Majority of professional scanners have similar funcitonaliy, although it may be called otherwise. For example, in IDS it is called "session".

FORScan for Windows provides a special tab for managing profiles:

Image

This tab can be used to delete, export (backup) and import (recover) profiles.

FORScan Lite for iOS and Android have the same functionality, but have no dedicated pages for profile management. FORScan handles it automatically. User can only remove the profile using Clear cache function:

Image

This functionality looks simple, but causes confusion very often. Let's review typical problems:

1. Users do not realize that FORScan performs full scan only at the first connect. So if for some reason the first scan was not performed well, subsequent connections will not be succesful. For example, user obtained an adapter with mechanical HS/MS switch but didn't realize how it works. So at first connect it didn't switch from HS to MS as requested. As a result, FORScan has not found modules on MS-CAN bus and it will not look for it anymore. We have a lot of complaints to support like this.

2. Another typical scenario is when user has changed something in the vehicle network, but didn't update profile. For example, added a new module. FORScan will not find it until the old profile is removed. Or user can replace a module (for example, upgrade IPC). New module may have quite different functionality inside and FORScan may be unable to work with it properly until new profile is created.

3. If we add some new module or parameters to FORScan databases, FORScan will not find it until the new profile is created.

4. Unfortunately, profiles of different FORScan versions may be not compatible with each other. This is actually a problem of FORScan design: a lot of information in profiles are connected to FORScan database. Some database changes can make some of information inside of profiles not valid. This is why we recommend to remove old profiles when new version of FORScan is installed.


Fortunately, almost always these problems can be easily fixed by removing old profile (clearning cache) and subsequent reconnect.

Locked