Ant has successfully read the tune which is currently running the car (legend!!! )
It is written as a VNV6 $A5 tune.
I have downloaded TP5 and got all the software stuff sorted. PM'ed VL400 and will hopefully und up with one of these suckers.
I also need to convert the tune to $12p, what's the best way to do that?
I'll attach the file if anyone want's to have a look at it.
as was stated the WOT part of the tune is good, but cruising and idle the wideband 02 only ever sees an AFR above 13 on over run. And yes is smells as rich as it runs.
You do not have the required permissions to view the files attached to this post.
best way to do the transfer from that tune to 12P is to get the main modified tables out and copy into excel, then if you need to added extra cells, ie. if you need a 65kpa column between 60 and 70 then add it in and use excel to average the cells either side to get the extra stuff added then copy into TP5 12P tables.
unfortunately its a bit of a slow and manual process but thats about all i've ever done in the past.
No matter what the question is, the answer is always more horsepower!
Have been comparing differences between your tune and ASBY.
The idle spark table looked funny, and I reckon there is a mistake in the $A5 xdf. I reckon F1 Idle should be at 0x38 instead of 0x36 like it is now.
To fix, right click on "F1 Idle" in the parameter view, and click 'edit paramater xdf info', and change 'address (hex)' from 0x36 to 0x38. Hit apply and close. Save the changes. The idle spark tables should be right now.
antus wrote:Have been comparing differences between your tune and ASBY.
The idle spark table looked funny, and I reckon there is a mistake in the $A5 xdf. I reckon F1 Idle should be at 0x38 instead of 0x36 like it is now.
To fix, right click on "F1 Idle" in the parameter view, and click 'edit paramater xdf info', and change 'address (hex)' from 0x36 to 0x38. Hit apply and close. Save the changes. The idle spark tables should be right now.
I haven't had a chance to have a look at it in TP yet.
Hopefully when I do what you just said will make sense.
The original idle spark table had some values that were all over the place (like 0 and 50 deg), changing to 38 and it looks better now - and from working with the code the offsets should also have the idle spark table and the straight away the main spark tables with no space between, with 38 this happens.
The default TPS table is also incorrect, it should be 1A. There might be other tables wrong so be careful - if tables do not step smoothly through the rows/coulumns its prob wrong!
Its also worth nothing its because the tune is $A5. When you have trusted code and definitions (eg 12p) thats not the kind of thing you need to worry about!
antus wrote:Its also worth nothing its because the tune is $A5. When you have trusted code and definitions (eg 12p) thats not the kind of thing you need to worry about!
Got most of my tables nutted out for the 12p conversion.
I'm not too worried about the VE values as I can easily see and change them on the fly.
I am a little concerned about extrapolating the Spark advance past 4,800 to redline. Whats the norm for a reasonably hypo 6 to be doing in the upper region of the map? holding constant? (what I have done) or to slightly increase a degree or 2 up to redline? (bout 6,500).
Was there a setting in my old map (VNV6 $A5) to increase the spark once it was out of the mapping range? or did it simply hold it's last value?
) 
