Ok, but when I look into *.ecu file of ME7Logger, I find all RAM variables ME7Logger can log, deffined with ECU specific RAM address.
This address you will find also in a Damos or A2L for that specific ECU too.
These are the values, INKA also logs, when I use INCAs application tool. So INKA will log the same way like ME7Logger AFAIU ?!
So, if we have EDC15.map and EDC15.ecu file with the RAM adresses for EDC15 specific values, ME7Logger can log EDC15, IMO.
I don´t think Bosch got defferend protocolls to log ME7 and EDC15 for theire application system, but I don´t know jet
You have no idea what you are talking about.
Instead of spewing out random gibberish go and read the KWP2000 specification.
INCA can log as many parameters at once as DDLI allows, whereas with ME7Logger the amount of variables is limited by only CPU performance.
That said, ME7Logger will not log ANY EDC15 EVER, because the method used is a specific exploit only found in ME7.
If you want to log EDC15, write your own tool that will use DDLI and read the EDC15 FR for how many variables can be logged simultaneously using that method.
As for logging unlimited number of parameters, you need to reverse engineer EDC15 DDLI routine and see if it susceptible to a similar array overflow hack as ME7.
