RomRaider

Since installing my WBo2, my tuning interest has spiked. Unfortunately, I've noticed that my AFR also spikes. To 12 to be exact.
A lot of things happen all at once at this moment.

Attached is a log of 3rd then 4th gear pulls. Apologies if their quality is low. Any tips on better logging would be appreciated.
Unfortunately, due to technical difficulties (my patience) I didn't log WBo2 sensor.
I've included Primary Open Loop Map Enrichment for reference VS Final Fueling Base.

It seems to happen right after the "rich dip" described in (viewtopic.php?f=40&t=7442 )
I have applied changes to "Tau Input A Rising Load Activation A" and "B" which seems to have fixed (at least in this log) the issue in 3rd, but not 4th gear.I have only logged one 3rd gear pull.

It coincides with overboost. Second attached log is from earlier this year. Target boost, turbo dynamics, wastegate, WBo2 included (in lambda, sorry).
You can see the moment of FFB spiking, coincides with Some funky wastegate business.

I'm struggling to work out what is going on here. What is coming first and what is causing what.

Car is ADM Liberty GT Spec B. A2UG002T
Process West Top Mount, Process West CIA, id1050x, parallel fuel rails, FPR, ATP Sti Silver Ball bearing turbo (very similar to GTX3071), TGV deletes, 3" catted turbo back exhaust.

Any insight would be hugely appreciated!

are you logging on the sd card to the openport? unfortunately, your logging speed/polling rate is too low to really use for any of the fueling relationships you're looking for.

case in point, the duration of time between polling to two fueling bases which would be identical if polled at the same time, come out as different amounts because of the amount of time (in milliseconds) between the two items being requested.

ideally if you were fast polling on ssm k-line you would get three to five times more data per second.

ideally you don't want to log too many things, which you're not, but whatever you're using isn't really going to be good enough for what you want.

BtSSM works well, and so does romraider logger from laptop/notebook, when you set it to fast polling.

also, the more 4 byte parameters you log, the slower your polling speed. try to pick a 2 byte parameter whenever possible.

logging two final fueling isn't necessary, but if you're logging wideband and fueling, they should probably be in the same base scale. (lambda or gas AFR) to make the conversions easier.

My clutch went boom.

So things are on hold, but thanks for the reply. I'll get some better logging done when I'm back on the road!