MembersPage/EricN/WBSensor (2006-03-16 04:43:08)

MembersPage/EricN/BuildNotes

Started setting up my WBO2, as per the[manual]

Adjusting "pump zero pw" dutycycle

  1. In MegaTune, under settings then under wideband settings, changed the Pump zero pw (wbo2_pump_pw_zero) to try and get pump+ to pump- = appr 0 Volt. I was getting absolutely no change at all, it was originally set at 102 and read 0.4v. I finally realized that after adjusting and saving the value to EEPROM (mcs) ECM reset (eg. BootLoader flash-checksum test, or power down/than up) needed (or trigger or force WBO2 on with mde02 than off with mde00) so the new value actually gets used. Ended up at 101 (0x65) made 0.1v. Type Mcd in terminal program, got wbo2_pump_pw_zero=65. Perfect!
  2. Took me an hour to figure that out, next step will have to wait till another day.
  3. Couldn't wait, on to the next section: (this is also pump testing!)
  4. Readings (with a stolen config.txt) were
According to the[manual] that is wrong, so I adjust it. No lcd yet so doing it through MegaTune, kind of a pain actually. Setting the wbo2_nernstdc_target did not do much of anything, and I had to restart my board every time for changes to take effect. Set it to 0x96 and went on to adjust wbo2_pump_pid_ki. I noticed that they did not multiply to 0x4000 so I adjusted wbo2_pump_pid_ki to 7C and now I get
  1. Played with the rest of the settings. This is the final outcome again (I think)

wbo2_warmup_ramp=32 # 0x32 is extremely low, use 0xA0..0xFF

wbo2_abs_limit=E4 # try to increase a bit, eg. 0xF0

wbo2_limit_maxt=A0 # try to increase to 0xFF

wbo2_fallback=60 # try to increase to 0x80

It's not a good idea to apply high ego_rich_limit. If there is misfire, the O2 in the exhaust will result in more fuel, which will make the problem worse. Tune richer (with req_fuel, or j[] table), so the ego takes away 5..15% fuel normally. Reasonable to set ego_lean_limit up to 25%, but keep ego_rich_limit low, preferrably max +5..+8%.


I decided to double check my readings with a good multimeter with a battery that wasnt dead. All my readings went up a little bit. I am able to adjust voltage between ground and nernst and the voltage between nernst (pin1) and pump- and nernst (pin1) and pump- (pin 5)to spec but no matter what I do, measure the voltage between ground and pump- (pin 5)is always 4.01v. I can screw the readings up on the other 2 but I always get 4.01v on that 1. When I first issue the mde02 command, before the O2 readings start showing, nernst (pin1) and pump- (pin 5) is like .14v, the other 2 read 4.01. Just for kicks, I pulled the resister off of pin 5 and checked the voltage, it was 4.01. Is 4.01v ok or is there something I am missing?


After not hearing anything about the above readings, I assumed they are ok. I changed from the above config to marcells new wb config just to see if I could get the readings any closer. I have v3.2 with firmware 18. Unfortunately, no difference so I left it at that. With everything now attached to the vehicle, when I try and do my free air calibration, when I issue the mde02 command, I end up triggering the input trigger and running at 3000rpm.

This is most certainly bad ground problem. Redo the ground connections, with many thick GND5 connections (and GND and flyback are also a must, of course). Make sure the onboard bridge between GND and GND5 is cut.

Injectors are clicking away and I assume the coils are too. I ran out of daylight trying to figure it out. Is this normal too??? The only thing I can think of is this, I used sheilded wire for the o2 sensor and the sheilding goes to the same ground as the input trigger. I have yet to disconnect the sheild to try it. Is that a possible cause??? My new config is [here]

PROBLEM SOLVED

The wiring I used was from a Honda. The vr sensor wiring had a sheild on both wires. I disconnected the shield from the vr- wire and all is fine.

Oops, not really, hit the brake, injectors click and some coils fire, big flames out of throttle body. Completely removed wire harness, changed around all the grounds, re-routed some wires, cleaned up all the grounds on the truck, hook it all up with all the sheilds in place, it works good now.


NEW PROBLEM

I issue mde02 and it takes about a minute for the sensor to start its readout. When I start the truck, I assume that should also trigger the 02 to work. The heater comes on just like typing mde02 but I never get a readout of the AFR. I have to type mde02 to get it to finally work. Any thoughts??

ANSWER:

THe wbo2 can be manually started through Manmde02bye command but you will not get a reading in megatune (i assume you mean this when saying 'a readout of the afr') unless you issue a bye after enabling manually. Also when you start the engine, wbo2 is started automatically (that means no manual intervention is needed, it can be handy when tuning afterstart enrichment or low temp warmup enrichement though, which are usually over before wbo2 is heated up)

STILL HAVE THE PROBLEM

I am using the keyboard plugged into vems to type mde02 so I do get a reading in megatune or on the lcd that way. If I just try and start the truck without typing mde02, I never get any afr readings. I do have the heater turn on though, it just does not seem to warm up enough to work. I have only waited for about 5 minutes for the readings to show up, should I wait longer??

If wiring is OK, it's likely a misconfiguration.

The rampup was definitely way too low. Also, measure supply voltage, and take a snapshot of the relevant LCD page that has Ri and nernst (via RS232: Manmlp04 or so, than mll).

FIXED

I am not sure if this is the cause, but I changed out the spark plugs because the truck was only running on 1 cyl, literally. Started truck without typing mde02, heater comes on, and about a minute later, o2 starts to read.