Ef8sirjunkie

Having problems putting the bin into the ostrich. ECU is P28 auto i converted it buy cutting RP17 and jumping RP18 runs car fine if i have J1 unhooked (doesn't throw any codes). I also cut J12 for use of my Hulog. and i am runing crome 1.5 (free edition of coarse).


1. connect ostrich to lap top open device manager and look at port and baud settings. ( have tried alot of different ports and baud rates)

2. open crome then load a p28 or p30 rom.

3. remove checksum

4. settings - real time programing - Moates Ostrich/Burn 1 set com port and baud rate ( 4 some reason it will change to 115200 or 920000 after clicking detect connection and it will say connected).

5. save changes made then click real time toolbar button. then press "Put" I get
""Timed Out the operation failed after 128 attempt(s) with 10 milliseconds each attempt.

I have no clue why i cannot connect anymore i even searched on here and found another thread about using Tuner Pro RT i downloaded it but i cant work it for crap? any help guys please!

lilpooh21186

make sure your baud rate is the highest like 9200000 or some ---- like that

blowngsr1wn

also in the port settings in the control panel they can get screwed up. i had the same prob. it was the the port settings in the computer not in crome
hope that helps Wes

Ef8sirjunkie

i have the first ostrich i think the ostrich 2.0 was made for 920000. ill try again ill set it at 9600 or 34800 and it will change to 115000 or some ---- like that and ill go and change the setting to 115000 also and nothing or leave it at 9600 then it will change and still same nothing. it detects a connection but just wont put it to the ostrich.

stenseltizm

11500 sounds familiar

at any rate after making any changes to the port settings make sure you save them then close and reopen crome. I had that problem before.

Ef8sirjunkie

found this
http://www.moates.net/documentation....entation_id=22
the only thing for a firmware update is for 2.0 should i update to that software?

Cray91

Download the firmware updater and read the "readme" file. If that doesn't answer it, contact craig at Moates. he is good about getting back to people. Also read any FAQs that he has there.

Ef8sirjunkie

!!!Thank You Craig Moates!!!

found out it was the stupid time out settings it was set at 10milliseconds and changed to 500miliseconds. works perfect!!

Tom-Guy

That works for Ostrich v2.0, ***** you for Ostrich v1.0


You mean 115000? That works for Ostrich v1.0, ***** you for Ostrich v2.0

lilpooh21186

thanx davis i have 2.0 i thought they all were the same