NefMoto

Good Morning all,

Feels like a noob question, but feel the answer may not be noob at all  :D.

So I have been tuning my R53 recently and seeing good results for part load fuelling and other bits, not touched WOT yet as running engine in, but I am looking for ways to improve logging speed.

I have seen a lot of reference on here to RAM logging whereby code in the ECU sends the values in RAM down the CAN/KLINE channels where it can be recorded...first question is is my understanding of that correct? Also seen KWP based logging which again may work, but unsure how...

So...does anyone have any experience of this with this ECU please? There is so little out there on the EMS2K it's a nightmare for someone wanting to learn...

Thanks in advance!

To add some more info to this post, in the event someone can help, here is where I am at.

I have used Testo with the EMS2K prg and can get a 5hz log rate, however that is not fully accurate as it takes 1s to cycle through the data I am logging.

So I made a custom PRG using the jobs for Air Mass, STFT, Engine Speed & Throttle position, and get a log rate of 1 per second.

Obviously I can use this for some data at cruise and mild changes, but this is nowhere near enough for any decent data collection.

I am aware of the memory areas in RAM which contain things such as throttle position, engine speed, coolant temp etc, but using Tool32/INPA seems to be the only way to request them.

The bottleneck in testo (I guess) seems to come from the need to send data to the ECU, then receive the response, and then decipher the response using the factors etc given in the PRG file. So even when I combine them, its still a case of Send request -> receive answer -> decode answer -> send next request -> receive answer etc etc.

Is there a way to send 1 request and get all the data I need? Or is there a way to have the data output by the ECU and effectively just "sniff" for it?

I ask myself exactly the same question !
for my part I managed to communicate only in ISO9141 and not in KPW2000

$2C is usually wide open on BMW. Implementations do not always follow the standard and can differ from ECU to ECU.

thank you very much for responding

I still have to figure out how to send several requests at the same time

Your first step is to stop using PRG files and EDIABAS and implement the whole thing using J2534 or KKL.

no actually i don't use this at all i did all the electronics myself also i am using an esp32 microcontroller to communicate with the K-line port i am coding the KWP initialization right now once initialization done my next step is to switch to fast mode

Very good.

You need ISO 14230-3 document, it will describe how the $2C service works.
Beware! On many BMW cars they made their own implementation totally of $2C. They just used it like $22 grouping on UDS and you can't define anything.
Then you can check if there is $23, but $23 is very slow if you want to read a lot of data.

On all the UDS cars you can use $2C to read RAM, and also depending on ECU vendor on some K-Line ones too.
I think someone posted here that they got EMS2K logged using $2C because it was possible to define ram cell addresses.

Of course you will need exact A2L or reverse the binary to know what the RAM addresses are.

I also have to mainly look at how to decode the message I receive because it is extremely long

how to open a .PRG file?

https://github.com/gushmazuko/bmw-advanced-tools/blob/master/app/EDIABAS/ECU/EMS2K.prg

With a special disassembler.
The PRG does not contain ram addresses.