FTO AUSTRALIA

Just got the software and cables 2 days ago, and have been using it while I am driving it.

Observations:

1> Used about 80% cpu, when it is logging data, on my laptop, a 1.6ghz Pentium M processor.

2> Engine RPMs is being under-reported, as the revs get higher. At 100km/h, 4th gear, on a tip GPX, it is registering about 3k rpm, versus the 4k rpm on my car tachometer.

3> Speed reading does not work, on my 95 GPX. Not sure if a 98 or newer FTO will have the speed reading working.


Anymore feedback from other users here?

The stuff I used:
EvoScan 1.3D USB OBDII/MUTIII/SSMII Datalogging Cable
Evoscan version: 2.8

Keep in mind that EvoScan talks to the ECU using a very slow serial connection. The values that you are reading are possible a second or 2 old.

Also, the ECU has a lot of urgent work to do like running the injectors, tasks like these cannot be delayed, so tasks like reporting to you what is happening are not at the top of the ECU's priority list.

I spend about 20 minutes on the freeway at 100km/h 80% of the time.

For that stretch, I am getting readings of 3000 rpm.

weird, mine is 95 gpx 4 speed tip.

4th gear at 100km/h @ 2900 rpm. (definitely under 3000 mark)

phunkydude wrote:weird, mine is 95 gpx 4 speed tip.

4th gear at 100km/h @ 2900 rpm. (definitely under 3000 mark)

Do you mean from the ecu, or the dash's tacho?

dash's tacho.

phunkydude wrote:dash's tacho.

Ok, this is real strange.

Probably why I cannot seem to feel the MIVEC kick whenever I try to activate it at 5.5k - 6k rpm.

I wasn't too worried though, as it just means I use less fuel.
But, now I am concerned.

Any other GPX tip owners out there who can give us more readings of the rpm at 100km/h from their dash?

Check with EVOScan that you are getting a reading from the ECU to give you temp. If this sensor has failed you wont get MIVEC as it thinks the engine is still cold.

My old gearbox 100km/h = 3100~
new gearbox 100 = 2900
this is both tip

Ok, will check later. omw to work.

Storm wrote:Check with EVOScan that you are getting a reading from the ECU to give you temp. If this sensor has failed you wont get MIVEC as it thinks the engine is still cold.

Which temperature reading are you referring to?

Coolant temps?

yotka wrote:

Storm wrote:Check with EVOScan that you are getting a reading from the ECU to give you temp. If this sensor has failed you wont get MIVEC as it thinks the engine is still cold.

Which temperature reading are you referring to?

Coolant temps?

Yup, the ECU gets a separate coolant temp reading from the one on your gauge and it wont let MIVEC engage until that tells it the engine is up to temp.

Is that sensor replaceable as i find that the fans arent kicking in early enough and its running rich.

Also can you run evoscan as your driving?

Yep. But more than likely all's it needs is a quick clean on a wire brush. Get covered in crap being in the cooling system.

silverGPX wrote:Is that sensor replaceable as i find that the fans arent kicking in early enough and its running rich.

Also can you run evoscan as your driving?

Yup, it's CAMSKILL have the sender.

And yes, EVOScan will run while you are driving. You can get it to show various gauges while you do as well.

Bennoz wrote:Yep. But more than likely all's it needs is a quick clean on a wire brush. Get covered in crap being in the cooling system.

Where are the two sensors located?

silverGPX wrote:

Bennoz wrote:Yep. But more than likely all's it needs is a quick clean on a wire brush. Get covered in crap being in the cooling system.

Where are the two sensors located?

If you look to the bottom of the coolant tower there is one to the radiator side, it has one wire and is the dash temp sender. If you look to the bulkhead side there is another one which has two wires in it, thats the ECU temp sender.