not sure if i missed it but proper setup with maft/gm mass air?
or is this not advised?
Printable View
not sure if i missed it but proper setup with maft/gm mass air?
or is this not advised?
Finally having some fun with this. Put my ECU/patch harness in last night and it started and idled right away on the stock 99 ROM. Check Engine light on, but expected since my car has no OBD2 emissions equipment.
Went out to the car this morning and flashed Chrome 1.0.1 with the periphery2 table set appropriately (left periphery0,1,3 alone). That completed successfully and the car starts/runs. (I have not tested driveability yet.)
Now comes the fun.
Check Engine light is still on. I wanted to read the DTC to see what's going on. I cannot get EvoScan 2.6 to recognize my openport2 cable. "OpenPort2 USB Cable not responding. Try disconnecting/reconnecting blah blah blah." It is not even getting to the point of trying to read the ECU... the program can't talk to the cable.
The internet says to try uninstalling/reinstalling everything. Did that, no change.
If anyone has seen this before and can offer wisdom, please let me know.
Details:
Win7 x64
Programs installed to C:\ECUPrograms folder
Have tried EVOScan in XP SP3 compatibilty mode & run as administrator (makes no difference)
EVOScan 2.6 and ECUFlash 1.43
EVOScan connection settings - using defaults for baud/timeout. Openport2. MUT3 checkbox, and EFI is selected from dropdown.
Just did an uninstall / folder removal / reinstall and still not getting anywhere. Installed EVOScan first (tried connecting without ECUFlash installed, no luck), then installed ECUFlash again and still no change.
Thanks
James
Perhaps I am doing something stupid here? First time using any of this software...
Attachment 4341
Stopping on this for now, got other things to do with the car today. Hoping to have it together for a meet tomorrow. Really don't want to put the 91 ECU back in if I don't have to.
Really puzzling since I was able to connect with the OpenPort2 and flash the ECU but I can't get EVOScan to log it or read DTCs (or so much as connect to the openport2 cable...).
Code reading has been hit or miss from me. Starting and stopping the logger function and then reading DTC's has yielded the most successful results.
I can't even get it to log. The sceenshot above was taken after I hit the "start datalogger" button.
But trying to read DTCs using the button at the bottom gives a similar "openport2 usb cable not responding" error.
Frustrating.
Wish I had an older computer to try this on to narrow down variables. Everyhing I have here is win7x64 though. Thinking about installing xp mode...
Yes, it is under heading "Vehicle pass-through interfaces" - Tactrix Openport 2.0 J2534 Vehicle Interface
I was able to get the DTC through other means (remembered I have a BlackStealth LCD I am working on installing - took that outside and hooked it up temporarily.)
Throttle position sensor.
But I still have to figure out this EvoScan issue or I won't be able to log/tune it when more mods get piled on. :/
ok just hooked up my ecu with everything needed and trying to read the orignial file on the ecu it asks which mitsu were working with on the ecu flash
none of them work ...
but if i use evoscan it hooks up fine
what did i miss
saw the section on cant read /write to ecu nothing there
Kx
restarted the computer problem fixed
wanted to keep a copy of the sl file just in case i sold the ecu
now off to deal with all the check codes
p0155 02 heater b2s1
p0161 02 heater b2s2
P0135 02 heater b1s1
p0141 o2 heater b1s2
p0443 evap purge valve
p0446 evap vent malfunction
p1104 Turbocharger Wastegate Solenoid
p1105 Fuel Pressure Solenoid
so far all codes fixed
tried editing the ECU Periphery code for ver 1.0.1 but wont let me save the file keeps saying access denied
Kx