|
prometey1982
|
 |
« Reply #2445 on: December 28, 2023, 09:37:53 AM »
|
|
|
Unless the engine is highly modified it is a waste of time because stock map is already going to be tuned for best power at high rpm.
If the engine is not DI, low RPM won't be tuned for best power, but tuning it for best power will result in absolutely insane fuel consumption and cat fouling because you'll be dumping straight fuel into the exhaust.
In case of Volvo's turbo engines they are tuned not propertly from the factory. I ran on dyno with different VVT positions and stock intake VVT positions isn't optimal. They move from -25 to 0 too early. And in high RPM range they move camshaft also not optimal. Need more retard. Exhaust VVT maps which I posted also helps to add torque in low RPM range. Это чувствуется пятой точкой) |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #2446 on: December 28, 2023, 09:44:04 AM »
|
|
|
The reason is tradeoff between efficiency and power.
The more overlap you add on low RPM on non-DI engine the more fuel goes in the exhaust.
Also in your case as I understand engine is not stock - turbo is not stock.
The bigger the turbo is, the more benefit you have keeping advance for longer.
If you log EMP by adding a sensor and then empirically find the optimal advance, you will find that EMP and advance have a very strong correlation.
Larger turbo -> less EMP -> can advance longer.
|
|
|
|
« Last Edit: December 28, 2023, 09:45:41 AM by prj »
|
Logged
|
|
|
|
|
prometey1982
|
|
« Reply #2447 on: December 28, 2023, 12:34:07 PM »
|
|
|
Also in your case as I understand engine is not stock - turbo is not stock.
The bigger the turbo is, the more benefit you have keeping advance for longer.
If you log EMP by adding a sensor and then empirically find the optimal advance, you will find that EMP and advance have a very strong correlation.
Larger turbo -> less EMP -> can advance longer.
Engine is stock excepts intake manifold. Turbo isn't stock but I got similar results on stock turbo and stock engines on other cars. What does EMP means? |
|
|
|
|
Logged
|
|
|
|
paan
Newbie
Karma: +1/-1
 Offline
