ECUFlash - Getting close!

[mad_sb]

Originally Posted by glorydays

So... is this option ready to use for the average noob or is this still a developer only type of deal... OR is it one of those "if you have to ask" type of situations?

It's one of those "if you have to ask" for the moment, but it won't be long before it's ready for the masses

[jamesm]

Originally Posted by Td-d

Well... not me personally, since I don't have a BRZ

Most of the open source tuning tools - i.e. MAF calibration, MAP compensation tables (those two in particular), speed density VE tables - that are available (see here: http://www.romraider.com/forum/viewforum.php?f=32) are in Excel. Excel is a dog for crunching files that are hundreds of Mbs large (which the OP2 in mode 23 logging very easily can generate).

Ruby makes sense - I mentioned Matlab or Octave, since that what the scripts put up were coded in. I just think it would be worthwhile to pool the collective programming / engineering brainpower on here to create utilities that can do the same function, but obviously much quicker than spreadsheets.

i've been working on this for a while, in ruby.. pm me and i'll send you my email lol.

[EAGLE5]

Is there a clear understanding of the algorithms the ECU uses to control injector firing? How about cranking?

[stugray]

Originally Posted by jsimon7777

Is there a clear understanding of the algorithms the ECU uses to control injector firing? How about cranking?

I asked similar questions on this thread:
http://www.ft86club.com/forums/showthread.php?t=49231

I would even like some simple state diagrams that show OFF->START->RUN_cold->RUN_warm->CLosedLoop->OpenLoop.

As they say "you can figure it out if you just read".

[ztan]

Originally Posted by vgi

would you also be able to pull 'fuel system status' and 'injection mode'?
ecutek guys say 1 is closed loop, 2 is open loop for fuel system status and 1 is port, 2 is direct, and 3 is combined for injection mode

Fuel system status:

A01C: FFF8DC0E (Colby gave me that one)
A01G: FFF8D2E2

returns an 8 bit parameter;
1=OL, not up to temp
2=CL
4=OL or decceleration fuel cut
8=OL due to system failure

Injection mode:
The parameter I defined above works:
1=Port injectors only
0=Direct injector only
Anything else = Port/Direct injection ratio

Note that this does not exactly tell the true story as it is the value before compensations/thresholds are applied.

You can also use the injector pulse width parameters to see what the port/direct injectors are doing (same for both A01C and A01G ROMs):
Port PW (before latency added):FFF887C8
Direct PW (I think): FFF887F0

[jamesm]

injection mode should be 1==port only 2==di only 3==combined.

[jamesm]

Originally Posted by vgi

after some logging we'll see if it's ever > 3

I wish you the best... I wish I knew enough about that stuff to contribute more.

[ztan]

Originally Posted by jamesm

injection mode should be 1==port only 2==di only 3==combined.

Do you know which RAM address is pulled for that? I saw the mode switch in Techstream but haven't found where that gets put in RAM.

The benefit of using the port/direct ratio RAM value is that you can see when your port/direct fractions change from 0 to 35 to 50 to 100%.

[jamesm]

Originally Posted by ztan

Do you know which RAM address is pulled for that? I saw the mode switch in Techstream but haven't found where that gets put in RAM.

The benefit of using the port/direct ratio RAM value is that you can see when your port/direct fractions change from 0 to 35 to 50 to 100%.

It's absolutely necessary for FI (or any time you change maf and injectors).

[jamesm]

Originally Posted by vgi

You could unless you sold your tactrix. I'm a noob and know pretty much nothing but you could log the known params addresses and see if anything is wrong, also check which params' addresses are missing from the 'required' for fi or 'goog to have' list. Then folks who have ida pro could probably pull those addresses.

i have ida pro and know some assembly but not enough to be useful. i think i still have my tactrix cable laying around somewhere...

[ztan]

Originally Posted by vgi

What is this param - Fuel_Status from default logcfg.txt 0xFFF8DBB0?
values range from 98.94 to 100

Fuel sender level

It doesn't matter if I filter my log Port_Direct_Ratio (FFF8A0F4) to 0 (DI only ) or 1 (Port only) - the E_Fuel_Injector_1_Pulse_Width_4byteExt_E60(FFF887C 8 ),
Ram_Fuel_Injector_1_Pulse_Width(FFF887D8),
Ram_Fuel_Injector_2_Pulse_Width(FFF887DC),
Ram_Fuel_Injector_1_Pulse_Width_4byteExt_E60???(FF F887F0)
columns still have values.
Shouldn't I see 0 pulse with on port injectors when in DI mode and vice versa?

That is one of the problems with this ratio: there are some compensations added afterwards and you will still get some fuelling values in an injector set when the table lookup suggests that you should be running none. The second and third value are the first IPW + latency added. The logic behind direct/port control is actually quite complex and a real snarl to try to work out from the ROM.

Fuel_Injector1_Latency(FFF8A048) is always the same - 68? Shouldn't it change with the fuel pressure?

Changes with voltage and MAP - will usually be around there.

[Ralph Spoilsport]

I got Colby's ecuflash beta, updated the firmware in my OP2 and recorded some stand alone logs yesterday (01C factory rom). It all appears to work and it's quite fast, yay!

Are there RR logger defs available yet? I want to try the "learning view" equivalent I understand has been added to RR.

[Td-d]

Been quite swamped at work, so unfortunately have not had much time to do heavy duty trawling for parameters, will try when I get a chance. Romraider logging alpha is up and running - but OBD parameters in mode 1, so much slower. Also learning I believe is not yet functional for the BRZs.

http://www.romraider.com/forum/viewt...p?f=14&t=10284



Sent from my iPhone using Tapatalk

[SkullWorks]

is anyone else going thru hell trying to get the beta to run on a Windows 8 laptop?

I have installed and used the official release ECUflash on my bothers WRX and got clued into downgrading the .netframework to 2.5 compatible to make the OP2.0 work in windows 8, but I can't get the BRz Beta Ecuflash to open on my laptop ATM...

Any brilliant ideas (already tried all compatibility settings for installer and installed program...as well as run as admin on both counts....)