NefMoto

Hi!

I'm not sure when it was that I first decided that men were for me. I think it was summer camp, 2001. We were going through a bit of a hot spell, and being a young, strapping boy I was always out and about getting into trouble. I'll never forget when I first saw him, hair glistening in the late afternoon sun. I wasn't sure what to do, as I was still relatively new to sexual experimentation. Up until this point my only experiences had been with cattle, and the occasional sheep. I found out from a few friends that he'd be attending summer camp here, and I hurriedly signed up myself.

This is the story of how a boy became a man. More to follow.

Thanks :)

Also, what I'm looking for, is do tune the same car from 150 hps to about 190-200 hps in full stock contition.
I can add my original file here, please, can someone check it, on some points I see that the axis is not right,
maybe it's right for the ecu, but not for human eyes :D

Or if someone can help me with already tuned file, i would be really thankfull.
Just want that all makes sence to me, would be great to compare my orig. file and fine tuned file.

Best wishes to all ;)

And the original file:

Audi A4 B6 1.8t 2002 AVJ FWD 8E0909518M 0001

 

Or maybe someone can help with *.xdf file ?
Just want to get stock chiptuning done and see how the car performs,
next year will get bigger turbo, injection, catback, inlet and want to
be sure that the engine is worth the effort.

Just a pic of my B6 new headlights :)

Ok, let's speed things up, first one, who gives me the working file
as requested above gets 30 € !!!

nmot_w is a RAM cell dude @ 0x00F89E

Unfortunately, I don't think that is what he is looking for. He's looking for the RPM axis location for a map

Unfortunately, he doesn't realize that the axis location has nothing to do with the RAM location of nmot_w

I know that but the answer was there in my answer to be fair lol, define nmot in iDA and xref/locate axis, done.

Yes, I was looking for the RPM axis for the map, because in one file the
axis lines up and in other file the axis isn't there, although the map data
is right there.

There's no data in this place...?

It's only there when the ECU is running in the car mate, the maps reference this spot for the axis input.

Unless some kind person knows where the axis is disassembly is required to find it.

Some axis can be miles away mate, some right there as you say.

If you PM me all the info via drive or dropbox/whatever I'll do it since I can lol and have a small amount of time now.

It is a RAM location, not a MAP location. You are very confused.

I am hoping to resolve at least his confusion about axis locations vs. actual running data location here and not via PM.

One more time: the contents of the RAM location are looked up in the axis table.

There is only one RAM location for nmot_w, but there are many, many, many different axis tables that use nmot_w.

And how can I specify that place to show up and to use it?

Yes, I understand u...thats's why there are many exises wrong, thats why I need to know how to get them right.

Two primary methods:

1) Start with a fully defined file similar to yours and look for patterns
2) disassemble the binary

OK, I'll try :)
Thanks

So, there are more than one RPM axis? I see different maps using different RPM axis addresses...why?

There are over 5000 maps. Every map has a different function. They may want different axis setups

No shit Sherloc

If nmot_w uses only one RAM place from ecu and is used as the RPM axis, why every other map isn't using the same RPM axis?

For example I belive that the KFMIRL rpm axis is the nmot_w, but in other hand for the KFZW/KFZW2/KFDWSZ and
for the KFZWMN is another rpm axis...why is it so?

I think that RPM's are rpm's nomather in which map they are...well, something makes a little sence,
we may need a different rpm's for a different map...for some it's ok to use like 480/780/1200/2000 and so on,
but for some we need 0 and smaller numbers...
was it close?

Jesus, I'm out, what a farce lol.


OP - read the FR and you'll see in the diagram where nmot and nmot_w come from and how they are used in say BBGANG can't miss that one in IDA lol.

Also the wiki read that.

I already told him this, and yes I would of course of posted it once I had the axis location, but omfg this thread sucks a$$.

Thanks, whats the FR?

I'm ------------><------------ this close to nuking this thread

Really surprised you didn't after the sherloc comment.

There's a little humor left in the world :D

To get it back on track:

1:  There is no PM carry on as you might have thought, I had little time then was out for hours to come back to that.
2.  I've PM'd him a drive link so he can upload everything.
3.  I'll post the axis location if he does and if I have time when he does.
4.  I think the newb section people should be able to grasp how a processor works and some basic ANSI C would help
5.  I'll try and explain it all then you can clean it all up?

Right OP disassembly ready, send me ze info!

Map packs and map names and which axis you need etc

Ok, thank you everyone for helping.
I figured it all out by myself. It makes berfect sence now.
You can delete the topic.

 ;D

Some chap adding nothing. After I spent and hour demcompiling for you as well as well.

Nye fucking nuke this shit

Wow. Maybe the point of your topic was for people that know to help people that don't know, not just you. It's better to leave the topic (with questions answered) so the next person can search on their own to find their answer. You sir, are a selfish prick.

I'm selfish...well...

So the answer to my problem was, that the *.xdf file wasn't made excactly for my soft and ecu number. Therefore there were maps and axises that fit in place at first try, but some maps were moved to another place in the ecu file. I had to locate the new map places and I used TunerPro to compare 4 files and also worked with WinOls as a parallel guide with two files.

So basicly what I did, is a complete new *.xdf for excactly my cars ecu.

Thank you for sharing. Not as many people are as brave. Young men like you give our great nation hope going forward.

Hahaha, this has made my Monday morning much better :)

Seriously, you could of found another related RPM axis for all you know it's guess work at that stage generally.

LOL @ Daz made my day  :)

I've could, but then I would have a problem with the map itself.

No you could of found any random rpm axis

It wouldn't have worked this way.

Please enlighten us then?

I thought that only thing I need is to get the rpm axis right,
but on my search I found out that the map location itself was
a few points shifted forward. So I had to locate the whole new
map address and for the map new axises also. Hope you
undestand, that was the reason I posted it on noob question,
I'm only been learning this stuff for a week or so.

You don't understand I suggest not changing that axis.  If it makes the map look nice fine but don't change it without knowing.  That's my 2p.  If it is the right axis it may also be shared as well.

Thanks, but I knew from the data of the map that it was wrong for sure.
I had about 5 maps that were ok and I remade about 30 last evening.
I think you best learn when you discover the best way for you that makes
sence finding on maps.

There is no substitute for hands on and doing it yourself for sure.

My advice is true though.... I had several wrong axis before I started disassembling.