Here are my latest tests with unregistered version 3.3 of FES :
I resinstalled the complete Win XP SP1 and tried SP2 and SP3 on my EEPC.
In the mean time, I changed the 512 Mo memory to a 2 Go ( Windows needs a lot, and a 1 Go memory wasn't really cheaper...)
FES runs fine, both with my Acer 5720G 'under Vista Home Premium and its 1.5 GHz CPU and the EEEPC.
I still face the "Latency too High" message, but the extra memory seems too add stability to the connection.
Monitoring the CPU frequency, it only uses up to 80% of the overclocked EEEPC...
and about 50% on my Acer laptop...
I only noticed that when using FES, and the car's engine is running, there are Latency messages coming up at the same time as electrical loads change (headlights on/off or vent running...)
As I also face trouble with the advance device, the engine runs unevenly.
Could the problem come from the VAG-COM interface? or its electrical supply which needs a smoother signal?
Last point, I opened the VAG-COM device and found that the FTDI chip in it is a FT 232 BL 1005 series.
Searching Google, it seems that chip is an old one (~2002 if I remeber well...)
FES is really perfect for troubleshooting!!!
I used it, this week, to find the problem I meet with the aircon system. As I have the electrical drawing for the car, it becomes very easy to runs test with FES and using a multimeter where FES cannot help.
I also used it to monitor the engine running, checking the RPM's and the advance correction.
On the graph, I found that each time the engine runs unevenly (RPM drop), the avdance correction drops to -3°.
Or the advance device is faulty, or there is an electrical problem on the device feed line... I got closer...
Many thanks Yani for this cool software!!!
May all of you have a very very good new year!!!
Good scans to all,
Cheers,
Vince