NefMoto

can`t save the KRKTE scalars value
any suggestions?

Are you using nyets 8D0907551M-20110328 file?
I seem to be having the same problem with the .xdf as well as one other person, it will not save the values of anything where as an older version of the .xdf will.

I'm the other person. A little more info:

Some maps cannot be altered with TunerPro's parameter editor when using the 8D0907551M-20110328 XDF. Some that I have found are:
- KRKTE
- CLAATS
- CLAATS2
- CDBKVP
- CDDSBKV
- CDAGR
- CKAGRL
- CDATR
- CDATS

There may be more. You can try changing the value, but when you "save" the value doesn't get stored. You can edit the value directly using TunerPro's hex editor, so I believe the problem is in the definition file.

Also, works fine with the older 20110122 definition file.

TunerPro is cool but editing scalar falls victim to its slider resolution. What I mean by that is that the slider has only so many pixels and if you move it by one pixel you suddenly jump several values less/more, not a single unit the value normally can move around in tune itself.

Just grab the KRKTE slider and move it left/right until it moves and notice how much it changes. Now compare it to actual resolution of the scalar which is 0.000167 per step and you will immediately see the problem. You can also change to HEX view and see how many units it changes per slider move.

Due to this feature, free typing also doesn't take since it rounds up/down the the nearest 'pixel' value... SUPER RETARDED.

The proper way to do this is to convert high resolution scalars like KRKTE to one row table and done.

Attached is an example for KRKTE.

I don't believe thats is the problem we (at least Matt Danger and I are having); though I am no expert in TunerPro and .xdf files.

When I use "8D0907551M-20110122.xdf" I can freely change the values and 'save' them and they do indeed change, however when I do the exact same thing with "8D0907551M-20110328.xdf" it never changes after I 'save'.

The is one problem I described above where you won't be able to save KRKTE values in desired resolution and another with the XDF you listed above. For that reason I am using (as a base) 01/22 version which is almost identical but has no issues.

Cheers.

What version of TunerPro are you running Julex? Mine does not look the same. I have Build: 5.00.7575.00
(https://lh5.googleusercontent.com/_9HYFFImPbcU/Tb9B7MnJXnI/AAAAAAAAAf0/Rkj161LIzVY/tunerpro.jpg)

I do not have 'Major Order' which is where I assume you change it to a table.

I just created new table and moved address, scaling etc to it.

Same version in XP Compatibility Mode so that I can run plugins I paid for in case I decide to move to a different box... namely Checksum plugin.

Testing that out now.

When it comes to variable resolution, don't forget that these values get stored in the internal formats used by the ECU. If the variable is an 8bit byte, then it only has 256 different values, and a 16bit word only has 65536 different values.

i'd still like to know what happened here.. .can you see any obvious differences in the xdf?

should i migrate my converter to using xml?

Unfortunately, Julex's suggestion doesn't solve my problem.

If you launch TunerPro w/ the 8D0907551M-20110328 XDF and attempt to modify KRKTE, CLAATS, CLAATS2 or several other maps by using the slider OR entering a different value the new value is not written. If you edit with the hex editor the new value does get written. I'm not sure how to troubleshoot further.

I believe it is a problem with the XDF because simply switching to the older 20110122 XDF solves the problem.

I believe the only difference between XDFs is how the MAF table is displayed so no biggie switching to old XDF.

what, specifically, are the differences for those map definitions in the xdf? I can't see anything obvious.

No, there are several other changes...

And the old MAF table crashed tunerpro.

I don't seen anything either besides the older XDF being in XML format. My knowledge of how the XDFs are structured is pretty limited so unfortunately I can't troubleshoot much further.

There are some entries missing in the header of the XDF file which TunerPro 5 seems to need.
After adding them it was possible to change and save values.

If you save the (old) XDF in TunerPro 5, it will be written in XML format,
and doing this showed that the line
  <REGION type="0xFFFFFFFF" startaddress="0x0" size="0x100000" regionflags="0x0" name="Binary File" desc="This region describes the bin file edited by this XDF" />
was missing in the header.

Here is the diff between orig and fixed XDF:
10,11c10,14
<       001034 BaseOffset       =0
<       001300 GenFlags         =0x0
---
>         001030 BinSize          =0x100000
>         001035 BaseOffset       =0
>         001200 ADSAssoc         =""
>         001225 ADSCheck         =0x0
>         001300 GenFlags         =0x0

That worked perfectly!

Thanks Setzi!

can you try this one too

Anybody want to help me add xml support to mappack?

If you're asking if this one works, it does not. The values do not get saved.

Odd, i just added the other bits. Do i need the xml header as well *even if the xdf isn't in xml*?

Ah. nevermind. the binsize item is missing in my later xdf exports!

try this one

This one works, thanks Nye :)

Beautiful!

Thanks for helping me figure it out.

I'll have an official release as soon as i can.

New map pack released here

http://www.nefariousmotorsports.com/forum/index.php/topic,200.msg4966.html#msg4966

ECUxPlot updated to make sure mapdump doesn't let you use -x without -i (so it can detect binary size)

http://nyet.org/cars/ECUxPlot/