That's weird, I always get a log file, Defogger always logs -can see it toggle 0/1 on switching but it won't act as a trigger , just continuously logs.

RPM trigger works though

In the older version of ecuflash, you needed to limit the number of characters that the parameter titles were using (i.e. not the number of param, but the title). Not sure if that's still and issue.

Steve - what version number is the new patch? PM me.

what do you guys think about using the cruise control button to log rather than the defogger? The timing out is kinda annoying, but then again I could just use the rpm trigger right?

That should work too, Merp uses it extensively in the patches for other Subaru roms. I'll see if I can find it - will need you guys to test addresses for me.

There's a newer version of the beta on the tactrix website, by the way:

http://www.tactrix.com/downloads/ecu...7_win_beta.exe

I finally got the B01C rom to log! The defogger parameter isn't working so I had to use the RPM trigger, and it worked. I didn't put all the new parameters, but the ones I did use some of them seem right but some of them don't. Here is a log file and my logcfg.

I see the defogger isvisible = 0 is still in your logcfg file - did you try and see if the defogger works with this line removed?

Yes, I tried that. I eventually just copied a new logcfg and started over, that's why it's still there

Looks like my csv didn't upload last night, here is the datazap.me chart. Looking over it this morning the only parameters that really don't look right are fuel_system_status and RPM. BUT the fuel_system_status_2 and the RPM2 look right. IAM is showing all 1's and IAT and IAT_2 both look right but one has to be ambient air(IAT), and other is actual intake temp(IAT_2) I think.

http://datazap.me/u/ml/b01c2?log=0&data=17-21-22-23

I was messing around with the OP2 tonight and found that there are some combinations that won't allow the logger to work. Throttle position in conjunction with one of the other params (can't find it now) will not allow the log start to trigger.

There are also a few that have combinations that force the logger to record when the car is on and off. AF_Correction1 and AF_Learning1 in combo make the logger record as long as the ignition is on.

When using both MAF and MAF2 params the defogger switch start doesnt work; as well as when using both MAF Voltage and MAF params.

This is a short list of the ones I found that cause the logger to run with the ignition on.

; similar to STFT / 100
paramname = STFT_AF_Correction1
paramid = 0xFFF8A5EC
isfloat = 1

; same as LTFT / 100
paramname = LTFT_AF_Learning1
paramid = 0xFFF8A774
isfloat = 1

paramname = STFT
paramid = 0xFFF8DB74
isfloat = 1

paramname = LTFT
paramid = 0xFFF8DB78
isfloat = 1

paramname = Direct_Injector_PW
paramid = 0xFFF887E8
isfloat = 1

paramname = Direct_Injector_PW_Ram
paramid = 0xFFF887F0
isfloat = 1

:D

*EDIT* I just realized that in previous logs I had these closer to the end and they worked just fine. When I put these to the front of the list it causes an issue.

So did you actually get the defogger to show in the csv files at all?

Yep!

http://i189.photobucket.com/albums/z...pse785614e.png

can you upload your logcfg.txt please! This is on B01C right?

Correct. Here ya go!

Please feel free to let me know if you can find any other params that are loggable. I have a few missing from here.
:thumbsup:

Just in case anyone was interested; I found the working addresses for both the IAT and Coolant temps for the ZA1JB01C, from the list provided. I also wrote a little scaling RPN to convert the both of them it to Fahrenheit. :D

paramname = IAT
paramid = 0xFFF8DBA4
isfloat = 1
scalingrpn = x,1.8,*,32,+

paramname = Coolant_Temp_F
paramid = 0xFFF8DB88
isfloat = 1
scalingrpn = x,1.8,*,32,+

The only problem is we need ltft/stft to work together.

Thought it might be helpful if people posted up their STOCK factory ROMs with latest revision's (CAL-ID's) so other with older ROM's could update

If you post them up I will add them to original post

Have A01G and B01C already.

Thanks

Steve, I've got all the roms - want me to Dropbox them to you?


Sent from my iPad using Tapatalk HD

Here's the link: https://www.dropbox.com/sh/eueghzbz9...KMUoVPXMs_pDga

Mate that would be great thanks probably just the latest revision of each :thanks:

So I was looking at OEM transient ignition retard tables in RomRaider and Ecuflash. Those looked normal in RR and off by about 20 in Ecuflash with 32BITBASE file I got from OP. So it would seem like the offset is off by that 20 in the base.

The link in the OP is to the wrong (standard) 32bitbase. This is the one that needs to be used:

https://raw.githubusercontent.com/TD.../32BITBASE.xml

Ok, this one has proper scaling reference, thanks.

fixed link in OP thanks

added latest roms from each series to original post thanks

Can someone test this out for me for A01C, fuel system status:

FFF8DC0F

8 bit value

For A01G it's FFF8D2E3

On A01G rom I have been using
FFF8D2E2
8 BIT
NO SCALING
it been returning fuel system status for ol cl fine

do you want me to test FFF8D2E3 ??

no problem will try it and log result :)

maybe my brains off today whats MRP ?

the logcfg.txt file im usng is attached to first post

@Td-d tried FFF8D2E3 on G rom always logged "0"

FFF8D2E2 appears to be correct address for suel system status ol/cl ect.

see attached files :-)

best I have is MAP manifold absolure pressure for G rom

;paramname = MAP
;paramid = 0xFFF87C60
;isfloat = 1
;scalingrpn = x,0.133322368,*

Exactly. Dale's put you ether a useful script for naming he ODB routines - there are two parameters that are in that routine, want to check if the other is Di/pi


Sent from my iPad using Tapatalk HD

Thanks, oh well...


Sent from my iPad using Tapatalk HD

Hey Vgi - yes, sorry, did not have the time to test yet.


Sent from my iPad using Tapatalk HD

Sup fellas, so I got the open source setup working. Now I notice that in Rom Raider I see no values so that I can log Knock, or any sort of KCA values? Am I missing something here? Thanks in advance.

Romraider logging does not work yet

logging is direct to SD card in tactrix adapter see first post

Thanks, I somehow missed all that. Got what I needed, I read the ROM and assumed I was done. I'll give all this a shot and revert, thanks bud.

Not strictly correct - there is a beta version of RR that logs the standard ODB parameters already.

All the extended params require SD card logging.


Sent from my iPad using Tapatalk HD

That's what I thought because that's the version I tried and it does log a few things but not everything I need. Which is why I asked since I didn't see any parameters for knock. I'm going to give the SD card logging a shot tonight and I'll report back.

Quick question guys. Got it all setup but not working. Which "logcfg" would I need to use if my ROM ID is ZA1JA00C? I keep reading through the end of that first post but maybe I'm just missing something.

Use either of the first two C logcfg files donr use the bo1c stuff it wont work
is your sd card foratted fat 32
make sure logcfg.txt is in root directory
you should get blue led flashing when you plug tactrix to obd port if not it not reading file

if you get logcfg.out it read logcfg.txt if you not getting a logXXX.csv then its not understanding your logcfg.txt file, look in logcfg.out for clues or it not reading obd port correctly ignition musy be fully on