Thats amazing guys! Thank you!

@D-VO what are you using for boost control? I know ztan is using an EBC but really don't like the idea of spending $500+ on what is effectively a box with pretty lights for the interior and I'd never bother with per gear boost etc.

That said, all my searches on the forum end up with people achieving this solution using ecutek. How is it done in opensource world?

Can anyone point me to a thread on here showing install using something like the Grimspeed 3 port solenoid?
Which tables on A01G are relevant?

Should add that I've already removed the Sprintex kit and is being replaced with a turbo kit. Installer and tuner are more than competent, but first turbo so I'm doing some leg work to save time. Was going to just go manual control but if I can get a boost control solenoid to play nice with romraider/ecuflash then great...

@dave- ECUtek is all done by repurposing the CPC solenoid control but uses custom maps to achieve boost control. I've not seen anything on OS that's comparable. I have CPC duty defined in Romeaider however there is no way to control this to be useful for ECU controlled EBCS using OEM ROMs.

My FRS is supercharged so no boost control other than the BOV that came with the KW kit. I have an Apexi AVC-R digital controlling the boost in my Evo though which is also tuned with ECUFlash. IMO its one of the best on the market. I tried tuning one of those GS ones on a friends Evo with no success unfortunately. Ever since then I've felt that going with a piggyback boost controller is best especially if you have an external wastegate.

I thought about working with the stock ECU, but was happier getting the pretty lights and control on the fly without pulling over for a 2 min reflash then waiting another 3 for AVCS to start working again. I also really like the boost graph that my GReddy OLED EBC gives me.

Tuning boost from scratch with duty cycle maps, integral and proportional maps is quite doable, but I suspect the time taken getting it to run just right would be too big once you factor in the time you need to reflash each tune. Now if we had live tuning...

Yeah EBC is a last resort. We'll start with a manual bleed and see how it goes. Leaving it up to the tuner.

Yes live tuning would be great but I suspect its not going to happen unless you quit your day job.

Is there anyone else logging incorrect data output from the Exhaust VVT in the ZA1JB01C ROM?

The scaling that was attached (scalingrpn = x,50,-) really didn't make any sense given the output on the Intake vvt. Without it, I'm seeing data that follows very closely to the AVCS table I have set, however the data logged for the exhaust VVT does not follow.

Note for Australian and possibly Eurropean BRZ 86 owners.

toyota and subaru appear to now be using separate ROM designations for MY 2016 cars

see here
http://www.ft86club.com/forums/showp...25&postcount=1

The roms that come from 2016 BRZ manual and toyota 86 Manual are no longer the same designation , its possible that they are compatable but best to use the identical romid that cam with car.

It possible the Auto brz/86 will be similar.

also note that G and I series seems to be for toyota and P & Q series now for BRZ.

P series in old designation was for japan rom.

Please be very carefull with your rom designations

I'm done with the Q definition, will post both P and Q defs shortly.

anyone interested in defining the rest of the Base Timing Idle (In Gear)(Above Speed Threshold) for ZA1JB01C, only defined/comprehensible up to 2000rpm then the headers are random. also I cant seem to save changes made to this table..
want to use this to play with some overrun things....

edit: Found using Kodename47's Defs.

Now another question. Can I safely use Kodename47's Defs to modify a stock ZA1JB01C, and include in it all the timing changes etc from an OFT_2.072_ZA1J700C rom that added power, and flash the stock rom (basically a mirrored image of the OFT rom but with added definitions) to my cars ECU using my openflashtablet

reason being I would rather benefit from additional definitions, than the LC/FFS settings etc.

The C series OFT definitions are all based on B01C so you can use them for a standard B01C ROM. Just don't touch the LC or FFS parameters if you're using the OFT definition on a stock based ROM. However as the OTS maps are based on B01C then you can use these anyway and keep the additional features.

okay, that makes sense to me,

