NefMoto

After using me7logger on my 1.8t going back to vcds to log med9 ecus is such a pain, anyone know if there are any plans on writing something similar for med9? If I can help in any way I can try and assist.

I forget the sample rate of VCDS, but I think in turbo mode its 10Hz for 3 4 item blocks (I don't recall excactly...don't have access to logs at the moment). If you use this, you can use the hack to the measuring block groups talked about in another thread (called make your own measuring blocks or something of that nature). Its not perfect, but using the item list in the func doc you can get access to just about any useful measurement. You also have the option to get some of your channels by hacking into the drivetrain canbus and sniffing off of there...you can get some pretty useful info off of it.

Send me a MED9 ecu, and I'll make a tool. Or at least try to make one.
I don't know if MED9 will talk KWP2000 over K-Line, if it will, it's pretty easy, if not, a CAN interface is needed.

@prj
Amazing offer from your side!
Any MED9? MED9.5.10? Non turbo?

I think pretty much anything will work, if you have some random ECU left over.

I am not sure if I want to make the detector for all the addresses (ME7Info style) though.
So it would not be noob friendly.

Or I can buy the ECU, if it's not stupid money. I am not looking to spend 200+ EUR on an ECU which will only ever live on my bench and never be used in a car.
You can also lend it to me and ask for it back if you need it, etc. I am not custom tuning any TFSi cars right now, so I don't have any ECU's either...

awesome offer prj wish I had a spare ecu to send you. re the vcds advanced measuring blocks its still a mission me7logger was perfect create your config with what you want and just start it not like vcds where I have to set it up everytime and me7looger works withe ecuxplot perfectly.

I understand and I'm thinking the same. A MED9.5.10 ECU can be bought for as little as 100 Euro, but you'll probably never use it again in a real car. (unless you deal with spare parts).
A type used in more often tuned models (2L TFSI etc.) would be more like 300 Euro.

I think I'll try to get one and lend it to you. No problem about the non-noob part, we can work on that later.

I don't know how quick MED9 is with sending blocks.
There is a limit of 20 RAM values logged at the same time...
Or well, you can specify the length for every value, so you can read bigger blocks of memory, but 20 unique locations.

With a single definition it looks like this, at start you do:
Send: DynamicallyDefineLocalIdentifier, DefineByMemoryAddress.
Receive: OK

Now loop:
Send: readDataByLocalIdentifier
Receive: RAM values

If this can be done at 50hz, like in ME7, then it's possible to do this:

Loop:
Send: DynamicallyDefineLocalIdentifier, DefineByMemoryAddress. #1
Receive: OK
Send: readDataByLocalIdentifier
Receive: RAM values
Send: DynamicallyDefineLocalIdentifier, DefineByMemoryAddress. #2
Receive: OK
Send: readDataByLocalIdentifier
Receive: RAM values

This would mean 40 unique values, but 4 times more commands, so maximum sample rate would be 12.5 hz.
I think actually 40 values and 12.5hz is pretty good. Especially if you can read out bigger chunks of memory.

I don't know how close the variables are aligned in MED9 ram. If there are a lot of values aligned close, then it could be done with a single command, and just read 20 chunks of memory.

Isn't it better ( = faster ) to log over CAN ?

ME(D)9 logger would be cool, tons of car there with ME/MED9 ecu !  ;D

I don't know if CAN is faster or not for this application...
The limitation is not the throughput of the connection, but speed of the ECU.

A programmable CAN interface is at least 100 EUR, and every one of them has a custom framework.
A K-Line cable is 5$.

So if it can be done over K-Line, I'm going to do it over K-Line.

If MED9 ECUs support KWP2000 over Kline, fine.

A CAN to USB cable is 99 euro. For example: www.canusb.com
That cable is used a lot on Saab Trionic systems and works good there.

I'll try to get an ECU to get this started next week. Will let you guys know.

Don't get an ECU, I had a kind offer from someone in PM to send me a TFSi ECU.
So if this does not fall through, I will have an ECU to play with.

If it has to be CAN, I will buy that 99 EUR cable. It will be useful in the future anyway.
But I hope it is possible with K-Line :)

Good news.
Let me know how it works out. In case you don't get an ECU, my offer still stands.

One tfsi ecu was send to you, prj. Success!  ;)

Thank you very much. I will make a few experiments once I receive it :)

Just a thought but instead of reinventing the wheel here, wouldnt it be possible to modify the source for me7logger to accommodate med9? I did try and create an ecu file from my med9 bin and it seems to locate the maps fine but errors out because of the file size difference?

No.

bump

anyone have any other alternatives to vcds................ i miss being able to use me7logger  :'(

ping  ;D

I have a MED9 here, kindly donated by a forum member, but zero progress.
Have not even taken it out of the box.

The spring hit and everyone wants their cars to be quicker, so I am swamped with work.

What ever happened here?

I'm interested in logging ME7.1.1 CANbus, I'm guessing MED9 and CANbus ME7 are going to be close and the same tools may work.

ME7 should always be possible via ME7Logger. Run a K-line if it's not there.

I took this file : http://nefariousmotorsports.com/forum/index.php?topic=6049.0title= and ran it threw me7info and it couldn't find the ram addresses. 

Junk yard ecu's are pretty cheap so might buy one and play with it over k-line (I don't have a car to test it with yet)

I'll look into adding it to my uds logger if there's interest etc.

I figured out the med9 diag stuff a while back I ida  but getting it to an ecu level file to log is a lot of work lol props to setzi.