namre
-
Posts
41 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Gallery
Blogs
Posts posted by namre
-
-
10 hours ago, cj said:
For point regarding your Fan on idle, you can try increasing your engine fan step from what looks like 0.4% up to 0.6 or 0.8%. The real problem is that your PID control for your throttle is not sensitive enough and so your target TPS is moving by 0.4%, but you actual TPS angle is moving by roughly 0.2% and so its not enough. E-throttle works roughly to the idea that the further you are away from target, the more "effort" the ECU will make to change the TPS angle. if you are only 0.2% off, its basically going to just let it be a bit off unless you have it tuned to be pretty sensitive. (screenshot from someone else's config so the values wont match yours)
You describe the idle as "not responding" when it first starts up in point 1. This might be somewhat by design. In you first log you can see the idle status is "hold-startup" until about 8.5 seconds into the log. Before this time its running a hard-coded set of startup numbers.
In your AC log it looks like your AC step up table is supplying ~1.8% TPS increase when your AC request is switched on. This is taking your idle (either RPM or MAP) ups too high and so while throttle idle control still looks to be active, ignition idle control has been disabled and so your ignition angle goes from ~16* to 36* as per you IGN 1 table. This combined with the nearly 7% of TPS your AC step up is giving you is making you idle at ~1600 RPM. try dropping the AC set up table values to maybe half what they currently are. Also check your ignition idle control numbers to see if they are being exceeded. See screenshot for the values you need to check. (again, not your actual config because you didnt post it)
Have you run through the guide in the help file where it talks about disabling all idle control systems, tuning open loop on its own, then enabling the idle control systems just to keep it stable. Its not supposed to be able to cope with massively different engine parameters, just to smooth things out and keep it running nicely if something isnt quite the same as when you tuned it.
Thanks. I have walked things through. About your last comment, I tried to disable ISC by deleting base position table but idle dropped to 500 rpm or so and stalled. I could not find how I can increase this without ISC. Can it be done by adjusting idle ignition table?
-
5 hours ago, Rob W said:
Another little issue there. Your warm up enrichment has 18-22% above 80*c. Engines will often be operating in that ECT range.
If you have a close look at log 3 at 89*c your avg Lambda at idle is .79, which is not far off WOT Lambda.
As soon as it hits 90*c the enrichment is 0% and Lambda jumps to .90 avg. Drops back to 89*c and richens up to .79 again.
Thanks for helpful comments. I will check these. For the moment:
I have already calibrated TP but its still around 4-5% dont know why. I will try to put lock out above that.
I have reduced to 900 rpm since it’s not fluctuating at that level.
For idle up tables I have zeroed the ac stepper but still there is a small fluctuation. Maybe its related to other points you mentioned.
About your second post, do you mean that The warm up enrichment should also be zero at 80 ect?
-
I have strange idle behaviors. It seems normal under 1000 RPM but can you please help on the following issues?
- My idle target table and base positions are all set. However when I first start the car, idle speed control does not come active. Idle stays as the car has already warmed up. If I accelerate a bit then it starts to work. If I restart it this time it kicks in after a while. See log 1.
- Idle fluctuates at 1000 or above rpm. You can see at the second logs that TP is almost same but there is an RPM fluctuation. See log 2
- Saying so, when ac clutch/request is on there is additional fluctuation. I am not sure if its connected to 2nd item. See log 3.
- Idle drops to 500 RPM when engine fan kicks in. See log 4.
-
Is it a bad idea to adjust fuel or ignition table according to this specific spot in order to eliminate problem from most probably my cams (being stage 3)? i know this will hurt my afr.
general question is that should the fuel and ignition tables have sequentially increasing or decreasing values all of the time?
is it possible to have some unsequential jumps where for example afr is off target?
thanks.
-
I will try it as soon as I have time. But as far as I recall there was no bucking at least was not noticeable this much.
I tried to eliminate mechanics -changed the fuel pump and plugs but no luck.
Would TPS calibration help?
-
13 hours ago, TimmyD said:
An "electronic valve controller", sorry I never realised that. In that case, I guess you wouldn't want the Link ECU doing closed loop aswell. My mistake.
Looking at your latest log, despite the oscillations they look pretty small in amplitude (it's zoomed in quite a lot).
Bit stuck on this I'm afraid, apart from the fuelling on acceleration looking too rich. I could have helped with setting up Link boost control, but I don't think that's your problem now.
I'm really confused. Ok my fuel pressure was a bit lower. I have corrected that one and problem at acceleration was decreased.
I realized that hesitation at the low TP was not happening when the engine is cold/warm (say before flooring). But it starts appearing after flooring couple of times.
So there is no hesitation at 100% TP, but there is hesitation after travelling (not before).
If it was ignition it should appear at flooring as well in my opinion. We have checked the plugs/gap they were ok.
Only remaining candidate might be fuel pump but then why its not happening at all circumstances then?
That's why I tried to check tuning as well since this wasnt the picture before retuning.
Totally stucked here.
-
Do you have any hint on whats happening in lower rpms? It happens when trying to stabilize the rpm but not on acceleration. Could it be also fuel related? This time AFR seems to be within the limits.
-
5 hours ago, TimmyD said:
I'm not sure what you mean by "EVC" ?
I believe that you're basically running open loop, i.e. from the wastegate table. However, the Boost Mode is set to 'closed loop'. I don't think this is what's causing your "engine hesitation" problem, but it would be a good refinement to carry out at some point.
From Impreza STI, 2.5 (2007), here's Target boost table:
I think the first thing to tackle is the fuelling IMHO....
Many thanks.
I will check the fueling first.
By EVC I meant that I have electronic valve controller (HKS) installed. So I have several boost modes. I am not sure according to which mode should I fill this table. Will it deteriorate the other modes for example? That's what I'm confused.
Is it better to change it basically to open loop if that's already the case in practice?
-
2 hours ago, TimmyD said:
I see a couple of things from the log that might be worth a look (pic attached)
1. It looks quite rich (0.68) at the start of boost, before stabilising later.
2. Boost Mode is set to 'closed loop' but the Target Boost Table only has a row for TP = 0%.
It should include rows up to TP = 100%.
Boost Status is shown as OFF all the time, due to the above I expect.
Hope that helps?
Thanks for the reply.
I am confused at boost target table in the way that if conflicts with EVC.
would it stabilize the boost further than wastegate?
finally I appreciate if you share a sample target table since I couldnot find it in the base maps?
-
16 hours ago, Richard Hill said:
Can you post a log file too? That would definitely help to see what might be causing the problem.
Hello,
Here are some log files I got. Hope it helps.
-
It's subaru sti 2.5. I will record the log file asap.
-
Hello,
We have engine hesitation esp. at boost area after retuning.
We checked the mechanical possibilities but could not find anything. The tuner says runtime values are ok at that stage.
Here is the base map.
Do you have any clue if there is any signal that this is about tuning?
Thanks for your help.
-
On 1/3/2019 at 12:16 AM, Adamw said:
I'm overseas on holiday so have only had a brief look, but the first thing I see is the MAP is reading wrong. As per the manual you need to make sure all inputs are set up, calibrated and reading correctly before starting . It should read near 100kpa with the engine off, yours is reading 25kpa.
Thanks. Calibration was the issue.
-
Hello,
Below is the max map kpa value from statistics section.
Do you know exactly what does this mean? Is it the existing tuned value? If so, from where I can find this since I could not find it anywhere? I would like to change it if it is the existing configuration but map limit table does not have this kind of value.
The issue we are facing is a kind of boost cut above 1.4 bars and need to be sure that it is not related to tuning. 1.4 bars appr. fits to the figure below. But in map limit table we have 300 kpa which would mean that there should be no boost cut till around 2 bars.
Thanks in advance for your help.
-
Hello gurus,
After we have installed the link base maps of sti v10 engine did not start.
Attached are two logs from pclink.
Can you please help on what causes this?
Thanks in advance.
Idle Problems
in G4+
Posted
OK. I have closed IIC and zeroed base position table and started from adjusting e-throttle target. It seems better now. I didnot start IIC again since this is where things get complicated and unstable. I guess this is not a problem?
Fluctuations happen over 1k rpm again. I believe this is also connected to my engine bucking problem at 2500 rpm. Deteriorating afr at this spot did not help. It might be mechanical due to lambda sensor or ethrottle or cams itself is all left maybe.
I have two widebands, one is lambda sensor just after the turbo and the other one is aem wideband sensor on some 30cms after the lambda. These two vary too much sometimes up to 2 points. And I've realized today that my lambda buzzes so much at the rpm fluctuation stage (at the bucking phase as well). This can be seen from the logs. It's too sensitive. When I check the other gauge it seems more stable. So which one to trust? Tuning was done according to lambda naturally.