ECUFlash - Getting close!

[jamesm]

Originally Posted by ztan

Thanks.
Which table/s did you alter to affect direct injection scaling? I can see the port injector scaling easily.
Did getting this balance right also help your tip-in knock?

the table in brzedit is called "GDI Flow Rate", not sure if it's defined in RomRaider or if so what it is called. Getting it right had no effect on the tip-in knock, though i had figured it might. the afrs are more stable getting back on the throttle, and when you're just cracking it open, but still no help in getting rid of the -1's

[Td-d]

Originally Posted by jamesm

the table in brzedit is called "GDI Flow Rate", not sure if it's defined in RomRaider or if so what it is called.

Yup, it is. Same name.

Sent from my iPad using Tapatalk HD

[stugray]

How are the table names defined?
Is there embedded text in the ROM?

[jamesm]

Originally Posted by stugray

How are the table names defined?
Is there embedded text in the ROM?

they are defined in an xml definition file used by the software, which is essentially a hex editor that uses said definition file to make things a bit more human friendly.

[stugray]

Originally Posted by jamesm

they are defined in an xml definition file used by the software, which is essentially a hex editor that uses said definition file to make things a bit more human friendly.

I understand that part. What I was asking is how do the definition tables get generated?
Do the reverse engineers have to decompile the code completely and understand every single bit of it, OR are the table definitions in ASCII embedded in the ROM code?

[ztan]

Originally Posted by Td-d

I think both are port scaling - the one I defined originally has the same logic that I've seen over and over in the roms - but it was pointed out o me ht the other value is that defined by oft and brzedit as the scaling. I would be interested to hear feedback from someone whether my original scaling does the job.

I have tested with the following.

Stock scalings: Td-d 222.32 (2707090/x); BRZ 228.05 (60000/x, 263.1 raw)

Stock ROM:
Idle till IPW1=0: STFT+LTFT = -7.15%

Stock ROM, all GDI maps changed to 100% port:
Idle till IPW1=0: STFT+LTFT = -11.05%

Td-d scaling to 232.32, GDI at 100% port:
Idle till IPW1=0: STFT+LTFT = -10.17%

BRZ scaling to 218.18 (275 raw), GDI at 100% port:
Idle till IPW1=0: STFT+LTFT = -13.1%

BRZ scaling to 240 (250 raw), GDI at 100% port:
Idle till IPW1=0: STFT+LTFT = -4.41%

BRZ scaling to 250 (240 raw), GDI at 100% port:
Idle till IPW1=0: STFT+LTFT = -0.48%

BRZ scaling to 250 (240 raw), GDI back at stock:
Idle till IPW1=0: STFT+LTFT = -0.32%

BRZ scaling at 235 (255 raw) and Td-d scaling to 235, GDI stock:
Idle till IPW1=0: STFT+LTFT = -2.71%

[jamesm]

Originally Posted by stugray

I understand that part. What I was asking is how do the definition tables get generated?
Do the reverse engineers have to decompile the code completely and understand every single bit of it, OR are the table definitions in ASCII embedded in the ROM code?

i'm pretty sure they have to decompile and understand the code. i don't think it's as simple as searching for strings.

[vgi]

Originally Posted by Td-d

If you guys can put together a request list of parameters required, I can start trawling around for addresses (once I'm back from holiday )

Is there any way we could help you?

so far i think ztan has asked already for defroster address so that standalone logger could be tuned on/off at will. the cruise control would work too.

Btw, how do you determine what is the length (num bits or bytes) of a specific parameter at that address? if i'm not mistaken then tactrix standalone logger by default (unless specified) assumes that it's a 1 bit param value, so the length should be specified for most of those?

[Td-d]

Originally Posted by vgi

Is there any way we could help you?

so far i think ztan has asked already for defroster address so that standalone logger could be tuned on/off at will. the cruise control would work too.

Btw, how do you determine what is the length (num bits or bytes) of a specific parameter at that address? if i'm not mistaken then tactrix standalone logger by default (unless specified) assumes that it's a 1 bit param value, so the length should be specified for most of those?

You have to look at the code to see whether it is using mov.b mov.w or mov.l to put the data in the various registers (whether an r register or an f register).

In terms of help, if you are willing to start pulling all the standard switches from the SSM routines (I see here's a discussion going on the RR thread) would definitely speed things up. I'm back in town in two days, so can get going again.

Sent from my iPad using Tapatalk HD

[mad_sb]

Originally Posted by jamesm

i saw the same thing tuning my car for e85. i would log fueling error with the ports turned off and get corrections in one direction, then log with ports only and get different results. getting both 'in spec' independently fixed virtually every drivability problem i had prior to doing this, particularly rough idle, rpms hunting, dipping rpms coming to a stop, stumbling at tip-in, etc. all related to big swings in afr introduced by the disparity in required trim when the switchover happens between injection modes.

you can use the 3 port/di ratio tables to set the ratio. 100% is port only, 0% is di only.

Yup, this miss-match exists stock and is what prompted me to write the first maf scaling how-to with brzedit.. I just didn't realize this was the cause at the time lol

[ztan]

Originally Posted by Td-d

If you guys can put together a request list of parameters required, I can start trawling around for addresses (once I'm back from holiday )

Once you're back from holiday, would be interested in seeing logging addresses for:

MAF voltage
Direct/port injection status or ratios
Knock sums
Defogger button

[Td-d]

ztan - can you test the following two addresses for me for MAF Voltage?

Ram_Mass_Airflow_Sensor_Voltage FFF848FE
Ram_Mass_Airflow_Sensor_Voltage_1 FFF8490E

Both 2 byte parameters (16bit)

[AdrianG]

Has throttle position for ZA1JA01C been found yet? I'm able to log now, but VirtualDyno won't open the file without throttle position, RPM and Time.

[Td-d]

Originally Posted by AdrianG

Has throttle position for ZA1JA01C been found yet? I'm able to log now, but VirtualDyno won't open the file without throttle position, RPM and Time.

In post 312.