Notices
ECU Flash

Flashing an Airtrek Turbo

Thread Tools
 
Search this Thread
 
Old Oct 7, 2017 | 05:43 AM
  #271  
VVV's Avatar
VVV
Newbie
 
Joined: May 2013
Posts: 28
Likes: 1
From: Moscow
Looks like most of the airtreks are now in Russia :-) I, myself, drive a 2.4l strokered Airtrek evey day now.
whats the trouble in connecting evoscan to ecu? Should be very simple.
Reply
Old Oct 7, 2017 | 05:48 AM
  #272  
VVV's Avatar
VVV
Newbie
 
Joined: May 2013
Posts: 28
Likes: 1
From: Moscow
The ecu is basically the same. Software differs - different maf size, injectors, turbo, etc.
​​
Reply
Old Oct 7, 2017 | 12:11 PM
  #273  
bradswims11's Avatar
Newbie
 
Joined: Apr 2014
Posts: 23
Likes: 1
From: Auckland, New Zealand
Sometimes connecting initially to the ecu can be tricky. I have used evoscan to download the tune before and then written the better 8070010 rom definition file onto my ecu from ecuflash. The standard files sometimes are really badly defined. I have my car manual converted, td06sl2r-20g turbo and custom water to air intercooler setup with way bigger fuelling system etc and the ecu still handle it fine. I plan on converting to the evo ecu and going to tephramod
Reply
Old Oct 8, 2017 | 11:47 AM
  #274  
poachersun's Avatar
Newbie
 
Joined: Feb 2012
Posts: 38
Likes: 0
From: New Zealand
It's been a while since i had my airtrek, but i initially had trouble with the evoscan cable second connection as the plug was different. I just re wired a different plug (male) into my airtrek so it could write.

Also need to change your write settings 7055 i believe (not 7052) as it's 512kb not 256kb.

I have a reasonable modded file somewhere, along with a reasonably good definition file for 8070010. I also had launch control on 8070010 with a evo 7 gt-a tune. I think people have used on airtrek but can be risky.

PM me if you want the def. file
Reply
Old Oct 8, 2017 | 06:09 PM
  #275  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
My understanding is that now all you need to do is use the newer Tactrix openecu 2.0 USB cable and mitsubishi adapter - using the other cables (1.3 etc) is the old way to do it? Also the Airtrek definitions are included in the latest open ecu software - there is no need to go hunting for the definitions...
Reply
Old Oct 8, 2017 | 08:04 PM
  #276  
Lasiorhinus's Avatar
Newbie
 
Joined: Nov 2012
Posts: 2
Likes: 0
From: Auckland
Interesting - I have the Openport 2.0 cable and the mitsubishi adapter plugs that certainly seem to fit quite well. I've tried reading the ECU both with and without the extra plug installed, neither seem to work.

What's the best software to use for this? ECUFlash just gives me errors.
Reply
Old Oct 9, 2017 | 05:40 AM
  #277  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
Originally Posted by Lasiorhinus
Interesting - I have the Openport 2.0 cable and the mitsubishi adapter plugs that certainly seem to fit quite well. I've tried reading the ECU both with and without the extra plug installed, neither seem to work.

What's the best software to use for this? ECUFlash just gives me errors.
Just re-read what i wrote above - going by the first post in this thread some modifications were needed to write but you should be reading the rom fine (with the 2.0 cable).. I havnt got my kit yet but will chime in when i do.
Reply
Old Oct 9, 2017 | 12:02 PM
  #278  
poachersun's Avatar
Newbie
 
Joined: Feb 2012
Posts: 38
Likes: 0
From: New Zealand
Like i said you need to change the read file from SH7052 to SH7055

I actually had to use evo 8 style read as mine was 2003, 2002 seemed to use older model.

1.3u evoscan cable is fine and worked for me, taxtrix is pretty good / better.

The Def. file i has was pretty full on with launch control, gear pressure and speed adjustments for the auto, lots of various timing maps and scenarios. Maybe it is included with ecuflash these days?
Reply
Old Oct 11, 2017 | 12:40 AM
  #279  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
Originally Posted by poachersun
Like i said you need to change the read file from SH7052 to SH7055

