MembersPage/SamuelLindkvist/AlphaN

Alpha-N test page.


Find the problem. Had to change config13 to 04 manualy and then upload config. So now it works like before. Is it possible to change this bit in megatune?


Firmware version = -D "2004/11/24 16:00"

The patch(es) that I made from the CVS head did not apply to Nov 24 firmware cleanly (that was the reason for the failed compile)

Therefore I made this [alphan_against_nov24_good.patch] directly for Nov24 firmware (no need for the earlier patches, just start again from a clean cvs snapshot without the old patches applied):

This patch works good, Thanks Marcell. =)

Have not started engine yet but TPS now follow load as i should.


Problem:

Alha-n tuning is not working ? Megatune ->useing MAP not TPS load the VE-Tables.

Ini file -> vemsv3_v13_r021.zip, firmware -> 1.0.13 rc3

I commited the following to CVS STABLE1_0 branch, comm.c MTsendRTvar?():

// high resolution MAP or load for AlphaN

case 4: return (config.hybrid_rpm_m ? engine.kpa_tps_blend << 3 : engine.kpa250) >> 8;

case 5: return (config.hybrid_rpm_m ? engine.kpa_tps_blend << 3 : engine.kpa250) & 0xFF;

When AlphaN is configured, this is load instead of MAP, so MAP is only visible on LCD (if there is MAP signal at all).


The way to patch firmware:

C:\vems\firmware>patch -p0 < ....patchfile.location....
patching file `global.h'
Hunk #1 succeeded at 177 (offset -1 lines).
Hunk #2 succeeded at 500 (offset -2 lines).
patching file `ve.c'
Hunk #1 succeeded at 214 (offset -121 lines).
Hunk #2 succeeded at 381 with fuzz 2 (offset -1 lines).
Hunk #3 succeeded at 296 (offset -120 lines).

C:\vems\firmware>

Than compile as usual


I checked

Sounds good.

You could also check with

Change hybrid_rpm_a and hybrid_rpm_m for these tests if more convenient that way.