just to clarify on the second part of what you said though, I can use your Stock Rom ZA1JB01C definitions in romraider to define and modify an OTS 700C rom(or B01C, whichever) ??? I didnt think that would work as I have read many times that OTS Tunes use OFT Defs.

thats what I am after, the added tables and such from your definitions for a stock rom. I only found the ones for a stock rom, so I figured I could just modify a bone stock rom, with all the OTS tune modifications (besides LC/FFS), and i tried it, but the OFT would not allow me to upload it to the tablet...

Maybe this explains it:
> Standard ZA1JB01C definition is for table/parameter addresses for ZA1JB01C ROM.
> OFT OTS Files ZA1J700C/ZA1JA00C/ZA1JA01C are actually ZA1JB01C files with internal ID data changed, so the ZA1JB01C definition has the correct addresses. All I've done is change the definition ID lookup to work on the OTS ROMs.
> OFT requires the same Cal ID as your stock ROM, so you cannot flash a ZA1JB01C file if your stock one was different. If your stock cal ID was ZA1J700C then you need the OTS ZA1J700C file to work.

Did you download my zip fie with all the C series definitions? If so that should be fully forward/backward compatible and you just add them all into Romraider.

Thanks for the clarity. I found your folder for the OFT C definitions. Originally when i seen the link for them I thought they were the standard OFT defs included in your post, and didnt include additional defs.
All loaded up now though and flashed into the car, time for overrun testing.

Thanks alot!

Sent from my LG-H812 using Tapatalk

Seems like this has popped to my attention, P0068 and P0069 CEL limits. The CEL is not enabled on G/I ROMs, but it is on the US cars. Haven't looked into any others as yet.

ZA1JB01C - MT
ZA1JB01D - AT

Hi all, i am owner of BRZ 2012 jdm auto. i hv purchase op2 cable and download my rom
ZA1J700B. But no luck on looking for any suitable def for this rom,tried change the cal id, but still cant find a match def. will it possible if i flash other region rom to my ecu? Hope to get help from this forum.

No do not flash a rom from another region to your car you must flash a rom that is compatable

700B is an old rom calibration.

See if you can find out from dealer if ZA1JA02B is compatable as it would appear it is the updated rom for your car but i am not certian, maybe look at Tech service bulitens in you country

you can create your own Flash Only definition for your unsupported rom but will not be able to edit.

Thanks steve99.

i hv try to contact brzedit. but seems they got no interest to reply me.
we do not hv any local tech bulletin as this car was bring in as recond car fr Japan to Malaysia.

i hv also thnkng to try za1ja02b rom. but i also not sure does this support on 2012 car.
sob sob

Are you looking to tune car or just update to latest rom.

maybe try talking to dealer in japan or maybe on japanese forum.

If you need full definito to tune you will need to post in the www.romraider.com forum in ecu definition request area, but those guys work for basicly free or donations and it can take some time

Youe could also try the open flash tuning guys to see if they can support your rom www.openflashtablet.com you get tunes and devie for $500 usa

not sure if you have ecutek tuners their but is quite expensive

Take it to Toyota or Subaru dealer for service. Have them apply all recalls and updates, don't commit to anything that costs money. Then once you've gotten the ECU updated, you will find definitions and tunes available.

too bad our local toyota and subaru dealer will not accept the grey import cars.

Yes we do have ecutek tuner. but i still prefer opensource. thanks for your info steve. :party0030:

Hi all,
need some help/clarification.

I've managed to pull my OFT tunes via tactrix cable and edit/check tunes with ecuflash.
Problem is, in ecuflash the Launch control / flat foot shift parameters does not show up (it does in RR).

Am i using the wrong Def in ECUFLASH ?
all other tables are identical to RR's.

thanks in advance

if you want opensourse definition for your rom then only td-d on romraider forum can help you

read and understand the info in Romraider tips link below, the oft roms have special software patch for lc\ffs and its only on some roms , romraider and ecuflash defs do not reference this patch only the oft definitions reference the software patch on oft roms.

