Tuner Pro XDF 1999-2000 F Body + Y Body

**LRT** · 07-23-2016

Originally Posted by evilstuie

so I can get it to a shop to dyno tune it? :)

You originally asked for help to get the car running, so you could then take it somewhere to have it dyno tuned.

You chose to use an EFILive COS - for which there is no XDF available. Had you used 2001 operating system 12202088, then you could have used the only OBD2 XDF created, and used Tunerpro to adjust things in the tune.

It is not really a DIY (do-it-yourself) project, when you ask someone else to do the tuning for you.

Altering the spark tables, by working in the raw binary code, would be quite a bit of work. I don't think you realize the amount of time it would take to do what you are asking.

**evilstuie** · 07-24-2016

Originally Posted by LRT

You originally asked for help to get the car running, so you could then take it somewhere to have it dyno tuned.

You chose to use an EFILive COS - for which there is no XDF available. Had you used 2001 operating system 12202088, then you could have used the only OBD2 XDF created, and used Tunerpro to adjust things in the tune.
It is not really a DIY (do-it-yourself) project, when you ask someone else to do the tuning for you.
Altering the spark tables, by working in the raw binary code, would be quite a bit of work. I don't think you realize the amount of time it would take to do what you are asking.

Hey mate, sorry I assumed you were using some other software so you could just copy and paste the tables into excel, make the changes by formula and paste back into the tune file. I didn't know you were editing the tune in hex.
I didn't choose the COS3, it was the OS that was on the 3rd PCM I'd bought to try and get the car running. I had the 1074 OS which had XDFs, but Dimented's LS1 Flash tool bricked them both when trying to change to a different OS, so I was stuck with what I got.

**evilstuie** · 12-09-2016

With COS3, it's a modified version of the 12225074 OS yes?Would there be much involved in modifying the XDF for this to work with COS3?

**LRT** · 12-09-2016

Originally Posted by evilstuie

With COS3, it's a modified version of the 12225074 OS yes?Would there be much involved in modifying the XDF for this to work with COS3?

First, a couple of assumptions. That you already have an accurate XDF for 12225074, and that this XDF also correctly calculates the segment Checksums.

Then, you would need to determine which parameters in the XDF are no longer used by the COS, and delete these parameters from the XDF.

Then, you would need to determine which parameters in the XDF have been altered (rescaled or repurposed) by the COS, and adjust the definition of these parameters in the XDF.

Then, you would need to locate and define all of the new parameters in the calibration created by the COS, and add these new parameter definitions (flags / scalars / tables) to the XDF.

**babywag** · 12-09-2016

If it was me I'd remove the chip(s) and burn on a supported OS, then resolder them on.

Since you have multiple bricks, seems like logical way to get 'em all back to operational?

If you choose an OS with an .xdf tuning could then be DIY

**evilstuie** · 12-15-2016

Babywag,That was my initial plan, but the programmer I bought (TL866) didn't come with the right adapter, and the BDM programmer I bought was only for 16bit controllers not the 32bit Motorola chip so I lost the energy to continue.I might see if I can get the adaptor and give it a try.

**evilstuie** · 12-17-2016

Originally Posted by LRT

First, a couple of assumptions. That you already have an accurate XDF for 12225074, and that this XDF also correctly calculates the segment Checksums.Then, you would need to determine which parameters in the XDF are no longer used by the COS, and delete these parameters from the XDF.Then, you would need to determine which parameters in the XDF have been altered (rescaled or repurposed) by the COS, and adjust the definition of these parameters in the XDF.Then, you would need to locate and define all of the new parameters in the calibration created by the COS, and add these new parameter definitions (flags / scalars / tables) to the XDF.

Ok, sounds like a lot more than I thought.I think I'll just have to put my car on hold until I can save up enough for EFILive. My plan was to take the car to a tuner to put on the dyno, but that is going to cost me at minimum $1000AUD, which would be fine if that was it.But I need to have the motor properly run in and have it able to idle long enough to check things like thermo fans kicking in, check for oil leaks, and all that, otherwise I'll take it to the dyno, they'll spend a day trying to tune it and at the end of the day come back to me and say there's something wrong or the plugs are fouled or the motor cooked, and take my $1000 as well.With 1500rpm the timing sits around 25 and sounds really good, but at idle its jumping between -8 and 12 and cuts out without throttle.

**LRT** · 12-18-2016

My two cents, would be what Babywag suggested - move to a 2001 OS (12202088 or 12208322) and tune it yourself, using TunerPro and the XDF and Checksum Plug-in that I posted. Dimented24x7's flash tool will work with either of those OS.

Dyno tunes aren't cheap - typical prices here begin at $650, but you are usually closer to $1000 by the time all of the issues in a conversion project are addressed.