---===The Official MAFT-Pro Thread===---

[UCSB VR4]

Originally Posted by venik

use the verify bin with emulator to make sure it's actually uploaded. Just because you click the upload button twice doesnt mean they are parrallel. I had the same problem, I forget exactly what made it finally do what i wanted. But I'm pretty sure it has something to do with when an upload fails, the tunerpro tells you it fails but it doesn't actually "know" it fails and it keeps the values that you "updated". The tunerpro keeps the changed values that you typed in, without updating to the maftpro. So the tunerpro keeps the new but false values, and the maftpro keeps the old values unaware that anything has changed. Then you download from the maftpro, and you get...tada the old values.

Not sure how correct that is, but what i did was change all the values to a random number like 84, then upload, then verify, then change them back to 45 50 55 60 80 100 120 etc and upload again, and verify again.

Also make sure when you change something with the keypad (i.e. airflow mode) make sure you download it to the tunerpro. If you don't, the tunerpro and maftpro won't be in-line which, like i said, seems to make it flip shit.

I agree that tunerpro could be written better

The tunerpro actually confirms that the upload was successful. I also can see minute changes made within tunerpro updated successfully to the maftpro (i.e. mainscale 0.5% change just to confirm, then immediately changed back on the maftpro). The car even drives differently after I uploaded the new bin so i know some changes are taking effect. I made sure that the maftpro and xsd were both configured for SD with axis airflow mode, still not maintaining settings after downloading from emulator.

any other ideas?

- Jeff

[venik]

ya it confirms it because it doesn't know they aren't parralel, did you try doing what I said? From what i understand the tunerpro only uploads what you've changed, so if it doesnt think you've changed anything it will give you the green bar on the upload. I wouldnt trust it until you use the "verify bin with emulator" button, and you know your bin has the values you want. Thats all i've got though maybe turbobob could help if im wrong.

[UCSB VR4]

Originally Posted by venik

ya it confirms it because it doesn't know they aren't parralel, did you try doing what I said? From what i understand the tunerpro only uploads what you've changed, so if it doesnt think you've changed anything it will give you the green bar on the upload. I wouldnt trust it until you use the "verify bin with emulator" button, and you know your bin has the values you want. Thats all i've got though maybe turbobob could help if im wrong.

Okay so anytime I upload a bin with a new "VE Table MAP axis" then click the "Verify Emulator RAM Contents Against Current Bin" button within tunerpro, I get an error: "verify failed(0)". When downloading bin from the emulator to my tunerpro, I can see that all other properties were updated correctly within the pro (even the new VE table cell values i put in there). It's just the axis that doesn't update within the pro.

It appears that my mods to the "VE Table MAP axis" are not sticking and effectively causing the "verify" error. Now what?

EDIT: I just decided to export my bin to a text file... I noticed that the VE Table MAP axis is updated with the new values, however, the VE Table (seen higher up in the .txt file) still has the old MAP axis values. This is all despite airflow mode/source being set to 0x04="SD User-Axis" on both the maftpro and within tunerpro. This must be a bug, what do I do?

EDIT again: I also have "Use VE Table #2" still set within the "system setup" on the pro, should this be changed to something else?

- Jeff

[venik]

did you try changing all the values to a random number like 84, then upload, then verify, then change them back to 45 50 55 60 80 100 120 etc and upload again, and verify again.

[TurboBob]

what version tunerpro are you using? (check help/about)

Bob

[Storm Strike]

I just have to say again that the stealth5.03 bin file TB posted ROCKS!!! I've only had to make minor tuning changes (mainscale and minor richening on high range) for my particular turbo/injector setup. I can easily run ~17psi of boost in 2nd gear from slow to redline with no knock. Hell, I bumped it up to 20psi of boost and only saw 1-2 counts of knock at ~6k+ rpm. Now I still have to get Tunerpro fully up and running so I can better log WB02 vs RPM and see the VE table cells moving around in real time. (Can that be logged as well for later review, or is it only real time?) I'm also thinking of playing with WOT AFR tracking to start, then PT tracking later on.

I still have a pile of parts to install. But now, with how great it's running, I'm thinking of only putting on the new FMIC, get new street tires, and maybe the racing oil pan, and hitting the open track days. I just don't have a good enough reason to take off the 13T's and install the 15Gs right now. Who knows, maybe I'll skip the 15Gs altogether, and put the value of those and the current 13Ts towards a 16G setup, especially a used setup.

Thanks again TB!

[UCSB VR4]

Originally Posted by venik

did you try changing all the values to a random number like 84, then upload, then verify, then change them back to 45 50 55 60 80 100 120 etc and upload again, and verify again.

thanks for the ongoing suggestions, i will try this and get back to you with the results.

- jeff

[UCSB VR4]

Originally Posted by TurboBob

what version tunerpro are you using? (check help/about)

Bob

4.13, is that old?

- Jeff

[venik]

Originally Posted by Storm Strike

I just have to say again that the stealth5.03 bin file TB posted ROCKS!!! I've only had to make minor tuning changes (mainscale and minor richening on high range) for my particular turbo/injector setup. I can easily run ~17psi of boost in 2nd gear from slow to redline with no knock. Hell, I bumped it up to 20psi of boost and only saw 1-2 counts of knock at ~6k+ rpm. Now I still have to get Tunerpro fully up and running so I can better log WB02 vs RPM and see the VE table cells moving around in real time. (Can that be logged as well for later review, or is it only real time?) I'm also thinking of playing with WOT AFR tracking to start, then PT tracking later on.

I still have a pile of parts to install. But now, with how great it's running, I'm thinking of only putting on the new FMIC, get new street tires, and maybe the racing oil pan, and hitting the open track days. I just don't have a good enough reason to take off the 13T's and install the 15Gs right now. Who knows, maybe I'll skip the 15Gs altogether, and put the value of those and the current 13Ts towards a 16G setup, especially a used setup.

Thanks again TB!

AFAIK 13ts and 15gs are dead even, so ya just sell them or something lol

Originally Posted by UCSB VR4

thanks for the ongoing suggestions, i will try this and get back to you with the results.

- jeff

np, it's easier for me to explain the wheel, than it is for you to reinvent it.

[Storm Strike]

Originally Posted by venik

AFAIK 13ts and 15gs are dead even, so ya just sell them or something lol

I always thought 13T's fell between 13Gs and 15Gs. Especially as my 13Ts are not built on WRX housings, but the stock 9B/13G/15G compressor housing. Still have the 13T wheel, but not the larger WRX housing. On the other hand, my 13Ts have the turbines clipped (10 deg, I think), whereas my 15Gs do not.