I have my NGK AFX hooked up today, hopefully someone is familiar with that.

My NGk controller reads accurately, but the signal to ms 3.0.3 is acting strange. While reving and going from rich areas to lean areas accoding to the NGK controller, the ms reads 12.30 until I hit a really lean spot like about 15.00, then the afr gauge in the ms shoots up to the max and comes down to 12.3 when I go rich again and stays there and doesnt fluxuate with the controller.

I rewire the whole ms, everything is working good, except this. I wired the power to my power block activated with ignition on the main relay. Grounded the two black grounds on the Ground block that the ms and sensor ground. The battery grounds to this too. There is also a ground from the ground block to the engine. I ran the yellow NGK analog signal to the O2 wire on the DIY harness. And Grounded the NGK signal ground to the same ground as the controller (ms ground) as the instructions said to do.

This is the only thing NGK said would cause issues. But the controller works well, and the ms is seriously wrong. My lag factor is 40 and settings are set to "Other Wideband". I didnt see anywhere in 3.0.3 to set a parameters for lamda, because mine has a range of 9:1-16:1.

 

I think I found it in tools/calibrate afr... Ill try that

 

I had the same problem with mine. Right now my problem is it doesn't move from 13.5 afr at all. Hope you find a fix cause I tried everything I could think of and I still come up empty.

 

I got mine working. Probably easier than yours. My fix was as simple as going to--- tools/ calibrate afr table, then selecting the appropriate wideband. In previous versions I had, there was no selection for my NGK wideband. Now there is. And I had previously overlooked this menu because I thought it was related to EGO which I dont use. But there is an area on that same menu in tools/ calibrate afr table, where you can enter custom ranges, which is what I thought I had to do because of previous versions not having a preset for the NGK.

Of course this is all with MSII release 3.0.3s I believe. And Im using tunerstudio. Not sure if you are using that version, because the previous versions were different.

I guess I was confused before, because in "project properties"/ settings-- You select your O2 type. Bam! Thought I was done. Wrong.

Hope I helped

 

Well I'm glad you have it running correctly. I haven't had any luck though. I too am running the same release (3.0.3s) but haven't been able to get it to work.

 

Ok.
Did you set up settings in project properties for wideband?

Do you use the same project each time you hookup or do you use Temp project?

Did you do the TOOLS/ CALIBRATE AFR TABLE--- To match your wideband?

Note: Once you do the calibrate afr table, and burn, it is burned to the ecu and doesnt need to be done again unless you reflash or something.

What Wideband are you using?

Not trying to undermind you, just trying to get the whole story to see if I can help.

 

Well I'm using the AEM UEGO wideband system and to answer your question about the burn in afr tools yes I did time and time again and it still reads only 13.5 afrs and no offense taken. I really appreciate the consideration and time taken to help diagnos. It use to work fine but after I installed Jean's P&H board for the injectors (which works excellent and recommended for anyone building a 'Squirt) it stopped working. I replaced the circuit components for wideband circuit on V3.0 board and still the same thing. It kind of sucks not having it work on the laptop to help aid in tuning.

 

Yikes! Sounds like an issue for Ken, or someone more familiar with the Jeans board. I dont use it and dont know much about it or where it connects to the main board. Sounds like the installation of that board has interfered with something, and I dont know enough about it.

 

Have you double checked the O2 circuit for faults? Do you have a jimstim? Does it work on there?

Have you tried measuring the actual voltage on the wire that you're connecting to the MS's O2 input?

Ken

 

I did measure the voltage to the input of the V3.0 board and it seems to be reading ok. The O2 signal on the jimstim seems to not read correctly. Not sure why but can't seem to figure this one out.

 

What firmware are you using?

Earlier firmware revisions wouldn't display the AFR until the engine was running, and then only in closed-loop mode.

Ken

 

In the old versions the gauge would kinda grey-out wouldnt it... I think if I wasnt running or cranking, mine used to show 16.00.

 

I'm actually using the 3.0.3t firmware. It was working fine just before I modded the injector circuit to the jbperf injector board. Everything looks good on the V3.0 board. R10,R11, and C10 all look good. I'm really stuck here can't figure out why it's doing this.

 

If you did a modification to the board, and then O2 input stopped working, then most likely you shorted or otherwise damaged something while doing it. The fact that you don't get AFR change when connected to the jimstim also points this direction.

The trick now is to figure out which component(s) in the O2 circuit are damaged.

Ken

 

Ok well according the V3.0 board build there are only 3 O2 components (R10, R11, and C10). I checked for voltage and/or voltage change and the only one I'm not seeing any voltage change is the R10. It ohms out correctly at 1K but still no voltage. It's at 0V.

Could not using the V3.0 main board for VR1 signal and using both LM1815 cause the afr's not to read?