FORScan v2.3.8 has new feature - ability to read PIDs from different modules simultaneously (aggregated output). Although we tried to make this function most transparent for end users, there are few things to mention.
In order to implement the aggregated output, a virtual module "All" was added to the Read PID section. Main page of the section has no any significant specific, PIDs are not marked as related to some module. But differencies can be found inside of the PID setup dialog:
Main distinction is that every parameter has its' module abbreviation as a prefix. So user can easily identify the PID's module. However, parameter navigation may be more difficult because of large number of PIDs in the list: in contrast to regular modules that rarely have more than 100 PID's, the virtual module may have up to thousand. So, to simplify the navigation, operator can use the filter string. For example, if we type 'ABS' there, we will filter out everything except parameters that gave the ABS abbreviation:
One more difference: only "Read" mode is available. The "Control" mode cannot be selected as the mode selection box is disabled.
Some other limitations have to be considered while using the aggregated output. Sometimes switching between buses may be quite resource consuming and require hundreds of milliseconds. So in many cases, using the All module may lead to serious performance dropdown (PIDs reading speed/frrequency). FORScan shows a warning when the PIDs setting dialog for All module is opened at the first time:
In some cases using aggregated output is difficult, impossible or senseless. FORScan may show additional warnings in such cases. For example:
In this example (Mondeo Mk3 TDCi) adding FIP/ICU PIDs usually doesn't make sense, as the egnine will stop at the first switch between modules. The aggregated output will continue to work, but ICU parameters on stopped engine are hardly interesting for anyone. In such cases we recommend to either avoid using aggregated output (so diagnose the ICU/FIP separately), or use PCM PIDs instead of ICU ones (many ICU parameters for this car are replicated to PCM).
How to read parameters (PIDs) from several modules at once
-
- Posts: 2
- Joined: Fri Apr 05, 2019 2:53 pm
- Vehicle: F150 XLT 3.5 ecoboost 2011
Re: How to read parameters (PIDs) from several modules at once
I've selected just a few PIDs and they show on the Dashboard and Oscilloscope but the Start button won't work. Am I missing something. I've been able to make changes to the BdyCM, I put in new Differential Gear and changed that but I just am having trouble checking the fix.
Re: How to read parameters (PIDs) from several modules at once
Make sure you have "stopped" anything in the other areas of FORScan such as your "start" of configuration / AS-Built.
Re: How to read parameters (PIDs) from several modules at once
Hi I am using this function to try and find out a fault with FIP reporting lost watchdog signal ,using pid for fuel pump monitor with a on off output, results is key on pid is off ,key cracking pid is on is the fpm the watchdog signal any help would be gratefully received
Re: How to read parameters (PIDs) from several modules at once
Hello,
I need support. Is it possible to prepare offline PID list that I would like to save while driving my car?
Than I connect my PC to the car and start collecting data.
Thanks in advance.
I need support. Is it possible to prepare offline PID list that I would like to save while driving my car?
Than I connect my PC to the car and start collecting data.
Thanks in advance.
-
- Posts: 1
- Joined: Thu Jun 10, 2021 2:54 pm
- Vehicle: Focus,1.6L Duratec-16V, 1.6L/115 PS
Re: How to read parameters (PIDs) from several modules at once
We need to have a specification of the parameter itself. Forinstance long fuel trim >+15% means AFR too rich, fuel consumption will be high. Scan tool only shows the scale min - max.