Hey so I am having a problem here. I had a good running ecu with a p72 base running previously on my gsr. So i decided to do some tuning on it. I configured it so I could switch the O2 input from narrowband to wideband on my mtx-l wideband output. I switched the output to wideband directly to the O2 input and then now I got a solid cel. So I maybe I just learned the hard way that you cant wire it directly to the O2 input? **** I was just following someone elses instructions.

 

The stock O2 circuit on the ECU pin D14 will ony read between 0v and 3.8v. So if you have your MTX-1 and it sends out a 0-5v signal. Anything over 3.8v may cause it to throw a code.

Who ownes H-SPEED ECU? If you know them maybe they could help you out.

 

Then again when I send 5v to the stock O2 sensor input on my test ECU it doesn't throw a CEL code right away. I can see on my laptop (datalog) that the voltage stops at 3.8v but it doesn't throw a CEL right away. Maybe you should look over your wiring, you may have mixed something up.

 

Something is not adding up. I put the narrowband back on the input and I tried my stock p72 and it worked fine with no cel. I can see the gauge reading the a/f just fine. But Its like my chipped ecu is fried or something. The cel just comes on solid and wont turn off. I am totally confused right now

 

What sortware are you using to tune with? You should be able to see what the CEL is for if you have dataloging capabiities.

 

Im using Chrome & moates burn 2.
The CEL stays solid. I cannot read the code, when I jump it it stays on solid...

Ok I figured out something. I tried two more ecus and reburned 10 times and same result. Then I tried a chip I burned yesterday and no CEL. So its a software problem it seems. Or maybe my burn2 ?

 

Make sure you remove the check sum routine from the ROM (.bin) file in Crome before you burn it to the chip.

Crome/Plugins/Enhancements/Remove Check Sum Routine

 

Tried that and still not working. Should I remove that from the plugins?

lol just learned the basics of uberdata just now. Im using that for now until I get chrome working...

 

I got another unrelated question. I just chipped a p06 for the same car and had one small issue. I tried using the automatic hi side switch for vtec and when I drove the car it hit vtec for about a second then threw a cel for 21 vtec. Do I need to use a 5151 instead? Also I used to transistor from q28 in q26. hmm I dunno if I can do that...?

 

You only need a 5151 if you are using a AX2 board or a P75.

The transistor at q26 should be C144 if you are pulling it from a stock board.

 

oh ok I understand. Anyhow I am still have problems with chrome. I tried urberdata and it works fine so I know its chrome. Its def something to do with the checksum cause it is def going into limp mode. I tried uninstalling the plugin completely. I dunno what do

 

bump anyone know about what could cause chrome to have a checksum problem?

 

Its simple to disable the checksum Plugings>Enhancements>Remove Checksum Routine. Make sure you are burning the chip correctly and that you are verifying the rom file after burning.

Also, I've never seen using the O2 input throw a CEL when using the analog 0-5volt output from a wideband. It simply stops reading around 3.8volts. Make sure you are also configuring the MTX-L properly within settings to read the 0-3.8 volt input or your ECU / software will be completely off..

 

I was out on a trip for a week and I am just now getting back to this. So yeah I am still having the same problem. I tried removing the check sum from several saved rom files and also tried just burning completely stock rom with and without the check sum and It does the same thing no matter what. btw the wideband was not causing the CEL it was def something to do with chrome when I tried to enable data logging.

unrelated issue but also my mtx-L wideband is having problems all of the sudden. It is throwing codes for bad O2 sensor so I am gonna contact innovate and try to get a new sensor since the kit has less than 300 miles on it. nothing but problems lately

 

Aright well apparently I figured it out. I had to disable the fuel injection test circuit. I still don't fully understand why this is but now it works flawlessly. Had nothing to do with check sum.