|
littco
|
 |
« Reply #60 on: June 12, 2012, 12:53:16 AM »
|
|
|
Getting back a little on track, Nice work.
I have a question and please excuse me if ive missed something. So using the original HN winols file you posted where abouts do I find the new LDRXN that changes as you select the mode you want?
I understand that is now, with the new coding a 3 axis map with the 5 selections being the new Z axis but is it possible to view and change those maps or are they the original LDRXN but with a multipler added to them to increase the load values?
I use tunerpro pretty much for all the stuff I do as it's easier for me, but obviously as far as i know it can't display 3 axis maps.
I have recently done a stage 2 tune on an HN and would love to try this on it as it has CC but would ideally like to put the LDRXN/k maps I have on there.
|
|
|
|
|
Logged
|
|
|
|
rajivc666
Full Member
Karma: +23/-2
 Offline
Posts: 127
|
|
« Reply #61 on: June 12, 2012, 01:26:35 AM »
|
|
|
Each time a map is selected a counter in the ecu RAM goes 1,2,3,4,5 and back to 1. That forms the Z axis, so depending on the counter the particular ldrxn 2D map is selected. You can clearly see it in winols. Also I have posted a tunerpro definition for I think the s4, you can go through that.
|
|
|
|
|
Logged
|
|
|
|
|
littco
|
|
« Reply #62 on: June 12, 2012, 01:50:14 AM »
|
|
|
With regard the address step in the XDF you did for the S4 it needs to be set from -4 to 2 for all 16bit lohi entries and from -2 to 1 for all the 8bit enteries. then you can save it and it will stay saved.
I've attached a copy.
So with the s4 one if I changed the valves in each line, getting progressively larger, ie more load, then when I select 1,2,3,4,5 I will get the LDRXN for that line which then becomes my new LDRXN?
And with regards the HN, I have a XDF for the HN if I where just to add the 4 extra lines to the LDRXN and LDRXNK in my XDF that would then become my new multimap..
I'm very impressed I have to say, I will definately be implementing this into my s3
|
|
|
|
« Last Edit: June 12, 2012, 01:57:06 AM by littco »
|
Logged
|
|
|
|
rajivc666
Full Member
Karma: +23/-2
Offline
Posts: 127
|
|
« Reply #63 on: June 12, 2012, 02:04:42 AM »
|
|
|
The ldrxn and ldrxnzk in default location is ignored. Another 3d map is created somewhere towards the end of the file , you can compare the stock file towards the end and you will find the 3d, ldrxn & ldrxnzk
|
|
|
|
|
Logged
|
|
|
|
|
littco
|
|
« Reply #64 on: June 12, 2012, 02:08:55 AM »
|
|
|
Got it.
|
|
|
|
|
Logged
|
|
|
|
rajivc666
Full Member
Karma: +23/-2
Offline
Posts: 127
|
|
« Reply #65 on: June 14, 2012, 08:18:02 PM »
|
|
|
Hi, for sometime I have been thinking about a passover( overtaking) switch, when acc= 100% and we press cruise button the ecu gives max available power for say 30 seconds, since its only limited time ( it can be deactivated for say other 30 secs) we dont have to think of component protection and may be open-loop boost ( this i am not sure). Think would be very fancy like NOS  . The custom code will track the modeled temperature and deactivate this mode if it exceeds certain safe values. Any takers. |
|
|
|
« Last Edit: June 14, 2012, 08:33:56 PM by rajivc666 »
|
Logged
|
|
|
|
|
vwaudiguy
|
|
« Reply #66 on: June 18, 2012, 01:22:35 PM »
|
|
|
That sounds like it could have some potential
|
|
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
|
littco
|
|
« Reply #67 on: June 29, 2012, 03:10:34 AM »
|
|
|
Could some check over this XDF for the 06a906032HN please.
I'm not sure the LDRXN is correct as I seems to have 5 maps
|
|
|
|
« Last Edit: June 29, 2012, 03:18:26 AM by littco »
|
Logged
|
|
|
|
Nottingham
Full Member
Karma: +13/-1
Offline
Posts: 204
|
|
« Reply #68 on: June 29, 2012, 01:22:04 PM »
|
|
|
Hi, for sometime I have been thinking about a passover( overtaking) switch, when acc= 100% and we press cruise button the ecu gives max available power for say 30 seconds, since its only limited time ( it can be deactivated for say other 30 secs) we dont have to think of component protection and may be open-loop boost ( this i am not sure). Think would be very fancy like NOS . The custom code will track the modeled temperature and deactivate this mode if it exceeds certain safe values. Any takers. The ME7.5 seems to have some kind of overboost function by default. KFLDRXO map specifies the air charge delta (added to LDRXN) and the sample points (rpm). There is also a value which specify the time the overboost is active, etc. By default the delta is set to: ~0,0825bar (8,25%) @ 3000rpm ~0,1275bar (12,75%) @ 3520rpm ~0,1350bar (13,50%) @ 4000rpm ~0,1125bar (11,25%) @ 4520rpm ~0,0675bar (6,75%) @ 5000rpm Only if someone would find a way to enable it  |
|
|
|
|
Logged
|
|
|
|
infinkc
Full Member
Karma: +6/-1
Offline
Posts: 94
|
|
« Reply #69 on: July 02, 2012, 02:50:12 PM »
|
|
|
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #70 on: July 03, 2012, 02:42:32 AM »
|
|
|
Maybe Rick can comment what he uses for moving the tacho needle. RaraK mentioned, that writing nmot_w might be enough. I guess I can test, but asking never hurts. It would be nice to have that feature for setting the launch control limiter. For manual tune switching it's not that useful IMO, as are 5 different settings... Manual tune switching is also only useful for valet mode or different fuel IMO, I am much more interested in using one of the rear O2 inputs to create a failsafe for meth injection. |
|
|
|
« Last Edit: July 03, 2012, 03:36:14 AM by prj »
|
Logged
|
|
|
|
trichard3000
Full Member
Karma: +6/-1
Offline
Posts: 57
|
|
« Reply #71 on: July 24, 2012, 12:20:56 AM »
|
|
|
I'd like to breathe a bit of life back into this thread. I live in a city where premium is 93 but I frequently drive to another city that’s 250 miles away where 91 is the typical premium. I’d love to build a three-way tune with stock, 91 and 93 tunes. I’ll be in a position to test the map switching capabilities in a couple of weeks (as I’m traveling with my car now) but in the meantime, I’m going to use TunerPro to start building some test bin’s that patch in some of the base stage 1/2 maps that are available in other base files. I’m starting with the following files: rajivc666’s WinOLS (Audi S4 (mboxmultimap) - 360857).bin - 4/18/2012 version Littco’s s4.xdf – 6/12/2012 version After digging through the thread, here’s how I think that this is supposed to work. Please let me know if this is right or wrong: - - There are three groups of settings available, each group contains settings for LDRXN and LDRXNZK (Boost/Max load), KFZW and KFZW2 (Timing), and KRKTE (Fueling)
- - For LDRXN and LDRXNZK, the original single row tables are ignored. They’re each replaced by a table with three rows, one for each setting group.
- - For KFZW, KFZW2, and KRKTE, the original locations are used for group 1 (Paired with the first line of the new LDRXN/LDRXNZK tables). Settings for group 2 are found (as per the S4.xdf file) at 2KFZW, 2KFZW2, and 2KRKTE, likewise with group 3.
- - The driver cycles through the groups by having the accelerator pedal pressed and tapping the brake at the same time. The MIL light will flash the same number of times as the selected group.
One question: Using the general M-box xdf (8D0907551M-20120516.xdf), TunerPro shows the original KFZW/KFZW2 with load on the horizontal axis and RPM on the vertical. With the S4.xdf file, the original tables aren’t mapped but the group 2 and 3 versions show the axes reversed. This may be a noob question, but is this just a difference in the way the xdf displays the underlying data, or are the values actually stored in memory differently? If so, does it matter? Thanks! |
|
|
|
|
Logged
|
|
|
|
|
littco
|
|
« Reply #72 on: July 24, 2012, 03:51:59 AM »
|
|
|
Underlying data is exactly the same, the axis in tuner pro can be changed round if you wish, just copy all the settings from x > y and vice versa and then switch the table from column to row and it will show it the other way round. Only reason this happens is that in the past I've just copied the values of the available winols file and these can change from file to file, so some have the RPM on the x axis and some on thè Y axis. Makes absolutely no difference to the .bin file though as it saves it all in the correct place, just your preference on how it reads.
|
|
|
|
« Last Edit: July 24, 2012, 03:54:19 AM by littco »
|
Logged
|
|
|
|
|
jibberjive
|
|
« Reply #73 on: July 24, 2012, 06:06:03 AM »
|
|
|
Starting hopefully next week I'll be able to do some M-box testing as well.
|
|
|
|
|
Logged
|
|
|
|
trichard3000
Full Member
Karma: +6/-1
Offline
Posts: 57
|
|
« Reply #74 on: July 25, 2012, 12:07:47 AM »
|
|
|
I went ahead and merged Littco's TunerPro XDF with the current, standard M-box one. (8D0907551M-20120516.xdf) This should make it a bit easier to start playing with various tuning options.
All of the normal M-box parameters are available with the following changes:
I created a new Parameter Category called "Multimap Specific." There are three subcategories matching the categories of the original parameters: Boost rlmax, Fueling, and Timing.
I renamed the Multimap parameters with these names:
Boost rlmax: LDRXN_GRPS1-3, LDRXNZK_GRPS1-3
Fueling: KRKTE-GRP1 (Orig. KRKTE), KRKTE-GRP2, KRKTE-GRP3
Timing: KFZW-GRP1 (Orig. KFZW), KFZW-GRP2, KFZW-GRP3, KFZW2-GRP1 (Orig. KFZW2), KFZW2-GRP2, KFZW2-GRP3
I changed the orientation of the KFZW/KFZW2 tables to match the standard XDF and I also removed the entries for the original LDRXN and LDRXNZK, which should now be ignored.
This is my first shot at tweaking XDF's so please use at your own risk and feel free to point out any issues.
Thanks!
|
|
|
|
|
Logged
|
|
|
|
|
