Professional Documents
Culture Documents
0 « Moates Support
Menu
Categories
All Articles (69)
Developers Corner (3)
General Info (13)
Hardware (23)
Chip Burners (7)
Dataloggers (2)
Emulators (11)
General (2)
ROM Switching Kits (2)
Learning and Tutorials (43)
Classes and Events (8)
ECU Chipping (6)
Ford Tutorial (3)
Getting Started (16)
How Tuning Works (12)
Manufacturer Specific (73)
Ford (25)
GM (24)
Honda (17)
Nissan (8)
VAG: VW / Audi (1)
Software (16)
GM OBD I Software (5)
GM OBD II Software (3)
Honda Software (4)
MoatesSoft (3)
Troubleshooting (30)
What you need for ___? (25)
BMW – setups (1)
Dodge (1)
Ford – setups (9)
GM – setups (11)
Holden (2)
Honda – setups (1)
Ostrich 2.0
Product Pages: OSTRICH_2
Related Articles: OSTRICH_2
https://web.archive.org/web/20210425124620/http://support.moates.net/ostrich-20-overview/ 1/7
1/3/23, 2:57 PM Ostrich 2.0 « Moates Support
The release of the Ostrich 2.0 was the marking point for the next generation of Moates products. Along with
a 75% size reduction, the Ostrich 2.0 also boasts many firmware advances. The Ostrich 2.0 connects to the
host computer with a baud rate of 921,600bps, which is the fastest bit rate supported by standard RS-232.
In English, this means uploads, download and verifies happen in less than 2 seconds for most ROMs.
There are also some new features for developers available on the Ostrich. Features like ROM tracing, and
window tracing allow developers to keep track of what addresses are being access within specific regions of
the ROM. This is helpful for reverse engineering roms, and can also aid in datalogging ECUs with limited
datalogging capability.
The following software packages are known to be compatible with the Ostrich 2.0:
CROME
Hondata
Neptune
eCtune
BRE
TurboEdit
TunerPro
To purchase the Ostrich 2.0, please see this item in our Online Store here
Environmental Compatibility
https://web.archive.org/web/20210425124620/http://support.moates.net/ostrich-20-overview/ 2/7
1/3/23, 2:57 PM Ostrich 2.0 « Moates Support
The Ostrich is NOT designed to be left in an engine bay!!! It will fail prematurely if exposed to the heat of a
bay. It is designed for a maximum operating temperature of about 80C (175F).
The Ostrich is NOT designed to be exposed to moisture!!! It will fail prematurely if exposed to liquids. It
will fail prematurely from condensation inside its case.
If you are going to use the Ostrich in harsh environments, try to do so for short periods of time and then
program a chip for long term use. We recommend this in general but it is especially important in harsh
environments.
Due to its internal battery constantly powering portions of the device, the Ostrich can easily be ruined by
condensation caused by sudden drops of temperature in humid environments. Returning the Ostrich to a cool
(~50-77F / 10-25C) , dry environment after exposure to high humidity before attempting to use again is a
very good idea. Placing it in a sealed bag with dry rice or another desiccant can help if condensation is
suspected.
27C32 (TBI GMs, Old Bosch Motronic) = 28 pin emulation cable, Socket Booster
27C64 (misc ECMs) = 28 pin emulation cable, Socket Booster
27C128 (misc ECUs) = 28 pin emulation cable
27C256 (misc ECUs) = 28 pin emulation cable
27C512 (misc ECUs = 28 pin emulation cable
27C010 (?) = 32 pin emulation cable
29F040 (?) = 32 pin emulation cable
We have NOT performed extensive testing to determine the fastest access time for the Ostrich2, but we
estimate that it is in the 65-80ns range. 90s is 100% safe.
In cases where you have a PLCC package chip, you CAN use the Ostrich 2.0 but you need a DIP->PLCC
adapter. We do NOT sell these. Logical systems seem to sell suitable adapters.
This is a list of application where we have found a SocketBooster to be necessary in SOME cases:
90-93 Nissan Z32 8 bit ECUs, 90-93 Nissan R32 Skyline 8 bit ECUs. (By extension, most 8 bit
Nissan computers around this age)
https://web.archive.org/web/20210425124620/http://support.moates.net/ostrich-20-overview/ 3/7
1/3/23, 2:57 PM Ostrich 2.0 « Moates Support
If you don’t see your ECM listed, email support@moates.net with the particulars of your application.
Power Consumption
User Jon Sole was kind enough to share this information with us. Jon measured the Ostrich 2 drawing about
71mA of power with USB disconnected in his application (3S-GTE) versus 16mA with USB connected and
supplying power.
While trying to use the Ostrich on a 3S-GTE platform, Jon discovered that the ECU would freak out and land
in limp mode with USB disconnected but run fine with USB connected. Suspecting that the difference in
power draw between an ordinary EPROM and the Ostrich was the culprit, Jon is going to try an provide a
secondary 5V power supply for the Ostrich to hopefully allow the Ostrich to be used with USB disconnected
without the ECU revolting.
http://www.adapt-plus.com/products/adapters/prod_dipplcc.html
http://www.logicalsys.com/
http://www.adapters.com/
https://web.archive.org/web/20210425124620/http://support.moates.net/ostrich-20-overview/ 4/7
1/3/23, 2:57 PM Ostrich 2.0 « Moates Support
We recommend you buy a suitable cable from us. You should not bother reading this section unless you
understand how EPROM addressing works and you have a specific need that cannot be met with a cable we
already sell. This is not for beginners. You are warned.
Parts can be found here (Page 106: PCI-24, PCI-28. PCI32, IDS-34)
The pinout of the Ostrich is more or less the same as the chips that it is designed to emulate, viewed from
above. The two switches define the possibilities – 24 pin(2732), 28pin (27C512) and 32pin (AM29F040).
A very important thing to note is that all pins are live in each mode, i.e. if you are using the Ostrich to
emulate a 27C256 in 28 pin mode, you must make sure that the highest address pin (A15, pin 28) present on
the 27C512 but missing on the 27C256 is in a defined state by using a pull up/down resistor. Although the
Ostrich has very weak internal pull-ups, allowing pins to float in an undefined state is likely to cause
problems. TunerPro RT and most software typically top-justifies bin files when uploading them to the
Ostrich so generally pull UP resistors are going to be what you need. If your target system has hard pull
downs (ground) on “unused” address lines, you will have to either disconnect these lines from the target
system and manually pull them high *OR* adjust where in the Ostrich’s memory bins are uploaded to.
In 32 pin mode, the Ostrich uses 32/34 pins with the same pin numbering scheme as a 29F040:
In 28 pin mode, the Ostrich uses 28/34 pin with the same pin numbering scheme as a 27C512:
https://web.archive.org/web/20210425124620/http://support.moates.net/ostrich-20-overview/ 5/7
1/3/23, 2:57 PM Ostrich 2.0 « Moates Support
In 24 pin mode, the Ostrich uses 24/34 pins with the same pin numbering scheme as a 2732:
https://web.archive.org/web/20210425124620/http://support.moates.net/ostrich-20-overview/ 6/7
1/3/23, 2:57 PM Ostrich 2.0 « Moates Support
Data Trace
The Data Trace feature of the Ostrich 2.0 allows you to observe which data in its memory is being accessed
by the target system. It’s a little more complicated than it sounds so there is a dedicated support page for the
Trace Feature.
© 2021 Moates.Net
https://web.archive.org/web/20210425124620/http://support.moates.net/ostrich-20-overview/ 7/7