Alfa 147 1.9 JTD 16V FES 2.6 connection problems KKL

[TribesMan]

Hi yani.

Today I discovered a bug in FES 2.6. When I tried connecting to my ECU with KKL cable, a few seconds after you press F10, the computer becomes laggy (mouse moves jerky) and then after 5-10s I get an error Failed to connect.

I tried 2 cables, same problem with both, and I tried connecting with FES 2.5 where it works fine. So there must be a bug in 2.6. I sent error report to your server.
ELM connection works fine on the other hand.

Also one other thing. There is a still stupid limitation with ELM cable and EDC16C8, that you can log only at reduced speed when compared to KKL cable. If I select 4 parametres I can log with 80/min when I use KKL, but only 30/min with ELM... That sucks

I hope you can get those two issues fixed.

[yani]

Please try the new version 2.6.1. It should fix this problem.

[TribesMan]

Tried it today and it connects with 2.6.1.
But new problem. Once I select a few parameters to log and I click Graph tab, I get non stop latency-too-high blinking in lower left corner. And it is impossible to log anything because there are too may data dropouts (almost every second logged parameter is 0...)
When I ho back to Parameters tab (or any other tab), the latency too high blinking stops.
The COM port settings are as they should be... and I tried it on two laptops. Same story.

[yani]

Did you try to set "KWP Timings" to "Default" in Settings?

[TribesMan]

Never noticed that there was an option for this... It was set to default... I will try other options as well.

Edit:
Fast and Optimal seem to work the best for me. They both behave exactly the same. Data dropouts are far less, maybe one in 50. I can live with that

Slow and Default are both problematic...

Can you maybe write something more what those options do exactly?

[TribesMan]

I think I've cracked it...

I resolved the problem with data dropouts when logging data. All I have to do was resizing the size of the window in which FES was running. I usually ran it maximized, but when I scaled it down from maximized to ~1/4 of screen size (1400x1050 screen resoultion) it started to work perfect. No data dropouts.
Latency time out was still blinking, but all the data was correctly logged.

Now I have only one request. Can you change colors in graph to something more contrasting? Amber and blue (and all other darker colors) are very hard to see against black background of the screen. Using colors like yellow, orange, bright green, turquoise, pink...will make it much easier to see... Also thickness of the lines could help a lot... making them 2 or 3 points thick instead of 1.
Also making font of the max and min logged values a bit bigger wouldn't hurt

[yani]

Hi,

You can change the colors and line thickness from Settings.

When you reduced the size of the window you actually reduced the area of the graph which is redrawn a few times per second.

As for the min/max font size - I think the font is big enough. I see that you are using high resolution screen and probably all your fonts are small... If you set the proper DPI in windows then everything will look normal.

Yani

[TribesMan]

Great! Never noticed those settings...

I guess I should read user manual more carefully.

I will try to fix the font size issue by my own

Thanks a lot.