|
which calibration are you working with? I've only seen a couple of the 'switch testing' roms, so I'm not sure if there are little differences between them and can't necessarily guarantee your rom should be set up identically.
the timing/fueling hacks need to also be associated with the setup of which table is being used.
in this example, I'm using just the intelligent mode table, as any of the 'merpmod timing hack' tables are larger than the OEM sized tables. but I chose the first one and set it up to target those tables of each set that is enabled.
provided that you set up your table switching correctly and you have no intention of using the OEM tables, then yes, those tables could be ignored and/or zero'd out. for posterity though, I just paste as much of the size and data that the table will accept.
the 'VE' parameter through the logger isn't calculated in a way that makes it useful, IMO. making corrections to the VE table is primarily using fuel trim correction data, and using that data as a factor against the VE table.
for example, in the logging software I use, I have a few data filters set up, which means that it only accepts and uses data in the histogram field, that passes different filter conditions.
I have a filter for too much dynamic throttle change, a filter that rules out all data outside of closed loop, a filter for 0% accelerator pedal position, a filter for 0% IDC, and a filter for fueling status (used with vehicles like DIT WRX that indicate which fuel mode info outside of just CL/OL/WARMUP) that essentially covers all the overrun cells that might be effecting data gathered during engine decel, where fueling on the VE table would not necessarily want to be modified. an enrichment or lean condition might be because of x-tau/wall wetting, or overrun tables, or tip-out. in this example of filters, I get everything that's closed loop, that doesn't have too much tip-in/overrun/warmup or idle data. Only off-idle, cruise, and closed loop data is taken.
Unless your manifold air temp is at a constant temperature, and coolant temp is at a constant temperature while datalogging, and is also the same temperature as rolled into the constant that is the logging parameter for VE would have it be, using the logged parameter for VE as a 1:1 transfer to your VE table will have you running in circles. This is not the same thing as "MAF compensated VE" like you see in the DIT WRX. Here, IAT/load compensation / baro / primary enrichment won't effect the hard value of what the logging parameter states.
for closed loop, STFT + LTFT = total fuel trim, divide that by 100, and then add 1 to that value, and you get a correction factor (factor = multiplier) and you multiply that against the cell of the VE table that it corresponds to. for open loop, wideband afr divided by final fueling base is the correction factor for the VE table cell. also for open loop, I offset the logging data by the wideband latency difference to the upstream (distance/exhaust velocity related) which can be figured out roughly using data from initial WOT and accelerator pedal movement from full to none, and how long it takes both the sensors to register changes, and the difference between them. it's usually sub 300 milliseconds, I tend to use about 200 to 210ms, which can be three or four polls. In the software I use, it compares FFB with the wideband data offset by three lines of data.
on the flipside, I use a filter that removes data where there isn't dynamic throttle change (change over time that exceeds movement percent values) and this data is used for tip-in, along with data for tip-in comps like IAT, ECT, and boost error. As a side on tip-in enrichment, using any of the 2016+ USDM STI boost error table as a starting point, and then getting your target boost table to accurately reflect what the motor is doing, and getting it better than 2 psi of boost error, will have your throttle response singing, and your erroneous fueling data simmered down.
| Attachments: |
File comment: setting up table switching
here, I only want to use set Intelligent 1 for each hack section that is enabled. (boost, timing, fueling)
image_2022-06-04_021406517.png [ 129.05 KiB | Viewed 736 times ]
|
_________________
if you're generous, feel free to donate.
venmo @ jon7009, 1047 when asked
jedilley@gmail.com for paypal
|
