Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: A concept for boost enrichment...


Guru

Status: Offline
Posts: 1233
Date:
RE: A concept for boost enrichment...


Ok, thanks Greg, i didnt realize you were using the extended boost fuel code. Let me know what you find.

Cheers

-Justin.



__________________

site_logo_small.png

www.WoolichRacing.comTune your bike to the Limit with our Advanced ECU Flashing Products



Senior Member

Status: Offline
Posts: 148
Date:

With the new code i had no luck it is very far off from my map i already tested that. With old code i have an issue when i try to past 14-15psi it seems like something is cutting the fuel. i double checked everything,pump,injectors, map sensor,fuel lines, nt switch, tps, gps, WG, EVERYTHING. I really can't understand what is the problem. I managed to rich 400hp with 15psi but that's the most i can get without problems. any help would be much appreciated my goal is 550-650hp if i can get it to work like it supposed to.

__________________

LIFE IS SHORT RIDE HARD



Guru

Status: Offline
Posts: 546
Date:

Matador did you completely convert your current values to the new scaling ?
Mine was a new map using my roadbike as the base level of 15 psi then scaling up and down from there for psi and rpm
but needed a lot of work in the injector balance and tps tables to get the base map right before the boost could be applied
tps jumps from hi numbers to low as the secondarys stage in ,

Your welcome to a copy of my bin to compare if you want

 



-- Edited by Maj750 on Wednesday 30th of May 2012 01:00:46 AM

__________________


Guru

Status: Offline
Posts: 953
Date:

I just brought my old map into the new extended code, I copied boostfuel data from the boost level above, meaning 6 psi from my old map, went into the 5 psi column. 8 psi from old map went into 7 psi on new map etc. I just went out for a quick ride and ran up to 12-13 psi without any issues, this was using version .101 downloaded a day or so ago.



Greg


__________________


Guru

Status: Offline
Posts: 546
Date:


Looks quite reasonable Greg
Actually the only thing i would want to see changed is the logging table to be scaled the same as the boost table to at least 31 psi
this deciding if a 8 should be in the 7 or 9 column or scanning the side bar for levels above 24 complicates things somewhat
but otherwise if there is a scaling issue in the boost fuel table and its fixed i would have to redo several bikes or lock my version and i expect there would be others in a similar circumstance

__________________


Guru

Status: Offline
Posts: 1247
Date:

I agree with the picking the closest values to change being kind of a pain.
I haven't done much with the charts for boost tuning as I mostly tune for high boost levels and rarely see less then 10psi, mostly 18+

If I put an intercoler on for next year, the lower boost levels will probably be of more interest.

The auto tuning and the charts are really great for street tuning, they are a bit tough to use for dyno or track tuning as the amount of data are a bit sparse. I usually look at trends rater than individual points for tuning at the track or on the dyno

The auto tuning is great for streetbikes on a load control dyno where you can just set an rpm to hold and slowly roll into the throttle, then bump the set rpm and slowly roll in again.



Damn, we are a picky bunch aren't we... 



-- Edited by sportbikeryder on Wednesday 30th of May 2012 01:47:37 AM

__________________


Senior Member

Status: Offline
Posts: 148
Date:

Maj have in mind that i use 82lbs secondary injectors and rcc fuel rail. I think that the problem is ;only with the big boost. Does any of u guys use high boost and also have the quick shifter function enabled? I am saying that maybe the overboost limit is causing this issue although i have set it at maximum range.

The bad thing is that i have a race this weekend and i will be racing with only 400hp LOL



-- Edited by Matador on Wednesday 30th of May 2012 07:02:43 AM

__________________

LIFE IS SHORT RIDE HARD



Guru

Status: Offline
Posts: 546
Date:

no quickshifter enabled yet but running to 28 psi with an ice/water intercooled gt35r 65 lb secondarys , my map may not suit but my setup may help give a clue to whats giving you issues

I run my inertia dyno at a few throttle positions /log,at a particular boost level usually a 100% 80% 60% , good cool down and do a 90,70,50 , then use the data from both logs to do a sweeping change mostly in tps with autotune if i am happy with the boost table , sidebar selection helps decide if the boost or tps needs attention as 60-70% tps is critical on the salt i can't afford to have differing a/f at different tps

