APH
Members-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Blogs
Everything posted by APH
-
Sensor failed. 3d Trim could work but not ideal, temporary suspend fuel trim and return to open loop will be easier to diagnose issue. Unreasonable fuel trim may not be a lambda sensor issue, it could be a tps/map sensor issue.
-
The total size of the log file is 33mb, even compress is 13mb.. Is there way i can reduce the data and export to .llgx file?
-
Here is a log of a Lambda sensor issue where no fault has been flag, where Lambda 3-4 while its driving and Lambda Trim just stay at max at all time. I suggest adding Lambda Trim Max/min fault could resolve few lambda sensor fault issue if fault unable to define. This is a LinkG4X Fury using internal Lambda. lambdaissue.csv
-
Some of the tunes we do are using full closed loop at all time. I wonder if requesting of Closed Loop Lambda Trim to be disable when Lambda fault on? This apply to all LinkG4X external or internal Lambda. Thanks, Brian
-
Adam, Thanks, for quick reply we will order the external e-throttle controller. Brian
-
I am a little confuse by how the manual document for e-throttle setup. So do i need external e-throttle controller or not? Thanks, Brian
-
2nd or 3rd only able to use a input sources, unless i use a math block (What are the way to use math block?) When anti lag status on with e-throttle target table set 0% APS and TPS is 20%. So When ALT status 1, APS reach 1%, over-run fuel function kick in and perform 100% fuel cut. I thought that is Integral Min clamp, if that is case it should call max/min duty? E-throtte idling PID doesn't perform integral negative clamp if i set the idle base position table to higher than actual.
-
1- There are no real way to have by pass air table for ALS using E-Throttle. 2- During ALS enable with overrun fuel still active. (E-throttle) 3- E-Throttle idling (idle actuator) Min clamp cannot input a negative value. (only add) Thanks
-
Thanks for quick response. Its all good now.
-
I am getting a error of TPS (main) (sub) tracking error. APP and TPS calibration preform successfully in setup mode, soon as switch to On mode i get this error. Thanks, Brian