|
nyet
|
 |
« Reply #15 on: January 23, 2026, 12:27:55 AM »
|
|
|
Yes, that wgdc makes zero sense.
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
Mike Tries
Jr. Member
Karma: +1/-1
 Offline
Posts: 34
|
|
« Reply #16 on: January 23, 2026, 02:39:56 PM »
|
|
|
Oh hey, I'm glad to hear from you nyet, and nice to meet you!
So yeah, I have a few binaries queued up and ready to go. I'm about to get blasted with a snowstorm here this weekend, so I'm hoping to get some logging done tonight and/or tomorrow before the snow ruins all the car fun. Hopefully, the changes I've made affect the tune in the way I expect them to, and I can work my way towards a better shot at getting the 70 and 80% linearization runs done right.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #17 on: January 23, 2026, 10:53:05 PM »
|
|
|
You're probably going to want to log more of the PID vars
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
grayjay
Jr. Member
Karma: +4/-1
Offline
Posts: 39
|
|
« Reply #18 on: January 24, 2026, 11:39:42 AM »
|
|
|
When ME7info is used to identify and setup RAM logging locations corresponding to the available data logging variables, ME7info does find most of useful variables for the ME7.5 8E0909518AK-0003 1037368072.bin being used for this and the stage 1 community tune tread. However, there is apparently an issue in ME7info such that it does not find and identify address for all the logging terms for ME7.5. Among the RAM logging locations missing from ME7info search of this and other ME7.5 .bins are the RAM locations needed to log the three PID terms; lditv_w, ldptv_w, ldrdtv_w (and also for some important torque intervention variables). These PID terms are exactly the three data logging terms needed to understand where to make PID adjustments to the tuned .bin in order to reduce boost over/undershoot.
Any suggestions for where/how to find the Ram Addresses for the 8E0909518AK-0003 1037368072.bin boost P,I,&D terms?;
lditv_w
ldptv_w
ldrdtv_w
|
|
|
|
|
Logged
|
|
|
|
Mike Tries
Jr. Member
Karma: +1/-1
Offline
Posts: 34
|
|
« Reply #19 on: January 24, 2026, 08:54:05 PM »
|
|
|
Good question, grayjay. What is returned on a log with those variables selected? Or is it more that they don't show up in the configuration file?
Nyet, are these the right variables to log? Do you know his to find them?
|
|
|
|
|
Logged
|
|
|
|
grayjay
Jr. Member
Karma: +4/-1
Offline
Posts: 39
|
|
« Reply #20 on: January 25, 2026, 12:21:05 AM »
|
|
|
The three PID terms lditv_w, ldptv_w, & ldrdtv_w are not present in the .ecu file created by ME7info (from any ME7.5 .bin file). ME7logger needs the addresses in the .ecu file in order to make the parameters available for logging. They cannot be selected for logging if they are not in the .ecu file. Similar inquiry for a different ME7.5 ECU discussed in following thread, the suggestions to disassemble the .bin file to find the address are way above my capability. http://nefariousmotorsports.com/forum/index.php?topic=21229.0title= |
|
|
|
|
Logged
|
|
|
|
Mike Tries
Jr. Member
Karma: +1/-1
Offline
Posts: 34
|
|
« Reply #21 on: February 01, 2026, 10:03:52 PM »
|
|
|
I went out and made a log. Due to road conditions, I wanted to cap speed, so I ran the test in second gear, while dragging the brakes a bit to load the engine. This usually produces similar results to running it in third gear. At the end of this pull, the boost pipe popped off, it's 10 degrees outside, and almost midnight... so this will be the best we can get for now, but I got to 5,700 RPM or so. That should be plenty to see what was going on in the lower RPM ranges where WGDC is too low.
Notably, I had been out making changes to KFLDIMX and other tables to see if any changes made any difference to the WGDC. Nothing that I did made any difference at all, including setting some pretty wild values (I was trying to see how those changes affected WGDC, or whether they affected them at all).
Is this being capped by something? Can you tell what it might be?
|
|
|
|
|
Logged
|
|
|
|
Mike Tries
Jr. Member
Karma: +1/-1
Offline
Posts: 34
|
|
« Reply #22 on: February 02, 2026, 08:55:03 AM »
|
|
|
I want to add that I pulled up VCDS and checked in on the mass airflow sensor readings. I replaced the MAF housing when I installed this turbo, and the cross-sectional area is 1.44 times that of the stock unit, so I multiplied everything on the MLHFM table by 1.44. This was the wrong move, and perhaps that's obvious to some of the guys reading this, but I might as well explain what was happening and see what you think.
With the larger MAF housing, the readings from the sensor would be lower than expected, causing the car to think less air was flowing than there really was, causing it to reduce fuel delivery, causing it to stall. Bumping this value got the car to run, and frankly, it ran well. It may have been the cause of one particular side-effect--when I drive the car after disconnecting the battery or flashing the ECU, for the first run up through the RPM, it will stumble and hesitate. I think it's resetting its fuel trims to correct the horrendously-tuned MLHFM table.
23 g/s at idle. That's what it was reading last night. Way too high--an order of magnitude too high. So, I kept the very highest value at 1.44 times, multiplied the very lowest value by 1.1 over stock, and interpolated the rest. Maybe there's an A6 tune somewhere (or something that this MAF housing came off of) that would have values I could just copy? Anyway, do you think this could be the cause of WGDC following such an odd curve?
|
|
|
|
|
Logged
|
|
|
|
fknbrkn
Hero Member
Karma: +219/-24
Offline
Posts: 1551
mk4 1.8T AUM
|
|
« Reply #23 on: Yesterday at 01:49:04 AM »
|
|
|
start with the fueling and hfm first and not mix it with ldrpid and others.
fill kfldrl with zeros for initial runs
set ndldrapu with 9999 to avoid underboost dtc
there is a software available here to calculate mlhfm with larger housing. only genuine bosch sensor would work here btw
another option here is to get tt225 maf sensor and copy mlhfm from it.
check the ps_w / msdk_w / mshfm_w at idle then at wot, fix air path first
then fr_w and trims
get your base boost
and only after make an approach to 'tighter wastegate' section at wiki
do not use gpt for that, absolutely waste of time here
|
|
|
|
|
Logged
|
|
|
|
Mike Tries
Jr. Member
Karma: +1/-1
Offline
Posts: 34
|
|
« Reply #24 on: Yesterday at 12:00:17 PM »
|
|
|
Yes! Agreed. I believe fuel is where we want it to be. Mass air sensor is a genuine Bosch unit--same one that came with the car. It's inside an Audi housing--just a larger one from a different car.
I found the tool, and I'm going to run it tonight to get MLHFM under control. grayjay pointed me towards it, and I'm grateful that it exists.
I'll follow the procedure you've outlined and see where it goes. Thank you for chiming in.
|
|
|
|
|
Logged
|
|
|
|
Mike Tries
Jr. Member
Karma: +1/-1
Offline
Posts: 34
|
|
« Reply #25 on: Yesterday at 03:16:31 PM »
|
|
|
Using ChatGPT was just a fun experiment to see what it was capable of. What's running on the car now has not been touched by ChatGPT at all.
|
|
|
|
|
Logged
|
|
|
|
|