__________________


Senior Member

Status: Offline
Posts: 148
Date:

Ok if u can send me the bin file i will test it and see if i can find anything. Is this with new or old code? Thanks my mail is dimbusa13 @ gmail.com

I will also try without shifter and see if this is the problem. And something else can someone tell me what is your voltage at idle and at heavy load? Maybe those big injectors need 14+ to work without issues.

__________________

LIFE IS SHORT RIDE HARD



Senior Member

Status: Offline
Posts: 148
Date:

Greg thanks it was very helpful. The problem was with my spark plugs lol.
500 bhp and raising!!!!

__________________

LIFE IS SHORT RIDE HARD



Guru

Status: Offline
Posts: 1247
Date:

Matador wrote:

Greg thanks it was very helpful. The problem was with my spark plugs lol.
500 bhp and raising!!!!


 Very cool...what was the spark plug issue?



__________________


Senior Member

Status: Offline
Posts: 148
Date:

I really can't understand that. Anything above 12-14psi and I had misfire like hard cut.
Changed them with new just as a precaution and there u go 20 22 24 psi with absolutely no problem.
Guess that voltage and ignition spark do a lot in high power application
I am going to play with dwel map after the race and see the results.
Anyone played with that?

__________________

LIFE IS SHORT RIDE HARD



Guru

Status: Offline
Posts: 1247
Date:

I haven't really messed with the dwell. If you do, keep in mind that it may alter your ignition timing a bit. I may hook my oscilliscops to the crank or cam sensor and the primary side of a coil to see if I can determine ignition timing as well as coil charging characteristics.

I typically use NGK CR10E plugs gapped at .018"

__________________


Guru

Status: Offline
Posts: 546
Date:

Got to the point myself of putting new plugs in every time i put a bike on the dyno ,and anytime i develop a misfire wish there was a way to reliably clean and test them , i have a hundred or so i can't bring myself to either throw out or use

my dwell is std but using the NLR sim

Hope both of you get some good racing in this weekend



__________________


Guru

Status: Offline
Posts: 1247
Date:

From Aug 4, 2011 in the autotune and datalogging post:
jkwool wrote:

Hi John

Just released change for the GM 3bar ext option, you can select this in the auto tune settings, once you have selected this it will remember the setting, but the first time you should close the engine data viewer and reopen to pick up the change.

I have also improved the visual display on the engine data logging screen to make it easier for you to see what is going on while on the dyno, let me know what you think and if there are any improvements that can be made.




__________________


Guru

Status: Offline
Posts: 546
Date:

Ok found the extended boost fuel stuff hidden in there, always thought the 3 bar was all i needed and did not look further
But in changing back and forward as i thought i had a different reading with the extended boost fuel log , i have locked up the logger

"Index was outside the bounds of the array at ecueditor_25k8 enginedataviewer.openfile() "

even closing and reopening editor does not help

 

next try gave an unhandled exception

index was out of  range Must be non-negative and less than the size of the collection

Parameter name :index

Details

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.Collections.ArrayList.get_Item(Int32 index)
   at System.Windows.Forms.DataGridViewRowCollection.SharedRow(Int32 rowIndex)
   at System.Windows.Forms.DataGridViewRowCollection.get_Item(Int32 index)
   at ecueditor_25.K8EngineDataViewer.ShowBoostHeaders()
   at ecueditor_25.K8EngineDataViewer.ShowLoggedBoostValues()
   at ecueditor_25.K8EngineDataViewer.ShowMap()
   at ecueditor_25.K8EngineDataViewer.B_AutoTuneSettings_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 (RTMGDR.030319-2600)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 built by: RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
ecueditor.com
    Assembly Version: 2.5.5.99
    Win32 Version: 2.5.5.99
    CodeBase: file:///C:/Documents%20and%20Settings/Owner/Local%20Settings/Apps/2.0/8R6M7OPN.04C/0OY6ZKM6.KHN/ecue..tion_0000000000000000_0002.0005_8601a2cfe3579963/ecueditor.com.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 built by: RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.276 built by: RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
