85 Frankenstein

Hello, I just installed the moates G1 adapter and ostrich on my 165 ecm. Before I did this I was data logging and had no connection issues. Now, the ostrich is working and the data logging is having connection issues. It will connect and feed live data, however, it says data error about once a second and then the data freezes, then it flashes connected for a very short time? Very confusing. I followed the directions for installing the hardware very carefully. Anybody have any ideas? Thanks Adam

85 Frankenstein

Its really odd, when looking at the graphs, it looks as though it might actually be connected for the majority of the time, they look pretty good and they seem to follow the engine data. It's probably good enough to get me the info I need. It's just really strange how it keeps flashing back and fourth between connected and data error.

85 Frankenstein

Also, I forgot to say when TP was connecting fine, it was with the stock $32B AKFT bin for 88 305 m5 3.08, after installing the G1 adapter, and ostrich I now cannot get to connect in $32B period, it turns a purple color and says connecting, but never connects, and the intermittent connection almost continuous is with the 89 $6E bin and mask.

85 Frankenstein

When I exited TP it asked me if I wanted to save the modified data acquisition file like it was changed but i did not change it?

85 Frankenstein

From the research I have done it is appearing that I should try to change the some sort of time or pause something in the da file editor, I am not sure exactly what to change or what to change it to? Does this make sense to anybody?

85 Frankenstein

Just wanted to let everybody know in case they are having the same issue. I was instructed to raise the latency timer in the device manager.
With the aldl cable plugged in, I went to the device manager and right clicked on the cable, usb comm port 3. Then I selected properties, under port settings I clicked on advanced. Then I set the latency timer to 16. Now it connects perfect. Hope this helps somebody at some point.

85 Frankenstein

Also, when I tried data tracing with the ostrich, it would now not do it, so I changed the latency timer to 30, now it will data trace, emulate, and read the aldl cable at the same time, hope this helps.

This link has a good explanation of the latency timer: http://us.focusrite.com/answerbase/p...y-timer-issues

oddscrounger

I was only able to connect by raising the minimum timeout period (for read and write) to 900 milliseconds.


It now doesn't flash DA Data error anymore... but I get junk data. Frickin' frustrated