i've been using ATF+4 valvoline full synthetic ATF fluid ever since i had the tt-engine swap. as usual, my fluid looked nearly mint as it was being flushed out.
i'd like to know if anyone has any practical, hands-on experience using both of these brands--or has some empirical evidence comparing the two (google doesn't appear to have anything). i'm mainly curious because my gut instinct is to stick with magnafine; however, the wix was about $5 cheaper. i PAMPER THE HELL out of my car during maintenance...because i want to "run it" without worry. obviously, i'll take the best available. perhaps, that isn't either of the two i've listed. if so, what else do you recommend?
the filter is an inline 5/16" nipple size. ]]>
It's got both timing maps, both fuel maps, injector scaling, injector latency, redline, and MAF size. Note that this definition file only works with the 1999 3000GT VR4 ROM with an ID of 238606. I don't have a lot of time to do a full on ECU Flash / ROM editing tutorial right now. Rather than assuming what you guys do or don't know, go ahead and throw the questions out there and I'll do my best to answer.
Don't worry if you think they're 'noob' questions. This is some pretty crazy stuff with a lot of mixed info out there, and it's new material for a lot of people, so I'll try to take it easy. Hopefully the mods will go easy on this thread too ;)
Anyway, the ROM and definition file are posted below. Download ECUFlash from here Main Page - OpenECU (it's free)
XML/Definition file: http://www.xtreme3s.net/ECU/23860006.xml
99 VR4 238606 file: http://www.xtreme3s.net/ECU/99TT.bin
Save the ROM file anywhere you like. Open up windows explorer, go to Program Files\OpenECU\ECUFlash\rommetadata and create a folder called 3000GT. Save the XML file into that folder.
Launch ECUFlash and then open the ROM file. It should find the definition file and open the ROM.
I've got files for other 98 and 99 3000GTs, but I'm trying to keep this as simple as possible for the moment.
Couple important notes:
If you don't have a 98 or 99 3000GT, this does you no good. That said, the ROM file I posted is for a 99 VR4, but all three 98 and 99 models are flashable. I have a couple different revisions of the 99 VR4 ROM, one each for the 99 base and SL, and a 98 SL ROM.
If you do not have an OpenPort 2.0 adapter, you won't be reflashing your car. OpenPort 1.x devices CANNOT work. They are physically incapable of outputting the tight tolerance reflash voltages that the 98-99 ECUs require. 01+ ECUs are more tolerant of voltage fluctuations. ]]>
Quote:
|
Originally Posted by 87 Turbo
(Post 1448812)
Well I been reading up on a 3000GT VR4 built and the owner is using a Ford GT fuel pump for his built, here what he said:
 Yes, I know we are all familiar with this car but we MAY not all be familiar with how this baby runs. The car employs two fuel pumps which are conveniently dubbed "Ford GT pumps". The interesting thing about these are how powerful they actually are. With the 3/S community, the weapon of choice when it comes to fuel pumps is usually the Walbro 255LPH followed in second by the more expensive Denso Supra Pump. The Walbro as advertised flows 255lph for about $100 and the Supra pump flows about 277lph for about $200. Just ONE of the Ford GT Pumps are said to flow over 400LPH and support over 600rwhp on some Domestic V8 applications. However, recent testing has shown that the flow number is actually closer to 350-370lph. Maybe that doesn't sound like such a big deal to you but it does to me...especially seeing that one can be had for around $80 Brand New! The fuel pumps are about the size of the Walbro 255 and it looks like it is configured in a way that major accommodations will not need to be made. This is the fuel pump that I will run on my setup with a hotwire kit. We will see how it performs and how easy it is to run with our stock fuel setup. Once again, just a single one has supported the fuel needs for 600rwhp mustangs so it should be plenty for my build. For $80 it doesn't look like you can go wrong! NOW, the question is it true? I search and came up with not much to said. Can any one verify it? If so where can we get one? I pretty sure the dealer would cost more than $80. |
Quote:
|
Originally Posted by 87 Turbo
(Post 1448834)
Well here a flow chart for it... I think it legit but where to buy one is the question.
 Here a pix of it.... Look kinda small compare to a HKS 380LPh and others out there.  |
if this has been touched on..please let me know i can delete, or if mods want to delete.. ]]>
First, let's discuss what this thread is NOT about.
If you do not have either a 1998 or 1999 3000GT (all models) then this thread is not about you. Period. The sole exception to this is if you have an older car and either have swapped, or want to swap, a newer ECU into it.
If you fall into that category, please do not ask about how to do such a swap. Come back after you've actually got it up and running.
If you want a canned how-to, then don't bother reading any further. This thread is for people who want to learn and take an active role in developing these solutions. If you're the kind of person who's intimidated by "wall of text" or you like to post "tl;dr" then please, go away.
If you just want to wait on the sidelines for the cool stuff to happen, that's your choice. But please do not post in this thread if that's the case.
=================================
So, what's been done so far?
The Tactrix OpenPort 2.0 logging/programming adapter is currently the ONLY hardware on the market that will allow you to program a 98 or 99 3S with your own changes. There MAY be some other packages that'll let your reprogram your car, but they generally don't support the 3000GT, nor do they allow you to write your own changes. They rely on 'canned' tunes or 'licensed' shops.
OpenPort 1.x adapters DO NOT WORK. This is a HARDWARE limitation. They cannot provide stable reflash voltages as required by the 98-99 ECU and cannot be modified to do so.
I have personally reprogrammed 98 SL and 99 VR4 ECUs on a test bench at home, and I also programmed Hans Ertl's 98 SL with a lower rev limiter in the hotel parking lot at NG09.
I have ROM files on hand for all three 99 models, and also for the 98 SL.
What I do NOt have are complete definition files. I haven't had nearly as much time as I'd like to work on disassembling the 98-99 software. What I do have are basic definitions. With these, you can reprogram your fuel and timing maps, replace your MAF with an Evo MAF (for instance) and re-scale your fuel injectors.
Think of it like an SAFC without all the drawbacks (check engine lights, advanced ignition timing, etc)
There is still a TON of development and testing to be done. I cannot (and will not) do it alone. I'll share what I have, and try to help jump start it, but if you guys want this YOU will need to take a more active role in making it happen.
So read up on what's possible. Start with the OpenECU wiki (All articles - OpenECU) Educate yourself. Ask specific questions. If I know the answer, I'll do my best to share it. If I don't know, I'll try to point you in the right direction. If it's obvious you haven't done your homework, then I'll probably just ignore you ;)
With all that said, let's open this up to questions. Please be specific. ]]>
This will work on ANY Mitsubishi with a 16-pin diagnostic port and MUT-III logging protocol support. This has NOTHING to do with OBD2. It's pretty much any Mitsu-based car from 1994 until 2007-ish.
(If you've got friends with Subarus, this will work on most of their cars too)
Now, let's get a few things out of the way before the questions start rolling in. PLEASE read this before you dig into the thread.
I have an older OpenPort 1.x adapter.
Good choice in cables, but this thread ONLY applies to the OpenPort 2.0.
I have a 91-93 3S. Does this apply to me?
No. Your car has neither the necessary connector nor the correct logging protocol (Mitsu's prior to 94 had MUT-II logging)
I have a 94-97 3S. What can I do?
You can log your car with this. Keep reading.
I have a 98-99 3S. What can I do?
You can log your car AND you can reflash your ECU. More on that later.
=============================================
Ok, now that that's out of the way....here's a quick summary.
Purchase an OpenPort 2 adapter from Tactrix.com
Purchase a compatible Micro SD card from anywhere. Don't waste your time with anything over 2GB. 2GB is enough space to store logs for pretty much the lifetime of your car
Set up a log configuration file on the SD card
Plug the adapter into your car, and it'll automatically connect to the ECU, and when it sees data that match the conditions you set in your config file, it'll start logging data to the card. When the "stop" conditions are met, it'll stop logging.
When you're done, take your OpenPort 2 back to your PC, download the .csv (comma separated values) files into a decent text editor, MS Excel, or your log analysis software of choice.
Tactrix is talking about adding a log analysis interface into their ECUFlash software, but it's only being talked about at this point. It is not even in beta, so don't hold your breath for it.
If you want to see the numbers while you're driving, you'll still need a laptop and a copy of EvoScan ($25)
I've been testing this for a couple weeks on my 94 Stealth TT. It works great, and I don't even have the most recent revision of the software.
Links:
Tactrix: tactrix
Logging config details: openecu.org • View topic - Openport Stand-Alone Logging Beta
Oh, and that reflash thing for the 98-99 cars. The OpenPort 2 is currently the ONLY adapter that will allow end-user (IE YOU) to program your own 3000GT. You can COMPLETELY re-write your ECU. But to do that, we need people to get on board with buying the adapters, and CONTRIBUTING to the task of analyzing how the ECU software works so we know exactly what to reprogram.
The DSM guys (as usual) have already done some legwork here. But there's still a lot of 3S specific work that needs to be done. I am not going to do it by myself. I don't even own a 98-99 car. People need to get involved instead of waiting for someone else to take all the risks and spell everything out in a handy how-to document!
So what are the downsides? There pretty much are none. The only one I can think of off the top of my head is that some of the logging parameters in EvoScan and the Tactrix sample configs are flat out WRONG for older cars like ours. It's very easy to fix them and I have most of the definitions for how to do so. But I'm not going to go to the trouble of writing it up unless people start getting involved and contributing back into the knowledge base.
I will help whenever I can, but I haven't got the time to do all the legwork myself.
As I said earlier, people need to start stepping up and taking a far more active role in this development. There's precious few of us who are doing so, and some like myself are really getting burned out. The knowledge is out there. But it's not going to be handed to you on a platter.
If you want it, come and get it :) ]]>