Mapped The Bug Yesterday, Have A Look!
#1
Scooby Regular
Thread Starter
Mapped The Bug Yesterday, Have A Look!
Mapped the Bugeye yesterday aiming for 16/17psi boost, it's not quite hit target figures but getting close, fairly hard to get a decent 3rd gear pull around where i live without travelling miles, but heres the log of what i did yesterday, feels strong from low down revs and pulls clean, getting knock in strange places which could be down to the exhaust catching
Spec
Forged motor
3" turbo back
de-cat'd up pipe
stock tmic
stock inj
Spec
Forged motor
3" turbo back
de-cat'd up pipe
stock tmic
stock inj
Last edited by Petbeemer; 18 June 2010 at 02:40 PM.
#3
Scooby Regular
Thread Starter
Engine Speed (RPM)
Engine Load (Direct / RAM)
Ignition Total Timing (degrees)
Knock Correction Advance (degrees)
Manifold Relative Pressure (Corrected or Sea Level) (psi)
Intake Air Temperature (F)
Mass Airflow (g/s)
Primary Wastegate Duty Cycle (%)
Throttle Opening Angle (%)
Lambda 1
Should that not be enough?
Not using det can's although i have a steth, couldn't hear any 'pinking' from the motor and as it look's on the log the only time it notes any sort of det it's actually not boosting so imagine its picking up noise from the exhaust catching underneath
#6
Scooby Regular
Thread Starter
#7
Former Sponsor
iTrader: (3)
is your knock correction table flattened? if not it would be more worthwhile to log the feedback correction and fine learning as knock correction is only showing you the timing from the advance tables net of corrections and this is misleading.
Also worth noting that the lambda reading you will be logging is notoriously inaccurate.
Also worth noting that the lambda reading you will be logging is notoriously inaccurate.
Trending Topics
#8
Scooby Regular
Thread Starter
is your knock correction table flattened? if not it would be more worthwhile to log the feedback correction and fine learning as knock correction is only showing you the timing from the advance tables net of corrections and this is misleading.
Also worth noting that the lambda reading you will be logging is notoriously inaccurate.
Also worth noting that the lambda reading you will be logging is notoriously inaccurate.
#9
Former Sponsor
iTrader: (3)
if you read the faq's on romraider it will talk about it. I wasnt saying you should necessarily do it as it does have it's downsides but it would than mean that the knock correction value you are logging would easily show if the ecu is pulling timing. Better to log the knock values themselves as logging knock correction is meaningless IMO.
#10
Scooby Regular
Thread Starter
if you read the faq's on romraider it will talk about it. I wasnt saying you should necessarily do it as it does have it's downsides but it would than mean that the knock correction value you are logging would easily show if the ecu is pulling timing. Better to log the knock values themselves as logging knock correction is meaningless IMO.
#12
Scooby Regular
Thread Starter
I designed the mappable ecu config's for the early Evo some years ago, i knew nothing about electronics before that, so it proves it's worth a shot!
Ecutek have ruled the roost for too long!
#13
Scooby Regular
Thread Starter
Ok knocked a little off timing at top end IAM gone to 16 so i presume ecu is 'happy' with the tune
fine learning knock is stable but still not hitting target boost pressure, and that's after a good tweak on the arm so presumably im loosing pressure somewhere? or could it just be differences between turbo's?
fine learning knock is stable but still not hitting target boost pressure, and that's after a good tweak on the arm so presumably im loosing pressure somewhere? or could it just be differences between turbo's?
#14
Former Sponsor
iTrader: (3)
What up-pipe did you fit and what turbo?
I see you have flattened the advance table - it does make it easier to read one line and see if corrections are happening.
Interesting with the signal from the ecu dropping out on the first pull, this is often det induced so it may be worth checking timing/fueling/det again to be safe.
I see you have flattened the advance table - it does make it easier to read one line and see if corrections are happening.
Interesting with the signal from the ecu dropping out on the first pull, this is often det induced so it may be worth checking timing/fueling/det again to be safe.
#15
Scooby Regular
Thread Starter
What up-pipe did you fit and what turbo?
I see you have flattened the advance table - it does make it easier to read one line and see if corrections are happening.
Interesting with the signal from the ecu dropping out on the first pull, this is often det induced so it may be worth checking timing/fueling/det again to be safe.
I see you have flattened the advance table - it does make it easier to read one line and see if corrections are happening.
Interesting with the signal from the ecu dropping out on the first pull, this is often det induced so it may be worth checking timing/fueling/det again to be safe.
Would the signal dropping be nothing to do with ecu re-set on the first pull?
#17
Scooby Regular
Thread Starter
what's the gains over 3 port? just better managment of the WG?
#19
Scooby Regular
Thread Starter
#21
Scooby Regular
Thread Starter
Thread
Thread Starter
Forum
Replies
Last Post