Beware some oft roms are calid adjusted and can cause problems with tactrix\ecuflash rom flashing, if you dont understand whats going on with oft roms its very easy to brick your ecu.

A02B is indeed the latest that will be compatible with the hardware (there is an F00B, but that's a 2015 IIRC).

This will need to be defined, none of the B series seem to have ever made it to the queue. Odd.

Thanks to all who have contributed to this thread. It has been very helpful.

Does anyone happen to have OVC Duty logging parameter addresses for OP2 on the B01C ROM? The only one that I've found that seems to work is 0xFFF8C20C, but I don't know which bank this is in reference to.

Thanks.

These are the ones I have:
Ram_Intake_OCV_Duty_Left FFF8C20C
Ram_Intake_OCV_Duty_Right FFF8C218
Ram_Exhaust_OCV_Duty_Left FFF8C3C8
Ram_Exhaust_OCV_Duty_Right FFF8C3D4

Thanks. Were these released somewhere else?

I don't think so...

Has anyone else encountered problems with logging after the recent firmware update on the OP2?

After plugging it in, the leds keep on running the 'rainbow cycle'. At first I thought about a misconfigured logcfg.txt, so I tried stripping it down to the bare essence without success. I tried the g-series one linked in the op as well. Still rainbow cycle.

Picked up a fresh micro sd card, put it in and still no luck.

Weird thing is, I'm still able to read out the rom and even writing to the ecu works without any problems.

The currently installed version on my Tactrix device is: 1.16.4647
Could anyone check logging capability with above mentioned revision?

PS: my logcfg.txt

mines working ok, but I have not updated in last couple of months.


ill check what version it is.


your SD is formatted FAT32 ?


do you get a logcfg.out file with the debug info in it ?

Don't have laptop connected to Tactrix for logging, it must be standalone for logging to work.


make sure you use a simple text editor it doesn't like any non-text characters in the logcfg.txt file


assume it all worked ok before update ?


I'd try bending both rows of pins inwards slightly (an old full size SD card or similar works well) to get better contact with obd socket.

For the record, there is logging with a laptop connected, but it's the standard OBD2 style logging, like what Torque does. Just want to make sure which kind of logging he's doing.

I was trying to do the OP2-standalone sd-card logging.
Both sd-cards I've tried were formatted fat32. File encoding should be ok, too.
Took tons of logs since last year, so yes, it was working before.

I'll try bending the pins since the device is basically useless without logging capabilities. :-(

A logcfg.out file is generated everytime I plug the Tactrix in, but I can't spot anything unusual out of it. Here's a copy of my last try: click

I too am having logging problems using same firmware revision as freerunner.
New tactrix cable direct from tactrix.
Successfully reading and writing ROMs.
Tried multiple logcfg.txt from this thread and those loaded with latest ecuflash. I can get a logcfg.out but no CSV files.
Attached logcfg is a minimal version that are tried immediately after a successful ROM read.
Logcfg out.txt is the logcfg.out file renamed so that I could attach here.

Tried two sdcards, reformatted at least twice. They are 8gb but this is stated as OK on the cboles development thread on openorg

Very interested in feedback on this.

Thanks in advance. (Thread has been invaluable getting the flashing side of things going).

Thanks steve

looks like a bug in tactrix firmware.


Please contact the Tactrix support guys at www.tactrix.com

If both of you guys contact tactrix it should get sorted pretty quick, they are usually very good considering their is only two guys in the company ;-)

Tactrix emailed and support request created on their support manager. Fingers crossed for a reply since my previous query was acknowledged by the software but no followup. I know they're small so maybe on holiday etc.

Looking forward to checking IAM and MAF scaling once the logger works - will use your helpful links !!!!

Rgds
Steve

At least I'm not the only one. I've begun to doubt me.

Email sent. I'll keep you up to date if any news pop up.
Thank you anyway, Steve.