Here's my current log config: http://pastebin.com/tNTbKqzK

paramname = Load
paramid = 0xFFF8DB84
isfloat = 1

assuming that ram address is correct for your rom type your reading the "load" from the ECU it calculated by the ECU and not scaled by the tactrix ie no scaling is applied to value read from ECU.

The values you should range from almost 0 at idle to about 1.3 full throttle under load

None of the configs from the OP scale load, so I'm guessing the address isn't right, or something similar.

try @phrosty he is on b01c or d rom sure he has a working logcfg.txt for that rom. strange load does not work as most guys would want that for maf scaling.

B01C/B01D load:

I've got a B01C/B01D log file pre-made with all the typical fields here.

Added

I rom logging file
D rom logging lile
Cam timing log parameters for G & I roms thanks @ztan

General question here about bad flash a while back.

Basically went to flash like normal and it failed, don't recall the error and can't find the full log but I left the ignition on and only hit write again. It worked but I got the following error on the second write attempt. I assume it is because the first failed write erased everything?

Did I avoid a brick by leaving the ignition on and just doing another write? Or is ecuflash smart enough that it would just been able to write the ROM again regardless of what I did with the ignition?

You will probably never know.

but always safer to try writing again before turning ignition off as you can always try again after turning ignition off.

The ECU is still in program mode from previous write attempt, till ignition is turned off.

Their are three ROM area in the ECU

1. SH Boot area (very low level boot area) need serial communication to access ie soldering wires to ECU
2. USER BOOT Area can be accessed via OBD port
3. USER ROM area - the area flashing devices read/erase/write/talk to.

Appears all flashing devices only write to the third area USER ROM area.
So you connect your flashing device, it initially tries to communicate with the software code in the USER ROM area via OBD communication method. If no response the Tactrix and other system can try communicating with the USER BOOT area code. This is your get out of jail free card if flash fails part way through.

Main causes of failed flash are bad connection to obd port, low or flat car battery or laptop issues.



As I understand it Tactrix tries to communicate with the ECU via the OBD communication method first . I believe this is communicating via the software thats contained in the rom you flash. You only get one go at this method as USER ROM area is ERASED before write takes place.

I suspect what happened was

1. Initial flash failed part way through for unknown reason.
2. USER ROM area now erased or partial write
3. Second time tectrix tries to talk to ecu via code in USER ROM area which is trashed it fails
4. Tectrix tries comms via USER BOOT code, comms established , USER ROM area erased and written successfully.


The big problem occurs when you write complete rubbish code, or for some reason the partially written rom cause the ecu to loop or go into some other weird state where you have no communication via the OBD port.

Check your obd connection by either READING ROM or LOGGING and wiggle connection if it drops out during READ or you get heaps of short log files you have connection issues.

Yeah I suspect it was bad connection, though I always do a read first and that was fine. Possibly the port/pins are damaged from constantly unplugging a scangauge and connecting a BT dongle or tactrix at the track to collect data. Haven't tried a write since but logging has been fine.

I use a short obd extension cable for this reason and leave thet plugged in all the time so i dont wear out port on car.

even better buy one with an inbuilt switch

[ame="http://www.amazon.com/gp/product/B00UR5XBMW/"]Amazon.com: OBD 2 16pin Male to Female Right Angle Diagnostic Extension Cable with Power Switch: Automotive[/ame]

Yeah hindsight and all.

Oh, that's clever.

Hi All,

Just wondering Has anyone got a rom raider logging definition made yet?

Also about almost bricking the ECU, My laptop battery (was faulty and showing wrong battery level) has died before during a write and i turned ignition off and then on and was able to write the flash again fine. Its also happened on my WRX before (i know need a new laptop battery) and same thing it was able to write fine on retry.

No romraider logging available for brz/86 other than basic obd stuff.

The RR guys busy on 2015wrx ecu, best talk to them re any work on rr logging for brz/86

only option with tactrix is the SD card logging at present

Re batterys , I would not push your luck, best to plug laptop into mains power , only have ecuflash running and disable wifi . Also make sure car battery is good.

Tactrix/ecuflash has OEM recovery mode (user boot) if normal obd mode (user rom) fails but its still possible to get ecu into a state where it wont recover when laptops or car battery dies mid flash if the user rom area loops or goes into a weird state due incomplete flash Same with any other flashing system.

added ZA1JA02J rom for middle east region

@steve99 was able to flash a friend's auto 15' FRS with Stg. 1 93 pumpgas ROM.

I let Ecuflash correct the checksum.

The Ecu did not want to accept the key (like it was an Ecutek/BRZEdite, etc. locked ECU but it was not, he bought the car brand new fresh from the lot), until it finally accepted it and successfully flashed the ROM.

I can't thank you enough for this post. It helped tremendously!!

He has a D00D ROM.

thanks

usually that sort of thing is caused by bad connectio, tactrix adapter has thin pins ,i bent mine inwards slightly.

or you hit go to flash without waiting 15 secs

i always do a read first and wiggle cable to see i have a soild connection the obd ports in thes cars can be a intermittent.

I always do a full read before doing a write.

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.

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.

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.

+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

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

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.

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:

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

Logging OFT E85 using A01D...
 

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

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

yes but it's not that simple...
 

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

I'm not
 

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

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.

Here is my log...
 

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

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.

The defrost button works for me. Yeah, yeah... timeout.

@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