Getting started with Chrome. n00b questions.

[Chris@Rvengeperformance]

Have you logged the thing? What does the TPS read at idle and driving around. You can pretty well test the TPS with the engine off and just work the pedal to make sure evoscan has a smooth up ramp on the signal.

[Chris@Rvengeperformance]

I can't remember all the test conditions for the TPS but one of them is if the sensor reads no voltage while the RPMs are increasing. A quick log will show if the sensor is working. You don't even need the engine to be running. Just turn on be ignition and check the TPS ID.

Thing is though, not all OBD2 readers are created equal. You mentioned that you haven't even plugged in the tactrix so that tells me you haven't flashed the ECU with the correct periphery setup. I wouldn't be surprised if there is nothing wrong with the TPS and CEL is on for a bunch of OBD2 faults which your scan tool isn't reading correctly.

yeah and haven't some of the OBD2 and or mut requests moved around? Could break an off the shelf logger.

[fast_eddie_72]

Thank you - that's what I needed to know. I may have gotten the wrong impression from the vendor. I thought the unit came with everything taken care of for an otherwise stock car. But to be honest, when I read more about the peripheries, I thought that might not be the case. If they need to change, then that is almost certainly the problem. All I've done is plug the box in.

I think I have enough understanding to make those simple changes. Periphery 2 - 15, 14, 13, 11, 10, 9, 3 and 1 to off. I'll see if I can manage that. If I run into a problem I'll report back.

Thank you for the help so far. This is something basic, but I'm really at the very beginning stages of all this. I've read a lot and watched some videos. I'm sure I can do it at least at this really basic level.

(edit) I haven't logged anything. I was trying to do that last night but couldn't get Evoscan to connect. I assume it's the 2.0 cable driver issue that I asked about above. The directions that came with the ECU say "you can now use any OBD2 reader".

[Chris@Rvengeperformance]

I guess the ecu vendors are trying to limit their liability, but they should at least give you a basic setup sheet with the ecu about what peripheries you should change for your year car if they intend on selling these as a plug and play replacement of stock ecus.

It makes no sense these days to get a rebuilt non flash ecu, so I can understand why some people want flashable and the newer better hardware, but don't necessarily want to learn to tune.

[fast_eddie_72]

That's me exactly. I just wanted an ECU that worked and didn't want to buy a factory ECU that would have the same cap problem. This seemed like the best solution. I still think it may be, but I have to figure out enough of this to make it work. I tried plugging in the Tactrix cable but can't get it to connect. I uninstalled ECUFlash and downloaded it from the Tactrix site as someone suggested above. I'm hoping it's that driver issue. I'm headed back out to the car now. Wish me luck.

[fast_eddie_72]

Okay, well, I think I've made some progress. But not quite there. I think I'm stuck here.

"Extract the 23862006.XML fileto:
C:\***File Folder you installed EcuFlash***\EcuFlash\rommetadata\mitsubishi"

If I put that .xml in that folder, EcuFlash won't work. It says "EcuFlash could not recognize this ROM image using any of the current definitions." If I take take that .xml out of the Mitsubishi folder, I can open the ROM. But when I tell it to read form the ECU, I get the "J2534 error [no data was read]"

EvoScan seems to work now, except I have no idea where the file actually goes.

[Greg E]

The XML is just the map of the .bin file you read and write from the ECU. ECUFlash uses the XML to map out all the tables and information in the tables. This has nothing to do with the actual flashing. Just opening the file on your PC so you can edit it.

[fast_eddie_72]

I can't seem to find a solution to the J2534 error. It is seeing something. At the bottom of EcuFlash, it says 1999 Mitsubishi 3000GT VR4. So it's getting that much. (Oh. Duh. It's getting that from the ROM I have open). It feels like I'm just doing something wrong.

[fast_eddie_72]

Hum. I think maybe I'm having an issue because my laptop is Windows 8 and I'm not extracting files correctly. Investigating. Going to run out of time on this today, but I do feel like I made some baby steps. At lest the cable is working. Thanks.

The XML is just the map of the .bin file you read and write from the ECU. ECUFlash uses the XML to map out all the tables and information in the tables. This has nothing to do with the actual flashing. Just opening the file on your PC so you can edit it.

Or maybe not. Oh well. I can open and edit the .bin in EcuFlash. So I guess that's working okay.

[fast_eddie_72]

(edit-again) It does look like I have EvoScan working correctly.