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

[Sportsguy83]

Thanks. I did do a full read before write and waited more than 15 secs everytime but definitely sounds like it might be the pins.

Great thread man.

[aagun]

can any one help find J rom logcfg.txt

[steve99]

Originally Posted by aagun

can any one help find J rom logcfg.txt

the guy you need is @Td-d he should be able to give you a list of ecu ram addresses for your J series rom he will need to know which rom eg A02J then you can substitute thoe ram addresses into a G series logcfg.txt to make a J series logcfg.txt as scaling should be same.
best to emial him from www.romraider.com forum he is moderator their.

[B-R-Z]

Hey Steve, I went into romraider last night and was thinking of enabling FF shift option. When I use the RR def included with the roms, the option is not there. However, when I use the oft def, it appears. Is it not safe to edit rom when not using RR def? Using b01c 91 uel ROM.

[Kodename47]

Originally Posted by B-R-Z

Hey Steve, I went into romraider last night and was thinking of enabling FF shift option. When I use the RR def included with the roms, the option is not there. However, when I use the oft def, it appears. Is it not safe to edit rom when not using RR def? Using b01c 91 uel ROM.

The B01C OFT tunes are not cal ID hacked so both standard and OFT definitions are compatible. If you're using the OFT ROMs then the LC and FFS coding is there so use whichever definition gives you visibility of the parameters.

[steve99]

Originally Posted by B-R-Z

Hey Steve, I went into romraider last night and was thinking of enabling FF shift option. When I use the RR def included with the roms, the option is not there. However, when I use the oft def, it appears. Is it not safe to edit rom when not using RR def? Using b01c 91 uel ROM.

+1 on what @Kodename47 said.
lc ffs is a patch to rom code so only oft defs will have the tables to adjust parameters.

make sure you only have one def linked in romraider as it might pick the wrong def if they are for same rom.

make sure your using oft v2defs for v2 tunes and not the old v1.5 defs,

v2 defs come in v2 tune zip flle

[B-R-Z]

My car came with a A01C ROM and I was told (I think by Steve) that OFT A01C is a cal-id hacked B01C. It is safe to use B01C ROM and B01C defs, correct?

[steve99]

Originally Posted by B-R-Z

My car came with a A01C ROM and I was told (I think by Steve) that OFT A01C is a cal-id hacked B01C. It is safe to use B01C ROM and B01C defs, correct?

Yes you can just use B01C defs and roms in a car that originally came with A01C , their is and idle fix tsb out for dealers to update all cars on earlier roms B01C on customer complaint re idle.

http://www.ft86club.com/forums/attac...1&d=1395947828

Roms later than B01C may not be compatable

see first post in this thread for rom compatability

[phrosty]

So right now we treat log records as snapshots in time, but in reality there's some serious skew going on -- if we poll 20 parameters, the last parameter polled is a lot closer in time to the next record than the current one.

It'd be interesting if we could measure the skew for each column. Maybe with the first row in a log being their offsets in time. Know if Tactrix has a way, or if we could calculate it based on the Tactrix config?

[Kodename47]

Originally Posted by phrosty

So right now we treat log records as snapshots in time, but in reality there's some serious skew going on -- if we poll 20 parameters, the last parameter polled is a lot closer in time to the next record than the current one.

It'd be interesting if we could measure the skew for each column. Maybe with the first row in a log being their offsets in time. Know if Tactrix has a way, or if we could calculate it based on the Tactrix config?

How would it measure it and genuinely why would it matter? You don't need data that accurate. Does it matter if your ignition timing is 0.01 degrees different, or your MAF voltage has increased by a mV since the time value given?

Playing devils advocate here, but to do that as accurately as you suggest you would need an individual row for each cell of data. Seeing as each row is given a time value, to separate each column's data poll (or skew) you would have to allocate that poll a time value and therefore you would have a row that shows the time value and then one cell of data.

It's the logging resolution that really matters, if that's good enough then the data you collect will be more than adequate.

[phrosty]

Originally Posted by Kodename47

How would it measure it and genuinely why would it matter? You don't need data that accurate.

If I can get better accuracy, why not? More of a curiosity, certainly not a need.

Assuming each record follows the same plan, I think having the start of the file look like this would be sufficient:

Time,RPM,MAFv,FBKC,etc...
+0ms,+0ms,+20ms,+10ms,etc...

Then you could calculate each cell's actual time as an offset from the "Time" column.

[Jaden]

So, it was my understanding that all the OFT's use a B01X that was changed for each bin and had a renamed calid, but when I use a B01D logcfg, I get zeroes for many params including engine speed/RPM...

This makes logging pretty much useless.. Any ideas what could be going on?

Jaden

ok so I re added the B01D logcfg and went out and did another log. It does show rpm but it doesn't seem right. I think it's off. Here is my log file. I know I redlined a couple of times and it idles at 700 so I don't understand why I'm getting these numbers...ok can't attach csv... oh well

[aagun]

Make sure that you useing correct logcfg file for your rom type

[Jaden]

Originally Posted by aagun

Make sure that you useing correct logcfg file for your rom type

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