Pages: [1]
Author Topic: first time tuning. mk4 12v VRT.  (Read 6822 times)
beetleboosted
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« on: April 20, 2016, 10:43:58 PM »

Aight...  to kind of introduce myself, i've lurked and learned LOTS of stuff over the past year or so with things besides actual tuning.  A close friend of mine has a '01 GTI, AFP 12v VRT, 5 speed.  he did a moderately budget minded build on it with a T3/T04e.  Its got all necessary maintenance and such done, so none of that should be an issue.  WOT it spools pretty nicely by about 3k rpm.  running 8-10 psi.  It currently has software on it from a popular tuner that sells their work via social media.  i'll refrain from naming unless necessary.  To put it politely, it runs like garbage, and the tuner doesnt seem to want to support it...  My mission: write a proper tune for it so that it runs like its supposed to. 

i found a proper stock file and xdf here, and thats what ive used so far:
http://nefariousmotorsports.com/forum/index.php?topic=4620.0

I have the demo version of Winols, but would prefer not to use it if possible, as i'm far more familliar with Tuner Pro. 

i was able to set KRKTE via "cheat number" to what seems to be pretty close to necessary for his injectors.  440's @ 4bar. 

i also did some work to MLHFM to try and get the MAF readings proper. I first tried to scale it using mafadjust, from the stock 70mm ID (best of my measurable ability) to a 83mm ID 2.7t MAF housing.  it ran OK (no boost), but not quite like it should.  CFM readings seemed to be exceedingly high for the given RPM range, and the MAF would exceed range and shut off with any more than about 4k rpm (again no boost) so i just started taking stabs into the dark for scaling, with little to no luck.  i then tried to scale it to the 4" MAF housing and stock sensor that he's been using.  scaled from 70 to 96mm, and it ran mediocre, but very rich.  On a whim despite knowing it would probably be WAY off, we stuck the 2.7t's sensor (Bosch) in the 4" housing, didnt change MAF table, and it idles properly at about 14-15:1 AFR...  it actually ran quite nicely overall and had decent low rpm/load/boost drivability.  light pedal input and low boost, like a lb or two, it would stay around 13:1-ish, which seemed acceptable all things considered.  but... high rpm it would still exceeded MAF range and kick off the MAF, and confuse everything.  one major hiccup with that particular setup was that ignition timing seemed to be a good bit off as well, but i dont remember what the readings were.  Timing tables have not been touched.  i want to get MAF and fueling proper before i poke at timing, etc. 

so...  Here's where im asking for help...  if someone could give me some insight as to what i might be doing wrong, MAF scaling or otherwise, as well as some suggestions on what else would benefit from changes.  Also, the definitions dont seem to be right on a few things. the tables are there, but the locations seem to be incorrect. 

i've read a lot, but not everything, and im not completely clueless as to what i'm doing.  ive just not come across any other posts with something similar for me to go by and get a good "running go" with.  plus missing a few critical tables is hindering progression. 

if things attach like i expect, you'll find my various bin's, the changelog of whats what, and my xdf. 
Logged
Carsinc
Sr. Member
****

Karma: +17/-2
Offline Offline

Posts: 447


« Reply #1 on: April 20, 2016, 10:53:17 PM »

Do you have any logs, if not ok. Ok what maf do you want to use?
One option would be to use that S4 maf and just borrow the maf data from a S4file
I find that works better, but please get rid of some timing.
Logged
beetleboosted
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #2 on: April 21, 2016, 01:18:35 AM »

Do you have any logs, if not ok. Ok what maf do you want to use?
One option would be to use that S4 maf and just borrow the maf data from a S4file
I find that works better, but please get rid of some timing.

Again, please keep in mind that this is my first time ever to poke at values and stuff it in a car...  Starting with what I assume is a stock file.

I don't have any logs yet. I have legit VCDS, but my laptop is currently unavailable. I've been adjusting with TunerPro, and flashing with my desktop, bench harness, and MPPS. The info we've watched so far has been from a wideband AFR gauge, and a OBD2 Android app the car's owner has set up, I wanna say it's Torque...??  Maybe...

I am perfectly content with using the S4 MAF. I tried to find a 2.7t file to pull the MAF table from in the first place, but didn't have any luck with anything that had definitions I could read. It likely exists, I just couldn't find it...

"Please get rid of some timing..." I appreciate the input, but more information than that would be appreciated. Again, this is my first time, and the xdf doesn't seem to be fully defined, so I don't know if offsets and all for various things are even correct.
Logged
_nameless
Hero Member
*****

Karma: +342/-466
Offline Offline

Posts: 2802



« Reply #3 on: April 21, 2016, 02:45:50 AM »

