NefMoto

Technical => Tuning => Topic started by: RSMtune on January 18, 2025, 12:32:20 AM



Title: 1.8T AJQ with AMU injectors running rough help
Post by: RSMtune on January 18, 2025, 12:32:20 AM
Hello there,
have a struggles with injectors calibration on the Audi TT 1.8T.
Engine is AJQ 1.8T with stock injectors 0280155897 which are rated for 289cc/min @3bar.
New injectors are 0280155892 which are 358cc/min @3bar.
KRKTE and TVUB are copyied from the AUM 225hp map directly.
But car is running rough, cannot hold idle when its cold, lambda corrections goind to 25%.
Can anybody say any advice on this please?
Do I have to adjust something more ?
Stage 1 tune is included in modded file.
Car has blow off valve, 3bar regulator and straight pipe.
ECU: 8N0906018A


Title: Re: 1.8T AJQ with AMU injectors running rough help
Post by: _nameless on January 18, 2025, 08:36:58 AM
Awesome data logs


Title: Re: 1.8T AJQ with AMU injectors running rough help
Post by: RSMtune on January 18, 2025, 08:41:47 AM
Awesome data logs

Very useful answer, many thanks...
Searching for an answer from someone, who had similar issues when calibrating bigger injectors.
Newbie does mean nothing...


Title: Re: 1.8T AJQ with AMU injectors running rough help
Post by: Leonhard on January 19, 2025, 03:52:07 AM
AJQ: 0280155897 -> 310cc/min -> 0.1024
APY: 0280155892 -> 384cc/min -> 0.0832

AUM -> 150PS version, better use APY maps

simple conversion: KRKTE new = (ori flowrate / new flowrate) x KRKTE ori = 0.0827
hits ori APY value quite well (keep in mind: calculation works only with same ECU clocking)

if you got "used injectors", spray pattern / flowrate should be checked first

transform FKKVS as well, don't forget axis values,

don't hesitate to start logging and tuning FKKVS


Title: Re: 1.8T AJQ with AMU injectors running rough help
Post by: RSMtune on January 19, 2025, 04:02:45 AM
AJQ: 0280155897 -> 310cc/min -> 0.1024
APY: 0280155892 -> 384cc/min -> 0.0832

AUM -> 150PS version, better use APY maps

simple conversion: KRKTE new = (ori flowrate / new flowrate) x KRKTE ori = 0.0827
hits ori APY value quite well (keep in mind: calculation works only with same ECU clocking)

if you got "used injectors", spray pattern / flowrate should be checked first

transform FKKVS as well, don't forget axis values,

don't hesitate to start logging and tuning FKKVS


Many many thanks for an answer.
I see that I mistype engine code, injectors are from AMU not AUM.
Yesterday FKKVS map was copyied from the AMU 225hp file.
Idle is good, cold and hot, no issues, just lambda correctionis going to the -25% sometimes.
Car is running fine, power good, only issue is that sometimes when car's hot and after the pull I engage neutral, engine stalls. After restart all fine.
Car has aftermarket BOV which getting air out with "sound effect" when switching gears.
So this also can be an issue with engine stalls or ?
KRKTE used is 0.0835


Title: Re: 1.8T AJQ with AMU injectors running rough help
Post by: Leonhard on January 19, 2025, 05:21:18 AM
you can raise TEMIN up to 1.00 or even 1.20 (ori value 0.75) to prevent lambda controller lowering too hard.
Check TE (which is in measuring group 02) at hot idle reaching lambda=1, TEMIN should not be higher.


Title: Re: 1.8T AJQ with AMU injectors running rough help
Post by: _nameless on January 19, 2025, 10:33:40 AM
Very useful answer, many thanks...
Searching for an answer from someone, who had similar issues when calibrating bigger injectors.
Newbie does mean nothing...
Because you are new you don't feel you have to follow the forum rules? Cool.


Title: Re: 1.8T AJQ with AMU injectors running rough help
Post by: prj on January 20, 2025, 06:38:05 AM
This dude is tuning other people's cars for money, has no idea how to log the car, has no idea what a bov does to a car with a MAF, and is wondering why his shit doesn't work.

Classic.

And yes, you deserve this, because you didn't read the sticky and did not provide what is required here.
You're not calibrating shit, you're just throwing random numbers into the ecu, as evidenced by the complete lack of understanding of the underlying hardware and no logs.