APH Posted May 14, 2022 Report Share Posted May 14, 2022 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 Quote Link to comment Share on other sites More sharing options...
Adamw Posted May 14, 2022 Report Share Posted May 14, 2022 Assuming it is Link CAN lambda or Fury internal, then yes, If there is more than one then the ecu will remove the faulted device from the Lambda average and just use the remaining sensors that are working, or if there is only one device CLL will be disabled. Some 3rd party lambda devices however do not have adequate error reporting or fault detection to disable CLL. Quote Link to comment Share on other sites More sharing options...
Vaughan Posted May 15, 2022 Report Share Posted May 15, 2022 If the lambda value is greater than 9 or less than 0.1 it is considered to be in fault and isn't used for CLL calculations Quote Link to comment Share on other sites More sharing options...
APH Posted May 16, 2022 Author Report Share Posted May 16, 2022 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 Quote Link to comment Share on other sites More sharing options...
Adamw Posted May 16, 2022 Report Share Posted May 16, 2022 Can you attach the link log file .llgx Quote Link to comment Share on other sites More sharing options...
APH Posted May 16, 2022 Author Report Share Posted May 16, 2022 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? Quote Link to comment Share on other sites More sharing options...
Confused Posted May 16, 2022 Report Share Posted May 16, 2022 You can use one of the various "cloud drive" services like Dropbox, Google Drive, Microsoft One Drive etc to share larger log files & tunes once you've used your limited allowance on forum uploads. Quote Link to comment Share on other sites More sharing options...
Vaughan Posted May 16, 2022 Report Share Posted May 16, 2022 15 hours ago, APH said: I suggest adding Lambda Trim Max/min fault could resolve few lambda sensor fault issue if fault unable to define. You could do this with 3D Trim Limit tables with the lambda value on one axis Given the engine was still running at a lambda value of 4 was this a failed sensor or a massive exhaust leak pre sensor? Quote Link to comment Share on other sites More sharing options...
APH Posted May 17, 2022 Author Report Share Posted May 17, 2022 7 hours ago, Vaughan said: You could do this with 3D Trim Limit tables with the lambda value on one axis Given the engine was still running at a lambda value of 4 was this a failed sensor or a massive exhaust leak pre sensor? 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. Quote Link to comment Share on other sites More sharing options...
Adamw Posted May 17, 2022 Report Share Posted May 17, 2022 I think what Vaughan was suggesting is something like below. If Lambda went above 2.00 or below 0.67 there would be no correction allowed. Vaughan 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.