TunerPro User Forum

BrendanSmall

Save it as a .txt, then change the extension to .xdf

BrendanSmall

Found a nice forum about this today...

check out www.dsmecu.com

They have a speed density bin file, and xdf.

BrendanSmall

If it were possible to take a peek at the code after the SD mods, it'd be easy to implement. I've often wondered this too.

BrendanSmall

I've learned the error of my ways since that post, lol. I think I read and re-read all the posts on NefMoto a million times, super helpful :D. My attitudes were born of intimidation of ME7, it's not as scary as I thought, now that I've learned a bit more. Could that XDF (and tuning wiki) be applied ...

BrendanSmall

Tunerpro doesn't do that, it's simply a tuning program. If you know the map addresses, you input them into tunerpro, and you can make changes to the mapping in a graphical format.

The ROM has to be read/written to the ecu by another program.

BrendanSmall

Creating the xdf is easy, it's straight translation of map addresses into the software. Unless the person making the xdf knows exactly what each map does, all you'll have is a file loaded full of maps without axis values, populated with raw bytes. To accurately make an xdf for someone, you need to d...

BrendanSmall

Meh. I have never even been in a BMW, never tuned one, never plan to own one. Your work is useless to me. I'm commenting on the fact that you like to tell people how much smarter than them you are, when they ask a question about something you view as simple. If I'm a lowest of the low tick parasite,...

BrendanSmall

It's 256, FR Wilk is correct.

BrendanSmall

Wasn't referring to you

.

BrendanSmall

Why are all BMW 'tuners' so cocky and/or arrogant?

Who cares who made the 'best' XDF. Sounds like there's a lot of hurt feelings going around.

BrendanSmall

Yeah...never mind this. The file I'm working with is bad...sigh.

BrendanSmall

I've tried many different combinations of files, hex editors, memory size, hex offset, you name it...but the file I download from the Ostrich to my PC is always 4 bytes/hex offset from where it should be. I can verify the file with TunerproRT (both 7.00 and latest version), and even Emutility will v...

BrendanSmall

Yep, worked

.

BrendanSmall

Link?

BrendanSmall

Right click -> save as

.

BrendanSmall

I think I've sorted it, although there are a LOT of maps in those bins that could be similar to the ones you're looking to edit. A 64kb bin file is going to have a lot of extra maps to play with, but the ones I found are only slightly offset from the mod.xdf, so I think they're the same ones. Can't ...

BrendanSmall

Unfortunately, no. It's a 'different' motronic, since it's controlling mechanical fuel injection (technically). I've peeked at the code, but it doesn't resemble modern Motronic hex at all.

BrendanSmall

I've seen that one, and while it has 30 maps that 'supposedly' allow you to tune the ecu...is it tuned properly? ;) Every tuner has their own philosophy about tuning ME7x, and to be brutally honest, 30 maps out of 500+ is a terrible ratio for tuning. Understanding how ME7 works (which I don't propos...

BrendanSmall

Unfortunately, the stock Motronic 7 or 9 is VERY complex. To create an XDF for either would be a huge undertaking, as there are 500+ maps/functions/scalars in each, IIRC. Every map works off another, so it's very difficult to figure out which ones would be needed to do a proper tune, if you only con...

BrendanSmall

I use an Ostrich with the 18" cable on my Digifant-1 equipped cars, with no issues. What program do you use to upload to the emulator?

BrendanSmall

Well duh, don't I feel stupid...that fixed it!

Many thanks!

BrendanSmall

Hmm, I'll give that a shot!

BrendanSmall

This is a conundrum for me right now, I can't figure it out. -Tunerpro V5 build 5197 (although the recent one does the same thing) -64kb bin file -Ostrich 2.0 -XDF of my own making, for VW motronic 2.9. I can upload to the emulator, and if I download it to a file, it comes out clean as a whistle. If...

BrendanSmall

For now I've simply added a '+0' after the parentheses, seems to work. It's not a big deal though, since my older laptop is still running a previous V5 build, that doesn't have the same bug.

If only my math teachers could see me now, lol.

BrendanSmall

Ah, gotcha

.

BrendanSmall

Tracing is broken?

BrendanSmall

Cool, thanks! Both for not thinking I'm nuts, and for the wicked bit of software called Tunerpro! .

BrendanSmall

