EFIDynoTuning Forum

I had kind of given up on any MZAK0 support. Barely poke around anymore. Until today. Glad it's up and running.

Now to load my hex files into TunerPro and see what I can see.

Working on an '04 F53.

Thanks!

I wouldn't hooray just yet. You have to be a premium member to do any real tuning on mzak0 as the xdf I have posted right now is pretty basic and no adx.

what all is done to the truck?

I tweaked some shift points years ago. Like to do a little more of that. Haven't used any of these tools. Basic is ok to start, I'll check out the premium membership.

So yeah, no go. Stuff all opens and loads, but values are out of whack. .bin file must not match the .xdf. I KNOW I have MZAK0. Any suggestions?

did u have the key on when u read it?

post the file and ill take a look

It's an old binary file I flashed into the controller using other tools.

It is possible that it has (improperly) a header or something that the tools I used added or ignored.

Tim

You need to read the tune file out with the qh.

What did you use you to read and write the file? What did you use to edit it?

that 217k file isn't any standard format that I'm aware of although it is an actual bin

MZAK0ZD is the WAU1 cal which is a revision of the VMA2 base cal I use for the v10s I do.
Henry simply changed the tire revs for the larger tires and kicked up the gear ratio and enabled vehicle speed calc and was done lol.

I figured out what they did.

6 bytes in the front
01 00 06 e000 20
bank 0

9 bytes
7c 00 02 00 07 c0 00 20 01
bank 1

9 bytes
10 00 02 00 07 e0 00 20 09
bank 9

0x28000
9 bytes
f5 00 02 00 07 e0 00 20 08
bank 8

end of file
11 bytes
40 00 02 00 07 00 e0 ff 08 10 00

obviously those bytes are defining sizes checksums and banks

Anyway, thats a bone stock file you have. You failed to change any shift points.

Correct, that is the unmodified file. I'll pm you some details, if that's OK....

ok