Notices
ECU Flash

Flashing an Airtrek Turbo

Thread Tools
 
Search this Thread
 
Old Oct 31, 2017 | 03:20 AM
  #286  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
Thanks guys - i bought a DW 200... seems pretty straight forward. will report back !
Reply
Old Nov 1, 2017 | 05:26 AM
  #287  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
Ok! So i got the 1.3U yesterday and today got it connected. It needed the 2nd connector modified (green wire to the tactrix reflash cable using bullet clamp) before i could read anything. Once that was done it did read the ECU.

However the only option under ''select vehicle type' in ecuflash that uses the sh7055 '512'kb' memory module also uses 'mitsukernalocp'... so after reading the ecu it is telling me i have a 2005 model as this combo is used for the 2005 definition (i have a 2003). The definition for the 2005 is no where near as complete as the 2002 defiinition (no AT options etc).

So how can i set the read method to be 'SH7055' and 'mitsukernal' as all the other options that use mitsukernal are only 256kb?
Reply
Old Nov 2, 2017 | 03:50 AM
  #288  
WytWun's Avatar
Newbie
 
Joined: May 2010
Posts: 51
Likes: 6
From: Canberra, Australia
You will need to create a custom read template file. You can find others by searching but you can also create one by going into the "read templates" subdirectory with ECUFlash's metadata directory and copying the read_evo7.xml file (call the copy something like read_airtrek.xml). Then edit the copied file to change the ROM size and vehicle name.
Reply
Old Nov 2, 2017 | 06:18 AM
  #289  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
Originally Posted by WytWun
You will need to create a custom read template file. You can find others by searching but you can also create one by going into the "read templates" subdirectory with ECUFlash's metadata directory and copying the read_evo7.xml file (call the copy something like read_airtrek.xml). Then edit the copied file to change the ROM size and vehicle name.
Aha! i knew there must be a way - thanks for that!
Reply
Old Nov 3, 2017 | 03:48 PM
  #290  
limaynard's Avatar
Thread Starter
Evolving Member
 
Joined: Nov 2012
Posts: 282
Likes: 4
From: Sydney
Originally Posted by OzAirtrek
Aha! i knew there must be a way - thanks for that!
I may still have all of the files, let me check.
Reply
Old Nov 4, 2017 | 01:39 AM
  #291  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
