ycming said:

The data logging is created in an excel spread sheet automatically, there are 3 columns whichs logs error if there exist one. Tomorrow, i'll unplug some sensor see if it logs anything!

Ming

Click to expand...

We're all still on tenterhooks here

Has anyone looked into using a Bluetooth <-> serial module? eBay items 350373211607 or 190415094533 for instance. It seems they use 3.3v so a level converter would be required too, eg MAX3232CPE. But once made up and plugged in it could be quite convenient, especially considering the Cinq ECU connector is in the engine bay, not in the cabin. It would also allow phones and other Bluetooth devices to communicate with the ECU.

They may only work as 9600 baud however, would this be an issue?

i think the problem would be with getting it to change baud rate after initialisation startrek does this but i doubt you could get your phone to do the same over bluetooth

I would have thought it's doable. Anyway, I was mainly throwing the idea out there for laptop users, as it would be easier/tidier than running a lead through the bulkhead or between bonnet and door seals.

BlueDanGroup said:

I would have thought it's doable. Anyway, I was mainly throwing the idea out there for laptop users, as it would be easier/tidier than running a lead through the bulkhead or between bonnet and door seals.

Click to expand...

I don't have sound proofing also i have a hole drilled behind the dial clock so i can run the speedocable easier. The hole is big enough for me to run that cable

Ming

ok bit of a curve ball question here...

does this stuff work with the mk1 panda, is it the same type of ECU on them?

Try checking if this document lists the ECU you are interested in:

https://www.fiatforum.com/attachment.php?attachmentid=5191&d=1118006911

There are four mk1 Panda-s there

ok next daft question how do i know what code my ecu has?

peterainbow said:

ok next daft question how do i know what code my ecu has?

Click to expand...

Well, if the ECU box has 6F or 16F printed on it, chances are very good that you are all set

ah now to go and see if i can see that

My program is almost finished now and tested using the real IAW-16F.EB ECU, so please give it a second try.

http://sourceforge.net/projects/iaw-scan/files/



All sensors are "emulated" by the potentiometers, that's why the IAT graph looks like it looks...

I've almost forgotten - IAW 18F and IAW 18FD are not the same, IAW 18F is the same as IAW 8F (SPI/MPI-Full Group).

This looks tidy!

Will this work with window 7?

Use this:

http://sourceforge.net/projects/iaw...U_Scan_BIN.zip/download?use_mirror=netcologne

Thanks
Ming

Yes it fully supports Windows 7 in both x86 and x64 versions. Also with the version 0.2.0 there was introduced a support for standard KKL USB cable with FIAT 3-pin adapter.
http://iaw-scan.sourceforge.net/
http://sourceforge.net/projects/iaw-scan/files/

P.S.
To insert link if you have under 5 messages it is enough to edit message and paste links into this edited message...

ahh so the 0.2.0 version, is the updated version . I am going to try this on my cinq sometime this week! I'll be using the KKL version!

Does this read out the error codes (management light ?)

Thanks
Ming

Yes, it reads error codes, status flags, adaptation parameters, live data, can erase trouble codes and perform active tests.
What is not done yet is entering emergency immobiliser code (instead of using acceleration pedal) and changing adaptation parameters (it was anyway blocked in newer units).

There is no special KKL version, program is one for both interfaces and "automagically" detects used interface - but remember to always select propper COM port in the Initial Configuration menu (selection is not remembered after exiting application - I'll correct this soon).

Feedback would be appreciated - especially ISO codes and ECU markings of cars using IAW-16F detected as Unknown (i.e. Seicento 1.1SPI).

You should use "true COM" KKL cable or USB-based, but prefferably based on FT232 chip, with two separated K lines. If cable worked with Neil's StarTrek-Punto it should also work with mine IAW ECU-Scan.

P.S.
KKL support is introduced with a great help of Neil (Barnacle) - thanks again!

i have an 1.1 SPI fase 2, a portable pc and some spare time... what else do i need to run that cool program? cable, adapter, holes??? does this work? Cable USB / OBD II Diagnóstico VAG kkl 409.1 where does it goes?

All you need is a Laptop running MS Windows XP or newer with.NET Framework 2.0 installed, the VAG-COM 409.1 USB cable and OBD-2 to FIAT 3-pin adapter cable. The FIAT 3-pin Diagnostic Link Connector is located under the bonnet near the ECU. Originally it is plugged into a blind socked.

all right. let´s see if i can get my hands on those cables

Been testing these three app´s to monitor my 1.1 SPI 16f fase 2 ecu. Will share the following results:

IAW ECU Scan - So configured the vag program, on the usb port forced dumb mode. Go to the ecu application shows me the usb port as com 24, select auto ecu and it timeouts... select my ecu the 16f it hangs... Status connecting...(iso: 00-00-00-00-00-00). what now?

FIAT ECU Scan - doesn´t connect because it doesn´t see the com 24 as a valid port although it can test it succesfully...

Startrekunto program - Works great. Plug and play. Using interface com 24(usb).

adr1ean said:

IAW ECU Scan - So configured the vag program, on the usb port forced dumb mode. Go to the ecu application shows me the usb port as com 24, select auto ecu and it timeouts... select my ecu the 16f it hangs... Status connecting...(iso: 00-00-00-00-00-00). what now?

Click to expand...

Use most recent version (currently 0.2.16) and do it in the following order:
- connect interface to the computer
- connect interface to the car
- run the program
- select COM port
- click [Connect] or press [F10]
- turn the ignition ON (MAR) when requested.
Before first connection in the program session the ignition must be OFF for at least 90sec in order to Power-Latch turn off. If you force-select ECU-Type you don't have to wait these 90sec., but anyway you must not turn the ignition ON before requested. No special configuration of USB ISO-KKL cable is required. I've tested this program on P3 500MHz laptop running Windows 2000 SP4, Pentium M 1,6GHz laptop running Windows XP SP3 and Core2Duo 2,8GHz desktop PC running Windows 7. However since some time I havent done compatibility tests using ISO-KKL cable, but I don't get any other signals that something broke in support for this interface.