ZA1JE00I stock rom added to first post

2015 Auto trans for Australia/Europe/South Africa

ZA1JA01G/ZA1JA02G files.I've just been loojking into someone's tune and I've noticed something. I have the 3 MAP sensor scales in my definition:
However upon comparing in ECUtek I have A correlating with the Atmospheric pressure sensor values. This may be worth confirming. It would also explain the extra values over the US ROMs as they don't have a atmospheric sensor.
@ztan @Td-d

When I put in my 3Bar sensor, I changed MAP scaling A,B, and C to all read the same and the altered scaling has not affected my ambient pressure readings at FFF8D290.

The value that 1000CC scales is stored in FFF87C80 - I have not logged this to see what it is yet.

I'm currently seeing what happens with just B and C changed. It's also a turbo setup. I had initially set all 3 the same which is how I noticed the above. ECUtek also only has 1 MAP scaling table which ties in with C.

Scaling C is definitely the MAP sensor.

I can't find where Scaling B is used yet, I can't find references in it to the ROM yet.

Scaling A is another sensor, I don't know which.

The 16 bit value is stored in FFF87CBC, after scaling sits in FFF87C80. I logged this just now engine off and got a steady 0V (=-20 kPa using stock pressure sensor scale and 3kPa if using 3Bar pressure sensor scale). I think it is unlikely this relates to ambient pressure - anyone want to log and see what this one is? These RAM addresses should be the same between A01G and A00C/A01C.

Here's a new ROM: ZA1JF10G - EUDM 2015

Hey steve
is that rom from the my16 car that issupposed to have a few more hp, dont have a def to look at tables can ecutek see them ? be interested if thier was tuning changes or its all to o with revised intake manifold ?

[32pfom

I don't now much more that what I said in the post. Also realised that the file was named wrong, it's an F10G.

I've just checked the AVCS, Ignition timing and fueling against an A02G. There are no differences.

thanks,

i got an F00C usa rom and ecuflash def, theier are some rearly minor changes in knock correction max A, ol fueling and throttle mapping, cl compensation tables, so minor to be negligable.

I've gone through and updated all my definition files. I found some poorly defined idle ignition tables and I have added some tables so that many of the files are now more complete and matching across types.

Standard File Definitions:
ZA1JB01C Definition xml
ZA1JB01D Definition xml
ZA1JA01G Definition xml
ZA1JA02G Definition xml
ZA1JA01I Definition xml

Custom File Definitions:
ZA1JA01G with Metric Conversion
ZA1JA02G with Metric Conversion
ZA1JA01G with Metric Converion & Ratio Tables (ECUtek Comparison)
ZA1JA02G with Metric Converion & Ratio Tables (ECUtek Comparison)


OFT Zip Files
OFT Manual - Contains LC and FFS
US C Series OFT
ADM/EUDM G Series OFT

OFT Auto
US D Series OFT
ADM/EUDM I Series OFT

This one will come in the my17

I had a quick look at the latest ZA1JF00C rom and its same tuning as previous roms bar some very minor fueling and timing changes like 0.5 degrees and 0.5 or less AFR changes in a couple of places cannot see any HP in it.

After the last complaint, I have done a complete set of cross checking and fully defining what may reasonably be required. As I possibly have the most defined G series definition, I have gone through C,D and I and defined all the same tables. The folder structure may be different to others but I have tried to stick to Romraider's native naming structure where possible. I have checked that all tables are directly comparable. The links below have been updated. The only things that I now can't define easily are the CEL codes, although if anyone needs any that aren't defined then I'll see what I can do ;)

The main updates:
All cranking tables defined (A through to J)
All Idle Tables (A through to I)
CL/OL Delay tables specific to AT or MT
Rev Limit B
Idle Ignition Timing specific to AT and MT
Idle Throttle Targets & Failsafe

If you downloaded on my last update, I would suggest that you download again.

no chance for idle AVCS :cry::cry:

Not seen it defined and I don't have it on ECUtek either so can't test it. It's not really a required parameter.

Hey guys - I'm busy defining F10G, just been stupidly busy at work, time's at a premium...

there are in techstream as a test option , it is single controls

Are we talking tables, or logging parameters? Normally, AVCS is not at play during idle for a range of reasons (oil pressure not being the least of them).

If it's tables, PM me, and maybe I can help.

@Td-d feel free to update your github with my defs. They were all originally based on your latest definitions.

Thanks for that, will do when I get some time this weekend maybe. Outside of doing the Ecuflash defs as metric some time back, just have not had the bandwidth to allocate to it, rather time consuming...

THX ^^

I update my rom ja01j

i ganna email you about what what i have information about AVCS

ZA1JF10G is up: http://www.romraider.com/forum/viewt...p?f=34&t=12178

I've also ported the LC/FFS code across for the OFT ;)

Hi @Td-d noticed the new F01C def on github has LC/FFS tables if someone tries to edit those parameters (insert values) a stock non patched rom its probably bricked ecu .

Would it be better if standard defs had those tables removed from def ? :iono:

thanks

Yeah, ideally they should not be in there for a stock rom - but no, it won't do anything even if you do edit it erroneously - the code is in empty space in the rom, so all you would be doing is changing a couple of long words, which are not referenced, from 0xFFFFFFFF to whatever the float value is.

