Pages: [1]
Author Topic: 1.8T 8E0906018B KMIRL and ESKONF help  (Read 1665 times)
ama11deus
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 33


« on: March 03, 2022, 12:11:20 PM »

Hello everyone,

I am trying to get into tuning my car with nefmoto. I have successfully read and saved my .bin (1.8T 8E0906018B AVJ). I have also found a definition file which I though was correct, but there are two things I'd like to ask:
1. Since the xdf I found is lacking in some maps I decided to download a .bin and .xdf for a 190HP 1.8T to compare my maps and have an example of how to tune it. The first map I opened was KFMIRL and when I compared those two I noticed they have different values on their axes. I checked the other maps and most of them seemed to align. Here is my map:

As you can see the RPM's go as high as 16k. And on the other map they go to 6020 which is way more reasonable. I searched the forum far and wide and I only found this:
Quote
MAP FOUND: KFMIRL 16x16 @ 0x153E4
I checked my HEX address and its the same as the one here. Is the xdf I have correct? Or is something wrong with it?
2. In the definition file there are two ESKONF's: ESKONF and ESKONF 2. Why and what for?
I attached a .rar with my .bin and the .xdf I found. Any help would be greatly appreciated.
EDIT: Also what does this mean:

When im trying to edit the categories of an XDF parameter.


« Last Edit: March 03, 2022, 12:51:08 PM by ama11deus » Logged
denniss112
Full Member
***

Karma: +7/-1
Offline Offline

Posts: 114


Audi TT 99' | 180+HP FWD


« Reply #1 on: March 03, 2022, 01:30:12 PM »

Since you are new, I suggest switching to WinOLS ASAP. There are better deffinitions available for WinOLS, and its a bit more powerful then TunerPRO. What I did, was looking for the software including alot of definitions on AliExpress. I believe you can find one for 10 EUR or less.
Logged
Sandstorm3k
Sr. Member
****

Karma: +10/-14
Offline Offline

Posts: 402



« Reply #2 on: March 04, 2022, 01:21:22 PM »

I do all my work with Tunerpro, what you are seeing is just a wrong axis. They're wrong in a lot of maps but it doesn't really matter.

Most of the times the axis is close to a map in hex.
Logged
Pages: [1]
  Print  
 
Jump to:  

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