Jump to content
SAU Community

O2 Sensor Wiring With Powerfc/datalogit


edizio
 Share

Recommended Posts

I'd like to have a go at getting O2 closed loop feedback working with datalogit so I can get some stable fuel ratios off boost.

I don't have a fuel temperature sensor so on long journeys, it seems like I am getting some small fluctuations when temperatures change. That, I think, is the only explanation I have for my fuelling going slightly lean (0.5 AFR), on a long journey (150+ miles). I've checked air temperature, voltages, fuel pressure and all the corrections available to me to no avail. I've also raised before that I get a lean condition when turning air conditioning on which is annoying again; grounding all seems fine and voltage corrections seem fine. I've been investigating and found that from most tuners, you'll get these problems if you're running everything in open loop because there's just so many things that need correcting, i.e. a small rise in fuel temp changes the amount delivered.

I've got a regularly calibrated MTX-L wideband that I use for tuning which is plumbed into AN1-AN2 on datalogit. I've got O2 feedback turned off because I don't have any narrowband sensors on my car but I was thinking that I would be able to turn the MTX-L to provide output in lambda instead of AFR.

If I do this, where do I sort the wiring? is it basically wiring the wideband into the loom that goes into PowerFC? Datalogit just shows 0.005 for O2-1 and O2-2 constantly.

I would assume that once PFC sees the wideband putting out the voltages it expects for the O2 sensors, it shouldn't care whether it's a wideband or a narrowband and my AFR problems will go away. I can have the MTX-L display gadget just understand the voltages I tell it and to display the AFR accordingly so I shouldn't notice any visual changes.

Edited by edizio
Link to comment
Share on other sites

I don't know if the PFC has the capability to make the automatic corrections you are looking for.

If not you need one of these:

http://campaign.r20.constantcontact.com/render?ca=13724212-ccee-4b4a-9b30-b3988d06b7a7&c=0ff310d0-1d6f-11e3-b800-d4ae5275b546&ch=107f9960-1d6f-11e3-b805-d4ae5275b546

Link to comment
Share on other sites

The link ecu is the eventual plan however I have got a few jobs to do first that are more serious.

Powerfc does have o2 sensor feedback but not as detailed as the link. Ie, only one target value as opposed to idle/off boost etc.

Basically this is a wiring question. Pfc corrections are working great for less than a 100 mile journey but heat soak, lack of fuel temp corrections due to no fuel temp sensor, etc is just sending me a tad lean off boost.

Edited by edizio
Link to comment
Share on other sites

All you need is for your wideband controller to have a narrowband simulation output. Whatever those two terminals are get connected to the narrowband input on the ECU. Job done.

If your wideband controller doesn't have a narrowband simulation output, then you are shit out of luck. There is no way to wire it up otherwise.

Link to comment
Share on other sites

Im not to sure, and from what i see you cant have the power fc self tune the fuel. I use a AEM wide band with a 5v output i use that, and hook it up to my data logger then log the AFR's remember to calibrate the channel.

Thats about the only way i know to do it. Log then work out the correction, then input it.

I'm not sure of what a a narrow band simulation is. Sorry will google it though

Link to comment
Share on other sites

Im not to sure, and from what i see you cant have the power fc self tune the fuel. I use a AEM wide band with a 5v output i use that, and hook it up to my data logger then log the AFR's remember to calibrate the channel.

Thats about the only way i know to do it. Log then work out the correction, then input it.

I'm not sure of what a a narrow band simulation is. Sorry will google it though

Narrow band simulation is a feature on some wideband meters that sends a signal via another wire to the ecu that replicates the signal it would have got from the stock Lambda sensor to regulate idle and cruise afrs - that's what the OP was after. Fully automatic regulation of the AFRS is only possible on some newer ecus such as the Link that I linked above.

Link to comment
Share on other sites

I understand thanks for that KiwiRS4T. So no more need for a oem stock 02 sensor. Cleaner looking engine bay.:D Now that you mensioned it i wounder if thats what the green wire is for on my wide band. I never pay no attention to it.

