DIY ECU remap project....
#1
BTT
As we now have some RR Figures -
http://www.scoobynet.co.uk/bbs/threa...=115197&Page=8
Corrected link
[Edited by Chris.Palmer - 9/2/2002 2:43:08 PM]
As we now have some RR Figures -
http://www.scoobynet.co.uk/bbs/threa...=115197&Page=8
Corrected link
[Edited by Chris.Palmer - 9/2/2002 2:43:08 PM]
#3
Drag it!
iTrader: (1)
Join Date: Jun 2002
Location: Flame grilled Wagon anyone?
Posts: 9,866
Likes: 0
Received 0 Likes
on
0 Posts
Just to let you know mine is MY00 and TD04 it peaks at 1.2 bar in 5th and settles at about 1.15bar. Thats with the TEK2 though. So it must be able to reach that boost level. Hope this is of some use to you.
edited to say isnt 0.6 bar crudely what you get when the ecu is in get you home mode?
[Edited by P20SPD - 9/3/2002 11:11:50 AM]
edited to say isnt 0.6 bar crudely what you get when the ecu is in get you home mode?
[Edited by P20SPD - 9/3/2002 11:11:50 AM]
#5
I am sure it's the fuel map!
97-98 shouldn't be very difficult, I know it doesn't have the eprom socket, and needs a header/ribbon soldering in place, not to mention moving a couple of surface mount resistors, but nothing too technical.
What may be more interesting is seeing if it has more than one ignition map, all in good time.
Edited to add: The seperate I/O controller is a pain in the older ECU as running the assembly code on a simulator means the analogue inputs are all converted to digital prior to the main cpu. On the newer controllers you can look up the address and write some input to the a/d port. I don't have a clue on the older ecus as all the controller datasheets are very rare, and not in soft copy.
Paul
[Edited by Pavlo - 8/6/2002 9:42:49 AM]
97-98 shouldn't be very difficult, I know it doesn't have the eprom socket, and needs a header/ribbon soldering in place, not to mention moving a couple of surface mount resistors, but nothing too technical.
What may be more interesting is seeing if it has more than one ignition map, all in good time.
Edited to add: The seperate I/O controller is a pain in the older ECU as running the assembly code on a simulator means the analogue inputs are all converted to digital prior to the main cpu. On the newer controllers you can look up the address and write some input to the a/d port. I don't have a clue on the older ecus as all the controller datasheets are very rare, and not in soft copy.
Paul
[Edited by Pavlo - 8/6/2002 9:42:49 AM]
#7
Thanks ECUTEK, Your input is always welcome.
Nobody appears to be establishing or retaining a comercial interset in phasec 1s anymore (no profit in it - hardware ie daughter boards + mapping etc make it uneconomic),
The intention is for this info to be open source (ie at cost ie - no profit/ no commercial interest).
Any help from the "professionals" is welcomed & gratefully recieved.
PS (If its any concellation - if ECUTEK produced a deltadash or TEk3 for Pre My97s - I'd buy it
HopefullY - an open source version for pre MY97's will be publishd soon )
Thanks
Chris
[Edited by Chris.Palmer - 8/6/2002 9:36:47 PM]
Nobody appears to be establishing or retaining a comercial interset in phasec 1s anymore (no profit in it - hardware ie daughter boards + mapping etc make it uneconomic),
The intention is for this info to be open source (ie at cost ie - no profit/ no commercial interest).
Any help from the "professionals" is welcomed & gratefully recieved.
PS (If its any concellation - if ECUTEK produced a deltadash or TEk3 for Pre My97s - I'd buy it
HopefullY - an open source version for pre MY97's will be publishd soon )
Thanks
Chris
[Edited by Chris.Palmer - 8/6/2002 9:36:47 PM]
Trending Topics
#8
Paul
Looks like your making good progress with the 91-96 unit. Are you sure that the table you have in the picture is the fuel map ? I ask only because we did the same thing about 6 months ago, and our fuel map didn't look like that. I'd be interested to know what makes you think that is the fuel map.
I don't think you'll find the 97-98 unit as easy to do. The main problem is that the board has no external EPROM socket. Also unlike the 96 version where there is a seperate I/O controller IC, the 97-98 version does everything in the one microcontroller.
We've nearly got it done, but not quite - and trust me, it's an a lot harder than the 96 version. But if you like a good challange, it should keep you amused for a few months !!
Let me know how you get on.
Andy
Looks like your making good progress with the 91-96 unit. Are you sure that the table you have in the picture is the fuel map ? I ask only because we did the same thing about 6 months ago, and our fuel map didn't look like that. I'd be interested to know what makes you think that is the fuel map.
I don't think you'll find the 97-98 unit as easy to do. The main problem is that the board has no external EPROM socket. Also unlike the 96 version where there is a seperate I/O controller IC, the 97-98 version does everything in the one microcontroller.
We've nearly got it done, but not quite - and trust me, it's an a lot harder than the 96 version. But if you like a good challange, it should keep you amused for a few months !!
Let me know how you get on.
Andy
#10
Scooby Regular
Join Date: Jul 2000
Location: Lancashire
Posts: 2,209
Likes: 0
Received 0 Likes
on
0 Posts
Paul,
If you want some help or guinee pig for the 97/98 version, I'll volunteer, as you know I already know my way around the ECU a bit.
I don't mind buying a secondhand ECU to play with.
Andrew...
My in-car select display is working well, I just need to package it now, I aleady have a couple of customers!
If you want some help or guinee pig for the 97/98 version, I'll volunteer, as you know I already know my way around the ECU a bit.
I don't mind buying a secondhand ECU to play with.
Andrew...
My in-car select display is working well, I just need to package it now, I aleady have a couple of customers!
#11
Can you send me a picture of your ecu pcb?
There are 2 types of ecu for 97-98, they should both use the same sort of board, but have different connectivity.
Paul
There are 2 types of ecu for 97-98, they should both use the same sort of board, but have different connectivity.
Paul
#12
Scooby Regular
Join Date: Jul 2000
Location: Lancashire
Posts: 2,209
Likes: 0
Received 0 Likes
on
0 Posts
Paul,
Is that question aimed at me, if so yes!
I was just about to edit my post to say that AFAIK the PE phase1 conversion (which is essentially the same as you guys are developing) uses the same hardware for all Phase1 ECUs.
Have you got a dump from a 97/98 ECU yet?
Andrew...
#14
Scooby Regular
Join Date: Jul 2000
Location: Lancashire
Posts: 2,209
Likes: 0
Received 0 Likes
on
0 Posts
Paul,
If you let me know the format you need for the dump, I should be able to generate one, or send me a copy of your software and I'll just use that.
Andrew...
If you let me know the format you need for the dump, I should be able to generate one, or send me a copy of your software and I'll just use that.
Andrew...
#15
Andrew, do you have windows?
It's very slow at the moment as the older ecu doesn't let you get multiple bytes at a time.
I can put something on a cd or email it.
It's very slow at the moment as the older ecu doesn't let you get multiple bytes at a time.
I can put something on a cd or email it.
#16
Scooby Regular
Join Date: Jul 2000
Location: Lancashire
Posts: 2,209
Likes: 0
Received 0 Likes
on
0 Posts
Paul,
I don't believe in windows, I have implemented OS/390 on an Intel 80836 cluster (just like the old microcoded IBM2900 processors) and use a 3270 as a remote terminal, I can put the whole thing in my trailer with a small generator so can log my ECU on the move....
...of course I've got freakin' windows
Feel free to email it to Andrew.Carr@dsl.pipex.com
Andrew...
I don't believe in windows, I have implemented OS/390 on an Intel 80836 cluster (just like the old microcoded IBM2900 processors) and use a 3270 as a remote terminal, I can put the whole thing in my trailer with a small generator so can log my ECU on the move....
...of course I've got freakin' windows
Feel free to email it to Andrew.Carr@dsl.pipex.com
Andrew...
#19
So you are not a true Linux geek after all Andrew. Program is currently written in Labview, but needs a little tweaking to run as a stand alone app. Need to work on in this week.
Pete, lurking as usual?
Paul
Pete, lurking as usual?
Paul
#20
Scooby Regular
iTrader: (1)
Join Date: Oct 2001
Location: South East
Posts: 1,300
Likes: 0
Received 0 Likes
on
0 Posts
Paul,
nice to see things are moving quite well.
As you know, I've got an ECU reader i've written for 97's, with nice (well - not really that nice ) visual guages and values for most of the important stuff done (rpm, boost, speed, throttle pos, coolent temp, batt volts etc).
Hove you sourced a select monitor PLUG ? or are you just 'wire stuffing' when you hook-up ?
I REALLY need a supplier for one of these.. makes it so much easier to demonstrate / test on other cars!
when you say 1st RR test will be 31st aug - is that at Tuning Japanese (with the E'bourne massive guys?) if so - I mite make a trip up there and meet you in person & see how things are going / show u my efforts! ???
cheers & keep up the good work!
Steve
nice to see things are moving quite well.
As you know, I've got an ECU reader i've written for 97's, with nice (well - not really that nice ) visual guages and values for most of the important stuff done (rpm, boost, speed, throttle pos, coolent temp, batt volts etc).
Hove you sourced a select monitor PLUG ? or are you just 'wire stuffing' when you hook-up ?
I REALLY need a supplier for one of these.. makes it so much easier to demonstrate / test on other cars!
when you say 1st RR test will be 31st aug - is that at Tuning Japanese (with the E'bourne massive guys?) if so - I mite make a trip up there and meet you in person & see how things are going / show u my efforts! ???
cheers & keep up the good work!
Steve
#22
My car in a MY97 and trying to connect a OBD II sanning tool, actually is the AutoTrap.
I find out that the connector plug does not match the ISO STD, I have pin 4,5,12,13 & 16, and as I find out I need pin 7 to make it work.
Does any one have discover how to make it work??
I find out that the connector plug does not match the ISO STD, I have pin 4,5,12,13 & 16, and as I find out I need pin 7 to make it work.
Does any one have discover how to make it work??
#23
S'duck, umm, currently using paperclips of all things!
They are just the right size to fit snugly in the socket contacts, and being steel, stiff/strong enough not to bend when you put them in. I just cut them about 15mm long and soldered wires to them. You might need a fatter than normal iron tip as the solder needs plenty of heat to take to the plated surface.
Paul
They are just the right size to fit snugly in the socket contacts, and being steel, stiff/strong enough not to bend when you put them in. I just cut them about 15mm long and soldered wires to them. You might need a fatter than normal iron tip as the solder needs plenty of heat to take to the plated surface.
Paul
#24
Tato,
I don't know the details of 97 impreza, and I didn't know they were imported to Peru!
I am using the yellow connector that looks like this:
I realised I also have an OBD connector, which is black with more pins.
Paul
I don't know the details of 97 impreza, and I didn't know they were imported to Peru!
I am using the yellow connector that looks like this:
I realised I also have an OBD connector, which is black with more pins.
Paul
#25
Hi guys,
That does look like a fuel map to me. Subaru tend to have a fuel map that contains AFRs rather than injector milliseconds, so may look a little different to some other ECUs. I have not checked these earlier ECUs, but it is likely that $80 in the fuel map is approx. stoich AFR. Values lower are leaner, values higher are richer.
For example: C3 in the bottom right corner is high RPM + high load fuelling. To work out approx AFR try...
$80
--- x 14.7:1 = 9.65:1 = stinking rich.
$C3
Note: This is very 'ish' with every disclaimer you can think up.
Also have a look at the two lines of data above the fuel map - these are axis scaling maps. The first line ($10 to $88) is the RPM scaling in 50RPM increments for the y axis i.e. 800 to 6800 RPM. The second line will be calculated load scaling for the x axis. These scalings allow you to alter what load or RPM point a line corresponds to. E.g. if you were to raise the rev limit, you may want to rescale the fuel map so that you have some points higher up at say 7200 & 7600 RPM.
Also no turbos until 2001 are OBD-II compatible, so no point in trying standard OBD-II readers unless you have a new age car.
>I have pin 4,5,12,13 & 16.
# 4 & 5 is ground
# 16 is 12v
# 12 & 13 are tx/rx though not necessarily in that order.
97/98 is mappable, but you are going to need to make another board. I believe these ECUs have edge connectors, not ROM sockets.
I hope you find this useful. I don't mind helping so long as it's all kept open source.
Cheers
Steve
EcuTek.
That does look like a fuel map to me. Subaru tend to have a fuel map that contains AFRs rather than injector milliseconds, so may look a little different to some other ECUs. I have not checked these earlier ECUs, but it is likely that $80 in the fuel map is approx. stoich AFR. Values lower are leaner, values higher are richer.
For example: C3 in the bottom right corner is high RPM + high load fuelling. To work out approx AFR try...
$80
--- x 14.7:1 = 9.65:1 = stinking rich.
$C3
Note: This is very 'ish' with every disclaimer you can think up.
Also have a look at the two lines of data above the fuel map - these are axis scaling maps. The first line ($10 to $88) is the RPM scaling in 50RPM increments for the y axis i.e. 800 to 6800 RPM. The second line will be calculated load scaling for the x axis. These scalings allow you to alter what load or RPM point a line corresponds to. E.g. if you were to raise the rev limit, you may want to rescale the fuel map so that you have some points higher up at say 7200 & 7600 RPM.
Also no turbos until 2001 are OBD-II compatible, so no point in trying standard OBD-II readers unless you have a new age car.
>I have pin 4,5,12,13 & 16.
# 4 & 5 is ground
# 16 is 12v
# 12 & 13 are tx/rx though not necessarily in that order.
97/98 is mappable, but you are going to need to make another board. I believe these ECUs have edge connectors, not ROM sockets.
I hope you find this useful. I don't mind helping so long as it's all kept open source.
Cheers
Steve
EcuTek.
#26
Thanks stephen,
We've been working on this for about a month now and we have the map scales for ignition, boost, boost duty cycle, some anonymous 8x8 map.
We have maps for fuel, ignition, ignition retard, boost, boost duty cycle, some anonymous 8x8 map and MAF scaling.
We have limits for boost, speed, load, revs.
Have a fuelling constant, MAP sensor scaling and offset.
80h is indeed stoch, ignition is plain deg BTDC boost is mmHg/8 abs duty cycle is %, revs = rpm/50. There are 3 stage rev (limit=120000000/rpm) and speed limits (limit = kmh / 2) , and I suspect the boost limit is mapped to throttle position also.
I am trying to figure the "anonymous 8x8 map" and a few other things, but on the whole we have it covered.
Will release a few more details on what's what once we have confirmed them on a car/ecu. There is also the issue of 2 different code types which have some maps in a different place.
Paul
We've been working on this for about a month now and we have the map scales for ignition, boost, boost duty cycle, some anonymous 8x8 map.
We have maps for fuel, ignition, ignition retard, boost, boost duty cycle, some anonymous 8x8 map and MAF scaling.
We have limits for boost, speed, load, revs.
Have a fuelling constant, MAP sensor scaling and offset.
80h is indeed stoch, ignition is plain deg BTDC boost is mmHg/8 abs duty cycle is %, revs = rpm/50. There are 3 stage rev (limit=120000000/rpm) and speed limits (limit = kmh / 2) , and I suspect the boost limit is mapped to throttle position also.
I am trying to figure the "anonymous 8x8 map" and a few other things, but on the whole we have it covered.
Will release a few more details on what's what once we have confirmed them on a car/ecu. There is also the issue of 2 different code types which have some maps in a different place.
Paul
#27
Thanks,
I do have the same configuration on my plug, so they must have the same type of protocol.
I do now that the Subaru scaner will fit all models.
So the question is, If it is not OBD what protocol Subaru uses??
Tato
I do have the same configuration on my plug, so they must have the same type of protocol.
I do now that the Subaru scaner will fit all models.
So the question is, If it is not OBD what protocol Subaru uses??
Tato
#29
Scooby Regular
Join Date: Jul 2000
Location: Lancashire
Posts: 2,209
Likes: 0
Received 0 Likes
on
0 Posts