Jump to content
SAU Community

Recommended Posts

Just trying to diagnose some possible running rich issues. After replacing my 02 sensor, my town economy increased slightly (down to 12.5-13L/100km) but my 96 stagea still was using 12.5l/100km on the freeway which seems odd. I figure its running rich since theres tailpipe soot, and the exhaust pops when you rev it in idle.

Now to the ECUtalk oddity: it has a overall trip litre/100km measurement which is always optimistic. eg if I used 12.5L/100km, as measured at the fuel pump, ecutalk will read 10L/100km.

So where is the fuel consumption measured from? Could this contribute to too much fuel being injected?

Link to comment
https://www.sau.com.au/forums/topic/363477-ecutalk-and-fuel-consumption/
Share on other sites

Ecutalk from my experience uses injector size and injector duty cycle to calculate fuel consumption.

As for consumption itself, get yourself a wideband AFR kit or borrow one. Will tell you how rich is it really running.

yeah ECUtalk calculates the fuel economy based off injector size and ecu mapping. if your economy is worse than the ecutalk is calculating then either the fuel pressure is higher, or the injectors are fouled (being fouled doesn't always mean it will be injecting less fuel. it can mean that is actually injecting more fuel as the injectors may not close properly, etc).

the other thing that may possibly be causing the oddity is that the odometer might not be working properly, so the KMs you are using for the calculation are actually more than what the ecu is reading (and what you are actually doing). if you, or someone you know, has a gps, use it to keep track on the distance you go between fill-ups (most will have trip logging. in the case of most Garmin ones, just tap the speed window on the map screen and you can reset trip totals from there).

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

    • 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. 
    • Holy hell! That is absolutely stunning! Great work!!!
    • It does when you start adding everything else in. But it's not just compute. It's the logic. Getting your timing right (I'm not meaning ignition timing for the engine). Making sure of your memory mappings, seeing your interrupts. Microcontroller devices only have so much capacity. For the most part, you want all those timers and interrupts in use on your engine control, which means you're left with less than ideal methods for timing and management of other control functions.   Let's put it this way, my job is all about building custom hardware, that goes into cars, and integrates with them. We're also waiting on a media confirmation from SpaceX too fora world first we've just completed with them in NZ too. It's not just the little toys I play with. But you know, you can think and believe what you want.
×
×
  • Create New...