TwitterVB
    Assembly Version: 2.5.0.0
    Win32 Version: 2.5.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/Owner/Local%20Settings/Apps/2.0/8R6M7OPN.04C/0OY6ZKM6.KHN/ecue..tion_0000000000000000_0002.0005_8601a2cfe3579963/TwitterVB.DLL
----------------------------------------
System.Deployment
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Deployment/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
----------------------------------------
Lxsoft.Controls.LedControl
    Assembly Version: 1.0.2755.28697
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/Owner/Local%20Settings/Apps/2.0/8R6M7OPN.04C/0OY6ZKM6.KHN/ecue..tion_0000000000000000_0002.0005_8601a2cfe3579963/Lxsoft.Controls.LedControl.DLL
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
AquaGauge
    Assembly Version: 1.0.2800.27798
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/Owner/Local%20Settings/Apps/2.0/8R6M7OPN.04C/0OY6ZKM6.KHN/ecue..tion_0000000000000000_0002.0005_8601a2cfe3579963/AquaGauge.DLL
----------------------------------------
AGauge
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/Owner/Local%20Settings/Apps/2.0/8R6M7OPN.04C/0OY6ZKM6.KHN/ecue..tion_0000000000000000_0002.0005_8601a2cfe3579963/AGauge.DLL
----------------------------------------
System.Windows.Forms.DataVisualization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.DataVisualization/v4.0_4.0.0.0__31bf3856ad364e35/System.Windows.Forms.DataVisualization.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


 



-- Edited by Maj750 on Thursday 31st of May 2012 04:40:05 AM

__________________


Guru

Status: Offline
Posts: 1233
Date:

Hi Greg

Are you able to send through the log files so i can reproduce the problem?



__________________

site_logo_small.png

www.WoolichRacing.comTune your bike to the Limit with our Advanced ECU Flashing Products



Guru

Status: Offline
Posts: 546
Date:

Ok more playing
I can run as extended logging but not reverse the action
Good enough for now

__________________


Guru

Status: Offline
Posts: 1247
Date:

Maj / Matador,
Any isues / bugs with teh extended boost fuel code, specifically with the pressure based ignition retard?

I am on the fence about converting. I believe I am going to go back to the dyno and sort of start over (going as far as to pull the gate off to get a base TPS map and build from there)
I may even venture toward the 5 bar sensor. I know that is fairly uncharted territory, but I will hook up a pressure / vacuum source with the data stream active and see how it responds. If it looks to be inline with where it should be I am going to make the switch.

I think I will use your technique to some extent for tuning, although I think I will make up a percent fuel addition table based on calculated density ratio of the turbo (taking into account efficiency and theoretical air conditions) to be used for the percent add calculations (and probably add 5% additional for cushion).

John

__________________


Senior Member

Status: Offline
Posts: 148
Date:

Sorry but i didn't had time to test the boost ign retard i run with no timing pulled. I managed to make a new personal record of 7,812 but i lost a bearing on number 3 and my crank also bended. I pulled the motor out for rebuild with 1/2 studs new balanced crank and new bearings.



-- Edited by Matador on Saturday 16th of June 2012 05:44:06 PM

__________________

LIFE IS SHORT RIDE HARD



Guru

Status: Offline
Posts: 546
Date:

Hope you can identify the cause and stop it happening again , congrats on the PB

Last tuneup on my 750 LSR bike had me change back to the legacy version, was getting rediculous numbers in the boost fuel table with no room to progress
went from 200s to 50s ~15 psi , sent Justin the logs and bin of both the busa running great on extended boost fuel and the 750 not and still to send the 750 legacy running great

no idea why as Justin said the code is unchanged for a long time , maybe its something to do with the busa/gsxr bin

__________________


Guru

Status: Offline
Posts: 1247
Date:

Too bad on the motor....we've all done similar a few times...

I may make the switch to the new version to see how it goes. Either way, I will be re-doing the base TPS fueling.



-- Edited by sportbikeryder on Saturday 16th of June 2012 10:16:08 PM