Originally Posted by limaynard
I may still have all of the files, let me check.
That would be great thanks! Did you have the 2 byte logging working in the MUT table? Im trying to get my head around that but i know i dont have the values anywhere (and they don't seem to be in the 2 byte thread).

I go the DW 200 fuel pump installed yesterday - not quite a drop in replacement. The pump itself is the right size (the electrical connectors need a simple modification). However the fuel pump carrier assembly is quite different to the evo. Still seems to be working fine
Reply
Old Nov 4, 2017 | 10:38 AM
  #292  
bradswims11's Avatar
Newbie
 
Joined: Apr 2014
Posts: 23
Likes: 1
From: Auckland, New Zealand
I could send you my tune which is the most defined 80070010 file. I will have to go through and adjust all of the values and table back to stock though as I am manual converted and run a TD06SL2R-20G on my car so everything is fairly modified from stock values haha. If you save and download your original tune and then load on this tune over the top of it it will give you everything you need in terms of 512kb file size, ultra defined trans maps and the 2byte load as well. I got it off a guy in nz who had a very fast airtrek and it has been golden for me. Drop your email below and I can also send you the read file as well in case you don't have it
Reply
Old Nov 4, 2017 | 04:23 PM
  #293  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
Originally Posted by bradswims11
I could send you my tune which is the most defined 80070010 file. I will have to go through and adjust all of the values and table back to stock though as I am manual converted and run a TD06SL2R-20G on my car so everything is fairly modified from stock values haha. If you save and download your original tune and then load on this tune over the top of it it will give you everything you need in terms of 512kb file size, ultra defined trans maps and the 2byte load as well. I got it off a guy in nz who had a very fast airtrek and it has been golden for me. Drop your email below and I can also send you the read file as well in case you don't have it
Brilliant! - PM sent
Reply
Old Nov 4, 2017 | 06:50 PM
  #294  
limaynard's Avatar
Thread Starter
Evolving Member
 
Joined: Nov 2012
Posts: 282
Likes: 4
From: Sydney
Originally Posted by OzAirtrek
That would be great thanks! Did you have the 2 byte logging working in the MUT table? Im trying to get my head around that but i know i dont have the values anywhere (and they don't seem to be in the 2 byte thread).

I go the DW 200 fuel pump installed yesterday - not quite a drop in replacement. The pump itself is the right size (the electrical connectors need a simple modification). However the fuel pump carrier assembly is quite different to the evo. Still seems to be working fine
I had the same problem with pump. Never got 2 byte logging working.

I am running a scan on a corrupt disk trying to find the files. I let all of my stuff go when i sold the Airtrek in 2014...
Reply
Old Nov 19, 2017 | 03:54 AM
  #295  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
Power cut issues

Hey all,

So im having an issue where my AIrtrek is just totally dying under load. To me it feels like a fuel cut. For example pulling away from lights or just accelerating and the power will just totally drop mid rpm as if i had taken my foot of the pedal. Take my foot off and put it back on and usually seems fine. The strange thing is its not at all regular, i could drive all week and it never happen.

Any ideas on the cause? My thoughts are it is the ecu cutting fuel or a dirty filter (is there another fuel filter in the engine bay?) The fuel pump is new so that's not the issue and until it happens the car drives smooth and as per normal.

Could excessive knock cause it? i noticed on a log im getting 6 or 7 knock under load about 4500 rpm. Im using 98 RON so i found this surprising...
Reply
Old Nov 20, 2017 | 04:37 PM
  #296  
limaynard's Avatar
Thread Starter
Evolving Member
 
Joined: Nov 2012
Posts: 282
Likes: 4
From: Sydney
I would check the stepper motor. Not a big job. Mine went and it would do the same thing.
Reply
Old Nov 20, 2017 | 04:39 PM
  #297  
limaynard's Avatar
Thread Starter
Evolving Member
 
Joined: Nov 2012
Posts: 282
Likes: 4
From: Sydney
You can get them online.
Reply
Old Nov 21, 2017 | 04:32 AM
  #298  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
Originally Posted by limaynard
I would check the stepper motor. Not a big job. Mine went and it would do the same thing.
Thanks i will try that. I would have thought that the idle control wouldnt effect it under load (3000rpm) but it has had a low idle every now and again..


Did you also have idle symptoms?
Reply
Old Nov 21, 2017 | 01:37 PM
  #299  
limaynard's Avatar
Thread Starter
Evolving Member
 
Joined: Nov 2012
Posts: 282
Likes: 4
From: Sydney
Originally Posted by OzAirtrek
Thanks i will try that. I would have thought that the idle control wouldnt effect it under load (3000rpm) but it has had a low idle every now and again..


Did you also have idle symptoms?
Yes, it would try to stall at low revs but it would die (sometimes) when i tried to accelerate. It finally went when driving through a national park and I had to call NRMA. He had no clue but after spraying WD40 down the intake it started and I got home. I decided to take stepper motor out (IACV) and there was a small bit of plastic broken.
Reply
Old Dec 7, 2017 | 12:54 AM
  #300  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
Ok so after a lot of reading (and advice from other members here - thank you) it seems my best option is to be getting rid of the 89970017 rom and flashing the 89970010 so i have all the definitions working (just coping the defs wasnt working as the axis memory addresses are wrong).

Has anyone here flashed from 017 to 010? Others seem to have done it..

what should the read method be? (010 is mitsukernal and 017 is mitsukernalocp). Id love to hear someone'else has done the same exact version change - i really dont want to brick the ECU! haha
Reply



All times are GMT -7. The time now is 03:55 AM.