logic

iTrader: (2)

1g: http://www.dsmlink.com/images/forums/1GECUPinout.pdf
VIII: http://evoecu.logic.net/wiki/USDM_VIII_ECU_Pinout

It looks like DSM pin 6 is airflow sensor reset on the '91+ ECU, or idle switch on the '90.

Pin 14 should be the idle switch on a '91+, airflow sensor reset on '90.

So, assuming your GVR4's wiring is in the '91+ style (my apologies, I don't know the GVR4 well at all), you'll want to put DSM pin 6 to Evo pin 19, and DSM pin 14 goes nowhere. Reverse that if you have '90-style wiring (which seems to be what most folks here have; bunch of pop-up lovers here ).

Broxma

iTrader: (14)

For some odd reason, not related to voltage, my ECU locked at the second attempt to flash the new MAF settings. I grabbed the Aktivmatrix program to unlock it and it was fine. I am still yet to figure out the MAF Added setting since my map does not have one.

I am using ROMID 9417(?) I think, basically the initial map I pulled off my Evo. I haven't installed my WBo2 yet but the car runs very well, gets into boost and seems relatively happy with things. My current issue is the car dies coming out of throttle however I believe that to be mechanical since it did the same thing with the 1G ECU.

I am going to create a second 91+ pin out tomorrow once I get back from my geology final. It's not that different but people get confused so I'd like to avoid that if possible.

/brox

OZ Rally

iTrader: (15)

Thanks for the help guys. Harness is all finished, now it's time to wait for some free days to get it all installed.

eyebrowski

Are you guys noticing timing curves similar to the stock ECU or does it like Evo style timing?

Jack_of_Trades

iTrader: (17)

In the cruise section I had great results with the stock Evo mapping but anything higher than 100 load will totally depend on the turbo/engine configuration.

Broxma

iTrader: (14)

I think the timing curves are very compression dependent. My setup with the Evo pistons is running fantastic on a stock Evo map. I would think the stock block 1G could take more timing up top with the lower compression and could probably use less down low to help with spool, but that's just my initial thoughts. I'd have to have one in front of me and tune on it for a bit to find out. I'm still working on a few bugs in the system right now before I will have a chance to start flashing maps but once I get something I like I'll gladly post it.

/brox

Ceddy

Here is the 1G Timing map, EcuFlash style, if anyone needs it.
With the Load axis figured out.

BlackMage

Well I got my OpenPort 2.0 connector, finished my harness, installed everything. And now the only thing that works between EcuFlash and EvoScan is EvoScan in generic OBD II mode. Everything else causes EvoScan to lock up and EcuFlash won't "respond."

eyebrowski

I am having trouble writing/reading to the ECU for the first time.

-EcuFlash is connecting to the open port 2.0 cable
-OBDII port is wired up per diagram on pg 11
-OBDI port pin has been moved per the diagram on pg 11
-Battery is fully charged
-I can not register on ActiveMatrix to download the ECU unlocker for some reason, so I have no idea if the ECU is locked

I am getting error:
[19:10:45.998] J2534 API Version: 04.04
[19:10:45.998] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[19:10:45.998] Device Firmware Version: 1.07.2597
[19:10:49.373] sending init sequence 1 (0001)
[19:10:49.574] interface close

I have double checked my pin out wiring. Schematic I used:
https://docs.google.com/fileview?id=...M2FiZjYy&hl=en

Any ideas?

VETTE_50_TH

iTrader: (5)

Make sure the obd2 port is getting proper power with the op2 cable in. Mine was only getting 4.35 v with it in and 12 with it out. Might want to check that out.

eyebrowski

I had low voltage at the OBDII port, I ran a temporary line directly to the battery.

I am now getting:
[20:17:37.907] J2534 API Version: 04.04
[20:17:37.907] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[20:17:37.907] Device Firmware Version: 1.07.2597
[20:17:40.992] sending init sequence 1 (0001)
[20:17:44.306] sending init sequence 1 (0003)
[20:17:47.621] sending init sequence 1 (FFFF)
[20:17:50.365] no response to any known code
[20:17:50.365] interface close

VETTE_50_TH

iTrader: (5)

Hmm. I would try the unlocker then. It looks like its trying to communicate but it cant. There is an unlocker on here. I think its only the .1 version though.

eyebrowski

Does anyone have a copy of the unlocker they can email me? eyebrowski@gmail.com

VETTE_50_TH

iTrader: (5)

Its in this thread.

https://www.evolutionm.net/forums/ec...ocked-out.html

eyebrowski

Does the unlocker need to match the version of EcuFlash?

Unlocker states: "launch ECUFlash 1.28" and I am running ECUFlash 1.42

Anyways, with the version of ECU unlocker you linked to I get one line of closer, I am now getting:

[20:31:54.970] J2534 API Version: 04.04
[20:31:54.970] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[20:31:54.970] Device Firmware Version: 1.07.2597
[20:31:56.722] sending init sequence 1 (0001)
[20:32:00.007] sending init sequence 1 (0003)
[20:32:03.282] sending init sequence 1 (FFFF)
[20:32:06.556] sending init sequence 1 (F0F0)
[20:32:09.290] no response to any known code
[20:32:09.290] interface close