Arnoud

PM sent to John.

Vilhuer

John, if you have ready made harness available for wide band sensor and TechEdge I'm also interested. I have couple of setups which have 2J1 controller and I think they can be updated to use 4.9 sensor. If you don't mind Arnound we could save on shipping costs by geting one package.

John Speake

Thanks Erkka. It a 5 way termianl block and has the correct 3 pin plug to fit stright into the existing LH O2 cableform to pick up power and a way to feed simulated NBO2 from the WB unit back into the LH.

It also has a flying stereo lead for the WB signal to plug into the SharkTuner.

dprantl

Well, it was simply because I got a very good deal on a brand new stock 928 nbO2 and my X-pipe has two bungs. There really is no other reason.

Dan
'91 928GT S/C 475hp/460lb.ft

Hilton

Yes I have John's Techedge harness - works a treat. I'm currently using it in my '87 along with NBsim as I've got an emissions test to get through. (Techedge 3A2 with LSU 4.2 sensor).

Speedtoys

This is where I am at now, Im off by just over a full point (reading 15.xx instead of 14.xx, etc) in the sharktuner on my Techedge 3x unit.

Techedge's www page isnt horribly clear..on how to update the tables you mention here.

But..it looks like its just a firmware update.

Need to go see what O2 sensor I have in the car tomorrow AM.

simos

Agree with speedtoys, the product is great but webpage horrible.

When you go to WBUtil ReFlash page, you need to unmark the code only box. Otherwise you only update the code but not data. Both(code/data) are in same .HFX file and needs to match to used Techedge unit and sensor. http://wbo2.com/sw/hxf.htm


If one replaces the LSU 4.2 with 4.9, pls. note that 4.9 lead has different style connector and you need to replace the connector from existing extension cable, to match it to 4.9 cable plug.
The partnumber for connector kit(terminals & seals) is CNK17025 and for the plug itself PLG17025. The LSU 4.9 Techedge partnumber is 017123 (Bosch 0 258 017 123). Check also the needed cable lengths, they are different on 4.2 and 4.9 sensors. http://wbo2.com/cable/connkit.htm

More about new LSU 4.9
http://www.ecotrons.com/Bosch%20LSU%...20sensors.html

If you don't have Sharktuner in hand, you can use TEWEBLOG software to test the functionality of sensor and Techedge unit. You need to configure the AFR display to match your sensor. LSU 4.2 = version 1.5 and 4.9 = version 2.0. http://www.devtechnics.com/tewblog.htm

Arnoud

Thanks Simos, for the additional sharing on this subject - good practical info for us all to have.

Vilhuer

Nyt käsket Simo ton muijan heti veke tosta valkosen etupelliltä. Eihän toi ole edes sun lintta. Olkoon mikä anorektikko vaan niin alumiini menee länään.

simos

Just a reply to Erkka's mail....

Vielä mitä, sehän on täys ikänen

Speedtoys

Just verified im up to date on firmware, and set to 4.2 sensor...etc..etc

I still read 15.7 when the car should be delivering 14.7.


Idle, anywhere, I did pass smog ok, but..for ****s and grins, what should the WB read at idle?

Jim Morton

Jeff:

Getting the output correct is more than doing the firmware. You need to upload the correct calibration tables for your particular sensor and make sure the correct calibration curve is used for each of the individual WBO2 outputs.

It is somewhat obscure that you can use any of the WBO2 outputs for any output calibration despite how it is hard labled on the box. As example, when I want to use NBSim and use my large LED display as well as feed an output to my dyno, I need to be very careful that I confirm each output channel vs. the selected calibration before I do the flash. In short, make sure all output channels are as you wish for claibration and output boundary (AFR 9.0 at "x" volts vs. AFR 19.0 at "y" volts, etc.), before you flash.

Speedtoys

We should visitn when I get back from Haifa.

Im also sick as **** of this vbrrraaation that is everywhere, but peaks out at 3k.

jcorenman

14.7 (that is, hunting up and down a few tenths as the LH tweaks fuel up and down in response to the NBO2 sensor reading, but averaging around 14.7).

Assuming you are running a separate NBO2 sensor, and assuming that you are seeing the 15.7 (average) on Sharktuner, then the cause for this could be one (or more) of the following:

1) A difference in range for the Techedge analog output versus ST2's analog input. The default output range for the Techedge is 0-5v representing AFR of 9-19. The input range for the ST2 is set by the "WBO2 law" window, and must be the same. (The default is the same AFR 9-19, so you should be OK there-- but check it).

2) Incorrect "free air" calibration for the WBO2 sensor, i.e. a long time ago (should be done every few months), or it wasn't calibrated in "free air".

3) A wonky WBO2 sensor, or wonky NBO2 sensor. Try changing one, or the other, and see if it changes. (Don't forget a new free-air cal for a different WBO2 sensor). NBO2 sensors don't require calibration, but they do need replacing occasionally-- some say every 60K miles or so.

4) A ground problem. The Techedge has an optional differential WBO2 output, which means it will compensate for a ground loop and voltage on the ground connection-- IF the "WBlin(-)" wire is properly connected to the shield (signal ground) for the ST2's WBO2-input, and the internal jumper is removed (see the Techedge website). I believe that the jumper is removed, and the ST2 pigtail wired correctly, on the Techedge you have-- but check it. (In any event a separate, solid chassis ground for the WBO2 is highly recommended).

And back on topic, I think this is the best argument for using separate NBO2 and WBO2 sensors: If there is only one sensor, how are you going to know if something is out of cal?

Cheers

Hilton

Thanks Jim for this brief bit of info.

Since switching to the wbo2 harness supplied with the ST2 and making use for the first time of NBsim (part of making my setup portable between cars), I've got a suspected signal noise issue (CO monitored via an exhaust gas analyser is jumping all over the place under constant load/throttle), and now suspect its signal noise.

Just to confirm my understanding of your comment above - should I be wiring a separate ground wire direct from the chassis to WBlin- as a reference for the WBO2 signal voltage (and making sure the shunt jumper is off)? I need to open up the controller and check the shunt's default state, and also check the LSU 4.9 jumper is there (my sensor is also a suspect in the readings - so will probably buy a 4.9 one too)

edit: Just saw your follow-up post above - pretty much covers the options. I'll explore the wiring this weekend and see if I can get more consistent readings on the car with the NBsim (compared to the other car which is non-cat and uses the CO potentiometer setup).