Alpha-N Y axis not switching over to TPS

[dll67]

Working on a Alpha-N tune and I noticed at least 1 table hasnt switched from MAP to TPS.
I used the Idle VE Table for MAP before and now that I have switched to Alpha-N the idle VE table still shows "fuel load %" as opposed to TPS % causing my idle VE to never activate.

Idle VE Wrong.jpg

[dll67]

Do I just need to just lower the "Y" values to reflect a TPS curve rather than a MAP curve?

[jsmcortina]

[dll67]

CAN1_CurrentTune.msq

CurrentTune1.msq

Heres my MSQ's

[jsmcortina]

You are on quite an old firmware where the fuel load shows as a %. In current firmware it swaps between kPa and TPS% etc. depends on the fuel algorithm you use.

Note that if you do decide to upgrade, you might want to consider pre-1.4.1 beta1 as it has some CAN fixes over 1.4.0

James

[dll67]

I thought I was on 1.4.1? I'll look into that

[dll67]

1.3.4 ?
I know I had 1.4.1 beta loaded. Jean mentioned I should try it when I was having problems with my IOx on CAN.
Thanks for mentioning that. Sometimes it just takes a fresh pair of eyes

[jsmcortina]

The MSQ I loaded says pre-1.2 alpha 7.

Assuming I loaded the correct tune. Best just to Save Tune As and hit enter. Then you get a unique filename, that's why "CurrentTune.msq" is blocked on the forum.

James

[dll67]

The MSQ I loaded says pre-1.2 alpha 7.

Assuming I loaded the correct tune. Best just to Save Tune As and hit enter. Then you get a unique filename, that's why "CurrentTune.msq" is blocked on the forum.

James

I think that was the wrong tune .. I dont have pre-1.2 alpha 7 in my firmware folder and I only run my own tunes ... This motor is way to finicky
Either way it wasnt the firmware I meant to have in there so I uploaded 1.4.1 beta 1 to my MS3X and drove home. Nothing changed visually in the 'Y" axis of the "Idle VE Table", and still no idle VE activation.
Loaded the firmware and msq then saved as "current tune 1.4.1.beta 1.msq" before drive home, got home and it only updated "current tune.msq" after shutting down. Did I miss something or is there no way to only use and have update, a unique, save as "current tune.msq"?
Ive also noticed if there is a hickup when loading the main controller at startup it will disable the main controller and switch to the "CAN1_Current tune.msq", at least thats whats displayed in the lower right dialog in TunerStudio ...

TS bottom window.jpg

So now I have 3 different "current tune.msq'" to keep track of.