Welcome to Bimmerfest -- The #1 Online Community for BMW related information! Please enjoy the discussion forums below and share your experiences with the 200,000 current, new and past BMW owners. The forums are broken out by car model and into other special interest sections such as BMW European Delivery and a special forum to voice your questions to the many BMW dealers on the site to assist our members!

Please follow the links below to help get you started!

Go Back   Bimmerfest - BMW Forums > BMW Model Discussions > M Series > E36 M3 (1995-1999)

E36 M3 (1995-1999)

Reply
 
Thread Tools Display Modes
  #1  
Old 04-08-2013, 01:37 PM
anjindd0t anjindd0t is offline
Registered User
Location: tennessee
 
Join Date: Apr 2013
Posts: 2
Mein Auto: M3 e36
ECU not recognized by AIM Data acquisition?

Tuner folks,
I bought a track ready e36 M3 arms-length from the builder, through a dealer. Very nice ride, was advertised as having a Z3-M s52 motor installed for the build, runs great. This "appears" to be correct, dynos at 268rw. Funny thing is that the ECU VIN comes up as coming out of a 1994 325iC with a 2.5L engine (?). That's 3 different years and models between car, engine and ECU Since it does run great, any thoughts on why a builder would do this? Also and pro/con on getting the correct ECU for this engine so the AIM data acquisition system will recognize it? Thanks in advance for insights!
Reply With Quote
Advertisement
  #2  
Old 04-28-2013, 06:24 PM
mda185 mda185 is online now
Officially Welcomed to the 'Fest
Location: NJ
 
Join Date: Aug 2012
Posts: 476
Mein Auto: 95 525iT w/S52, 03 530i
Quote:
Originally Posted by anjindd0t View Post
Tuner folks,
I bought a track ready e36 M3 arms-length from the builder, through a dealer. Very nice ride, was advertised as having a Z3-M s52 motor installed for the build, runs great. This "appears" to be correct, dynos at 268rw. Funny thing is that the ECU VIN comes up as coming out of a 1994 325iC with a 2.5L engine (?). That's 3 different years and models between car, engine and ECU Since it does run great, any thoughts on why a builder would do this? Also and pro/con on getting the correct ECU for this engine so the AIM data acquisition system will recognize it? Thanks in advance for insights!
That model year (1994) has an OBD 1 computer and fuel injection system. The S52 was an OBD 2 engine. It is fairly common to convert S52 engines to OBD 1 and install the intake manifold from that era. It flows better at high rpm than the OBD 2 intake manifold. The common ECU used for this conversion is the one used with the 2.5 liter engine that came in 325i and 525i cars from 1993-1995. A tuner chip would have to be installed in the OBD 1 ECU to run the S52 and the most common ones are from Turner, TRM, and Active Autowerks IIRC. I don't know anything about the AIM data acquisition system but if it relies on an OBD 2 connection, you won't be able to do that. Converting your race car to OBD 2 is possible but will be a fair amount of work. You will need the proper engine harness, sensors, throttle body, mass air flow meter, and ECU. You will also need to have the ECU modified to eliminate EWS starter interrupt.
Reply With Quote
  #3  
Old 04-28-2013, 07:42 PM
anjindd0t anjindd0t is offline
Registered User
Location: tennessee
 
Join Date: Apr 2013
Posts: 2
Mein Auto: M3 e36
ECU not recognized, solved

Thank you very much mda185, that 'splains it. Will leave it alone then as it runs just fine the way it is!
Reply With Quote
Reply

Bookmarks

Tags
aim, data acquisition, ecu


Forum Navigation
Go Back   Bimmerfest - BMW Forums > BMW Model Discussions > M Series > E36 M3 (1995-1999)
Today's Posts Search
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On



Forum Jump


All times are GMT -7. The time now is 09:36 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.
© 2001-2011 performanceIX, Inc. All Rights Reserved .: guidelines .:. privacy .:. terms