Multiecuscan

@wellij81 - you got right. I saw this issue first time using new versions.
I didn't change anything in laptop ( just FES version ), no eather the tools ( I have the same one for a long time )
@ Yani - my dear why don't you wanna belive that it is not a net. framworks problems here.
I have all this one installed in my laptop for a long time.
I told you that if I unistall new version and I install back old versions till 2.5, 2.6 or 2.7 I can work with my VAg kkl tool but when I install back new version I couldn't work with same tool ( latency too high and it disconecting rapidlly.
Please check this isuue in the softwear of multiecuscan not in other things like configuration of laptops of net.framworks.
I will help you with tests if you like whenever you need.
Good luck

mattydr67 wrote:@wellij81 - you got right. I saw this issue first time using new versions.
I didn't change anything in laptop ( just FES version ), no eather the tools ( I have the same one for a long time )
@ Yani - my dear why don't you wanna belive that it is not a net. framworks problems here.
I have all this one installed in my laptop for a long time.
I told you that if I unistall new version and I install back old versions till 2.5, 2.6 or 2.7 I can work with my VAg kkl tool but when I install back new version I couldn't work with same tool ( latency too high and it disconecting rapidlly.
Please check this isuue in the softwear of multiecuscan not in other things like configuration of laptops of net.framworks.
I will help you with tests if you like whenever you need.
Good luck

Can't you understand that the other people probably have different problem than yours!
You are really not helping me (or anyone else) with these posts.
You first wrote somewhere that version 2.5 and 2.6 work fine, but 2.7 and 2.8 do not work. I spent some hours trying to compare the differences between 2.5/2.6 and the newer version and found nothing. Now you write that 2.5, 2.6 and 2.7 work fine but 2.8 and 3.0 do not. Which is more correct?
You don't say which car/module you are trying to connect to (so that I at least have a clue in which type of protocol you are experiencing problems and that I can try to find what has changed).
I understand that you don't believe it, but these problems can be caused by so many factors that I cannot describe them all.. It can even be caused by bad video drivers.
You just explain everywhere that the software has bugs and that is causing the disconnect problems. Yes, the software has bugs, but that's not causing the disconnect problems.

So, please tell me which version works for you and which does not, and also which module/car has problems. This way I can try to identify which of the changes has caused your problems.

guys, guys ...... PLEASE STOP.
I created this topic to come together to the heart of the problem
Each of us who write in this or a related theme has a problem with latency and disconnection or lack of connection to the engine ECU, ABS, etc., or for that 90% of us laptop uses the same or similar values ​​that we possess laptop = problem with the work of the FES .

However, I think that speaking and writing in advance that the FES has a bug or is underdeveloped is an insult to the author of the program.
Gentlemen! pointing out and bring to the problem of the Whole that the FES is wrong does not lead to anything.
Yani is not a miracle worker - in order to have and know how everything had to have the house all the car models (ECU drivers) that supports the FES, and all the laptops on which we work, then there would be any problems.

I think that we should first pass in the subject, all data and observations that we see during the tests and trials of the FES, burn movies, screan do, described in detail, step by step how and what we do - what settings to use, how many configurations were doing tests- so I am doing and send to Yani and politely wait for a response. Then what does Yani recommended.

Maybe common BUT helpful Force you get where the problem is that our concerns with the FES and with our laptops.

respect for all of you Darkman

@ Darkman

Great, you've found the right words.

Greetings Eddy

