Learning View v1.0 RC3

rtbrjason · **Posted:** Sun Jul 10, 2011 12:49 pm

MasAyinde wrote:

This might be a newb question, but it seems as though the load range cells for the FLKC table are ECU specific, correct? There is no way to have my 05 LGT (521N) display the more detailed ranges like those that I see for the WRX and STI?

You can't add cells, but you can change the ranges. It's the "fine corrections column (load)" under knock control. Mine are set as:

1.70
2.10
2.40
2.75

I have FLKC disabled under 1.3 load, so the first range is 1.3-1.7, the second 1.7-2.10 and so on.

merchgod · **Joined:** Thu Mar 30, 2006 2:38 am **Posts:** 5336

reuna wrote:

Thank you very much Merchgod! Group N support seems to work well. I didn't know that group N ecu builds the FLKC table as generally FLKC is disabled and only FBKC is active in grpN ecu.

I guess the P0107 is related to my 3bar GM MAP sensor scaling (not possible to set a positive offset in 16bit ecu).

A/F learing #1 seems to be way off. This must be due to VE table because injector scalings were fine in a MAF based ecu.

Thanks for testing this! It appears the A/F Learning MAP axis conversion is incorrect. I'll get that fixed.

EDIT: Actually, I'm not seeing an issue with the conversion in the code. Can you post up the LV log? Did you change the A/F Learning "Airflow" ranges in RomRaider at all?

reuna · **Joined:** Mon May 15, 2006 8:06 pm **Posts:** 32

merchgod wrote:

EDIT: Actually, I'm not seeing an issue with the conversion in the code. Can you post up the LV log? Did you change the A/F Learning "Airflow" ranges in RomRaider at all?

A/F Learning ranges were changed indeed. I changed them back as per "STi Computer Orig.hex" and now MAP based ranges make more sense and fueling seems to be more stable.

Thanks again for this great application!

02rexwi · **Joined:** Wed Jul 16, 2008 11:32 pm **Posts:** 324

So does that mean the FLKC is indeed active in the group N ROM?

ckibue · **Posted:** Mon Jul 11, 2011 5:40 am

02rexwi wrote:

So does that mean the FLKC is indeed active in the group N ROM?

I have gotten mine to work on a couple of JDM STis here, change in IAM too has been observed.

td-d · **Posted:** Mon Jul 11, 2011 9:24 am

reuna wrote:

merchgod wrote:

I guess the P0107 is related to my 3bar GM MAP sensor scaling (not possible to set a positive offset in 16bit ecu).

Sorry OT, but change the Manifold Pressure Sensor Limits (CEL) "low input" table down, and you'll get rid of the P0107 error. I just had this with an Omni 3bar sensor as well, sorted it out.

fastblueufo · **Posted:** Mon Jul 11, 2011 9:49 pm

merchgod wrote:

Thanks for testing this! It appears the A/F Learning MAP axis conversion is incorrect. I'll get that fixed.

EDIT: Actually, I'm not seeing an issue with the conversion in the code. Can you post up the LV log? Did you change the A/F Learning "Airflow" ranges in RomRaider at all?

Bill,
I noticed that the LV will show 2 temp codes for the ocv even though I have the codes disabled. Will the temp code cause the cel to be on? Could this be the cause of the cel staying on when using the group n rom? I have used a code reader before but it always showed no codes. I guess it didnt have the ability to read a temp code off the ecu.
The 2 temp codes I get are p1307 and p1309.

CSXRT4 · **Joined:** Fri Apr 17, 2009 5:19 am **Posts:** 42

fastblueufo wrote:

merchgod wrote:

Thanks for testing this! It appears the A/F Learning MAP axis conversion is incorrect. I'll get that fixed.

EDIT: Actually, I'm not seeing an issue with the conversion in the code. Can you post up the LV log? Did you change the A/F Learning "Airflow" ranges in RomRaider at all?

Bill,
I noticed that the LV will show 2 temp codes for the ocv even though I have the codes disabled. Will the temp code cause the cel to be on? Could this be the cause of the cel staying on when using the group n rom? I have used a code reader before but it always showed no codes. I guess it didnt have the ability to read a temp code off the ecu.
The 2 temp codes I get are p1307 and p1309.

I've disabled these in the code and the cel still comes on

reuna · **Joined:** Mon May 15, 2006 8:06 pm **Posts:** 32

td-d wrote:

Sorry OT, but change the Manifold Pressure Sensor Limits (CEL) "low input" table down, and you'll get rid of the P0107 error. I just had this with an Omni 3bar sensor as well, sorted it out.

Thanks for advice! I changed "Manifold Pressure Sensor Low Input" down to 0.05 V and no more P0107.

td-d · **Posted:** Thu Jul 14, 2011 9:18 am

No worries, also had it and it was damn irritating...

goixiz · **Posted:** Wed Jul 20, 2011 10:12 pm

where are the screenshot files kept
i have a hard time finding them

MFB · **Posted:** Wed Jul 20, 2011 10:14 pm

Its in the same location where you put LV.

goixiz · **Posted:** Wed Jul 20, 2011 10:43 pm

MFB wrote:

Its in the same location where you put LV.

i thought so too but i saved it a few times and its not where the LV program resides

windows 7 (64bit)

i know i press ok when i select screenshot then a popup came up with the file name and then i went in th house to look for the file and cant seem to find it

MFB · **Posted:** Wed Jul 20, 2011 11:27 pm

Since your win7, you can just easily do a search. Also take an lv again and see the directory it displays after saving your file.

archdude · **Joined:** Mon Jul 11, 2011 3:28 am **Posts:** 6

Hi merchgod,

Do you think you could add support for ECU ID 5112147007 2009 Impreza 2.5i AT?

RomRaider

Forum rules

Learning View v1.0 RC3

Who is online