Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB - Please post a logcfg file that works for OP2.0

- Software Tuning (https://www.ft86club.com/forums/forumdisplay.php?f=88)

- - Please post a logcfg file that works for OP2.0 (https://www.ft86club.com/forums/showthread.php?t=55758)

Please post a logcfg file that works for OP2.0

I cannot get my OP2.0 to log anything in standalone mode.

Would someone please post a logcfg.txt file that they have personally witnessed working on a BRZ.
I would even appreciate seeing the logcfg.out file that it generates.
My ROM is ZA1J700C if that helps any.

I dont even care what data is in it.
I just want to verify that my tactrix is even capable of logging.

You can use the logcfg.txt found in the program files directory to test the logging mechanism, it will generate logs. The numbers are all garbage though as they aren't reading the correct addresses for your ROM. You need to flash on ZA1JA01C for the logging to actually work.

I thought I would still be able to log "something" but I would need the definitions if I wanted to know what the data means.
For instance the mem addr for RPM on a ZA1JA00C is 0xFFF8DB80

So if I try to log:
paramname = RPM
paramid = 0xFFF8DB80
isfloat = 1

with my ROM (ZA1J700C) I should still read something from 0xFFF8DB80 but it might not be RPM.

Quote:

Originally Posted by stugray (Post 1454295)

You're right, that's exactly the behavior I was getting. Rpm at idle was a steady -1.37886 on that ROM.

- AdrianG

Quote:

Originally Posted by AdrianG (Post 1454270)

You can use the logcfg.txt found in the program files directory to test the logging mechanism, it will generate logs.

I tried the BRZ example logcfg file provided with ECUflash, but I added a trigger for RPM > 0. I got nothing in the logcfg.out file except the init information.

If I am reading garbage maybe the trigger never worked.

Quote:

Originally Posted by AdrianG (Post 1454304)

You're right, that's exactly the behavior I was getting. Rpm at idle was a steady -1.37886 on that ROM.

- AdrianG

What did you use as a trigger?

No trigger, it starts logging as soon as it turns on. Not ideal, I know, but AFAIK the defogger hasn't been discovered yet.

Here's what I use, the ones below the comment at the bottom seem to work on ZA1JA01C but not sure if you want them for your test. If you delete/comment out everything at the bottom it'll be an unmodified copy of the file (i think).

Code:

type = obd

protocolid = 6 ; ISO15765

mode23txaddrwidth = 4                ; mode23 req format info

mode23txlenwidth = 1                ; mode23 req format info        

mode23rxaddrwidth = 0                ; mode23 req format info

mode23uds = 1                        ; lets OBD channels know you are using mode23 UDS

sortpids = 1                        ; sort these PIDs by value to potentially make for fewer requests (=faster)

calcsampinterval = 1000                ; timing parameter - leave as is - will make default for release version



; here are some known RAM addresses for ROM ZA1JA00C

; addresses are likely different for other ROMs

; you can comment out ones you don't need, but keep in mind that with

; the block read nature of UDS, reading extra parameters that have

; adjacent addresses comes at very little bandwidth (=sample rate) cost



paramname = load

paramid = 0xFFF8DB6C

isfloat = 1



paramname = cool_temp

paramid = 0xFFF8DB70

isfloat = 1



paramname = STFT

paramid = 0xFFF8DB74

isfloat = 1



paramname = LTFT

paramid = 0xFFF8DB78

isfloat = 1



paramname = MAP

paramid = 0xFFF8DB7C

isfloat = 1



paramname = RPM                                

paramid = 0xFFF8DB80                                

isfloat = 1                                



paramname = speed

paramid = 0xFFF8DB84

isfloat = 1



paramname = advance

paramid = 0xFFF8DB88

isfloat = 1



paramname = IAT

paramid = 0xFFF8DB8C

isfloat = 1



paramname = MAF                        

paramid = 0xFFF8DB90                                

isfloat = 1                                                                



paramname = fuel_press                                

paramid = 0xFFF8DBA0

isfloat = 1                                



paramname = lambda

paramid = 0xFFF8DBA4

isfloat = 1



paramname = O2_volt

paramid = 0xFFF8DBA8

isfloat = 1



paramname = evap

paramid = 0xFFF8DBAC

isfloat = 1



paramname = fuel_level

paramid = 0xFFF8DBB0

isfloat = 1



paramname = amb_press

paramid = 0xFFF8DBB4

isfloat = 1



paramname = O2_curr

paramid = 0xFFF8DBB8

isfloat = 1



paramname = cat_temp

paramid = 0xFFF8DBBC

isfloat = 1



paramname = ECU_volt

paramid = 0xFFF8DBC0

isfloat = 1



paramname = abs_load

paramid = 0xFFF8DBC4

isfloat = 1







; experimental parameters below this line



paramname = accel_pedal_angle

paramid = 0xFFF8922C

isfloat = 1



paramname = IAM

paramid = 0xFFF816F4

isfloat = 1



paramname = throttleplate_angle

paramid = 0xFFF89030

isfloat = 1



paramname = requested_torque

paramid = 0xFFF8B490

isfloat = 1



paramname = knock_advance

paramid = 0xFFF8B0AC

isfloat = 1



paramname = fine_knock_correct

paramid = 0xFFF8B14C

isfloat = 1



paramname = feedback_knock_correction

paramid = 0xFFF8B0B0

isfloat = 1



paramname = engine_load_4byte

paramid = 0xFFF89148

isfloat = 1



paramname = Intake_temp

paramid = 0xFFF87C64

isfloat = 1



paramname = ignition_total_timing

paramid = 0xFFF8ADF8

isfloat = 1



paramname = gear

paramid = 0xFFF895D9

isfloat = 1



paramname = requested_torque

paramid = 0xFFF8B490

isfloat = 1



paramname = gear_calculated

paramid = 0xFFF895DA

isfloat = 1

excellent! Thanks for the help. It worked.

Coincidentally I set it up to trigger on RPM.
I removed the trigger and it did log finally and the RPM value was zero the entire log so of course it wasnt going to start logging.

Now I will get back to trying to log voltages from the OEM pins on the OBD connector.

Good luck! Now get on with flashing ZA1JA01C before you torch your DI seals. ;)

- AdrianG