That's exactly what I'm getting in evoscan. It may be entirely possible that I've screwed up my evoscan settings since I was last working on the ecu. Merry Christmas (or your Holiday of choice) to you! Thank you guys for your help, especially with it being the holiday season. It's possible I screwed up or missed a periphery, but if so shouldn't I get a code related to that periphery? IE: second set of o2 sensors, egr system, etc?Ī missed periphery also doesn't explain the vehicle speed sensor code coming and going when the car is running, not moving, and the code not storing. However according to my readings I'm not getting any counts for knock sum. The car is a 91 TT, running a 98sl ecu, flashed with the stock chrome v2 rom (for TT), with the only changes to the rom being injector size, latencies, the peripheries indicated as required by the chrome ecu website, and CEL alert for knock enabled. Ok, I had a nice post typed up here, went to edit it for an autocorrect typo and the mobile version of this forum seems to think the "reason for editing" field and the "delete post" button are the same thing. I'm stumped at the moment and would appreciate any help. but if that were the case shouldn't I be getting a code for whatever one I screwed up? And that still wouldn't explain the code 24 not registering in the memory. I thought I had them all correct for a 91 TT using a 98SL ECU. I suppose it's entirely possible that the constant check engine light is a mis-set periphery. If I hit "read code" it might be there, then if I immediately read it again. Yet it doesn't? I checked multiple times with the car running and it seems that the code comes and goes. This is where things start getting fuzzy for me, as that code is supposed to store in memory from everything I've read. With the car running, I get a code 24 (vehicle speed sensor). Reading the codes with EvoScan (key ON engine OFF) I get no stored DTCs. ![]() To start viewing messages, select the forum that you want to visit from the selection below.Īfter discovering that my check engine light had burned out, and fixing it, I have a new problem. You may have to register before you can post CLICK HERE to register If this is your first visit, be sure to check out the FAQ by clicking the link above. The 3000GT / Stealth / GTO Mods and Tech support Some of the finest minds in the community use our forum and post here. The 3000GT / Stealth / GTO Classifieds The perfect place to find that part you need or sell the part you no longer need. The 3000GT / Stealth / GTO Garage Members Cars from across the world If you feel something is missing or have a suggestion that you think will help, please don't hesitate to send me a PM or post a comment in the suggestion forum. We should have all of the features you'd expect and maybe a few new things to use. ![]() If you are coming from another forum many things will seem similar many things will be different. I believe that a site with the members and the community as the focus can do the job better in the long run. ![]() The 3000GT / Stealth / GTO community needs a site that's focus is the support of the community and not to make money. While they may provide a stable platform if you look closely you'll see that the decisions they make are designed to make them money and keep you on the forum. These sites fail because they are not focused on serving the community they are focused on making money for their owners. Some of the major 3000GT / Stealth / GTO sites despite their size do not do a good job servicing the community. Welcome to, The enthusists site for the the Dodge Stealth, the Mitsubishi 300GT and the Mitsubishi GTO.Tuning, Engine electronics and ECU discussions.
0 Comments
Leave a Reply. |