Confused with MPTune

[jonnymopar]

Sorry to bring this one back from the dead. I've got a couple of cals that I want to make into burnable .bin files. I have the cal files and the newest .asm file for a SMEC in the same directory. I keep getting "major error" when compiling. It says to refer to the .lst file, but it is HUGE and I have no idea what I'm looking for. Little help?

[ShelGame]

In MP Tune, there's a menu option for 'Erorrs'; select the compile errors. It will give you a precise list. Post that list and I can help you.

Most likely, your template is older than the .asm is setup for. Probably has some missing/imcompatible table definitions.

[jonnymopar]

This is the error I'm getting:



But after that error comes up, the "Errors" menu returns these:




The cal file is based on one that you had given me last October. Since then, boost control has been change to T1 style, and the first three error masks are now set to 16, 17, and 18 respectively (to try to eliminate a check engine light from using hi-Z injectors). I'm attempting to use v19.5 of the code base to see if I can get computer-controlled boost working.

[ShelGame]

Hmm, OK. Post the .lst file. I'll check it out.

[jonnymopar]

Ok, so see if I'm looking at this correctly. As it says in the message, look in "T-SMEC_v19.lst". I saw another file called "T-SMEC_v19.err" that contained the following:

?ASxxxx-Error-< > in line 10202 of C:\Users\User\Documents\cals\T-SMEC_v19.asm
<u> undefined symbol encountered during assembly

So I looked at line 10202 of the .lst file:

u D3B1 1F 00 00 01 [ 7]10202 brclr 0x00, X, #opt_BangBang, StoreSparkCutCounter

The bang-bang option was introduced in July of this year, so the calibration I have definitely pre-dates that. I think it is an issue with the version of the template, as you mentioned. Next thing to try is transferring all the settings to a new template without screwing everything up. Can you tell I'm new at this??

[ShelGame]

Ok, so see if I'm looking at this correctly. As it says in the message, look in "T-SMEC_v19.lst". I saw another file called "T-SMEC_v19.err" that contained the following:



So I looked at line 10202 of the .lst file:



The bang-bang option was introduced in July of this year, so the calibration I have definitely pre-dates that. I think it is an issue with the version of the template, as you mentioned. Next thing to try is transferring all the settings to a new template without screwing everything up. Can you tell I'm new at this??

Whoa! You don't have to copy over your cal. If that's the only error you get, it's an easy fix. Just copy this OPTN2 data over the one in your template (using plain-text editor like Notepad, it should be near the top) ...

OPTN2_CalCustomOptionConfigFlags2:
    ;mpgrp 0_-_Setup\A_-_Cal_Configuration\
    ;mptbladdr 0x02C9
    ;mptbltype 5
    ;mpsubtype n
    ;mptbllname CalCustomOptionConfigFlags2
    ;mptblcname OPTN2
    ;mpxaxis IN 0 255 X
    ;mpyaxis OUT 0 255 Y
    ;mptbldesc These_are_options_available_to_enable_in_this_custom_codebase.
    ;mpchoices Spark-based_Rev_Limiter  Fuel-based_Rev_Limiter  Launch_Control  Bang_Bang  Bit4  Anti-Lag_Timing  T2_Boost_Control  WB-2-NB_Conversion
    .byte 0x05                       ;Point 1
    opt_WB2NB  			 = $%10000000	 ; Internal WB to O2 sensor conversion
    opt_T2BC			 = $%01000000	 ;
    opt_AntiLag	     		 = $%00100000	 ;
    opt_bit4 			 = $%00010000	 ;
    opt_BangBang     	     	 = $%00001000	 ; use bang-bang style rev limiter when enabled
    opt_StageLim		 = $%00000100	 ; Suppress the EMR (Emiss Maint Reminder) Code
    opt_FuelRevLim		 = $%00000010	 ; Use the fuel-based rev limiter
    opt_SprkRevLim 		 = $%00000001	 ; Use the spark-based rev limiter

... and save. You will then need to go in to MP Tune and setup the flags again to your liking.

[jonnymopar]

Nice! That sounds way easier. I'll hopefully get a chance to try it out this week.