Jump to content
SAU Community

Recommended Posts

Does anyone know when the ECU in skylines (specifically RB25DET) run in Closed loop lambda control mode, ie; adjusting the air fuel ratios based on O2 sensor readings. I have heard it only runs closed loof on cruise (after sufficient time at constant RPM), but I have also heard they run closed most of the time, only going into open loop on full throtle.

Thanks in advance.

Link to comment
https://www.sau.com.au/forums/topic/73982-closed-loop-lambda-control/
Share on other sites

The tuning on the factory ecu has the car in closed loop with anything below atmospheric pressure in the manifold.

i.e, it doesnt go out of closed loop and into open loop until you hit 0 vacuum or any positive pressure above that.

The only reason it would not be in closed loop under those conditions is if the sensor was stuffed or the engine had just been started. (It takes a few minuted for the O2 sensor to warm up)

They are pretty good, the design of the combustion chamber with good squish zones allow them to run closed loop/stoich ratios even under low manifold pressure. Alot of older cars will go into open loop when the manifold is still under vacuum.

I hope that all makes sense.

Taking note of the PFC I find the O2 sensor is in closed loop under light acceleration and cruise. It reacts very quickly, if you are within a closed loop enabled load point then you will be in closed loop.

The o2 sensor is disabled when you hit certian load points, nothing to do with manifold pressure/vac.

You should make those load points closed loop enabled as well.

If the factory ecu can run with stoich mixtures anything under 0 manifold vacuum the powerfc should as well.

Or alternatively, disable closed loop altogether and tune light load to leaner then stoich to pick up even more economy where possible.

SAFC is usually only used to lean out the open loop high load/boost areas. This is where you make your power gains, especially with the Nissan ECU's that run way rich under load.

If you change the AFM voltage in closed loop with the SAFC, the ecu will re-adjust the mixtures to 14.7:1. However the timing would have still changed because you changed the AFM voltage to the ecu with the SAFC.

I'm suprised they stay in closed loop that much. I'm getting about 12-13L/100km from a manual R33, maybe I should change the 02 sensor out of routined maintenance.

If it is running 14.7 most of the time I would think fuel consumption wouldn't be that bad. I guess it's got a lot to do with how often you put uyour foot into it also.

  • 1 month later...

I had my car run up on the dyno to check whether the O2 sensors were working on my GTR. I was interested in knowing when it was in closed loop, as that's where the best fuel economy should be.

Apparently the standard R32 GTR is in closed loop until around 3000 rpm if it is under light load (< 30% ?). Mine stays in closed loop until 4200 even under full load. His guess was that at 4200 rpm, my 80mm AFMs were putting out the same voltage as the standard AFMs did at around 3000 rpm.

The result is that I'm still in closed loop when I'm on 4 lb boost.

Does his suggestion sound reasonable?

Apparently its optimal to have the car run in closed loop up until around 30rwkw.

I think the PFC uses the fuel map to determine when to bump out of closed loop mode. Once the fuel map value goes over 1.047 or something. It may also have a little to do with the throttle position sensor.

I really have no idea, possibly its a little of both.

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


  • Similar Content

  • Latest Posts

    • First up, I wouldn't use PID straight up for boost control. There's also other control techniques that can be implemented. And as I said, and you keep missing the point. It's not the ONE thing, it's the wrapping it up together with everything else in the one system that starts to unravel the problem. It's why there are people who can work in a certain field as a generalist, IE a IT person, and then there are specialists. IE, an SQL database specialist. Sure the IT person can build and run a database, and it'll work, however theyll likely never be as good as a specialist.   So, as said, it's not as simple as you're thinking. And yes, there's a limit to the number of everything's in MCUs, and they run out far to freaking fast when you're designing a complex system, which means you have to make compromises. Add to that, you'll have a limited team working on it, so fixing / tweaking some features means some features are a higher priority than others. Add to that, someone might fix a problem around a certain unrelated feature, and that change due to other complexities in the system design, can now cause a new, unforseen bug in something else.   The whole thing is, as said, sometimes split systems can work as good, and if not better. Plus when there's no need to spend $4k on an all in one solution, to meet the needs of a $200 system, maybe don't just spout off things others have said / you've read. There's a lot of misinformation on the internet, including in translated service manuals, and data sheets. Going and doing, so that you know, is better than stating something you read. Stating something that has been read, is about as useful as an engineering graduate, as all they know is what they've read. And trust me, nearly every engineering graduate is useless in the real world. And add to that, if you don't know this stuff, and just have an opinion, maybe accept what people with experience are telling you as information, and don't keep reciting the exact same thing over and over in response.
    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
×
×
  • Create New...