Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB
Page 29 of 79 « First 1925262728 29 3031323339 Last »
Show 40 post(s) from this thread on one page

Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB (https://www.ft86club.com/forums/index.php)
-   Software Tuning (https://www.ft86club.com/forums/forumdisplay.php?f=88)
-   -   Tactrix EcuFlash Info for BRZ 86 FRS Rom flash update and logging (https://www.ft86club.com/forums/showthread.php?t=62332)

steve99 06-28-2015 11:20 PM
Quote:
Originally Posted by Jaden (Post 2302623)
I've tried both A01D and B01D... Because it's an OFT rom type I'm not sure which is right because they use a different base rom.

The base file I'm using doesn't tell me either because it's a modded one to go with the OFT specific roms which are named based on the name of the rom file you use, which is A01D in my case but isn't necessarily that type.

JAden
Your living dangereously. my friend

oft v2x tunes for D series roms are usually based on B01D except for D00D which is D00D
v1x tunes based on A01D from memory

you rearly need to confirm with hex editor so you use correct ecuflash definition
their are three instances of calid in rom all three should be same in unadjusted rom

in oft rom the first two arround 8000 and 10000 may be altered the third calid arround 13000i s the real calid

Jaden 06-29-2015 01:15 AM
I'm not
 
Quote:
Originally Posted by steve99 (Post 2302769)
Your living dangereously. my friend

oft v2x tunes for D series roms are usually based on B01D except for D00D which is D00D
v1x tunes based on A01D from memory

you rearly need to confirm with hex editor so you use correct ecuflash definition
their are three instances of calid in rom all three should be same in unadjusted rom

in oft rom the first two arround 8000 and 10000 may be altered the third calid arround 13000i s the real calid
I'm just talking about the logcfg...I was very careful in ensuring I had the right match for the bin before flashing it. In fact I had created a thread telling people what to look for when bringing up the bins to verify that it's accurate.

Jaden

steve99 06-29-2015 01:36 AM
Quote:
Originally Posted by Jaden (Post 2302833)
I'm just talking about the logcfg...I was very careful in ensuring I had the right match for the bin when flashed it. In fact I had created a thread telling people what to look for when bringing up the bins to verify that it's accurate.

Jaden

Ok thats great :-)

post your log up to datazap.me and post the link make sure you make it public.

you might have to check the logcfg.txt against the ram address lost for your rom type.

i cannot check the ram addresses as i am on G rom, if it looks like their no good then you will have to ask the romraider dissassembly guys eg td-d or maybe the tactrix guys to have a look.

Jaden 06-29-2015 11:32 AM
Here is my log...
 
1 Attachment(s)
Here is one of my logs and I'll attach the logcfg file I'm using.

Jaden

http://datazap.me/u/jaden/log-1435591610?log=0&data=9

I did verify the addresses based on what has been put out there for the B01D...

steve99 06-29-2015 04:23 PM
Quote:
Originally Posted by Jaden (Post 2303148)
Here is one of my logs and I'll attach the logcfg file I'm using.

Jaden

http://datazap.me/u/jaden/log-1435591610?log=0&data=9

I did verify the addresses based on what has been put out there for the B01D...

remove the trigger lines they never seem to work well, it will just log any time its plugged in then.

conditionrpn = RPM,0,>
action = start

conditionrpn = RPM,0,==
action = stop

phrosty 06-29-2015 04:59 PM
Quote:
Originally Posted by steve99 (Post 2303615)
remove the trigger lines they never seem to work well, it will just log any time its plugged in then.

conditionrpn = RPM,0,>
action = start

conditionrpn = RPM,0,==
action = stop
Indeed. Be careful of these. I left the car alone for a weekend and came back to a huge log of a car that was off, and a dead battery. I always unplug it when not in use now.

Ultramaroon 06-29-2015 06:05 PM
Quote:
Originally Posted by steve99 (Post 2303615)
remove the trigger lines they never seem to work well, it will just log any time its plugged in then.

conditionrpn = RPM,0,>
action = start

conditionrpn = RPM,0,==
action = stop
The defrost button works for me. Yeah, yeah... timeout.

steve99 07-13-2015 12:52 AM
2 Attachment(s)
@NotSoJDM

reply to your PM

see first post in this thread for compatability
most of the newer stock roms their

cars that came with A01C are compatable with B01C rom and your better off using that as its a later rom with some extra factory updates for idle stability ect

see below for older ones

steve99 07-20-2015 07:12 PM
ZA1JE00I stock rom added to first post

2015 Auto trans for Australia/Europe/South Africa

Kodename47 07-28-2015 06:50 PM
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:
Code:
<table name="Manifold Pressure Sensor Scaling A" storageaddress="1000CC" />
<table name="Manifold Pressure Sensor Scaling B" storageaddress="1000E4" />
<table name="Manifold Pressure Sensor Scaling C" storageaddress="11CC20" />
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

ztan 07-29-2015 06:17 AM
Quote:
Originally Posted by Kodename47 (Post 2338404)
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:
Code:
<table name="Manifold Pressure Sensor Scaling A" storageaddress="1000CC" />
<table name="Manifold Pressure Sensor Scaling B" storageaddress="1000E4" />
<table name="Manifold Pressure Sensor Scaling C" storageaddress="11CC20" />
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.

Kodename47 07-29-2015 06:25 AM
Quote:
Originally Posted by ztan (Post 2338908)
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.

ztan 07-31-2015 07:05 PM
Code:
<table name="Manifold Pressure Sensor Scaling A" storageaddress="1000CC" />
<table name="Manifold Pressure Sensor Scaling B" storageaddress="1000E4" />
<table name="Manifold Pressure Sensor Scaling C" storageaddress="11CC20" />
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.

Kodename47 09-16-2015 04:22 PM
Here's a new ROM: ZA1JF10G - EUDM 2015


All times are GMT -4. The time now is 06:32 AM.
Page 29 of 79 « First 1925262728 29 3031323339 Last »
Show 40 post(s) from this thread on one page

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
User Alert System provided by Advanced User Tagging v3.3.0 (Lite) - vBulletin Mods & Addons Copyright © 2026 DragonByte Technologies Ltd.


Garage vBulletin Plugins by Drive Thru Online, Inc.