Flashing DA: Data Error after installing G1 and ostrich

85 Frankenstein · Post by **85 Frankenstein** » Sun Feb 16, 2014 7:59 pm

Hello, I have been able to connect to my 165 ecm consistently with the moates aldl cable. I just got their g1 adapter and ostrich, now it will connect, but it flashes data error very quickly and I am not sure exactly why. I have found other people mention the same problem and the answer was to change a delay or pause in the ADX editor. I think this is what I need to do but I am not sure what exactly to change and how to change it. Any help is appreciated. Thanks Adam

Post by **Mangus** » Mon Feb 17, 2014 1:00 pm

What year vehicle, and what definition?

You shouldn't have to change any pauses in the ADX. There is a latency setting in advanced settings for the cable's COM port in device manager. It defaults to 16. If it's already at default, you should be fine. If you previously set it to a low value, try increasing that value.

85 Frankenstein · Post by **85 Frankenstein** » Mon Feb 17, 2014 1:31 pm

Thank you so much I was pulling my hair out of my head with this one!!!!
I set the latency timer in the advanced settings to 16 as instructed and it works great, it was set to 1.

Post by **Mangus** » Mon Feb 17, 2014 1:36 pm

Cool. I have mine set to 6 or so, for a little more data throughput, but still avoiding the error.

85 Frankenstein · Post by **85 Frankenstein** » Tue Feb 18, 2014 8:41 am

One more quick question, after I set the latency timer for 16 and the aldl cable began to work very well, I plugged in the ostrich and started getting error messages again, so I raised it to 30 and they both began to work together without any errors. I did a little searching around and found a very good explanation
here: http://us.focusrite.com/answerbase/pci- ... mer-issues

After reading the article, it made me think that I would probably want to set the latency timers for both items the same and as low as possible. Does this sound right to you?

Also, the ostrich instructions that I found do not specify what com port number to use like the aldl cable from moates, which specifies com port 3 preferably. Do you know if this is important to set up a certain way?

Post by **Mangus** » Tue Feb 18, 2014 9:11 am

Your link doesn't work.

One virtual COM port should not affect the other. I'm surprised to hear that you had to change the ALDL driver setting when the Ostrich was attached.

TunerPro automatically detects the Ostrich; there's no port configuration necessary.

85 Frankenstein · Post by **85 Frankenstein** » Tue Feb 18, 2014 9:19 am

Fixed the link, thank you very much for your help!!!