qh issue with tunerpro on a lb3 ecu

[Boostcoupe]

ok so this is on my 1986 turbocoupes, so i swapped my pc1 and small vam to a lb3 and large vam, did the pin swap got it together and it runs great so far.
so i put the quarterhorse on it, i downloaded the la3bin from eecanalyzer.net(only place i found any of the 2.3t bins) and loaded it into the QH, it starts but running rich (9.7 on my wideband) and i am assuming the timing is way retarded with a sluggish rev and i can hear the turbo spooling.

i tried downloading an lb3 bin with the same result, and i also tried reading the stock lb3 bin off the ecu, which i believe i did it right and that one also runs the same, but i can pop the QH off the j3 port and it runs great on the stock tune.

this is using tunerpro rt, the t23b.xdf, universal adx from here, everything seems to be connecting fine and uploading to the QH fine, it seems this should be plug and play right? could it be that the bin files are meant for BE? or should that even matter?

[decipha]

i never wrote the patch code for the turbo coupe

read out your stock tune and post it, when i get time ill post up an xdf with te logging code

[Boostcoupe]

that would be awesome,

hopefully i am doing this right lol, thanks decipha for the help

[decipha]

no thats not right its only 16k, read out the full 56k even though your ecu isn't but 32k or prob less it would be ideal so we get it all

details are in the getting started write up on the homepage

[Boostcoupe]

ok i think i got it now lol.

[decipha]

did u write it to the qh and verify all is well?

[Boostcoupe]

yes just did and it runs good no issues.

[decipha]

excellent, as time permits i'll rip through it and post up an xdf for it, its not priority so it'll be months before i do it unless someone specifically gets development for it, but it'll be on the list, i'll prob write some extra code for it as well to do some pretty neat things as well considering the capabilities are less than desire-able with the VAF

[motorhead1991]

I have a padded LA3 already, and it plays well with the T23B xdf.

If I knew the RAM addresses I could whip up the patch sometime soon.

[jsa]

LA* and LB* acquired from all over the web.

Some have been tweaked for MAF code, so would not work for VAF.
The defs may need updating for them to work in BE12.

You could take the info from the defs and transfer it into TP.

Motorhead, correct or not, there are patchcodes and payloads in the defs.

[Boostcoupe]

excellent, as time permits i'll rip through it and post up an xdf for it, its not priority so it'll be months before i do it unless someone specifically gets development for it, but it'll be on the list, i'll prob write some extra code for it as well to do some pretty neat things as well considering the capabilities are less than desire-able with the VAF

thanks that will be great!! ya i definitely want to get rid of the vam just still researching what would be the best route to go, aka speed density, maf, ecu swap.
i want to stick with eec and QH just for the fact that i have 2 other fords to tune and would rather not buy a megasquirt for each car.

[Boostcoupe]

I have a padded LA3 already, and it plays well with the T23B xdf.

If I knew the RAM addresses I could whip up the patch sometime soon.

not sure if you are referring to me or decipha? i wouldnt know where to find the ram addresses, i am fairly green in the eec tuning world lol.

[Boostcoupe]

LA* and LB* acquired from all over the web.

Some have been tweaked for MAF code, so would not work for VAF.
The defs may need updating for them to work in BE12.

You could take the info from the defs and transfer it into TP.

Motorhead, correct or not, there are patchcodes and payloads in the defs.

thanks, i saved those and will see what i can figure out, it seems most of the 2.3t stuff is geared towards BE, i guess i may have to bite the bullet and purchase BE also.

[jsa]

, it seems most of the 2.3t stuff is geared towards BE, i guess i may have to bite the bullet and purchase BE also.

That's what it boils down to. Use the software that has your catchcode definition or expend a lot of resources on making a definition for another software package.