Author Topic: Flashing 1999/2000 ECU's (Read 7411 times)

Isaurio · « **Reply #125 on:** September 04, 2011, 10:11:18 AM »

Do you want a stock map log. Or what i have now? My low trim is on the 12.

SPD_FRK · « **Reply #126 on:** September 04, 2011, 10:33:12 AM »

Send me a stock log file if you have it, and then what you have now

mysticj · « **Reply #127 on:** September 04, 2011, 12:41:10 PM »

The 3GKT, GSX/GST, & 2G Diamante runs the same MAS just different part numbers. Yes it rated like the 399/482 but once you remove the honeycomb, you will see all restricted it is. The 011 MAS is pretty much like the 501 MAS.

foxbrand · « **Reply #128 on:** September 04, 2011, 01:45:02 PM »

^I can confirm that as well
the #609 MAF that the 2g 3000gt (all models) appears identical to the #338 MAF, I can tell you this from seeing the two side by side myself

mrg7243 · « **Reply #129 on:** September 23, 2011, 07:55:24 PM »

Just a few quick questions can someone give me definitions for each of the words so I can better understand the tuning "lingo" I am trying to understand is

Rom-

Definition file-

XML-

Maps-

Isaurio · « **Reply #130 on:** September 23, 2011, 10:39:43 PM »

Umm.

Rom. Is known as read only memory. Is a set of empty boxes to store things. The code is not deleted if you take the power off, unlike the RAM, Ramdon access memory, it only store memory or instruction as long there is power. Power is gone information is gone. In programing you store instructions in form of codes. In our pcm and ecu is store as hex code 0-f.

Definition is another word we use for ecuflash situation. Is the xml code with the right memory location withing the ROM.

XML is a translator. Is main use on web pages to use a code and traslated for something we could read and see. "understand". Easy calculation for the computer. Ecuflash uses the xml as a guide or translator so we could read and understand. Hex code to decimal numbers with some math involved on it. -_- The code could looked like hex FF and xml with ecuflash looks like 255 in decimal number.

Maps is a set of translated codes to something we could see. Is like a map=guide. We could see the instruction of the pcm or ecu uses to calculate some number for a giving value. is a set of tables with values so we could look and change a giving value. Ecuflash with the xml definition is possible and easy to see and change a code. Hex. Oct or binary numbers.

mrg7243 · « **Reply #131 on:** October 14, 2011, 08:12:07 PM »

Thanks Isaurio makes sense now.

Alright now here is my issue I am getting the J2534 error timeout when I try to read my ECU in ECUflash. Does anyone have any insight on this. SPD FRK is going to look at it tommorrow but I just want to see if anyone had and solved this issue. Here is the log sheet.

SPD_FRK · « **Reply #132 on:** October 14, 2011, 09:31:31 PM »

Like I told Matt tonight, Marc and I have never run into this issue on any of the vehicles we have flashed. The original owner of that cable ("silvertune" on club3g) had same issue with his car and was never able to get the cable to work. Given what I know currently I am led to believe this is likely a cable issue causing the error.

mrg7243 · « **Reply #133 on:** October 14, 2011, 11:07:57 PM »

You are not allowed to view links. Register or Login

Like I told Matt tonight, Marc and I have never run into this issue on any of the vehicles we have flashed. The original owner of that cable ("silvertune" on club3g) had same issue with his car and was never able to get the cable to work. Given what I know currently I am led to believe this is likely a cable issue causing the error.

Yeah I am thinking it is somewhere between the ob2 and the reflash connector. I have been talking with Isuario tonight and trying to work through it. But nothing. Lets see tommorrow.

SPD_FRK · « **Reply #134 on:** October 15, 2011, 11:40:18 AM »

Sitting here in Matt's car now.

Just tried reading his ROM file, ECUFlash was prompted to update firmware (something I have never seen this thing do before with the multiple flashes I have done). Still get a J2534 error message.

Am able to log via EvoScan and display and delete DTCs, but this cable for some reason will not read the ECU. I know my version of EcuFlash is golden and everything else as I have read/flashed a number of vehicles with it already, including Bj's locked 2000 ECU I was able to pull the ROM file but not edit it and flash back to the ECU. Matt's car I can't even pull the ROM file from the ECU.

Isaurio · « **Reply #135 on:** October 17, 2011, 06:56:58 AM »

It sounds that is the mitsu flash connector. If you get evoscan reading the ODBII is good, meaning the tactrix should be ok. He should try another connector or check the flash connector under the dash.

SPD_FRK · « **Reply #136 on:** October 17, 2011, 12:37:47 PM »

