OP2 logging discussion

[D-VO]

I made a scaling rpn for the Manifold relative pressure to read boost (psi) if anyone wants to try it against their known good boost guage. This paramid is for the B01C.

paramname = Manifold_Relative_Pressure(PSI test)
paramid = 0xFFF88F78
isfloat = 1
scalingrpn = x,0.0193367747,*

I'm using a KW SC kit and the boost looks about right when compared to what I see on the forums.

[d1ck]

Originally Posted by Td-d

Try this:

FFF8DBD0 Ram_Fuel_Air_Commanded

This worked using the following scale:

x,14.7,*

[D-VO]

@Td-d: Do you have the paramid for logging AFR commanded on the B01C ROM?

[Td-d]

Originally Posted by D-VO

@Td-d: Do you have the paramid for logging AFR commanded on the B01C ROM?

RAM:FFF8DBE8 Ram_Fuel_Air_Commanded

[steve99]

I have added these additional AFR commanded and boost parameters to the Tactrix info post see files attached to that post

http://www.ft86club.com/forums/showt...10#post1645010

[mad_sb]

Does anyone have the address for cruise control on / off for ZA1JA00C?

I have logging working without any triggers using some of the configs from: Tactrix EcuFlash Info for BRZ 86 Rom flash and logging

But I'm not having any luck triggering with defog.

[steve99]

Originally Posted by mad_sb

Does anyone have the address for cruise control on / off for ZA1JA00C?

I have logging working without any triggers using some of the configs from: Tactrix EcuFlash Info for BRZ 86 Rom flash and logging

But I'm not having any luck triggering with defog.

I have found that the triggers are very hit and miss, very often dont work at all, i have given up on them even trying to use coolant temp or rpm was no good.

suspect their is some issue with op2 code..
@Td-d might be able to hel but hes is on holidays, or the taxtrix guys


i think @vgi may have it working

[Toyota John]

What are the code differences between logging A01C and B01C?

[Td-d]

Originally Posted by Toyota John

What are the code differences between logging A01C and B01C?

The best way to check that would be to look through the two definitions and compare. From what I recall, it was not anything significant (mostly in as yet undefined areas of the rom to do with idling if I'm not mistaken).

[mad_sb]

Originally Posted by steve99

I have found that the triggers are very hit and miss, very often dont work at all, i have given up on them even trying to use coolant temp or rpm was no good.

suspect their is some issue with op2 code..
@Td-d might be able to hel but hes is on holidays, or the taxtrix guys


i think @vgi may have it working

Thanks for the info .. I used OP2 stand alone extensively on my evo X and ralliart sportback. Both of those I triggered using cruise control. Sadly I can't find either config file these days to look at the various triggers i used.

I can log the defog param perfectly fine, but it never see's the trigger... Very strange, I may play around with parameter order. In the mean time I can at least log and with a good sample rate.

[mad_sb]

Update:

I got the defog trigger working. In my case the issue was the encoding type of the logcfg.txt file. At some point I switched the ecoding to plain UTF-8. Using this encoding, none of my files would work. When I switched them back to "UTF-8 without BOM" they worked perfectly. I verified this by taking the working no-trigger file and saving it to UTF-8, which broke logging completely, then saving it back to UTF-8 without BOM and it started working perfectly again.

I'm using notepad++ and can change the encoding at will, i suspect windows notepad and some others might mess with the encoding, In fact I think I remember that from years ago with the ralliart. So... if you any of you are having strange logging issues or can't get triggers working on an otherwise working config, check the encoding type and make sure it us UTF-8 without BOM

[mad_sb]

I will try ASCII but i'm am 100% certain my issue was UTF8 vs UTF8 without BOM. Of Course that is not to say other formats don't work equally well, just that the OP2 does not read the UTF8 without BOM format correctly and results in parse errors.

Originally Posted by vgi

to be on a safe side i would rather suggest people use plane ASCII (ANSI) mode for their files. I don't know for sure but considering standard C/C++ reads/writes ASCII text file by default I doubt there was an effort made to actually support a full UTF8 character set supported.

ASCII is a subset of UTF8 (UTF8 was designed for backward compatibility with ASCII) so it's possible all the chars in your file were just ASCII. If any true UTF8 characters will be in your file I guess it may or may not work.

Also, many editors have a default encoding, you should check what that is. Many editors make an attempt to auto-detect encoding and if they detect some UTF8 characters they may place BOM in the file (BOM is a sequence of bytes (EF BB BF) that allows the reader to identify the file as an UTF-8 file). Windows notepad should be safe to use as default encoding is ASCII unless it detects UTF8 chars, then it will place BOM in the file. It also puts /r/n for new line instead of just unix /n, but it think it should be safe.

[BRZoomTX]

I tried using your log config on my A01C ROM, however I seem to be getting invalid values (ie. RPM is logged as "1" the entire drive). I also need to remove the defogger switch condition to get logging working. I've uploaded my datalog here:

http://datazap.me/u/slowbaru/93-octa...5-6-9-16-22-24

I am using the OFT Stage 1 93 octane OTS A10C ROM. If this is based off the B01C ROM, is it possible I have different memory addresses? Does anyone have information on how to verify the correct memory addresses to throw in to the log config file?

@Td-d @d1ck @steve99 Any one of you have ideas? Thank you!

Edit-


I tried using @AdrianG 's log config but I am still getting incorrect values. If someone could provide some info on how to verify the correct memory addresses it would be appreciated.

[steve99]

Originally Posted by [Ron]

I tried using your log config on my A01C ROM, however I seem to be getting invalid values (ie. RPM is logged as "1" the entire drive). I also need to remove the defogger switch condition to get logging working. I've uploaded my datalog here:

http://datazap.me/u/slowbaru/93-octa...5-6-9-16-22-24

I am using the OFT Stage 1 93 octane OTS A10C ROM. If this is based off the B01C ROM, is it possible I have different memory addresses? Does anyone have information on how to verify the correct memory addresses to throw in to the log config file?

@Td-d @d1ck @steve99 Any one of you have ideas? Thank you!

Edit-


I tried using @AdrianG 's log config but I am still getting incorrect values. If someone could provide some info on how to verify the correct memory addresses it would be appreciated.

you will need to use the B01D_B01C logcfg.txt third file from the end in this post

http://www.ft86club.com/forums/showthread.php?t=62332

their is also the B01C ram addresses if you need other addresses/parameters.