L.TRIM always at -100 / Knock count question
L.TRIM always at -100 / Knock count question
Hi, I have the 2019 1.5T civic touring (brazil version) and my logs and reading have always shown L.TRIM as -100... is this a bug or something? The -100 is in the logs and the headunit app. S.Trim works as should and indicates values usually below 10%.
Is there anyway I can get tu actually see what the L.TRIM value is?
Also, I am using +3 basemap with regular gas, and my commute is normally a 30min 18km trip. Every day I check the knock count and usually get around 10 to 15 knocks at the end of the trip. K. Control is normally around 54% and sometimes goes up to 60% when I do some WOT´s. I´ve never seen it below 53%. Should I be concerned about this and perhaps fine tune it to avoid these knocks, or is this a normal behaviour ?
With stock map the same trip would give me 0 knock count.
And just another noob question, where can I see the actual turbo pressure in the datalogs?
Thanks!
Is there anyway I can get tu actually see what the L.TRIM value is?
Also, I am using +3 basemap with regular gas, and my commute is normally a 30min 18km trip. Every day I check the knock count and usually get around 10 to 15 knocks at the end of the trip. K. Control is normally around 54% and sometimes goes up to 60% when I do some WOT´s. I´ve never seen it below 53%. Should I be concerned about this and perhaps fine tune it to avoid these knocks, or is this a normal behaviour ?
With stock map the same trip would give me 0 knock count.
And just another noob question, where can I see the actual turbo pressure in the datalogs?
Thanks!
Re: L.TRIM always at -100 / Knock count question
Post your calibration as well as a datalog showing the issue.
Re: L.TRIM always at -100 / Knock count question
I have attached my datalog for my today´s trip. I didn´t do any WOT´s but had some knocks, although the count was not as high as usual.
- Attachments
-
- basemap +3psi.fpcal
- (14.79 KiB) Downloaded 102 times
-
- basemap +3psi ida a viamao 2.fpdl
- (5.38 MiB) Downloaded 104 times
Re: L.TRIM always at -100 / Knock count question
And here another datalog from the same commute. This was 1 working day before the log above (and I had just reflashed my calibration before this trip).
I did some WOTs on this trip, and knock count was much higher.
I did some WOTs on this trip, and knock count was much higher.
- Attachments
-
- basemap +3psi ida a viamao.fpdl
- (7.76 MiB) Downloaded 87 times
Re: L.TRIM always at -100 / Knock count question
Our software engineer is looing into this.
Re: L.TRIM always at -100 / Knock count question
Ok thank you in advance.
And regarding the knock question, should I be worried or is it OK to run like this, with avg. 10 knock count in my commute?
And regarding the knock question, should I be worried or is it OK to run like this, with avg. 10 knock count in my commute?
Re: L.TRIM always at -100 / Knock count question
Don't worry so much about the knock count. Look instead at the knock level and try to keep the knock level down.
Re: L.TRIM always at -100 / Knock count question
You mean the k control? What do you consider a low value? Mine us usually in the range of 54 to 68%
Re: L.TRIM always at -100 / Knock count question
That sounds pretty reasonable.
Re: L.TRIM always at -100 / Knock count question
On this ECU the long term trim is not used so it will always show -100%. It is nothing to worry about.
Hondata
Re: L.TRIM always at -100 / Knock count question
Ok thank you for the information. Does my engine have any long term adjustment? Or does it rely only on s trim?
Thanks
Thanks