The thing is people have wired their flash connectors directly to the ECMs and had same issues. I am waiting to see what Matt gets from Tactrix on the matter because the J2534 protocol error is a communication issue with the ECM reading/writing/flashing ability. The reflash connector isn't damaged or pinned wrong when I looked at it and it makes contact.

The other factor is Marc and I both have never seen ECUFlash do the firmware update when trying to read the ECM, the drivers are already installed in EcuFlash and were proven to work previously with Marc's Tactrix cable on multiple vehicles without ever doing the update we saw with Matt's cable.

Datalogging is simply monitoring the data off the ECU from the individual data link connectors on the OBD port, there is no communication necessary with the ECU because you are simply monitoring the data being spit out from the ECU, essentially like installing a temp, oil, or wideband gauge...you are just monitoring.

Isaurio · « **Reply #137 on:** October 17, 2011, 02:16:35 PM »

This is DION cable. we where getting that code. and my conclusion was that the actual flash cable not having connection with the female jack. I wrap a thin wire around the male plug and put some tape on it. problem solved.

SPD_FRK · « **Reply #138 on:** October 17, 2011, 06:30:44 PM »

That is wierd man, the J2534 error means it cannot communicate with the ECU protocols. If the reflash connector is not hooked up, EcuFlash doesn't recognize an ECU, nor will it give you the pop up window to select make/model of the vehicle you are working on.

Isaurio · « **Reply #139 on:** October 17, 2011, 07:29:38 PM »

Not always true. The signal could be there but not 100%. You have input and output for it. The flash connector it just to short out the pcm to accept new rewrites. I think thats how it roles i could be wrong im a noob to this.

SPD_FRK · « **Reply #140 on:** October 17, 2011, 07:35:14 PM »

Well the 1.43 version Marc and I are running, if there is not a 100% connection EcuFlash won't even recognize an ECU at all. The other kicker is that many other reports of the very same issues have been made and documented with several different attempts and approaches to a resolution, including;

Uninstall/Reinstall drivers
Uninstall/Reinstall EcuFlash
Wire Reflash connector straight to ECU
Use XP/Vista/Window 7 OS

All of these have resulted in the same failure code (J2534 Error). The real kicker is why the cable is updating any sort of firmware on EcuFlash when a newer production cable did not and worked without issues.

Isaurio · « **Reply #141 on:** October 17, 2011, 08:25:17 PM »

Not sure about the update. So did you used your laptop matt "SPD" and have the same error.

SPD_FRK · « **Reply #142 on:** October 17, 2011, 08:30:43 PM »

Yea, used my laptop on it.

Isaurio · « **Reply #143 on:** October 17, 2011, 08:41:17 PM »

The only thing left is testing with a new set of cables.

SPD_FRK · « **Reply #144 on:** October 17, 2011, 08:55:56 PM »

Yea, we were going to try Marc's cable but didn't hear back from him in time Saturday to check.

mrg7243 · « **Reply #145 on:** October 28, 2011, 02:31:41 PM »

Okay well Isuario and Matt both know, but want to let the community know incase of the same thing happening. But after a long set of emails back and forth from me and tactrix they finally agreed for me to send it in for repairs. Just got an email back today stating that the issue was with the OP2 and it was ir-repairable so they are sending me a whole new set of cables, OP2, and Re-flash connector.

So for future reference if you get this error and stuff get on the horn with tactrix and have them repair or replace dont wait.

Its in the mail so I cant wait to get it in.

Isaurio · « **Reply #146 on:** October 28, 2011, 08:12:57 PM »

Nice. Good thing u getting that fixed.

mrg7243 · « **Reply #147 on:** November 04, 2011, 07:51:23 PM »

You are not allowed to view links. Register or Login

Nice. Good thing u getting that fixed.

Yeap

So I am pleased to announce that I was able to pull the Rom off the ecu. Now I just need a deff file and I will be ready to go.

Isaurio · « **Reply #148 on:** November 04, 2011, 09:28:31 PM »

Great news. I will hook u up with your own unique xml for you rom. Keep up the good work. Keep us posted. So it was the cable aftet all. Lol i told you.

mrg7243 · « **Reply #149 on:** November 04, 2011, 10:17:26 PM »

You are not allowed to view links. Register or Login

Great news. I will hook u up with your own unique xml for you rom. Keep up the good work. Keep us posted. So it was the cable aftet all. Lol i told you.

cool thanks again. Yeap tactrix did pull another stunt but I can take care of that later. But thanks god for wifi sitting here datalogging right now haha