%HTTP_EQUIV_ON_VIEW%
PGMFI Logo
Library> ECUHardware (r1.1 vs. r1.4) Destinations: Home | Library | Change Log | Index
Search | Go

 <<O>>  Difference Topic ECUHardware (r1.4 - 06 Feb 2007 - Jared Karagen?)
Changed:
<
<

Honda often used MCUs that had internal (on-chip) programs. These were often copy protected. There are Mcu Readers to defeat the copy protection

>
>

Honda often used MCUs that had internal (on-chip) programs. These were often copy protected. There are Mcu Readers to defeat the copy protection.

Added:
>
>

It is possible to switch between more than one program on your oversized EEPROM. All you need to do is add a pullup resistor to the extra address lines (A15, A16, Etc.), then to switch them, just add a debounced switch to the address lines to ground them.

Here is a diagram of 28 & 32 pin EEPROMS:

%META:FILEATTACHMENT{name="1.32_pin-2-28PinIC.jpg" attr="" comment="EEPROM pinouts" date="1170725945" path="1. 32_pin-2-28Pin IC.jpg" size="39713" user="JaredKaragen" version="1.1"}%


 <<O>>  Difference Topic ECUHardware (r1.3 - 31 Mar 2004 - Home.blundar)
Changed:
<
<

  • OBD2 AECU?s are quite similar.
  • OBD2 BECUs are quite similar.
>
>


 <<O>>  Difference Topic ECUHardware (r1.2 - 05 Mar 2004 - Home.blundar)
Changed:
<
<

Honda often used MCUs that had internal (on-chip) programs. These were often copy protected. There are Ways To Read AProtected MCU?

>
>

Honda often used MCUs that had internal (on-chip) programs. These were often copy protected. There are Mcu Readers to defeat the copy protection


 <<O>>  Difference Topic ECUHardware (r1.1 - 20 Feb 2004 - Home.blundar)
Added:
>
>

%META:TOPICINFO{author="blundar" date="1077236820" format="1.0" version="1.1"}% This page describes how the hardware in an ECU works, and fun things you can do with it. If you are just wanting to learn how to chip your ECU, you should look at What You Need instead. If you are looking for detailed information about what is going on inside a particular program, you might want to look at Rom Maps.

Honda definitely did not reinvent the wheel in terms of ECU technology for each new motor they released. Each "family" of ECU generally shares one or more PCBs that are populated with different components in order to run different motors. This really opens the door for ECUHardware Mods. Additionally, there are design peculiarities that carry over from one family to another.

ECU Families:

  • OBD0 Vacuum Advance ECUs from pre-88 cars lacking electronic advance distributors share some common features.
  • OBD0 DPFI ECUs from 88-91 cars are useless bastards that are 2 injectors short of being useful
  • OBD0 MPFI non-vtec ECUs from 88-91 are a definite family.
  • OBD0 Vtec ECUs like the PW0 and PR3 are a definite family.
  • OBD1 Civic Integra ECUs are a definite family.
  • OBD1 Prelude Accord ECUs are a definite family.
  • V6ECUs from the Acura/Rover/Honda Legend V6 cars, NSX and (?) V6 Accord have many common features.
  • OBD2 AECU?s are quite similar.
  • OBD2 BECUs are quite similar.

If you want to learn about how the Oki 66K MCU works, you should look at 66k Assembler Docs.

There are many ECUHardware Mods you can do to change how ECU hardware works.

Honda often used MCUs that had internal (on-chip) programs. These were often copy protected. There are Ways To Read AProtected MCU?

Ever wonder who designed honda's ECUs? Kehein Indiana Precision Technology is to blame...


{ View | Diffs | r1.4 | > | r1.3 | > | r1.2 | More }
Copyright © 2002-present by the contributing authors. All material on this collaboration platform is the property of the
contributing authors, and is covered by the Non-Commercial Share-Alike License unless explicitly stated otherwise.
Ideas, requests, problems regarding the PGMFI TWiki?? E-Mail the WikiAdmin
Site Designed By: Digital Fusion   Need a website?

Revision r1.1 - 20 Feb 2004 - 00:27 GMT - Home.blundar
Revision r1.4 - 06 Feb 2007 - 01:40 GMT - Jared Karagen?
%WEBCOPYRIGHT%