Turbo.Tim

I just installed the Link ECU in my 2003 Evo GSR (US). This is the first start up after a new motor install. When I start and run the car the in cluster temp guage never moves. But in the link software I can see the temp sensor is working. Before I start the car the temp matches the IAT sensor. After running the car for 5 mins I can see the temp change in the PC link software. But the needle never moves on the cluster. I am using AN temp 1 with Std Bosch NTC. Does the cluster use a different sensor than the ECU?

Thanks for your help. I swapped out one of the relays and Switching the pins was issue. My pump is now priming!

Ok I swapped the pins as suggested. I then changed the aux function from Fuel pump to "Test (ON)" and nothing happened. I did it for the AC and I hear a click from the engine bay. I tested the Boost and I can hear that clicking.

Thank you Adam. I will try to swap those and test it today. I did have an immobilizer. Is there a way to just test the fuel? Meaning a way to just force it to prime? I see I can test injectors. I tried turning the key off and on but its hard to tell.

I have the 4 plug. the starter spins but the motor will not catch and there is no pressure at the fuel rail. I have an external fuel pressure regulator with a mechanical gauge and it reads 0. I also dont hear the fuel pump prime with the key on. I am using the Mitsubishi EVO 4-8 PCB V1.5+ G4+ Xtreme Plugin map.

Hello, I just installed a new 2.2 motor in my Evo 8 and I am trying to start the car for the first time. The car would not turn over. I checked the fuel pump regulator and it is reading 0 psi. When i turn the key off and on I do not hear the pump prime. I have an aem uego wired into Lambda 1 on volt 9. Is there something that i have to do regarding the immobilizer? Do i need to add the vin?

Sorry I originally used a different laptop that had G4+. That would explain why i could not connect with the new laptop. Now I really feel like a noob

What I mean is I flashed the firmware on the ECU and added a map. I did it using the G4X software. It is a new build and the motor has never been fired up so I am not sure if it works. I am hoping it is not possible to install wrong firmware and brick it or something.

That sounds promising! Looks like I have aux 10. Thank you for the quick response. When I flashed the car I used the G4X software. Would I get an error if I tried to flash a G4+? Is the software backwards compatable?

Hello, I purchased an Evo 8 Link ECU from someone over a year ago and was just attempting to install it. I was originally told that it is the G4X so when I flashed the software I used the G4X software. But when I opened it up to install an expansion loom it looks like it is labeled EVO8+. How can i confirm what ECU I have and which software to use. Is the G4X software backwards compatible? I was told that this did E throttle. Is it compatible?

I am able to connect to the same com port with the surface pro. I did not see USB as an option. I tried different usb ports as well

I recently picked up a Link g4x Evo plug in ecu. I am able to connect with my surface pro but I am not able to connect using my laptop. See the error message attached. I verified that the driver is installed and using the same com port. Running out of ideas.

Hello, I am new to Link. I just picked up a Link G4+ plug and play for my 2003 Evo 8. I was previously tuned on open source. With my open source tune I was able to log ARF using my AEM wideband that was wired directly into the rear 02. When I try to configure Lambda 1 or 2 I see analog 1-12. Am I able to select where it is currently wired or will I need to move it to the expansion loom? Also how do i ensure Lambda 1 is the front 02?

I had a similar issue. When i open up the software it was really slow on my laptop. I have a very new laptop so this shouldn't happen. Going between menus was painful. I decided to open the app as admin and it was much quicker. I suspect since it needs to interact with the drivers it needs to be elevated. So what you can do is browse to the exe and right click and choose properties. Under Compatibility select run this program as an administrator