Link ecu looks good mate.

Link to comment
Share on other sites

Hi guys,

Thanks for the posts! I've been out of town so haven't had access to my computer.

Simulating the narrowband from the MTX-L; I'll have a read up on it and see if I can wire it into the PFC, I think it's slot 29.

Regarding self tuning, that's not really what I'm after and when I get the Link ECU, I'll probably be using that but for now, I'm happy with the on boost fuel ratios, just a bit tired at having slightly rich or slightly lean AFRs on cruise and idle with the PFC as I have no O2 sensors.

Thanks!

Link to comment
Share on other sites

Looking into it, you guys are right, the MTX-L does have a narrowband output. I believe the PFC is expecting 2x inputs so I assume I can just wire it up in parallel?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share



  • Similar Content

  • Latest Posts

    • The two diagrams are equivalent. The R32 one is just one sheet out of about 3 showing everything in the whole car all at once. And without knowing the functionality that occurs in the modules, they are both equally opaque.
    • 8v - 2.48ms 9v - 2.15ms 10v - 1.74ms 11v - 1.41ms 12v - 1.15ms 13v - 0.99ms 14v - 0.89ms 15v - 0.82ms 16v - 0.81ms I'm running these values on my RB20 Neo with 570cc Denso R35 stock jets and it's great. Also bought a set for my Legnum VR4, love these injectors!
    • Thanks for your reply,  Those blue/green wires running to the actuator aren't attached to anything, so I'm not sure how the central locking is still working. I will have to take a good look tomorrow, I don't have the car with me. After googling it seems like a pretty common aftermarket actuator which even uses the same green/blue wires the immobiliser required. i'll test everything tomorrow and if it's working i'll melt the solder, strip it, resolder and neaten it all up with some heat shrink. I don't have to understand it if it works hahaha I just don't want a fire/ short circuit. That R32 diagram looks more like a continuity chart? Can you make sense of this form the R34 manual? 10V is probably due to very flat battery, i'll recheck as well tomorrow, I did have to jump start it haha. Thanks again!  
    • So, COM doesn't mean comms. It means common. What common itself means will depend on the type of device. For a two directional actuator (ie, one that can push and pull on the same output rod) then the common will typically just be the earth connection. There will be at least 2 other wires. If you put 12V on one of the other wires, then the actuator will push. On the other 12V wire, it will pull. Can't quite make out what is going on with the wiring of your actuator. It appears to have several wires at the actuator plug, but there only appears to be 2 wires where its loom approaches the door control module, with at least one of the others cut off. I don't know these actuators off by heart. I'd have to look at a wiring diagram for one before knowing what the wires were about, and that's despite me having to replace one in my car not all that long ago. Just not interesting enough to have dedicated memory set aside for trivia like that any more. That actuator is an aftermarket one, not the original one, which probably died and was replaced. That might require some sort of bodge job on wiring to make it work. Although nothing should justify the bodginess of the bodge job done. As to the soldering job on the door module's loom plug. Ahhahhahaha. Yes, very nasty. Again, I cant tell you what any of those wires do. You'd need to study the R34 wiring diagram (if you can find one that shows the door module). I don't think I have any. I'd have to study the R32 diagram to start to understand what mine is doing, and again, even though I've had a problem with mine for the last 25 years (where it locks the passenger door when the driver's window reaches top or bottom of travel) I'm just not interested enough to try to to work it out. So long as it's not burning down, it's fine with me. Here's the R32 GTR diagram, which, confusingly, has rear door lock actuators and window motors on it!! As you can see, unless you understand the functions of the door lock timer and the power window amplifier, you'll never be able to work out how it works just from the diagram. I don't imagine that the R34 one is any better. Hopefully an R34 aware bod can help. FWIW, the two wires that are cut and joined look like they are both power supply - so hopefully it is not fatal to join them. The 10V you measured on the cut off free end of one of them is concerning. You'd expect 12V, and it might be the reason for the bodge job joining them together.
×
×
  • Create New...