^ tried that, still didn't find them ;) Have to do it the hardway, through tracing the logic...

Alright, Vgi - try these ones:

E_AF_Learning_1_A_StoredExt_E44_Range_A??? FFF81618
E_AF_Learning_1_B_StoredExt_E45_Range_A??? FFF81620
E_AF_Learning_1_C_StoredExt_E46_Range_A??? FFF81628
E_AF_Learning_1_D_StoredExt_E47_Range_A??? FFF81630

ok, will post tomorrow morning :)

B01C issue
 

@Td-d: Here's my logcfg.txt and logcfgout.txt for the B01C ROM. I also added a log of what shows up under the "RPM" and "Speed" columns. I disabled the defogger switch start to get it logging.

@D-VO - your defogger switch is not working because you've got it defined as an 8 bit value - needs to be float.

Engine speed parameter has the wrong address, should be FFF8DB98
For speed, try using FFF8DB9C rather.

I suggest going through the logcfg and comparing it to the address list posted, looks like some might not have been copied across.

Bingo...

I'm seeing a lot more correlation now between the LTFT and these stored values. In fact, there's only one value that I'm not seeing (-5.49806, which kicks in above 20 g/s - i.e. D range of Table A) which may be in another ram address - but on the most part you can see how it's using values either from the ranges in B or in A, depending on the MAF g/s.

I suspect that if I manage to dig out the fueling mode, it will demonstrate how it's switching across the two tables.

So that being said, it's not as useful as in the older roms - I was hoping to provide a way to see a 'learning view' in the absence of having that tool for the BRZs - but if the tables are different, it switches between the tables constantly.

@Td-d:
It's still not working. It's set up properly now.

paramname = Defogger
paramid = 0xFFF8939F
isfloat = 1
......................................
; logging trigger condition
conditionrpn = Defogger,1,==
action = start
conditionrpn = Defogger,0,==
action = stop
:iono:

Edit*
I'm assuming that when I get a value that looks like this (2.35E-38) under the defogger that its still the wrong address no?

I gave up on the defogger trigger on G series ROM. Could log it fine but triggering never seemed to work.

I just use RPM trigger or you can use something like coolant temp , or just plug tatrix in when your ready, it seems remarkably tollerant of being plugged in on the fly. ;)

I was thinking the same thing. I'm just worried that I'm going to inadvertently rip the port right out of the car. HAve you had success with those triggers?

@D-VO - my bad, it is an 8 bit value... It's curious - Vgi if I'm not mistaken got it working? Otherwise, I'll get back on trying to see what the issue is.

I just bought a OBD extension with 90 degree plug for port under dash. 90 degree plug keeps it out of the way and the other end routed to come out at centre console where its easier to plug in and not wearing out obd socket on car.

Try and clean out your logcfg file to only what you want logged (i.e. not just commenting out) - that's what Adriang did, and that seemed to sort it out.

I'm gonna give it a shot on the way home.

By the way: Whats the difference between KC Advance and KC Advance IAM in OP2?

I have my Knock Correction Advance Max table set to all 8.09's, so when using the OFT the KC Advance line would decrease in the event of knock. Which one of these lines would mirror that function? It's hard to tell currently since the KC_Advance lines raises temporarily to 8.086 then drops back down to 7.84, whereas the KC_Advance_IAM stays solid at 7.84. IAM is currently 0.97.

Dang...still no good. I've removed all comments and only have a few parameters left.

Strangely enough it logged just fine when triggered by the brake pedal (0xFFF89393). I still have a feeling the defogger has the wrong value in the logcfg fiile.

@D-VO - if you want to see whether it's the defogger switch or not, remove the isvisible=0 line (that basically means you don't see the value in the log). That will let you know if it's switching or not - I'm pretty certain it is the right value.

I have a theory - in Vgi's logcfg, the addresses are ordered contiguously, which follows the request to sortpids = 1, making for faster logging. Yours are not - maybe that's the issue.

@Td-d: Strangely enough removing the isvisible line from the defogger value made it work as its supposed to, but it still logs the defogger value...? It now shows the proper value of 1, and logs when the defogger switch is depressed. Success!! :happyanim: I still have my addresses scattered by the way. Now all I have to do is find the proper IAT and coolant addresses in the list provided.

Excellent!

CAN Mode 23 requests
 

Been playing around with CAN addressing again - pulling RAM data gives faster update speeds than the OBD routines.


Mode 01:

Request:
Response:
00 55 converted from int to dec/100 = 0.85 g/s

Mode 23:
MAF RAM address in my ROM is FF F8 7C 70

The 14 after mode 23 request: first 4 bits are size of response length descriptor, second 4 bits are size of ram address descriptor.

Request:
Response:

Code:

---

00 00 07 E8    63                    3F 59 99 9A
ECU response  OBD mode 23          RAM data
              response

---

3F 59 99 9A converted to float = 0.85 g/s

A01G AVCS RAM addresses: