Tactrix EcuFlash Info for BRZ 86 FRS Rom flash update and logging

[Kodename47]

Originally Posted by dave-

Just curious on file size differences compared to Td's RR definitions.

598900 Jan 20 09:34 RR ZA1JA01G - Metric & %.xml
599024 Jan 20 09:34 RR ZA1JA01G - Metric & Ratios.xml
834049 Jan 20 09:34 RR_ZA1JA01G.xml

Given you've added additional tables, do your def's have shorter/less descriptions or something which would account for the much smaller file size?

Edit:

Also there are some tables which are shaded pinkish in RR due to unknown axis? Are these correct?
AFR min/max Correction
Fuel Multiplier Display Offset
All the Fueling - Hotstart enrichment

In the original definitions there are quite a lot of unused old table names ported from older cars, namely boost control, that I removed as they aren't necessary. When I organised the file I found it easier for myself to remove these otherwise there was a large section of text I had to navigate around. Nothing necessary has been lost or removed.

The beta level tables are ones I haven't seen or know how they operate so I left them in the maximum user level state.

[Toyota John]

Originally Posted by Kodename47

In the original definitions there are quite a lot of unused old table names ported from older cars, namely boost control, that I removed as they aren't necessary. When I organised the file I found it easier for myself to remove these otherwise there was a large section of text I had to navigate around. Nothing necessary has been lost or removed.

The beta level tables are ones I haven't seen or know how they operate so I left them in the maximum user level state.

How did you remove the unused table names?

[dave-]

Originally Posted by Kodename47

In the original definitions there are quite a lot of unused old table names ported from older cars, namely boost control, that I removed as they aren't necessary. When I organised the file I found it easier for myself to remove these otherwise there was a large section of text I had to navigate around. Nothing necessary has been lost or removed.

The beta level tables are ones I haven't seen or know how they operate so I left them in the maximum user level state.

Thanks for the info.

Am I right in saying the opensource def's are still missing a lot of tables compared to other options like ecutek and brzedit? Has any done a comparison between them to get a rough idea exactly how much is different?

If brzedit offers more tunabilty than the current opensource defs, I'll just buy that. I'd consider ecutek (price dependant) if I could edit myself and not have to deal with the Australian Distro but not sure that is possible?

[Toyota John]

Originally Posted by dave-

Thanks for the info.

Am I right in saying the opensource def's are still missing a lot of tables compared to other options like ecutek and brzedit? Has any done a comparison between them to get a rough idea exactly how much is different?

If brzedit offers more tunabilty than the current opensource defs, I'll just buy that. I'd consider ecutek (price dependant) if I could edit myself and not have to deal with the Australian Distro but not sure that is possible?

Ecuflash has some tables that the retail version of ecutek doesn't and vise-verse. However if you are a big tuna you get lots more maps on ecutek and can requestest any map you want so i am told. They might be beta maps and may get passed down to use some day. I can't comment on brzedit. I don't think many people are using it anymore.

[steve99]

Originally Posted by dave-

Thanks for the info.

Am I right in saying the opensource def's are still missing a lot of tables compared to other options like ecutek and brzedit? Has any done a comparison between them to get a rough idea exactly how much is different?

If brzedit offers more tunabilty than the current opensource defs, I'll just buy that. I'd consider ecutek (price dependant) if I could edit myself and not have to deal with the Australian Distro but not sure that is possible?

@Kodename47 has merged ecutek and romraider defs to form the most complete defs you will find. for G series roms i believe

[Kodename47]

Originally Posted by steve99

@Kodename47 has merged ecutek and romraider defs to form the most complete defs you will find. for G series roms i believe

Yes, I've been comparing the what I have in ECUtek with those available in the existing definitions and finding any missing tables. This is only to get around the "missing" tables in the retail version of ECUtek hence I've only done the G series.

[Toyota John]

Originally Posted by Kodename47

Yes, I've been comparing the what I have in ECUtek with those available in the existing definitions and finding any missing tables. This is only to get around the "missing" tables in the retail version of ECUtek hence I've only done the G series.

Hook me up a C ROM

[Kodename47]

Just an FYI, I've changed some fine learning settings and now it's creating FLKC at low load like 0.1-0.3 etc. I've not changed any tables that should result in that so I was wondering if anyone had done the same? I'm currently on the A01G ROM, based on the fact that the A02G is defined the same I'll assume it's the same. Anyone tried on different ROMs?

What I've changed:
Fine Correction Retard Value - It still retards -1 no matter what I do.
Load Range - I've only adjusted the upper range
Rows and Columns for the FL Table in ROM - I've not set the lowest ranges any lower than stock.

TBH, it's stumped me a little. I was wondering if, like the Injector scaling, that maybe the ECU is using different parameters/settings.

Originally Posted by Toyota John

Hook me up a C ROM

Sorry John, missed this. It's all time, of which I have very little at the moment. When my house is done I'll try and copy across the G series definitions to the C series.

[Kodename47]

Following on from my last post, 114BEC seems to tie in with the FLKC retard value I'm seeing. This wasn't a defined address in the A01G/A02G definitions but is in the area of the ROM where all the Fine Learning values are.

I can't deduce the rest by looking through the hex, but one of the other settings I've changed must be the cause or have a knock on effect.




<table name="Fine Correction Range (Load)" storageaddress="114C20" />
<table name="Fine Correction Columns (Load)" storageaddress="114BC8" />
<table name="Fine Correction Retard Value" storageaddress="114BE8" />

<table name="Fine Correction Retard Value A" storageaddress="114BEC" />

[ztan]

I think that if you set the first FLKC load column to 1.0, you'll get corrections applied any time load is in that column (i.e. FLKC only increments in the first column when you are 0.72-1.0 load, but gets applied to the first load column which is 0.0-1.0). We don't know if FLKC incremented at <0.72 load or was only applied at low load.

The stock first load column cell is set to 0.72 so that no FLKC is applied in cells where there is no increment. In theory you could get a knock event between 0.72 and 0.70 which would activate the first column, but this is unlikely as load would be dropping whilst this hysteresis boundary was being crossed.

[Kodename47]

I have re-jigged the A01G and A02G definitions a little and to bring in line I have looked through the B01C definition so that all tables are named the same and are placed into the same categories. This should be a nice addition for those on B01C ROMs.
Download - ZA1JB01C Definition

There are no new tables defined, however essentially it allows direct comparisons as the tables are all now the same naming convention. Those using my G series definitions, it is worth getting the latest update.

[dave-]

Originally Posted by Kodename47

There are no new tables defined, however essentially it allows direct comparisons as the tables are all now the same naming convention. Those using my G series definitions, it is worth getting the latest update.

Is there a simple way to convert these to ecuflash xml's?

[steve99]

Originally Posted by dave-

Is there a simple way to convert these to ecuflash xml's?

Their is a utility in that converts romraider defs to ecuflash defs but your problem is you also need an updated 32bitbase file for ecuflash.

best option at present is do all your editing in romraider and just use ecuflash to flash.

untill tdd get arround to updating the ecuflash defs xand 32bitbase files.

[burdickjp]

I'm having trouble getting commanded AFR/primary open loop MAP enrichment to log correctly on a B01C ECU. Anyone have any luck?