TE and Ostrich
After fighting with Ostrich and TE 2.5.5 this weekend on WOT's car and never could get it to work. So we went to the burn a chip, pull over method.
What Settings are you guy using ( COM#, bit rate) and connecting methods?
Everything worked fine in chrome, so I know the hardware is fine.
What Settings are you guy using ( COM#, bit rate) and connecting methods?
Everything worked fine in chrome, so I know the hardware is fine.
Bump for problems
Im gonna try drive home and burn method this week (no laptop), hopefully with the 3 bar map if you can send it to mw, and I gotta start reading, cause the boost portion of that tune was ------- sick
Im gonna try drive home and burn method this week (no laptop), hopefully with the 3 bar map if you can send it to mw, and I gotta start reading, cause the boost portion of that tune was ------- sick
Just finished testing ostrich with TE 2.5.5 and it's working fine on my side. Make sure that the com port ostrich is using is the same as TE. Anyway I followed the instruction found here: http://www.moates.net/documentation....entation_id=15 and used the same setting . You might try to download TunerPro RT just for testing.
Here is my settings:
Ostrich (usb to serial converter, under device manager)
com port: 3 ( I had to manually change this since it was at com 7)
latency: 1
bits per second: 115200
data bits: 8
parity: none
stops bits: 1
flow control: none
TE (under options)
RTP COM port: 3
Good luck!
Here is my settings:
Ostrich (usb to serial converter, under device manager)
com port: 3 ( I had to manually change this since it was at com 7)
latency: 1
bits per second: 115200
data bits: 8
parity: none
stops bits: 1
flow control: none
TE (under options)
RTP COM port: 3
Good luck!
Originally Posted by JK_Motorsports
No one?
Have at it!
Thread
Thread Starter
Forum
Replies
Last Post
TomBones
Engine Management
30
Mar 1, 2009 05:30 PM
cloud
Engine Management
49
Dec 5, 2007 02:41 PM
MyVtec8yourV8
Engine Management
4
Jan 7, 2006 06:26 AM



