Alfa164Diagnostics

[wilco]

Ok, I think its time to release a version of the program i made to diagnose errors happening in our 164's

If you want to download it, or want to know what you need to run it; Please visit these links:

Alfa164 diagnostics version 1.0.15- setup.exe

version 1.0.15 update

version 1.0.16 update

FTDI drivers



This topic is used for any questions or problems you might have.


Unfortunately, i don't have the time to follow all other 164 forums, so i will only reply to most of the questions and remarks on this site.
I hope you understand.
Wilco

[164 TD]

Best invention since sliced bread!!!

I had it running today and I was able to go through all the systems!!!

Thanks for making this program and sharing it with us!!

[alfa east]

Is there a Nobel prize for altruistic 164 knowledge sharing? I'd like to nominate someone (actually, several people come to mind).

[Alfan]

If only this had come with my car, when I bought it

Works great, you just have to be a little careful when using it and driving at the same time...

[wilco]

I will extend it soon with an auto update function. Should work now but my laptop was messing me up so reinstalling
Hope it's usefull to you all
Glad to hear you got it working Arjen
And East... welll... dunno.. could be my first price ever am i nominated ?
Many thanks to Alan for the beta/roadtesting

[Ladin164QV]

Wow, thank You for sharing with us... I will test it as soon is my de-cat complete.

[Helli]

Wilco

first also from me many thanks for your work and for making it available here.

As you know, I have been involved in the discussions of 164 diagnostics on many levels.
Although I have collected now nearly all of the required Marelli modules, I was immediately intrigued by your approach.
And I tested it.

(1) My Airbag lamp was on again!
I connected cables and Laptop and it found the ECU and the Airbag system immediately.



Airbag and ECU are properly defined.
Under error type I do not know what V batt is. (Battery Voltage?)
Anyway, Status said that the error is corrected.

Now, I thought; I should reset the faults and the error lamp. But klicking the button "Clear Error Code" did not show any result. Since the program does not indicate via visual means, whether it is still doing something, I waited, but finally closed the program.

A subsequent test with the Marelli Tester showed "no Errors present" (so they were cleared after all).
I reset the error light and all is as it should be now.
---------------------------------------

(2) Since the test connector is easlily accessible a hooked the laptop to the ABS.

The program found an ECU, could identify it, but the ABS is "Unknown".
A pity!



Again many thanks.
Are you interested in more info, for instance on testing the M3.7?

[wilco]

Ah Nice it works for you.
I have to add your ECU code to the program, no biggy.
You might be right, easier to show what it's doing, and afterwards re read errorcodes.
The only thing is, sometimes you have to turn the key to the off and back to on position to restart the ecu so the errorcodes are really gone.
Vbat is indeed a too low battery voltage. could be a loose connector
But nice feedback so far. Thank you.
I will look into your problems

[wilco]

1.0.15 update: Download update
This is an update. In case you do not have the program allready, install that first!! from the link down here or the top of the topic.
Download

[wilco]

There seems to be a little update bug.
When you install it on another place D: for example, the updater will install the new update in C:\Program Files\Alfa164Diagnostics
So, until that is solved, you can fix this yourself by copying the contents of C:\Program Files\Alfa164Diagnostics to your installation path.

[Roadtrip]

Tried to install the driver, but there is no ftdport.inf file in the link provided. My computer does not recognize the device.

[alfisti-164]

Hi Roadtrip,

Welcome on this site! Thanks for registering!

I had the same "problem": just click the folder the drivers are in, and let your computer install the found device. (USB SERIAL PORT)
I will work fine.

Another tip: make sure that the com-port it uses is the first one! (Example: If your computer uses COM3, make sure the installed device uses COM1 or COM2) otherwise your computer might freeze.

Let me know how it turned out? Thanks!

[wilco]

did you unzip the file ?
Here you can download an unzipper
Winrar 32 Bit
Winrar 64 Bit

[wilco]

Hi Roadtrip,

Welcome on this site! Thanks for registering!

I had the same "problem": just click the folder the drivers are in, and let your computer install the found device. (USB SERIAL PORT)
I will work fine.

Another tip: make sure that the com-port it uses is the first one! (Example: If your computer uses COM3, make sure the installed device uses COM1 or COM2) otherwise your computer might freeze.

Let me know how it turned out? Thanks!

Also Com1 has a higher priority in windows. So less problems with timeouts.

[Maffia_Alfista]

Hi Wilco.

I have ordered the cables and installed the program but I don't understand how to install the "ftdiport.inf" driver.

If I double click on it it just open the text document. If I right click I can chose an "install" tab, but when I do that I just get an error messege saying..
"The INF file you selected does not support this method of installation"

Do I have to but the content of the rar file in some perticualar folder?

I'm running Win7.

Cheers // Daniel

[wilco]

click Start >> R mouse computer and choose manage in the menu.
In the window that opens, choose Device manager.
In there find the adapter. Think its under Ports.
right click on it and in the menu update driver software
click "browse my computer for driver software"
Browse to where ftdiport.inf is located.
Click next.
Windows should find and install the new driver now.

[Ladin164QV]

Yesterday I tested it, and its working beautifully. Its nice I can talk with so old ECU.

Thank You Wilco.

Only a question, can be somewhere set the refresh rate of the selected values?

[164 TD]

I have the original Alfatester and this is the refreshrate the tester works on as well. I think the bautrate is just that low.

[wilco]

It's exactly what Arjen says.
The protocol is just that slow. Nothing i can do about that. The only thing you can do is only use the sensors you need. Then they will update pretty fast.
The protocol was never designed for what you can do with the program. the tester also does not request so many sensorsat the same time.

[Alfan]

During my road testing of the sw, I have had no problem with connection on the latest version when going to work, which is about 40 minutes - but this is when you DO NOT click anything in the program after getting it all up and running! If you do, it most likely will lose connection and you have to reconnect. I have not tried more than 4 parameters at the same time, as it should not be needed.

I am currently driving a QV 24V and it is more tricky to keep connection in that car, compared to my Q4. You can try and adjust the response time at the bottom of the window.

[alfisti-164]

Wilco,

can you give me a few pointers on this problem please?

I can't seem to connect:


After a second or 10, and 5 reconnection attempts, the program freeses.


Updating works fine by the way!!

[alfisti-164]

Already got it, sorry...

The 12V wire didn't gave 12V. Connected it to the correct wire that did have 12V and it works fine... (off cource!)

[Alfan]

Already got it, sorry...

The 12V wire didn't gave 12V. Connected it to the correct wire that did have 12V and it works fine... (off cource!)

Been there, done that

[alfisti-164]

Ok, I have tested it on my twinspark and it works like a charm! However, when I hooked it up to my 24v (the main reason I got the cables etc.) the software doesn't go further then: Connecting to ECU...

I hooked up another Motronic module and got the same result.

[wilco]

lol atleast you found it out yourself (both of you)
is there no action at all from the lights ?
you should see the yellow one for "init"
when the ecu responds, you should see the green lighting up
When the program sends data, the red lights up
is there any response from the ecu ?

Btw. did the program recognize the TS ?