Posts: 3
|
|
« Reply #2448 on: December 28, 2023, 10:54:47 PM »
|
|
|
EMP – Exhaust Manifold Pressure
|
|
|
|
|
Logged
|
|
|
|
xM1ke
Newbie
Karma: +0/-0
Offline
Posts: 18
|
|
« Reply #2449 on: December 30, 2023, 06:28:11 AM »
|
|
|
If I change some values in my 50GPHJ bin in the following tables, the values in the table do not correspond to what I see in the logs. Can someone please confirm that the addresses for an EU 50GPHJ bin are correct:
KFLBTS
address: 19B5A (8 bit, HiLo, not signed)
rows: 23500 (16 bit, LoHi, not signed) - 12 rows
columns: 19C1B (8 bit, HiLo, not signed) - 16 columns
KFMDBGRG
address: 216E8 (16 bit, LoHi, not signed)
rows: 216C2 (16 bit, LoHi, not signed) - 12 rows
columns: 216DA (16 bit, LoHi, not signed) - 7 columns
|
|
|
|
|
Logged
|
|
|
|
keichi
Full Member
Karma: +11/-2
Offline
Posts: 105
|
|
« Reply #2450 on: December 30, 2023, 10:22:58 AM »
|
|
|
If I change some values in my 50GPHJ bin in the following tables, the values in the table do not correspond to what I see in the logs. Can someone please confirm that the addresses for an EU 50GPHJ bin are correct:
KFLBTS
address: 19B5A (8 bit, HiLo, not signed)
rows: 23500 (16 bit, LoHi, not signed) - 12 rows
columns: 19C1B (8 bit, HiLo, not signed) - 16 columns
KFMDBGRG
address: 216E8 (16 bit, LoHi, not signed)
rows: 216C2 (16 bit, LoHi, not signed) - 12 rows
columns: 216DA (16 bit, LoHi, not signed) - 7 columns
Addresses are ok. There is more to fueling then KFLBTS. There is also KFDLBTS (addition), LAMFA, ATR (addition), warmup-fueling, cat-heating fueling and so on. Mainly it's LAMFA. BTS, ATR but it depends on software version. |
|
|
|
|
Logged
|
|
|
|
xM1ke
Newbie
Karma: +0/-0
Offline
Posts: 18
|
|
« Reply #2451 on: December 30, 2023, 12:00:23 PM »
|
|
|
Addresses are ok.
There is more to fueling then KFLBTS. There is also KFDLBTS (addition), LAMFA, ATR (addition), warmup-fueling, cat-heating fueling and so on.
Mainly it's LAMFA. BTS, ATR but it depends on software version.
Thank you for confirming. In that case, I don't know what is going on as my BTS map (specifies 0.797 @ 183 load) is already a lot richer compared to the lambts_w value from the log here at 216 load. Shouldn't it be at least richer than my actual BTS map, because the addition can only add fuelling? What could be another issue causing this?  Also with regards to the KFMDBGRG map, the ECU does not seem to limit any load based on the gear according to the logs (the KFMDBGRG map limits the load based on the DRX, correct? So 70% of power means 70% of DRX at that RPM). |
|
|
|
|
Logged
|
|
|
|
|
prometey1982
|
|
« Reply #2452 on: December 30, 2023, 12:26:16 PM »
|
|
|
Also catalyst overheating protection can rich mixture. To disable it you should set CATR codeword to 0. CATR addr = 0x18A04
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #2453 on: December 31, 2023, 04:15:29 AM »
|
|
|
What could be another issue causing this? Lowpass time filter that limits rate of change for example. Btw always post logs instead of screenshots of some random tool. |
|
|
|
|
Logged
|
|
|
|
xM1ke
Newbie
Karma: +0/-0
Offline
Posts: 18
|
|
« Reply #2454 on: December 31, 2023, 08:39:13 AM »
|
|
|
I logged the car again and flashed the ECU with a weird oscillating BTS table just to see if changes have an effect - they do, but the targets do not translate 1:1 from the table to the log (e.g., requesting a minimum 0.81 lambda @ 6000 rpm through KFLBTS results in the ECU setting lambts_w to 0.84 @ 6000 rpm). Furthermore, even though my CWTATR is set to 0, the ECU seems to request a rich lambda on deceleration through lamsbg_w, which table would request something like this? Datalog: https://datazap.me/u/m1ke/log-31122023?log=0&data=2-21-24 |
|
|
|
|
Logged
|
|
|
|
rlinewiz
Jr. Member
Karma: +16/-1
Offline
Posts: 44
|
|
« Reply #2455 on: January 01, 2024, 08:47:27 AM »
|
|
|
Happy New Year!
Just wanted to drop by and say that. Not to go off topic, but it's been a little over a year now I've been reading this thread over and over just about every day, and I wanted to express my appreciation to you all for all I've learned. Because of this site, this thread, and the people therein, I've learned to do some pretty amazing things. I'm not going to go into detail but I'm working on some pretty deep stuff, and I remain committed to giving back to the community rather than using this info for profit.
Thank you all, and keep up the great work!
|
|
|
|
|
Logged
|
2005 S60R M66-Swapped // Self-tuned @ 22psi
[[forever coding for the OpenMoose project]]
|
|
|
xM1ke
Newbie
Karma: +0/-0
Offline
Posts: 18
|
|
« Reply #2456 on: January 02, 2024, 03:35:17 AM »
|
|
|
I am thinking my BTS fuelling is not working 100% because of cross flashing to 50GPHJ instead of changing the 50WRHJ the car came with from stock (I don't have the correct parameter log file to log on a 50WRHJ).
I flashed back to a 50WRHJ file and the car is driving much smoother. On the 50GPHJ file, the car had checksum errors in the ECM plus a not working rain sensor (for 9 months on the 50GPHJ file I had a not functioning rain sensor and now the minute I flash to the 50WRHJ file, its working again). I have no idea how the rain sensor and the ECU software are connected.
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #2457 on: January 02, 2024, 04:14:40 AM »
|
|
|
I am thinking my BTS fuelling is not working 100% because of cross flashing to 50GPHJ instead of changing the 50WRHJ the car came with from stock (I don't have the correct parameter log file to log on a 50WRHJ).
I flashed back to a 50WRHJ file and the car is driving much smoother. On the 50GPHJ file, the car had checksum errors in the ECM plus a not working rain sensor (for 9 months on the 50GPHJ file I had a not functioning rain sensor and now the minute I flash to the 50WRHJ file, its working again). I have no idea how the rain sensor and the ECU software are connected. I don't think that is the reason for the BTS fueling not working right, logging in more detail I am sure it can be easily found. That said, I have support for 50WRHJ in my logger if you want to go that route. |
|
|
|
|
Logged
|
|
|
|
daniel2345
Full Member
Karma: +11/-8
Offline
Posts: 200
|
|
« Reply #2458 on: January 02, 2024, 05:37:17 AM »
|
|
|
Please be aware, that since 50WRHJ new software versions are not named correctly. A different scheme is used to distinguish them.
There are at least four different versions of 50WRHJ with different software layout. And different diagnostic ids.
Best way in my opinion is to request or compare diagnostic id, which tells you which memory value is which diagnostic id.
Regarding BTS: there are some error paths which trigger different behaviour in fueling / BTS. They might got triggered in your cross flash environment. But what you describe sounds for me like cat protection or head protection which has a higher priority over BTS in Volvo files.
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #2459 on: January 02, 2024, 06:47:32 AM »
|
|
|
Please be aware, that since 50WRHJ new software versions are not named correctly. A different scheme is used to distinguish them.
There are at least four different versions of 50WRHJ with different software layout. And different diagnostic ids. On those ECU's where there is EPK present (search for /1/) you have to use the EPK to identify the ECU. But what you describe sounds for me like cat protection or head protection which has a higher priority over BTS in Volvo files. LAMKO is a minimum selector... |
|
|
|
|
Logged
|
|
|
|
|
