Second time using ECU+. No P0300
Thread Starter
Evolved Member
iTrader: (13)
Joined: May 2003
Posts: 1,060
Likes: 14
From: Orange County, CA
Second time using ECU+. No P0300
Well! I just installed and tuned (for 91 oct. map) the new ECU+ for my 03 EVO today without P0300 code. This is the same car that I got P0300 code more than a year ago when installed the previous version of ECU+. I was running out of time on the dyno so only making 406 whp and 330 torque (dynojet) but making power much faster and smoother than the SAFC tuned. The drivability is much better now on the big turbo comparing to the SAFC tuned.
The different on this car compared to previous are RNR GT35r, 780 injectors, dynoflash removed (custom tuned flash). I will post more info and dynosheets when I come back for a race gas tune next Friday preparing for a drag strip. I'm not sure what was causing the P0300 in the previously version of ECU+.
There were some issues that I ran into:
1) My injectors are 780 but when used the 780cc scaling from the ECU+, the car won't idle, switch to 660cc then it's ok.
2) There's enhancement needed on the user interface for the ability to type in an RPM number and the system will move the cursor to the corresponded position on the graph. This will help us quicker for the fine tune since moving the mouse within the 250 or 500 rpm interval on the graph is paintfully tedious and slowdown the tuning time significantly.
The shop that tuned the ECU+ for me also like it a lot too. Wonderful product for the EVO. Thank Tom! The software is easy to learn and use.
The different on this car compared to previous are RNR GT35r, 780 injectors, dynoflash removed (custom tuned flash). I will post more info and dynosheets when I come back for a race gas tune next Friday preparing for a drag strip. I'm not sure what was causing the P0300 in the previously version of ECU+.
There were some issues that I ran into:
1) My injectors are 780 but when used the 780cc scaling from the ECU+, the car won't idle, switch to 660cc then it's ok.
2) There's enhancement needed on the user interface for the ability to type in an RPM number and the system will move the cursor to the corresponded position on the graph. This will help us quicker for the fine tune since moving the mouse within the 250 or 500 rpm interval on the graph is paintfully tedious and slowdown the tuning time significantly.
The shop that tuned the ECU+ for me also like it a lot too. Wonderful product for the EVO. Thank Tom! The software is easy to learn and use.
Last edited by G20; Oct 29, 2005 at 10:41 PM.
Originally Posted by G20
2) There's enhancement needed on the user interface for the ability to type in an RPM number and the system will move the cursor to the corresponded position on the graph. This will help us quicker for the fine tune since moving the mouse within the 250 or 500 rpm interval on the graph is paintfully tedious and slowdown the tuning time significantly.
Tom
Basically I think he is asking like a find function similar to the one in notepad. IE a ability in the software to select an exact RPM and have the program automatically move the cursor to the corresponding point on the graphs.
I think what he is talking about is like how other systems work.
Say AEM or Hondata, it shows (as im sure you know Tom) what Flow+RPM cell you are at when driving. I think he is asking for something like that, so you can see exactly what cell you are at so you can make changes according to that cell.
This is much more effective while on an eddy current dyno so you can keep it at each cell and test it on the dyno, to see what kind of gains you can get with screwing with ingition timing.
He may also want that feature because he is having troubles determining when he is low/mid/high/wot.....
-Justin
Say AEM or Hondata, it shows (as im sure you know Tom) what Flow+RPM cell you are at when driving. I think he is asking for something like that, so you can see exactly what cell you are at so you can make changes according to that cell.
This is much more effective while on an eddy current dyno so you can keep it at each cell and test it on the dyno, to see what kind of gains you can get with screwing with ingition timing.
He may also want that feature because he is having troubles determining when he is low/mid/high/wot.....
-Justin
Thread Starter
Evolved Member
iTrader: (13)
Joined: May 2003
Posts: 1,060
Likes: 14
From: Orange County, CA
Sorry about not make it clear. I was tired last night after the tunning session. Yes! It's exactly what others said. Type in an RPM value and the cursor will move to the exact location on the graphs. Thanks.
Originally Posted by G20
Sorry about not make it clear. I was tired last night after the tunning session. Yes! It's exactly what others said. Type in an RPM value and the cursor will move to the exact location on the graphs. Thanks.
Tom
Thread Starter
Evolved Member
iTrader: (13)
Joined: May 2003
Posts: 1,060
Likes: 14
From: Orange County, CA
Hey Tom! Were you there when we were doing the tuning? That was exactly what we did as mentioned by you.
No it's not what Justin was saying but the post above his post. But what Justin mentioned is also a cool feature as well.
It's just a suggestion so it's up to you to implement it. The place I live (south Los Angeles) doesn't have much open road for the WOT tune and the cops are not very friendly with cars like the EVO so I like to fine tune it on the dyno and then do some quick adjustment on the road with load for the drivability.
So far I was only tuned for the WOT. There're Low, Medium and High that I don't have times to do. For those, I can hook my laptop in the morning and datalog it while driving to work then I can open it up to do some adjustment at work and apply to test it on the way home.
No it's not what Justin was saying but the post above his post. But what Justin mentioned is also a cool feature as well.
It's just a suggestion so it's up to you to implement it. The place I live (south Los Angeles) doesn't have much open road for the WOT tune and the cops are not very friendly with cars like the EVO so I like to fine tune it on the dyno and then do some quick adjustment on the road with load for the drivability.
So far I was only tuned for the WOT. There're Low, Medium and High that I don't have times to do. For those, I can hook my laptop in the morning and datalog it while driving to work then I can open it up to do some adjustment at work and apply to test it on the way home.
Originally Posted by tlcoll1
Ok, I understand what you want, but let me see if I understand the motivation. You're doing tuning on a real dyno, and you datalogged that run with the ECU+ software. Then you and the tuner guy are looking at the plot from the real dyno, and see a dip in HP at, say, 6500 RPM. Then you say, hey lets see what the O2 voltage was at that RPM, but it's a PITA because you have to carefully position the cursor until the engine monitor reads 6500 RPM. Instead, you want to type in an RPM, and the software will move the cursor to the next spot on the graph where the RPMs where 6500? Note that this is completely different than what Justin was saying.
Tom
Tom
Trending Topics
Originally Posted by G20
Hey Tom! Were you there when we were doing the tuning? That was exactly what we did as mentioned by you.
Tom
Thread Starter
Evolved Member
iTrader: (13)
Joined: May 2003
Posts: 1,060
Likes: 14
From: Orange County, CA
Instead of using dialog window, if you use the always-on-top or docking window then it'll be faster to use since I don't have to close / reopen the dialog when tuning for each RPM interval. Actually when tuning, I were open/close the ECU+ Head Settings dialog many times that I wish it's just a normal window so that I can move the mouse on the graph, identify the RPM that I want to adjust and directly change the value on the settings without open/close the settings dialog. The drawback of this method is the potential of user error is a little higher since it's easier to modify the settings.
Thanks.
Thanks.
Last edited by G20; Oct 30, 2005 at 09:56 PM.
Originally Posted by G20
Instead of using dialog window, if you use the always-on-top or docking window then it'll be faster to use since I don't have to close / reopen the dialog when tuning for each RPM interval. Actually when tuning, I were open/close the ECU+ Head Settings dialog many times that I wish it's just a normal window so that I can move the mouse on the graph, identify the RPM that I want to adjust and directly change the value on the settings without open/close the settings dialog. The drawback of this method is the potential of user error is a little higher since it's easier to modify the settings.
Thanks.
Thanks.
Tom
Originally Posted by Boltz.
Say AEM or Hondata, it shows (as im sure you know Tom) what Flow+RPM cell you are at when driving. I think he is asking for something like that, so you can see exactly what cell you are at so you can make changes according to that cell.
This is much more effective while on an eddy current dyno so you can keep it at each cell and test it on the dyno, to see what kind of gains you can get with screwing with ingition timing.
This is much more effective while on an eddy current dyno so you can keep it at each cell and test it on the dyno, to see what kind of gains you can get with screwing with ingition timing.
Tom
Never forgets a feature request
Originally Posted by G20
2) There's enhancement needed on the user interface for the ability to type in an RPM number and the system will move the cursor to the corresponded position on the graph. This will help us quicker for the fine tune since moving the mouse within the 250 or 500 rpm interval on the graph is paintfully tedious and slowdown the tuning time significantly.
On the ECU+ dyno graph, you pull up the dyno graph and there's no cursor, even though the tooltips display the X and Y values. Welp, I added a cursor that works like the cursors in the normal scrollable graphs. But what's cool is that now, when you move the cursor over the dyno graph, the rest of the cursors track it. So, if you move the dyno cursor up to a spot where you have a dip, say at 6200 RPM, the cursors in the other graphs move to the time where you were at 6200 RPM. This highlights *everything* that was going on at that instant without moving back and forth between the dyno graph and the other graphs, and provides an auto "go to RPM" function.
So what you'll want to do is that next time you're on the dyno, bring up the ECU+'s dyno graph. You'll see the same curve as on the real dyno, and be able zero in on those trouble spots using the ECU+'s dyno graph and the new back-cursoring.
It's hard to describe how cool this is in words, but when you use it, you go "oooh."
Tom
Thread Starter
Evolved Member
iTrader: (13)
Joined: May 2003
Posts: 1,060
Likes: 14
From: Orange County, CA



