


BTW I got a late model UK mk2 MR2 NA ECU today.

Dunno what rev it is





I really need to get my hands on a JDM rev 3 3SGTE ECU to see what MCU chip it uses.



Moderators: IMOC Moderators, IMOC Committee Members
JMR_AW11 wrote:Yes you do have to solder a small PCB into the ECU.This should only be carried out by a competent technician.
BTW I got a late model UK mk2 MR2 NA ECU today.ECU 89661-17500
Dunno what rev it is(1997?) but it looks like the piggy board will fit it
![]()
![]()
I really need to get my hands on a JDM rev 3 3SGTE ECU to see what MCU chip it uses.![]()
The trouble is they are hard to get hold of as people use them for upgrades to rev2 cars.
Blue4Ice wrote:If you could make it something like this:-
http://www.lotusespritworld.com/EGuides ... escan.html
then I would be very interested.![]()
When I have my esprit, freescan was a god send.
It was very useful in fault finding as you could see the output voltages of all the sensors as well as the actual readings.
![]()
I think I still have a pdf copy of the manual somewhere if you wanted to see it so that you could see all the functionality
Assuming it's not likely to get fried, I could probably loan you my Rev3 turbo ECU for a couple of weeks, would I get a board installed at cost for doing so?
rwilson_ie wrote:Just wondering where this development is at?
I'm interested in a Rev3 3S-GTE, if you have gotten your hands on one.
Ta
Rob
Another feature idea!..
.
![]()
How about a fault code reader that reads the code and looks it up on a database to display on the screen, in plain english, what the fault is?
JMR_AW11 wrote:rwilson_ie wrote:Just wondering where this development is at?
I'm interested in a Rev3 3S-GTE, if you have gotten your hands on one.
Ta
Rob
I've been taking a break from looking at ECUs.I'll look again in the new year.
The datalogger hardware is finished though, it works well.
it's just the user interface that needs more work.
I did reverse engineer the knock sensor routines for the JDM ECUs and can datalog all the relevant knock data.
The knock detection is quite clever and it retards ignition and adds fuel and it also remembers previous knock conditions(the ECU stores this as a kind of knock
'fear factor') and protects the engine in advance
(doesn't wait for the knock sensor the second time)
Over time this memory/protection slowly fades if there is no more knock and the ECU gets bolder again.The amount of ignition retard due to knock can be datalogged, as can the extra fuel and also the memory value of the fear factor can be datalogged as well.
![]()
(this fear factor actually has three values, each for a specific rpm range)
I also did a GUI for a pda which is far more convenient to use in a car.
Another feature idea!..
.
![]()
How about a fault code reader that reads the code and looks it up on a database to display on the screen, in plain english, what the fault is?
The datalogger can do this at any time(without needing the T to E1 link wire) so all I would need to do is write the text display.
It reads the codes direct from within the ECU MCU chip so it can display all the codes in the blink of an eye.![]()
(no need to count flashes)
I still haven't got hold of a rev3 ECU..
.
![]()
I tried to get one for sale on eBay- if there was one, and there were a few Rev3 owners, we could chip in and buy the ECU
?
Anyone willing?