load hacks is the only correct way to do na>fi. Without a properly modified file no matter what it's going to run like shit. Me7 ecus are load request you can not just add boost and fuel and adjust timing don't work like that. I give you credit for attempting yourself but you have so so much to learn before you tackle something like a vrt conversion. First and foremost logging. Vcds broad rate is too slow to see exactly what's going on and you can only log 3 variables at a time. Find me7 logger floating around the forum and figure out how to take proper logs. Second read the s4 wiki (again). I have done a few vrt's so if you have any further questions feel free to pm me
« Last Edit: April 21, 2016, 02:52:39 AM by Marty » Logged

Giving your mom a tuneup
Carsinc
Sr. Member
****

Karma: +17/-2
Offline Offline

Posts: 447


« Reply #4 on: April 21, 2016, 06:59:41 AM »

Listen to what Marty said, ME7logger will be your friend. I honestly can tell you I could not take you the full distance
with this file as it will be above my paygrade but there is alot of good info and good people here that could. My intenet was
to get you going on the right track so someone else could step in a help. 
When I said get rid of some timing I meant pretty much just that I dont know how much (again Logging) but leaning on the knock
sensor to keep your motor from blowing up is not a good move. Since we are still messing with the maf have you relocated the IAT
to somewhere after the intercooler? this will help with timing and is often over looked by even the best tuners.
Logged
vwaudiguy
Hero Member
*****

Karma: +53/-37
Offline Offline

Posts: 2024



« Reply #5 on: April 21, 2016, 08:37:29 AM »

load hacks is the only correct way to do na>fi.

Can this only be done in ASM?
Logged

"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #6 on: April 21, 2016, 08:48:43 AM »

You have the source code and a compiler?

You *might* be able to compile snippets of c into asm, but you'll still have to had patch stuff in, and probably do tweaks to the resulting code.
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please 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
beetleboosted
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #7 on: April 21, 2016, 09:13:18 AM »

load hacks is the only correct way to do na>fi. Without a properly modified file no matter what it's going to run like shit. Me7 ecus are load request you can not just add boost and fuel and adjust timing don't work like that. I give you credit for attempting yourself but you have so so much to learn before you tackle something like a vrt conversion. First and foremost logging. Vcds broad rate is too slow to see exactly what's going on and you can only log 3 variables at a time. Find me7 logger floating around the forum and figure out how to take proper logs. Second read the s4 wiki (again). I have done a few vrt's so if you have any further questions feel free to pm me

My thoughts were to get the MAF set right so it didnt shut down, and then poke at fuel maps and have it richen as necessary in high rpm's to compensate for boost, and adjust timing as well for the same conditions.  it might not be completely right, but literally ANYTHING would run better than it does now.   the v1.3 file i uploaded in my first post runs leaps and bounds better (without boost) than the tune he paid for...  v1.3 starts and runs effortlessly.  the other tune, after resetting everything, it lean detonates and whatnot until LTFT's kick in and richen up everything.  its horrendous. 

Could you point me in the direction of said load hacks and/or a proper file/definition to work with?  I'm not asking for a free tune.  If i had a proper file set up as needed to start with, I'm pretty confident that i could figure it all out. 

me7logger is on my to-do list, but i have to get my hands back on my laptop first.  long story... 

Listen to what Marty said, ME7logger will be your friend. I honestly can tell you I could not take you the full distance
with this file as it will be above my paygrade but there is alot of good info and good people here that could. My intenet was
to get you going on the right track so someone else could step in a help. 
When I said get rid of some timing I meant pretty much just that I dont know how much (again Logging) but leaning on the knock
sensor to keep your motor from blowing up is not a good move. Since we are still messing with the maf have you relocated the IAT
to somewhere after the intercooler? this will help with timing and is often over looked by even the best tuners.

I greatly appreciate any help. 
to my knowledge KFZW is untouched and stock.  i'm aware that depending on the knock sensors isnt a good thing, but it works to just make it run...  I have been more worried about trying to get MAF and fueling figured out.  everything ive read, it all says to poke at fuel first.  so that was my next step once i got the MAF set right.  make basic things in the file match the hardware in use, and then tweak from there   and besides that, from what i remember KRKTE was the only fuel related thing that was properly defined, so i cant poke at anything fuel related, besides injector scaling.  more reasoning why i came here looking for help. 

Daz (RIP) suggested we put a 1.8t IAT somewhere.  the current setup is a "tacotaco" 1.8t intercooler.  its not completely efficient, but its better than nothing.  a FMIC is planned in the future.  the IAT is currently stuffed in the MAP sensor location in said intercooler, is wired as necessary, and does seem to read proper temps.  none of which was suggested by the original tuner... 
Logged
beetleboosted
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #8 on: April 21, 2016, 09:14:54 AM »

You have the source code and a compiler?

You *might* be able to compile snippets of c into asm, but you'll still have to had patch stuff in, and probably do tweaks to the resulting code.

i speak computer, my day job is an IT guy, but that stuff is above my head. 
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #9 on: April 21, 2016, 09:51:47 AM »

Then likely hacking NA to FI w/o standalone isn't gonna happen...
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please 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
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.024 seconds with 16 queries. (Pretty URLs adds 0.001s, 0q)