TunerPro User Forum

That's easier

With the image you want on the screen, press the 'Print Screen' key, open up Microsoft Paint and then select paste. You'll now have a entire screen shot that you can trim down etc to what you want.

Version dated 7/09/06 now available.

Version dated 7/09/06 now available.

Right, the column and row labels, AFAIK you cannot cut and paste these

You can cut and paste from tables to and from Excel. To cut, right click and select 'Copy Selection' or use Ctrl + C. To paste, right click and select 'Paste Starting at Cursor' or use Ctrl + V.

fasterthanyou wrote:Got it....

Glad we could help

If only they were all that easy.

Mmm, quirk of the software? Guess we need Mangus to answer this one.

When in the 'edit item xdf info' try changing the 'address step' from positive or negative to get what you want.

Another bump

Using the difference tool again today made me wanting this feature.

If you are using the A9L xdf definition off here you need to ensure that the bin file is 64k. The first 8k needs to be padded out with null data so that the actual bin data starts at 0x2000. The xdf is set up this way so that the checksum calculation works correctly.

I see some confusion cropping up now! The table I was referring to is 'Table 31' on page 32. In all the many times I have read eectch98 I've never noticed the discrepancy between the two pages :shock: There's something amiss with 'Table 54', Ford favour binary point scaling and I cannot see how the ...

Hi Rick, I cannot say why CalEdit outputs the range it does. As far I can tell the stock A9L MAF output is correct in the xdf, it ties up with table in Tom Cloud's eectch98 document. As an aside, I've always wondered why metric units are used for the MAF transfer table when fuel delivery is measured...

Hmm, sorry I don't have any knowledge on those, but if you post your xdf and bin somewhere (or pm me for my email address) I'll see if I can spot why your conversions aren't working.

Which Marelli ecu is it for?

Covers the A9L, A9M, A3M, A3M1, A3M2, D3D1, S0Z and X3Z ecu's.

Use the 'watch this topic' feature to receive notification of the latest version.

A bit more info please, which ecu, xdf etc.

See http://fordfuelinjection.com/?p=17 for how to id your ecu.

What's the 4 digit catch code of the ecu?

Bumping this back up to the top.

Any progress on implementing this? Cheers.

If you are going to play with the Mustang then I would say go for the eec, as you say there's only one ecu to learn. I'm not sure if eec-iv's allow the knock sensor to be used so if you consider this critical it might mean going eec-v or other ecu. Some of your sensors will need changing for eec too...

Let us know how you get on. It sounds like this may be problem that Mangus is best qualified to look into, what OS and version of TunerPro are you using?

Sounds like we're back to the bin size/offset problem again. From the posts above, you are not using a 64k bin and are using the offset function (set to 0x2000, subtracted) to get around this. I have tried to reproduce this error by trimming my bin to 56k and using the offset and I didn't get a prob...

A fair few, for example lets say Ford offer 6 car models in the UK and there's 4 engine choices on each, half of those could have manual or auto gearboxes, half of those could have air con. This lot would probably means 44 different ecus (being conservative) and then there's the every other year cha...

Maybe Mangus will pick up on this thread and have an idea.

Sorry, I don't know how to convert ccf to bin files. On the Quiksnake forum thread 'New Binary Editor', Dale McPeters says he can but he doesn't elaborate on how.

How come all the calculated values are nonsense now? Is it because of the note on "padding" the file? Yes. I don't know how to do this. I use a hex editor (in this case HHD Software's) which has an 'insert' tool that allows you to insert blocks of data (with the same value) into binary fi...

It's probably as broad as it is long this one. People will generally suggest you go for what they have expeirience of. For example I'd say Ford as I know it can do what you want and I am using a Ford ecu to go onto a MR2. It would probably be a good idea to set out exactly what you want the ecu to d...

I may be completely wrong, but for us Ford users I think the Ostrich is only emulating the rom and all the useful information worth logging is held in ram and kam. As far as I know this isn’t presented to the J3 bus on the eec but then again how does the Tweecer datalog?

Do you perform a chip erase before programming?

Yes is the quick and simple answer but as always it's not that easy. It'll will depend on whether someone has already written on definition file for your particular ecu or if you can develop one yourself if it doesn't exist.

Under the 'system requirements' section of the site it states 'Microsoft Windows® 98 (Win95 *may* work, but isn't directly supported)' as the minimum OS requirements. This is probably your problem, you'll most likely need to upgrade your OS.

Updated xdf now in the download section

Sorted in the latest update, to be posted very soon, along with a general tidying up that I hope is going the right way for everyone. Keep the comments coming.

Currently I'm working on adding names to the A9L xdf in lieu of the offset addresses that are mostly used at the moment. Most of these are presently strategy names but the idea is to replace them with 'plain engish' titles as most people don't have the strategy docs (and probably don't want to have ...

Mangus or me?

xdf can be found here:
http://www.supportfitness.com/mark/tune ... inDefs.htm

bin can be found here
http://www.moates.net/fileman/index.php?dir=1)%20Stock%20Binaries/Ford%20Binaries

Which ecu are you interested in?

Hi, I'm afraid I cannot answer your question but am interested in the data file you have as I about to start on a eec-v myself. Is it freely available from somewhere? Thanks.

Sorted as of v4.13.0183, works flawlessly on eec-iv code

Sorted

Sorted as of v4.13.0183, now eec friendly

Sorted as of v4.13.0183

Sorted as of v4.13.0183

Doesn't happen to me on Win98SE. What OS and version number do you have?

Email sent

Hi,

Still getting the ever changing checksum and reset LSB check box problem with the new version (4.12.1709).

Cheers.

PS I like the new version and am finding my way around the new functionality.

I get the same problem too Version 4.12.1709 on Win98SE.

I get the same problem too

Version 4.12.1709 on Win98SE.

I've done a little bit more on this myself now. I have modifed my binary file by enlarging it from 56k to 64k and filling the first 8192 bytes with null data and changing the data start address from 0x2000 to 0x0000. Now when I save the binary the checksum is updated. This however leads to another p...

Excellent, looking forward to it

As above, can TunerPro handle signed values/tables? I've looked and cannot see it anywhere.

TunerPro User Forum

Search found 615 matches

Re: FIXED

Updated GUFB (A9L etc) xdf in the downloads section.

Can TunerPro handle signed values?