Page 2 of 3

Re: No connection to the ABS with an ASUS Netbook

Posted: 29 Mar 2011, 15:47
by Alfaeddy
Hi
here the log files from ASUS netbook course, there are no log for the ABS because no connection could be established.
But I have a log attached from my Medion laptop with the connection I get the settings and the KKL is the same
only I\'m not holding with ASUS on the ABS

Thanks and regards
Eddy

Re: No connection to the ABS with an ASUS Netbook

Posted: 03 Apr 2011, 17:07
by yani
EnIgMa wrote:it can't be a processor issue...

Come one guys :)
It's like every other softwares.

If your processor is lower then 1600, FES could run slower....nothing else.
It's like a videogame.. :D
This is not exactly true...
The communication with the ECU has very strict timing restrictions. If the program does not respond withing a specific time period (it is different for each ECU, but let's say 20ms) then the ECU simply drops the connection.

Re: No connection to the ABS with an ASUS Netbook

Posted: 04 Apr 2011, 09:29
by Alfaeddy
Hi Yani
Thanks for your answer

So my guess with the somewhat slow processor was not entirely wrong.
Can you fix the problem, perhaps by increasing the RAM memory?
Or can overclock the processor higher?
Because unfortunately I know now already some users who have connection problems with their netbook.
In most cases, with individual controls

Which would be very grateful for a solution


Thanks and Greetings
Eddy

Re: No connection to the ABS with an ASUS Netbook

Posted: 13 Apr 2011, 17:07
by wombi
Hi,
because nobody here knows what could lie.? :?:

Best regards
wombi

Re: No connection to the ABS with an ASUS Netbook

Posted: 17 Apr 2011, 21:02
by Alfaeddy
Hi
I think it should still be some people here have a similar problem.
So also can not connect with a Netbook.
I know now the 3 User sporadic connection problems here should also notify other so that together we can find a solution.

Thanks and regards

Eddy

Re: No connection to the ABS with an ASUS Netbook

Posted: 24 Apr 2011, 19:54
by tonne2
Hello
i´ve got the same problem. I don´t think that the reason is the processor. I´ve testet it with an Asus Netbook, and also with an Acer Laptop with Dual core 2x 1,5Ghz and 2GB RAM but no conection.
I´ve testet on:
Fiat Bravo year : 2000 105 JTD test : ABS - Airbag - no connection EngineEDC - test - OK
Alfa 146 year : 1996 1.9 TD test : ABS - Aribag - no connection
Fiat Punto year : 1996 type 55 test : Airbag - no connection
Lancia Dedra : 1996 test : ABS - no conneciton

I don´t understand why Engine EDC is running with both Computers but nothing else...
I tested the newest Driver. Computer settings COM1 , 4096 Bytes, reaction time 1 Second, no other Com Ports on Computer.
Interface is a KKL with usb.

Re: No connection to the ABS with an ASUS Netbook

Posted: 25 Apr 2011, 09:11
by wombi
Hello tonnes 2
I have exactly the same problem with ASUS 1005HA Processor 1.67
in this Forum viewtopic.php?f=4&t=2095
is written about it also ..
According to information provided by yani - it should go eigendlich - Requirements:
- Any hardware that runs Windows XP, Windows Vista, Windows 7
- Microsoft. NET Framework Version 2.0 SP1. Free, available from www.microsoft.com.
- K-line connection cable connected to USB / PCMCIA / onboard serial port, or ELM 327 v1.3 OBDKey 1:40 interface
- 1.5GHz CPU and better required
Perhaps it is also a Einstellunfsfehler in the program itself

Otherwise, it is a good program to recommend. ;)

Wait times what yani says!

Best regards
wombi

Re: No connection to the ABS with an ASUS Netbook

Posted: 07 May 2011, 09:13
by yani
Hi,

I spent one hour today testing with my ASUS 900HA (Windows Vista, Intel N270 CPU, 1GB RAM, ...) and a VagCom interface today. I did not have ANY problems at all. I tried reading all aparameters at once, recording graphs with many parameters, etc. And, not a single disconnect. I even tried to put the netbook to low-power mode and it was still working properly.

I think that you should check the following:
- interface driver version
- latency setting for the driver
- USB/chipset drivers
- version of .NET Framework
- power management settings
- running programs in Windows (there might be anti-virus or other running software which overloads the computer)
- loose USB connector (this already happened with some users - when they tried to use a USB port which fits more firmly all problems disappeared)


Yani

Re: No connection to the ABS with an ASUS Netbook

Posted: 31 May 2011, 19:52
by wellij81
Hi Yani,

I know it is difficult because you can't reproduce the problem, but we need a way forward on this. Many of us are having problems - see my new thread here:
viewtopic.php?f=3&t=2200

I have been through your list, as have many others, and don't know what to do - I cannot use the full functionality of a program that I have paid for.

I have the latest FDTI chip driver, as do many others, I have set the latency to 1mS, I have the latest drivers for my laptop, the latest .NET, I turned off power management, I disabled all antivirus/firewall/wireless, and I haven't got a loose USB socket.

I have used the most powerful up-to-date brand new laptop (definitely no loose USB sockets!) with Intel core i5 processor, and it is no different. What can I try next? You must get someone to demonstrate these problems to you. Have you seen the videos posted by Darkman in this thread?
viewtopic.php?f=4&t=2095&start=10

A few weeks ago you promised an update to improve the stability of the VAGCOM interface. Is that still going to happen?

Jon

Re: No connection to the ABS with an ASUS Netbook

Posted: 01 Jun 2011, 08:16
by yani
Hi,

Yes, the new version is ready. It is working much better with serial ports that have high latency.
However, I need to do a little more testing with it. Just a few more days.

I don't know what could be causing this problem with high latency on the serial ports.
It could be something with the chipset drivers or another USB device which is using a lot of system resources. Or it could be some background process (or service). I really don't have an idea.
Yesterday I spoke with a user who experienced exactly the same problems after re-installing his computer (it has been working fine before reinstalling). Then he downloaded and installed latest FTDI drivers and everything started to work perfect.

Yani