On the old firmware and software version I had my A/F ratio displayed in analog input 2 (Trim J14) and closed loop worked great. It also made for a nice A/F ratio display beside my fuel map for tuning. Now closed loop control does not work. Neither does autotune.

Now my fuel setup says to pick either the wideband 02 sensor on analog input 1 (Not even sure I have an analog input 1 no settings for this one) or pick wideband 02 sensor on 02 sensor input.

So I tried to hooking it up the wideband to the 02 sensor input and it displays a/f ratio's on the engine data page but datalogs in MV!! WTF.

Also when I hit home now on the fuel text map it always goes to the highest vacuum point in that rpm range!!

So whats the deal here?

How are you guys monitoring and logging a/f ratio's??

 

Spare a/d 2 has worked for me. Sounds like something got botched when the firmware was updated.

 

So I guess I should redo my firmware update again.
So hooked up to your spare a/d closed loop works as well as autotune?

Thanks for the reply.

 

Not sure on the closed loop o2 or autotune. I've used neither. The display works fine though.

 

I have my WBO2 on the O2 input. It shows up as that though I don't believe my closed loop is working. Haven't tried the autotune yet.

One issue I have that you have is the datalogs still show mv instead of afr that's shown on the gauge page. Anyone know what's going on there.

 

I'm in contact with Haltech AUZ. Via email. No outcome yet. The only thing so far is that the home button on fuel map text mode will be fixed. (Later update?) You should email them as well so that they know I am not the only one with this wideband issue.


They did tell me to hook up to A/D1. But I don't have anything saying what wire a/d1 is and its grayed out in the program.

Can anybody tell me where this analog digital input 1 is?

 

AD1 is the O2 Input on the E8.

 

Update:


Redid my firmware update. Closed loop control now works again under A/D2.

Autotune still does not. And if it only works with A/D1 then that input is grayed out in my software.

Haltech AUZ is looking at this issue. Other then autotune not working for me all is well

Ian

 

AD1 is not used on the E8 which is why its greyed out. It is considered the O2 input instead of the AD1.

 

Hey guys,

On a side note, both V1.71 and V1.89 are capable of handling multiple wideband O2 sensors, using any or all analog inputs (spare a/d's) set to wideband O2, the catch is that they all have to be the same brand and model since there's only one calibration option in the software which would serve for all the inputs. The other catch is that if you intend on running closed loop or target AFR (v1.89 only) the signal has to come in either on analog 1 or 2.

Have a look at the screenshot with all the O2 sensors through using all 7 analog inputs on an E11v2, there would only be 4 on an E8.

One other thing is that on v1.71, the datalog displays only mV or Lambda, but on 1.89 it does display AFR when configured as such.

 

I hope all those widebands aren't in the same exhaust stream!!

 

Hehe, no, this was done on a simulator board, each window is reading an individual 0-5v signal, hehe, just pretend its 7 individual sensors connected in different places.

So, if you have an E11v2, and you want to monitor all the exhaust streams of a 3 rotor, or a 6 cyl., just get your self as many widebands as you need, keeping in mind that they have to be the same model/brand.

 

^^^ do you know what the cost would be of a sensor setup that could hold up in a preturbo position on a rotary?

 

Is that a retorical or a trick question?

 

No, I know that the bosch's limit is about 1400 F and the ntk is about 1600 or so. With preturbo temps in the ~1700F area what manufacturers sensor could/would/does give lasting reliability.

 

The problem I have is that the A/D1 input when having an innovative wideband connected to it does not log in A/F ratio's. It actually datalogs in MV's. And not the proper mv's either. It does display proper a/f rations no the screen. Just not on laptop and ecu datalogging. I didn't bother trying if the autotune works.

So I still have my a/d2 connected to the wideband for datalogging purposes and have no autotune available.

Thanks for the good info.

Ian

 

I have the same problems with the WBO2 on AD1 in my E8. The logs show up in I believe a narrow band O2 output voltage. Don't know how or why its converted that way but it makes the logs basically worthless. I don't understand why they didn't just log to the AFR value or lambda value depending on what you display on your gauge page its there just log it. I do have O2 feedback working with custom RPM's but I do believe they have to have the same scale in all the maps or it won't work. Again it seems like there should be a better way to change the rpm scale than to go into every map. Especially if it has to be the same. I wonder if the software guys know about these issues. Do you know Claudio?

 

Guys, 1.89 does log in AFR correctly, on the screen, in the CSV file and displayed in the Haltech datalog viewer or in excel. I have verified this.

 

Ok. It may very work now for me but I have not bothered to try again. The first update to the firm ware 1.89 I moved my wideband from a/d2 to a/d1. It displayed correctly on the laptop but did not datalog correctly. Closed loop did not work. Only reason I moved to a/d1 was because I thought that is wy autotune did not work.

Attempted another firmware update and closed loop worked but I moved the wideband back to a/d2. Did not bother to see if a/d1 datalogged properly. And I will not bother again since my ecu and connectors is under the carpet where the stock ecu was

 

I have logs showing it not working but displaying correct on the gauge page and the display. Could it be when you use the Wideband on the o2 input only?

 

I have mine on A/D 2 and everything works fine. I have mine set to petrol numbers.

 

Mine works flawlessly in the datalogs but will not show up on the gage page

 

Spare A/D's done show on the Gauge Page, only on the Analog Inputs Data Page, and of course in the datalog, you may be right, O2 input may only monitor mV i will do a test.

 

Yes, the O2 sensor input will not read in AFR on the datalogs, only mV, and i get the feeling that when doing any sort of closed loop or target AFR, you will need to use Spare A/D 1 or 2.

 

Apparently on the e8 Spare a/d1 is the o2 input.