__________________


Guru

Status: Offline
Posts: 953
Date:

is anyone running boostfuel on a 1000 or busa way past 11.5K rpm?  Have a buddy trying busa firmware on 1000 and bike is going way way lean at 11.5K rpm and seems to stop reading rpm (like cursor on screen stops moving).  Haven't been able to see it myself yet but wondering who out there is using it successfully etc.



__________________


Senior Member

Status: Offline
Posts: 148
Date:

I tunned a 600 turbo bike with Busa firmware but I used the old code no problem with that.
I noticed that after 12000 it just used the same values on the last raw

__________________

LIFE IS SHORT RIDE HARD



Guru

Status: Offline
Posts: 953
Date:

how high did you pull to?



__________________


Senior Member

Status: Offline
Posts: 148
Date:

14500 with no problem


__________________

LIFE IS SHORT RIDE HARD



Guru

Status: Offline
Posts: 1233
Date:

Just fixed a problem in the boost fuel code related to overboost limit in the extended boost fuel section. The code was setting the overboost limit to the absolute sensor value i.e. 14.7 psi too low so if you put in 30 psi into the extended boost fuel screen it was registering 15.3. This has been fixed in the latest version of 2.5 just published.


Cheers

-Justin.



__________________

site_logo_small.png

www.WoolichRacing.comTune your bike to the Limit with our Advanced ECU Flashing Products



Veteran Member

Status: Offline
Posts: 52
Date:

Matador wrote:

I really can't understand that. Anything above 12-14psi and I had misfire like hard cut.
Changed them with new just as a precaution and there u go 20 22 24 psi with absolutely no problem.
Guess that voltage and ignition spark do a lot in high power application
I am going to play with dwel map after the race and see the results.
Anyone played with that?


 

I set every number from 11.6-15.4 volts that was under 43 to 43 basically over over 8000RPM



__________________

Home Built 06 Gsx-r 750 w/ Disco Potato .60 A/r 6.5lbs Pump gas 100% stock motor 211.54 rwhp...... going for 275 on E85 with ECU editor

Oh make it 237rwhp and 97lbs on E-85 100% stock motor 8lbs of boost. Thanks WIN Racing



Veteran Member

Status: Offline
Posts: 38
Date:

I have a strange issue with a turbo busa,it starts fine with the stock map sensor and idles at about 11.5 with stock IAP fuel map,when I connect the gm map sensor and enable boostfuel the bike can't even idle and I smell a lot of gasoline,something is making it run too rich to even idle.
I switch to a completely stock bin with a stock map sensor again and starts and idles fine....

Only thing I've done so far regarding fuel is an external pump and a manual fuel pressure regulator set at 3.2 bar.


Any ideas? Is there something I else I need to do when I wire the gm map sensor to the bin? I left all the settings stock just trying to make it run and get familiar with the boost fuel logging etc...



-- Edited by Balojohn on Sunday 19th of January 2014 11:15:37 AM

__________________


Veteran Member

Status: Offline
Posts: 38
Date:

Balojohn wrote:

I have a strange issue with a turbo busa,it starts fine with the stock map sensor and idles at about 11.5 with stock IAP fuel map,when I connect the gm map sensor and enable boostfuel the bike can't even idle and I smell a lot of gasoline,something is making it run too rich to even idle.
I switch to a completely stock bin with a stock map sensor again and starts and idles fine....

Only thing I've done so far regarding fuel is an external pump and a manual fuel pressure regulator set at 3.2 bar.


Any ideas? Is there something I else I need to do when I wire the gm map sensor to the bin? I left all the settings stock just trying to make it run and get familiar with the boost fuel logging etc...

 

 

-- Edited by Balojohn on Sunday 19th of January 2014 11:15:37 AM


 Everything is working fine now,the problem was a faulty 3 bar sensor. I replaced it and everything works well now

 

smile



__________________
«First  <  15 6 7 | Page of 7  sorted by
 
Quick Reply

Please log in to post quick replies.

Tweet this page Post to Digg Post to Del.icio.us


Create your own FREE Forum
Report Abuse
Powered by ActiveBoard