Is there a DI injector scalar somewhere in the ROM? The "GDI Flow Rate" table appears to be a correction factor? Surely the injector rate is no 1cc/sec @ 20MPa, 1.2V

gdi pressure multiplier check our the differences between an oft petrol and e85 rom is the easiest way thier is also a injector scalar to the pi

Sorry what I meant was has anyone discovered the DI injector Scalar, I can see the GDI Pressure Multiplier tables, but surely they multiply a scalar that's yet to be mapped?


Anyone got a disassembly handy?

The DI maps relating to DI flow & injection are:
GDI Flow rate (Probably the one you want)
GDI Pressure Targets A & B
GDI Pressure Multipliers A & B

A01G:
There is also another scalar which is used to multiply with the result of GDI Multipliers A and B before the value is passed to the GDI flow table:

has anyone had issues logging a ZA1JD00G with Tactrix and the G-series logcfg.txt from the first post? I have it logging data (LED's flash differently from the first post, just fast flashing all colours) but the data is wrong. Could the RAM address be different for late 2014/2015 ROM or perhaps I just have it setup wrong...


EDIT: found it here http://www.ft86club.com/forums/showp...&postcount=178

The ram addresses are different for the D00G rom, the g series logcfg.txt files is for A01G rom.

their is a dump of doog ram addresses in the first post you will need to substitute in the appropiate addresses into the old logcfg.txt files.

thge tactrix should recognise that old file it will just log incorrect, if its just doing the rainbow colours and not producing a log file or the error file its not connecting to ecu of your logcfg.txt is wrong

the file must be called logcfg.txt not logcfg.txt.txt or something and it must be in root directory.
dont edit it with a fancy text editor like word, just use notepad so no extra characters are added like formatting stuff.

Thanks mate, worked out the RAM addresses were different when the logs came back with wierd values.

Does anyone know the RAM address for MAF volts for D00G?

pm @Td-d he may be able to help with that

Hi there

I just want to ask about weird looking ALPHA tables before i try to flash them.

I already got a OFT and gained some knowledge about editing roms and OP2(Thanks for all the great work!)
My car got the ZA1J700G and i want to flash a little modified version of the OFT ZA1JA01G ( Ignition timing, Maf scale, Rev Limiter)

There are the 4 maps that look obvious way of the scales. All others seem ok!
They are all Alpha maps and maybe thats the reason for missing scales and way off RPM scales for example.
I used the OFT V2 ROM and this def file
https://github.com/TD-D/SubaruDefs/b...)/ZA1JA01G.xml

Here a Screenshot of the maps i found
http://abload.de/thumb/screenshot2015-10-191k3svo.png

When i temporary loaded the ZA1J700C Rom with the ZA1J700C OFT Def file Overrun fueling RPM resuming looks good, but the 3 Alpha Idle Control maps stil look off the scales

So, is it a bad idea to write the rom this way to my ecu?
(Sorry for bad english)

Best regards

definitly a definition mismatch, dont flash that.

oft roms have calibration id alterations to suit oft system.

read the romraider tips thread below in signiture.

if your going to use ecu flash then use A01G roms and defs assuming your car is compatable with A01G roms, yes 700G is compatable with A01G

Thanks for the hint @ steve99

I read the most treads about guides and "how to" but i am still in trouble with the def files.
Now I try to flash the untouched A01G ROM with the A01G definition file but the missing entries are like the same

From my unter standing, I need the newest 32BITBASE.xml from here:https://github.com/TD-D/SubaruDefs/b.../32BITBASE.xml put it to:
C:\Program Files (x86)\OpenECU\EcuFlash\rommetadata\subaru\Bases

need a updated definition files like this:https://github.com/TD-D/SubaruDefs/b...Z/ZA1JA01G.xml put it to C:\Program Files (x86)\OpenECU\EcuFlash\rommetadata\subaru\BRZ\2012

and the untouched ZA1JA01G which i took from here:http://www.ft86club.com/forums/showthread.php?t=62332
This file is not a modified calID one like some OFT ones, so the definition file should be the right one.
The log shows always the right paths of the base and definition file.

Compared to your guide(which i really like) i can't find any mistakes.
Would be glad if someone could verify / help with the problem :)

Ok had a better look.

Those tables you refer to are also corrupted using the defs i have in ecuflash and the 32bitbase i have been using for ages to flash A01G roms.

So it should be ok as long as you use A01G roms and defs just DONT edit any of those tables with corrupted values using ecuflash. Actually i would not even open those tables in ecuflash as even that may introduce a corruption, probably set your userlevel back to advanced not developer then ecuflash wont access those alpha tables.

i never noticed those definition errors as i do all my editing in romraider and i have never tried adjusting those tables you found.

ztan put us onto a good idle fix , just run 0% port injection at 0.2 and 0.3 loads ie zero out those coulums in the pi\di ratio tables



if you want to edit those tables use @Kodename47 definitions in romraider see here a few posts back just do all your editing in romraider then just flash with ecuflash.
http://www.ft86club.com/forums/showp...&postcount=411