@Yani -
I told you that in a post before in this thread and it was just one from many others ECU's that I tried.
So I didn't said nothing before because I expected that all this will be fixed and I'm still waiting to you to fix it and I'm pretty sure that you'll do it. ( I wasn't so intrested because I do not use your softwear usually but when I saw that the other guys have same problems I checked by my self and I post my conclusion. I do this becasue I have possibilities to check many car dailly.)
But if you said that I'm not helping you, it is ok I will stop posting here, even I wanted to help ( MEA CULPA ).
Please excuse me for the inconvinient.
My appologies.
Good luck

mattydr67 wrote:@Yani -
I told you that in a post before in this thread and it was just one from many others ECU's that I tried.
So I didn't said nothing before because I expected that all this will be fixed and I'm still waiting to you to fix it and I'm pretty sure that you'll do it. ( I wasn't so intrested because I do not use your softwear usually but when I saw that the other guys have same problems I checked by my self and I post my conclusion. I do this becasue I have possibilities to check many car dailly.)
But if you said that I'm not helping you, it is ok I will stop posting here, even I wanted to help ( MEA CULPA ).
Please excuse me for the inconvinient.
My appologies.
Good luck

Ok, sorry about this. Now I saw that you wrote somewhere that it is about 2.10.3 and 2.10.4. You posted too many times that this is a bug and I missed this particular note. Sorry once again for this.
There is a big difference between the communication with 2.10.x, m1.5.5, EDC15, EDC16, ABS 5.3, etc. The most problematic are 2.10.x and ABS 5.3 as these modules break the communication very easily. They are very sensitive to minor timing delays and they are very sensitive to electrical noise.
But, It is still not clear if the problem exists in 2.7 or only 2.8 and newer versions. So, please confirm where it is.
As I wrote earlier, I've checked the differences between 2.6, 2.7 and 2.8 a number of times and there is no difference for these particular modules (2.10.x, ABS 5.3).
Also, the problem of @Darkman and @wellij81 is different than yours.
It will be very helpful if you send a report (using the red Send Report button) after the communication breaks.

I posted in diffrent thread becasue I saw that it was pretty much the same "isuue".
So look how it "works":
I can connect to this ECU's 2.10.3 and 2.10.4 using 2.5, 2.6 and 2.7 maybe I will try 2.8 eather.
I can connect to the ECU and when I choose parameters it is ok but I have to look in the left down corner that the "Latency too high" advertisment not be showed becasue if this is showed and I select parameters in that time it will become a disconation.
If I used 3.0 or 3.01 I could conect to that ECUS's but in 2-3 seconds it disconected.
The problem when I saw this and then I saw that it is a problem for other members of this forum too was when I did check my own car (better to say my wife car) An Alfa 147 2001 1.6TS 120HP and when I connected to the ECU Bosch 7.3.1 all it was good but when I select too fast the parameter I saw the advertisment in the down left corner "Latency too high" and if I continued to select parameters in the same rythem the softwears it disconected. I use same tools but we talking about Vag KKL interface not about ELM327 becasue with this interface I haven't any issue in my wifes car but Bosch 2.10.4 or 2.10.3 I can't make a connection using this ELM327 tool.
This is the facts that I made it me to write here not to blame your work, just to review the issues I have and maybe other guys can have it too.
I will try to send you the reports when I will have the Alfa 155 again in the garage.
My wifes car I can amke a diagnostic anytime.
Ok I suppose you understand what I mean and I will send you report to se what happend becasue too many words here and this is not good.
I wanna you to know that I'm next to you anytime and I will never be against to you even you are sometime mad on me becasue I have a "big mouth". Ok this is me.
Keep in touch.
Good luck

Did anybody thought about fact that you MAYBE do not use the same FTDI chip, and drivers installed?

drivers: http://www.ftdichip.com/Drivers/VCP.htm
http://www.ftdichip.com/Drivers/CDM/CDM ... 20Info.rtf

chip inside KKL: http://www.ftdichip.com/FTProducts.htm

matty did you try latest drivers?

Boris
You thought well about this but I can tell you that I used and I checked everything till I post here.
I checked using old drivers and new ones.
Today I checked my wifes car AR147 Bosch Motronic 7.3.1 and everything works pretty much OK.
I mean aftera rapidlly setting 10-12 parameters one by another it shows Latency too high but it didn't disconected.
So I think that for this ECU Yani fixed the issue.
I will check in the next days again the AR 155 Bosch Motronic 2.10.4 and I will show the review.
Thanks and Good luck

hi friends,
I refresh : have any news?

Yani sent from two weeks ago, two programs that checked the latency and time ..... data and sent the results to Yani, along with reports disconnects when I'm working with FES, but so-far silent on the subject, apparently Yani has a lot of work.

Does anyone of you tried to do something or solve your problem?