Trying Me7Logger on a Volvo, late 01, early 02 S60 LPT auto. I put my ecu file in to create a template, it's a file I've not been able to find definitions for, although the odd maps are in the same place as in a defined older one I've got, I've managed to figure out a good few more just by spending time on all the different T5 auto and T5 manual newer and older bins too and actually got the car tuned up a bit so need some readings.

Found the page with the list of variables on it and was expecting to be able to find the alias and follow what I've got labelled and see if what I've done, is doing what I think it's doing. But I've pasted below what came up...

;
; Logging configuration template for file WinOLS (Volvo S60 (Original) - 359462).bin
;
; Template generated by ME7Info v1.20 (c) mki, 11/2010-03/2013.
; All automatically identified variables of the ecu are listed in this template.
;
; Make a copy of the template and uncomment the lines of variables which shall be logged .
; Optionally delete all unused lines and re-order the remaining lines as you like.
;

[Configuration]
ECUCharacteristics = WinOLS (Volvo S60 (Original) - 359462).ecu
SamplesPerSecond   = 20

[LogVariables]
;Name            [Alias]                             [; Comment]
wkra_0           ;{}                                 ; {last und drehzahlabh. Adaptionskennfeld f. wkr}
wkra_159         ;{}                                 ; {last und drehzahlabh. Adaptionskennfeld f. wkr}
zkrvf_0          ;{}                                 ; {Zähler, bestimmt die Frequenz der zyl.-individuellen Zündwinkelfrühverstellung}
zkrvf_1          ;{}                                 ; {Zähler, bestimmt die Frequenz der zyl.-individuellen Zündwinkelfrühverstellung}
zkrvf_2          ;{}                                 ; {Zähler, bestimmt die Frequenz der zyl.-individuellen Zündwinkelfrühverstellung}
zkrvf_3          ;{}                                 ; {Zähler, bestimmt die Frequenz der zyl.-individuellen Zündwinkelfrühverstellung}
zkrvf_4          ;{}                                 ; {Zähler, bestimmt die Frequenz der zyl.-individuellen Zündwinkelfrühverstellung}
zkrvf_5          ;{}                                 ; {Zähler, bestimmt die Frequenz der zyl.-individuellen Zündwinkelfrühverstellung}
zkrvf_6          ;{}                                 ; {Zähler, bestimmt die Frequenz der zyl.-individuellen Zündwinkelfrühverstellung}
zkrvf_7          ;{}                                 ; {Zähler, bestimmt die Frequenz der zyl.-individuellen Zündwinkelfrühverstellung}
zzylkr           ;{}                                 ; {Zylinderzähler der Klopfregelung}



Is the file just one of those awkward one's, or have I missed something ? Can I find and add the rest manually? Havent connected to the car yet, no point if I don't know what I'm looking at. Anyone logged these cars? What did you get?

Any advice would be much appreciated, I've attached my ori file if anybody fancies having a look and seeing if they get the same, I am working on a map pack for this layout but it's no where near complete. My car is now a HPT from what I've got so far but need to make sure before I can start going any further with it as I need to change hardware next then start scaling things I can't currently find...

What do you mean, this is a normal me 7 made by bosch like like any VAG car, it also has the standart odb2 requirments for logging(obviously) etc. If he wants to find more ram adresses for logging, AFAIK ( im not expert on this) he needs IDA or some way to trace them.

I didn't miss that but thanks. I've read that some people here put some serious work into the Volvo's too and didn't think I'd be the first attempting this. Might just buy a dice unit then.

ISO14230 has nothing to do with KWP

KWP is just a transport protocol standard.

ISO14 230 is standartised as kwp2000 though.


I was thinking of a 5 cylinder volvo in the future but , this throws me off a little bit :/ now. VR5 is my new goal though, that is VAG and it has some support.

No way!

Looks like ME7Logger uses a table in vag ecus which is used for the Measurement Blocks and other stuff which is not available in other ME7s.

The Volvo ECU might support readMemoryByAddress, but ME7Logger uses readDataByLocalIdentifier and a hack to circumvent the limits of
dynamicallyDefineLocalIdentifier. It directly writes to the memory address of the dynamic identifier table as the limit checks are not done upon reading but when defining.

So ME7Logger should rather be called VAGLogger IMHO.

This stuff does not work on my alfa ecus too, thats why i am working on a (patched) mcmess logging method.
Alfa/Fiat ECUs dont support dynamicallyDefineLocalIdentifier, but readMemoryByAddress, which can be used for logging but is a bit slow for many variables.
writeMemoryByAddress is implemented in some but does not work as it always reports an invalid format no matter how hard i tried.
And no its not a needed securityAccess login, i patched out the check for this, not even all ecus have securityAccess implemented anyways.

ME7Logger would not be hard to do, i basically have the cfg and .ecu parsing running and a KWP2000 HM-2 layer implemented,
but i do not own any VAG car and most likely never will, the ddli hack only applies to them.

So looks like i will not get around to replicate this part of ME7Logger, but it should not be too hard to implement.

ME7Info is another story, but i guess 360trev`s code could be expanded into something as capable or even more capable.

ME7Info is also quite VAG specific, will not find anything more than the stuff posted above on non VAG ecus.