No live data paramaters

[simran]

Hi this is my first poston this forum. I purchased a elm327 obd adaptor from ebay due to a problem with my ford fiesta 1.4 tdci on a 2008. The powertrain light (yellow cog) keeps displaying on my dash. I then scanned the car using the latest version of forscan and ended up with error codes for all four injectors, displaying short to ground, error for the maf sensor (malfunction), error for IAT (hight input), error for clutch switch (implasuable switch).

The injectors have been changed previosuly which were carried out a local garage to the previous owner in 2011. My first thought was i doubt its the injectors are all short to ground seems a bit odd. So i chnaged the clutch switch as it was the cheapest part, cleaned the maf sensor and IAT sensor. I then measured the output voltage from one of the pins on the IAT connector, which measured around 12v. From looking online the PCM shout only output max of 5V correct right?

I then rescanned the vehicle for fault codes and the only error code which remained was a short to ground in cylinder 2 and the powertrain light still remains, no power at all. I then tried to view the live paramters by selcting what PID i wanted to view, however, after clicking play, a message appers displaying turn car on but its turned on already and i am not bale to view any parameters. From my point obv veiwing the live parameters would show be if cylinder 2 is not owrking corretcly?

Any help would be appreciated, thanks

[FORScan]

I then rescanned the vehicle for fault codes and the only error code which remained was a short to ground in cylinder 2 and the powertrain light still remains, no power at all. I then tried to view the live paramters by selcting what PID i wanted to view, however, after clicking play, a message appers displaying turn car on but its turned on already and i am not bale to view any parameters. From my point obv veiwing the live parameters would show be if cylinder 2 is not owrking corretcly?

It looks like engine is in Limited Operation Strategy (LOS) mode, as a result it has no power. LOS mode is activated when a critical error is detected, in your case the injector in cylinder 2 seems to be the reason (although we recommend to re-read DTCs after some time, as other DTCs may (re)appear).

As for live data streaming, the problem looks odd (according to your description). The following steps must be done in order to read the PID data:

1. Press Setup button on double click on a gauge
2. Select PIDs you need in the left list (double click or press right arrow to select) and press the tick button. the dialog will be closed, and selected PIDs should appear on the dashboard.
3. You press the Start button and data should read.

If you process as described above, but the problem still exists, it may be a problem in communication with adapter and/or vehicle. if so, the only way to find out is to analyze internal FORScan logs. Please obtain them as described on the Contact Us page and email to us.

[simran]

Thank you for your help. I will try what you have said and hoepfully i should be able to view live data. If this not the case i will email over a log file. When i try to read a DTC on the PCM, it does not read and brings up a error. The button does have a yellow triangle with a ! symbol?

Could this be casued by the adaptor i am using? Its a switchable can adaptor which i purchased on ebay. It reads all the other units correctly as far as i know.
Thank You

[FORScan]

Thank you for your help. I will try what you have said and hoepfully i should be able to view live data. If this not the case i will email over a log file. When i try to read a DTC on the PCM, it does not read and brings up a error. The button does have a yellow triangle with a ! symbol?

Could this be casued by the adaptor i am using? Its a switchable can adaptor which i purchased on ebay. It reads all the other units correctly as far as i know.

This problem (periodic inability to read DTC from PCM module) might appear in versions prior to v2.2.*. If you have latest version installed and still experience the problems like described above, this sounds like adapter problems. Please email internal FORScan logs for detailed analysis.