I actually had to use evo 8 style read as mine was 2003, 2002 seemed to use older model.

1.3u evoscan cable is fine and worked for me, taxtrix is pretty good / better.

The Def. file i has was pretty full on with launch control, gear pressure and speed adjustments for the auto, lots of various timing maps and scenarios. Maybe it is included with ecuflash these days?
ok so based on what you and others have said i will get the 1.3u - seems that requires no modification to read / write unlike the newer 2.0.. and based on the year of my car that is what evoscan recommends. I spoke briefly with GregM and he also stated that the new Ecuflash has his definitions worked in..
Reply
Old Oct 11, 2017 | 11:43 AM
  #280  
poachersun's Avatar
Newbie
 
Joined: Feb 2012
Posts: 38
Likes: 0
From: New Zealand
You should be fine with either. I only purchased the 1.3U because it was cheaper. I never used a tatrix 2.0 on my airtrek or evo 7 GT-A. I did later on wish i purchased the Tatrix, because i had to purchase one for my Mazda 3 MPS. Would have saved me the trouble.

If the connectors plug in correctly, and you have adjusted the read file for reading 512kb data - she will work great!

If you are thinking about future cars etc Tatrix is the way to go.

Hopefully this helps, i am sleep deprived so lost my track of thought.......
Reply
Old Oct 12, 2017 | 05:18 AM
  #281  
C00LM4N's Avatar
Newbie
 
Joined: Sep 2011
Posts: 42
Likes: 2
From: Moscow
Both 1.3 and 2.0 are fine.
Change mitsukernel to mitsukernelocp or vice versa if it does not read/write (in both read template and rom definition xml files).
Boot pin must be plugged.
2.0 requires latest ecuflash and tactrix drivers (comes with evoscan, for ex).
Reply
Old Oct 12, 2017 | 12:16 PM
  #282  
poachersun's Avatar
Newbie
 
Joined: Feb 2012
Posts: 38
Likes: 0
From: New Zealand
Originally Posted by C00LM4N
Both 1.3 and 2.0 are fine.
Change mitsukernel to mitsukernelocp or vice versa if it does not read/write (in both read template and rom definition xml files).
Boot pin must be plugged.
2.0 requires latest ecuflash and tactrix drivers (comes with evoscan, for ex).
Ahh yes Mitsukernelcop - i had to do that as well! Brings back memories!
Reply
Old Oct 29, 2017 | 05:34 AM
  #283  
OzAirtrek's Avatar
Evolving Member
 
Joined: Oct 2017
Posts: 108
Likes: 11
From: Perth, Australia
Has anyone here replaced the stock fuel pump with a Walbro 255?

I assume the install is very similar to an EVO as described in this guide.. I guess i am just concerned about fitment compared to the stock pump.
Reply
Old Oct 30, 2017 | 12:24 PM
  #284  
poachersun's Avatar
Newbie
 
Joined: Feb 2012
Posts: 38
Likes: 0
From: New Zealand
Originally Posted by OzAirtrek
Has anyone here replaced the stock fuel pump with a Walbro 255?

I assume the install is very similar to an EVO as described in this guide.. I guess i am just concerned about fitment compared to the stock pump.
Yep it was pretty straight forward. Use gloves and be very careful of the parts. The first one i did i must have touched or tweaked the sensor / plastic air weight/ballcock. As it never quite read correctly afterwards.

Also there is a slight tweak i think the height was slightly tall on the walbro 255 into airtrek compared to evo, but it manages to fit
Reply
Old Oct 30, 2017 | 12:47 PM
  #285  
bradswims11's Avatar
Newbie
 
Joined: Apr 2014
Posts: 23
Likes: 1
From: Auckland, New Zealand
The walbro pump will fit fine with a little trimming of the bottom rubber spacer on the filter assembly in the tank that it sits in. I would recommend going for a deatschwerks dw200 though as they operate silently compared with the walbro. With this setup you wont over run the stock fuel regulator but will give you a little more fuel pressure up top if you're really leaning on it. I run a dw300 fuel pump but I also completely aftermarket fuelling setup to allow me to do that
Reply



All times are GMT -7. The time now is 03:37 PM.