Pages: [1] 2
Author Topic: Complete N00b, Boost question  (Read 7201 times)
MetalForLive
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 82


« on: March 21, 2018, 01:07:59 PM »

Hi All,

I am a complete n00b, but I read a littlebit in S4wiki and in this Board.
So the first thing I have done, is remove the VMAX, that worked well, now I created a new file to enable left foot breaking and delete the rear O2 Sensors, cause on Weekend the Downpipes from my S4 become replaced by RS4 Downpipes without pre Cats. Also I set NMAX to 7000.
The File is ready to flash, but I will do this on Weekend after installing the Downpipes.

So now I read a bit in the S4wiki over Boost and also in this thread, too http://nefariousmotorsports.com/forum/index.php?topic=6695.90

But I didn't get very smart by this  Huh
If I understand that right, for a Stage 1 tune I didn't need any Fuel improvements.

For Boost I have to increase the LDRXN ?
But to which values ?




Can anybody help me with this basics ?
If there is anywhere a good tutorial it would be great, too.

I want to increase my Boost from 0,9 to 1,25bar without breaking anything.

Later this Year I will buy new Intercoolers and go to a professional Tuner for Money, but between this time a little bit extra boost would be nice.
Logged
MetalForLive
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 82


« Reply #1 on: March 21, 2018, 01:50:27 PM »

Oh, found a XDF in the above linked Thread where the Values from LDRXN are converted to PSI.
But I didn't know if I can use this XDF for my ECU  Huh
Logged
MetalForLive
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 82


« Reply #2 on: March 21, 2018, 02:46:20 PM »

So I used the Stage 1 XDF and configured the LDRXN like this:



That lookes in the normal XDF like this:



Is this okay ?

Did I have to do anything with ignition or can I use the File now ?
Logged
gman86
Hero Member
*****

Karma: +45/-128
Offline Offline

Posts: 705


« Reply #3 on: March 21, 2018, 08:55:20 PM »

So I used the Stage 1 XDF and configured the LDRXN like this:



That lookes in the normal XDF like this:



Is this okay ?

Did I have to do anything with ignition or can I use the File now ?

I felt myself about to start writing a wall of text, but I've settled on simply - read the S4Wiki. There's so many other things you'll need to adjust and take into consideration rather than just "requesting more boost".
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12233


WWW
« Reply #4 on: March 21, 2018, 09:48:46 PM »

Did you look at any of the community tuning threads?
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

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 experience.
MetalForLive
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 82


« Reply #5 on: March 22, 2018, 01:07:12 AM »

Yes I did, in this one: http://nefariousmotorsports.com/forum/index.php?topic=6695.255
And I think I am now a little bit smarter about that.

On Page 18 the User FlyBoy S4  write a summary what he has done.


He put NMAX to 7000 and NMAXF tp 7300, I undestand what this does and do the same.

Then he starts changing the Air / Fuel Ratio, I understand that, too but my Problem is, the Values looks very different, is that maybe a Problem from the XDF ?
When i look at the Values from FlyBoyS4, there are above the Pedal Positions with 50 , 60, 70, 80, 90, 97.5 and under it are the Air/Fuel ratios for the pedal positions on the different RPMs.
In my file it looks like that:



Then he starts to change some Values in KFZW and KFZW2, if I understand this right from S4wiki, then this are the Cam timings, does I really have to change there anything ?

Logged
MetalForLive
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 82


« Reply #6 on: March 22, 2018, 02:15:17 AM »

If I compare it with Stage 1 XDF to the Values from FlyBoyS4 you can see, his values begin at 50, mine start at 0.46 and only come up to 0.90
Also the RPM starts in my file at 600, then going to 240 and then going up from 1000 to 5280.0.


Logged
jimmcgee5
Full Member
***

Karma: +7/-7
Offline Offline

Posts: 201


« Reply #7 on: March 22, 2018, 02:56:12 AM »

the xdf you are using is not correct for your ecu bin file . that's why the numbers don't match up , you need to start at the beginning and  find out your ecu model number and the correct xdf for it ! .
Logged
MetalForLive
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 82


« Reply #8 on: March 22, 2018, 03:07:34 AM »

But that should be the XDF for my ECU.

Here are my ECU Infos:

Quote
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: ¸D0907551G  2.7l V6/5VT     G   0001


So it should be the 8D0907551G.xdf
I used the XDF from Nyet.
http://nyet.org/cars/files/defs/
Logged
MetalForLive
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 82


« Reply #9 on: March 22, 2018, 03:20:49 AM »

Is it possible that this is an failure in the XDF ?

Because if I use the 8D0907551G.bin from http://files.s4wiki.com/stock/ the lamfa tables looks like this:

Logged
_nameless
Hero Member
*****

Karma: +323/-449
Offline Offline

Posts: 2694



« Reply #10 on: March 22, 2018, 04:35:39 AM »

Try using the right map pack for the right file my god. How simple does this shit have to be spelled out people?
Logged

If you are in the market for a tune and would like the ease of downloading and flashing a dyno tested tune for a fair price check out https://instatune.sellfy.store/
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12233


WWW
« Reply #11 on: March 22, 2018, 12:38:47 PM »

Use the 551m bin with the 551m xdf and you'll be fine.

ditch g
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

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 experience.
MetalForLive
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 82


« Reply #12 on: March 23, 2018, 12:23:26 AM »

I read about Crossflash, but thats to hot for me, cause it is my daily driver.
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12233


WWW
« Reply #13 on: March 23, 2018, 09:42:53 AM »

I read about Crossflash, but thats to hot for me, cause it is my daily driver.


If you aren't comfortable switching to M you should consider staying stock.
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

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 experience.
MetalForLive
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 82


« Reply #14 on: March 24, 2018, 01:59:13 AM »

So I downloaded the stock M ECU and the XDF for that.
If I am looking only at the Boost Table, I see this is much lower than on the original G ECU.

Okay, I can go in the above linked Thread, where the Community started to create a tune and align it to this values.
But the Question for me is, what is also different to the G box ? Will that work without issues ?

If I understand that right, the most 2.7 ECUs can be crossflashed, only some A6 ECUs makes trouble and 512kb to 1024kb isn't possible.


I think, first I use my original ECU file and disable the rear O2 sensors, then I can replace tomorrow my Downpipes without problems and then I start to look at the M box.
Logged
Pages: [1] 2
  Print  
 
Jump to:  

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