I was driving around yesterday tuning my new motor when I realized that I don't know how to tune past 7940. I was shifting all day at 8k, oblivious to the fact that the maps don't read that high.

So what am I missing here? Surely there must be a way to tune the higher RPMs. Considering the fact that my motor didn't detonate and explode at 8k (actually it was running rich), I know that the ECU still reads some sort of info out of uber. But... where are the cells for that RPM range?

 

I dont use Uberdata but I have a copy of 1.7 and 1.9 on this computer. Look in Rev Limits under RPM High.

 

convert to crome

crome has the ability to rescale the rpm colum's; i think uberdata has it to but you have to get congress to pass an act and a bunch of other bullshit.

 

unless your using a non-vtec bin you should be able to tune to 9000rpm under fuel high.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by non-VTEC &raquo;</TD></TR><TR><TD CLASS="quote">unless your using a non-vtec bin you should be able to tune to 9000rpm under fuel high.</TD></TR></TABLE>

Oh geez, good call. I was only looking at the low map.

Reason being is that I figured I'd tune to redline with the low map, then have the high map overlap it. That way, if there is some mechanical problem that prevents vtec from kicking in, I'll still have a tuned low map to fall back on.

But I'm still a bit confused as to why the low map doesn't also go to 9k. Hypothetically, let's say that after dyno tuning I conclude that peak power is at 8500. Now what if I'm doing redline pulls and vtec doesn' kick in? Doesn't that mean that the ECU will continue reading the low map? What will happen when the fuel and ignition maps cease at 8k and I go to 8500?

 

if you go above 8k on the low cam map only the fuel and ignition timing will just continue to read from the last colum.

so if you buzz it to 9000rpm on the low cam map only it will only get what you have set on the 8000rpm row.........i know it sounds kinda stupid but most other (if not all) EMS programs do the same.

 

Oh great - so my motor would run lean and explode. That does sound pretty stupid .

But I'd rather it read the last row than read nothing at all.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by EnzoSpeed &raquo;</TD></TR><TR><TD CLASS="quote">Oh great - so my motor would run lean and explode. That does sound pretty stupid .

But I'd rather it read the last row than read nothing at all.</TD></TR></TABLE>

you should realize you have a problem when the 2nd cam profile doesn't engage.

there is no reason you should rev that high on the low cam...

if for some insanely stupid reason you want to you could just richen up and pull timing from the last column

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by EnzoSpeed &raquo;</TD></TR><TR><TD CLASS="quote">Oh great - so my motor would run lean and explode. That does sound pretty stupid .

But I'd rather it read the last row than read nothing at all.</TD></TR></TABLE>
Why would your motor run lean?

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by tony1 &raquo;</TD></TR><TR><TD CLASS="quote">
Why would your motor run lean?</TD></TR></TABLE>

Well it'd be reading the 7940 row for all RPMs past 7940. So at 8,500 it would still be using the fuel/timing values in the 7940 row.

I just wonder becuase my old motor had some sort of problem and would never hit vtec. My new motor is fine, but you never know.

I like the idea of richening up the last row by the way. That's a good idea

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by EnzoSpeed &raquo;</TD></TR><TR><TD CLASS="quote">Well it'd be reading the 7940 row for all RPMs past 7940. So at 8,500 it would still be using the fuel/timing values in the 7940 row. </TD></TR></TABLE>

I think you can restate his question as, why would it be flowing so much better at 8500 rpm than at 8000 rpm that it would cause you to go SO lean you would blow up?

RPM doesn't require fuel... fuel follows the torque curve.

 

uberdata sucks anyway.

Go with Crome!

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by raene &raquo;</TD></TR><TR><TD CLASS="quote">

I think you can restate his question as, why would it be flowing so much better at 8500 rpm than at 8000 rpm </TD></TR></TABLE>

Don't ask me. All I know is that according to my wideband/uberdata, it does.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by _gurusan_ &raquo;</TD></TR><TR><TD CLASS="quote">uberdata sucks anyway.

Go with Crome! </TD></TR></TABLE>

now thats an intelligent reply

 

That's right, fuel consumption is based on torque. Torque is falling like crazy by 8k with vtec off. There's no way you'd need more fuel at 8500 than at 8000 with vtec off. Even with vtec on, most of the time fuel is tapering off well before 8500. If it doesn't work, then Uberdata just sucks....