Page 2 of 2

Re: Difference between 09-10 stock map and 11-14 stock map

Posted: Fri Nov 21, 2014 11:41 am
by GameOver69
Hondata wrote:The injector overrun has been switched over.

The throttle tables are different because a MT calibration has been converted to AT. We've changed FlashProManager so it preserves the table indexes when the calibrations are converted.

The closed loop target lambda tables are correct.
So to confirm, i should have no issues after flashing the stock base map calibration today?

Also besides removing the rev hang, what else can i expect from the stock base map?

Re: Difference between 09-10 stock map and 11-14 stock map

Posted: Fri Nov 21, 2014 12:01 pm
by Spunkster
A new beta has just been release which should fix all these issues.

You can download the beta here:

Re: Difference between 09-10 stock map and 11-14 stock map

Posted: Fri Nov 21, 2014 2:47 pm
by gphung
Spunkster wrote:A new beta has just been release which should fix all these issues.

You can download the beta here:
I will take a look when I get home tonight, thanks!

Re: Difference between 09-10 stock map and 11-14 stock map

Posted: Sat Nov 22, 2014 3:25 pm
by gphung
On V1.9.7.0 and confirmed the bug fixes :)

One issue though. I cannot log into the Vault. I'm using the forum credentials, and I've tried suggestions mentioned in the other threads to no avail:
  • Case sensitive username
  • Case sensitive password
  • Request lost password and use generated password after re-activation
I've clicked on the Check Internet Connection menu item and it confirms connection is ok. I was also able to look up and get calibrations from the Vault Search, but I cannot log into the Vault explicitly myself.

Thanks, and thanks again for the bug fixes! Appreciate the support.

Re: Difference between 09-10 stock map and 11-14 stock map

Posted: Sat Nov 22, 2014 4:07 pm
by GameOver69
Bug confirmed.

Re: Difference between 09-10 stock map and 11-14 stock map

Posted: Mon Nov 24, 2014 9:02 am
by Hondata
That's because of the forum upgrade; not FlashProManager. We'll look at this shortly.