ECU: Bosch Digifant-1 (VW Corrado). Tunerpro build: 5.00.6356.00 In the xdf, the original equation for converting the raw data to ignition in degrees was (X*-0.351563)+78, and it worked great in build 5.00.5197.00. Now with the new build, it's necessary to remove the parentheses in order to achieve ...

BrendanSmall

Yeah, I've found that and converted it all to an XDF. It's 'workable' but faaaaaaaaaaaaaar from complete right now, since I don't have a test vehicle

.
I've actually spoken to you via email about it

.

BrendanSmall

I suppose I could do that, I've got it posted up on www.ecuconnections.com right now, as a constant Work-In-Progress. If he is ok with it being posted in it's incomplete format. It's 90% done IMO, more than enough to tune a car VERY easily with

.

BrendanSmall

Tunerpro will automatically correct the checksum, but you have to configure it to do so. It's in the XDF Header info.

BrendanSmall

Cool, exactly what I wanted to know, thank you very much.
I'm writing the XDF, so I guess I'd better expend some energy on finding that checksum!

BrendanSmall

I'm assuming that I have to enter this info before it can start to work though?

BrendanSmall

I'm a little confused here. I've read that tunerpro automatically corrects the checksum, but I don't see how or where it does so? All the XDFs I've downloaded to check out the Checksum scalar have no 'conversion' calculation in them, so it seems to be primarily a viewer. I'm assuming that I'm off my...

BrendanSmall

No, I'm in North America and we never got the Digifant-3 cars (MkIII 16v ABF, etc). Our cars jumped right to Motronic 2.9 and beyond, so I have never looked at the digifant-3 stuff. Sorry

.

BrendanSmall

Crome is an OBD1 Honda chip tuning program, freeware. When we tried to burn the chips with Flash n Burn, the offsets would come out wrong (st512 chip, 64kb) and the car would run like poo. No matter what we did :(. On the Xenocron website there is a tutorial on how to burn with Crome, so we gave tha...

BrendanSmall

Well, it all depends on if you're ready to start figuring out Motronic or not ;). It's pretty easy to figure out how big the tables are, and what the x and y axis are supposed to be...but it's kinda tricky to decipher. Over at http://www.ecuconnections.com/forum/index.php?sid=683f357b143bdaeeb832670...

BrendanSmall

He wants to have tunerpro open and be able to see the RPMs on the screen/dashboard while emulating through the Ostrich2. So I have a dumb question. Why not use a Wideband that sends out a datastream and hook RPM to that and connect it to TunerProRT while emulating? Then you can also send boost pres...

BrendanSmall

He wants to have tunerpro open and be able to see the RPMs on the screen/dashboard while emulating through the Ostrich2. How? When Motronic 1.3 does not support any live data stream? The only diagnostic feature that it does is flashes fault codes, thats it. Person who tunes these ecus should know t...

BrendanSmall

He wants to have tunerpro open and be able to see the RPMs on the screen/dashboard while emulating through the Ostrich2.

BrendanSmall

I use the Flash 'n burn software from the downloads section. It does the offset by chip type vs. car type. Issues burning to Crome with it though, so we use Crome itself for the honda stuff.

BrendanSmall

Far from useable, but I've located and started converting the maps into XDF format. It's a slow process

.

BrendanSmall

I've been working on this XDF, making great progress too.

BrendanSmall

I've posted it here:
http://www.ecuconnections.com/viewtopic.php?f=7&t=41

Thanks for the help, and the forum!

BrendanSmall

Whoa...AWESOME!

BrendanSmall

<--- eagerly awaiting the results.
I have to say, it was quite amusing to see that trace dancing all over the maps, lol. I do like the real-time tuning part though, very handy even without tracing.

Thanks for all the work Don!

Chad

BrendanSmall

Well, duh...don't I feel smrt.

I mean...smart.

Yeah, that's it

.

Thanks!

BrendanSmall

I noticed this too. Thought it was odd, but it's technically still a beta.

BrendanSmall

Engine code ABA (north american 2.0 8v crossflow), motronic 2.9.

ECU part #: 037 906 258 AE

BrendanSmall

Unfortunately, all I have are stock bins

.

If those are helpful, I will certainly post them up

.

TunerPro User Forum

Search found 52 matches

Am I crazy? Downloading .bin from Ostrich to file...no go.

Can't download to emulator, V5.

Mathematical problem with the 'conversions' function

Tunerpro automatically calculates checksum? Really?