Improved FTDI Driver settings

Pages: [1]

« previous next »

Author

Topic: Improved FTDI Driver settings (Read 8936 times)

carlossus

Sr. Member

Karma: +38/-0
Offline

Offline

Posts: 394

Leon Curpa Stg1+

	Improved FTDI Driver settings « on: February 25, 2011, 09:00:58 AM »

Up to now I have failed to flash at any speed above 10400 baud, this meant 12 minutes to flash a 1Mb file.

However, since monoscan suggested these settings http://sites.google.com/site/monoscanen/how-do-i-configure-the-ftdi-driver, I tried it with Nefmoto and now it connects at maximum baud and flashes in 3 minutes. I am very pleased indeed.

I think the key is reducing the latency to 4ms.

My ECU is 06A906032HN.


	Logged

Tony@NefMoto

Administrator
Hero Member

Karma: +132/-4
Offline

Offline

Posts: 1389

2001.5 Audi S4 Stage 3

	Re: Improved FTDI Driver settings « Reply #1 on: February 25, 2011, 12:59:29 PM »

What was the latency set to before?

The NefMoto software sets the latency manually on the USB device when it opens it before connecting. Maybe the com port latency change has a different effect then the USB device latency, even though the NefMoto software opens it as a USB device...


	Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto

carlossus

Sr. Member

Karma: +38/-0
Offline

Offline

Posts: 394

Leon Curpa Stg1+

	Re: Improved FTDI Driver settings « Reply #2 on: February 25, 2011, 01:39:58 PM »

The default was 16ms.


	Logged

Tony@NefMoto

Administrator
Hero Member

Karma: +132/-4
Offline

Offline

Posts: 1389

2001.5 Audi S4 Stage 3

	Re: Improved FTDI Driver settings « Reply #3 on: March 13, 2011, 06:09:10 PM »

This makes sense for Monoscan but not for the NefMoto Flasher. Monoscan uses the FTDI USB device as a virtual comm port, and so it relies on the virtual comm port settings in the device manager. The NefMoto Flasher uses the FTDI USB device through the FTDI SDK as a USB device, and directly sets the device latency when it opens the device.

If you say it helps, then I believe you, but I have to assume that something weird is going on. Maybe it is an issue with having the device installed as a virtual comm port on your system, and somehow that is causing the explicit latency set through the FTDI SDK to be ignored.


	Logged

Pages: [1]

« previous next »

Jump to:

Navigation

Personal Tools

November 29, 2024, 09:59:45 PM

Welcome, Guest. Please login or register.
Did you miss your activation email?

Navigation

Personal Tools

Search