NefMoto

Here are some auto generated files.
They don't contain everything, not everything is correct, etc.

But they can be something to work from.
The way I generated these is by using region matching, and feeding the parser existing .kp and matching .bin files.

Approximately 2700 maps/constants in each file.

Fantastic files, thanks for sharing. Any chance on the same files for 557N? What tool are you using for the matching, some sort of Regex?

Phenomenal work, prj

I am using region based matching and searching for equal data...
Basically trying to find data that is exactly the same between two tunes at a minimum length and then extending around that area until non-equal data is hit.

It does not always work out, there are some guesses made, etc, but it can still reduce the manual labor by quite a bit.

That's awesome.  You are doing the pattern-search equivalent of a radial basis kernel in statistical learning theory.  So cool man!
Let's keep this energy going here.  Is there someway to re-group these like in Nye's XDF file by group?  How about the descriptions, can we make a master table and edit the German to English?

Bigger picture, have you been able to compare the K-box and M-box table intersections?

I don't really think there is any point grouping.

The way I work is I generate a such file, then start hand editing it.
I have everything ungrouped, except for the items that I am using to tune. I group those logically for myself.
So basically I move ungrouped items into grouped.
And the grouping is just to have an overview anyway, when I edit a parameter, I always use search.

I don't really care much for M-Box myself.
No idea why people tend to be so fond of it. There is no definition available, so you might as well work from the G-Box for example.
It's like some sort of "follow the pack" mentality.

I have not tried flashing a M-Box to K-Box yet, but if that's possible, then I don't see any point to use anything other than K-Box :)
If someone wants to work on it, I can post the source of the thing. But I pretty much don't plan to make any enhancements to it as it stands now.

The m-box is only popular because its the only relatively late box with a definitions file.

That definitions file exists (and is public) only because I made it (and made it public), and m-box was what I started working with (because I didn't know any better). Everybody else was busy playing secret handshake games and "omg I can't tell you anything because i spent so much money and you're a noob and blah blah blah"

If I could do it all over, i'd have done it with k-box.

If anything, the fully spec'd definition files make learning hard, because of the # of maps.

If somebody makes a pared down def file, with the "important" maps, you can bet that will be popular.

I agree, there is nothing fundamentally special about m-box itself.

It really only comes down to map pack availability.

I am thinking about taking your def and making a pared down k-box map pack and converting.

problem is, i need it all in a .kp :/

any progress in making a xdf->kp converter? :)

It's not only you who uses the M-box. There are quite a few tuners in the US who are using M-box as well for some reason.

I will let you in on a little "secret" as to why you /should/ use K-box. 16 bit load axes. Meaning no stupid 190 load limit in any of the important maps. No underscaling of LOAD.

Haven't tried....

There were only two choices in the US before the g-box damos leaked - H or M (for stage 1)

IIRC APR started with F/K when they went to K04s, but they made the least amount of power, and the most aggressive tunes (stage 1, 2, 3, and homebrew) and were M-Box based.

The rest is inertia.

Pro tuners, as you know, are lazy. They had base files and saw no good reason to start all over with another box.

xdf -> a2l should be the more easier way?! ;)

is there an a2l spec?

i would like to know also.
today I stuck with a newer version of vectors asap2 Editor/viewer that is now able to read in some older .a2l files with certain syntax of IF_DATA without begin and and structures... :(

Hey prj, do you (or anyone) by chance have a K-box 95040 dump that you could post/send me?

Posted from Thomas here:  :)

http://nefariousmotorsports.com/forum/index.php?topic=2308.0title=

Yup, posted when I messaged him about it.  Him and prj have been great resources for me today, as I try to go to a K-box tune.  They both have helped a ton.

Assuming all goes well, will your pending release of a working k-box tune require a boot flash?

I don't know yet, I'm going to try with an M-box EEPROM first.  And I wasn't necessarily intending to release my file (as no one would really want it, considering I've got a HPS PMAX MAF sensor, GT turbos/external wastegates, 1000cc injectors, I'm likely to run 5 or 6 bar base pressure, etc). I'll definitely let people know how it goes with getting it to work on an m-box car though (but that'll happen when I get time, so don't hold your breath).

You've studied the RS4 bins a ton though, so I'm hoping you'll make the switch as well, so we can chat about the tuning differences :)

I doubt it is significantly different... if anything, it is probably WAY easier.

I'm already using a lot of K04 PID and ARMD maps, plus stupid tweaked load axes.

I can't wait to make the switch!

I know the differences will be subtle, but I'm glad that you (and possibly others) are going to switch as well so that we can chat about those subtle differences (like different map dimensions, slightly different stock values [probably closer to where we would modify them to anyways], different cam changeover, etc).  I'm curious to see how my cam switchover notch will look with this file as a basis.

Absolutely, I fully intend to move to the K-box, just making sure I have no down-time.  Believe it or not I daily my beast...  :)

Understandable, my car is my daily driver, main means of transportation, and only running car right now ha.  That's why I'm going to do this K-box business on a spare ECU I have, so any issues and I just pop my other ECU in.

actually, it looks like i may use the Q-box :)

http://nefariousmotorsports.com/forum/index.php?topic=2305.msg21665;topicseen#msg21665

the biggest problem will be to get the ram locations for all the various things i've added to ME7 logger :/

the q-ship lives?

nyet, don't you think setzi's me7 logger command line prompt executions should get the complete list of variables?  can we involve him in this discussion somehow?
the airbox flap maps will need modifying for most people...  luckily RS4Boost unraveled that secret a few weeks ago.
was it prj that enabled the launch-control modification?

It will find most of the variables, but none of the ones I added on for mbox logging

Added a list of the known 551K/Q RAM variables here:

http://nefariousmotorsports.com/forum/index.php?topic=2306.0title=

and informations about disassembled RS4 air flap function here:

http://nefariousmotorsports.com/forum/index.php?topic=2283.msg21675#msg21675

This XDF needs alot of user-originated organization.  I'm working on it now;  we need to accelerate this community change-over.