NefMoto

Technical => Data Logging => Topic started by: setzi62 on July 29, 2011, 03:58:15 AM



Title: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on July 29, 2011, 03:58:15 AM
Pushing a little bit forward on the logging front ...
Here is my ME7Logger package now available for everybody,
has been tested successfully on different cars.

It consists of two tools: one to generate ecu characteristics files
(similar to properties) out of ecu images, second to log data.
No GUI for klicky guys, no graphics, just console programs.

/sales_mode=on  ;)
Will outperform commercially available tools on speed & flexibility:
 - Up to 50 samples per second possible.
 - Up to 127 independent variables can be logged at same time.
 - Open for expansions: whatever you want to log, you can define it.
 - No fiddling with licenses/hacked programs needed.
/sales_mode=off

- It's free for hobby use,
- It's NOT for noobs. Not a connect-and-log tool,
  before logging you should have your ecu image available.

Last but not least: buy a commercial program if you want
to make someone liable for damages/not working logging tools  :)

Update 12.08.2011, some fixes/changes done:
- Experimental FTDI native driver support added, option -f
- Logger start time synchronization added, option -t
- Logger absolute timestamp added, option -a
- Allow TAB's also in trace config files
- Variables zwbasar_<xx> for all available cylinders
- Variables wkraa_<xx> limited to available cylinders
- Minor changes, some variables added

Update 09.09.2011, some of the requested changes/fixes done:
- Single sample option added (result is output just to the window)
- More variables determined for images with code variant (missing tans(IAT) for one image)
- zwbasar_<xx> now really available for all available cylinders
- Some more variables added
- Some alias names added, some changed


Update 02.04.2012 to version 1.17:
(Updated 04.04.2012 the ME7Info in the .zip, fixed path error)
Changes in ME7Logger:
- Reworked general timing calculations, timestamps, sync to full second
- Fixed local time in absolute timestamps (option -a)
- Supress logfile writing when output goes to stdout (option -R)
  useful if output is piped to external evaluation tool/filter
- Added option -m: Timestamp format milliseconds
- Added option -h: supress printing header information in logfiles
- Added option -b: set logging baudrate for communication,
                   override baudrate from ecu file
- connection method "double slowinit" added (helps with "instrument cluster" problem)
  To use double slowinit set in the [Communication] section of the .ecu file:
    Connect      = SLOW-0x00
    DoubleDelay  = 12           ; Possible values 1 .. 100 (delay in 100ms)
  This only allows to connect while engine not yet started.

Changes in ME7Info:
- Reverted back to zwbasar_0 .. zwbasar_3
  (Array size NOT dependent on number of cylinders)
- Some variables added:
 + zwoutar_0 .. zwoutar_3
 + zwsol
 + redist / evz_austot
 + lamfaws_w / lamfawkr_w / lamfaw_w / lamfwl_w / lamrlmn_w
 + perffilt_w / perfmax_w   => This is CPU-Load
    It helps in finding out the max. logging capabilities of your ECU.
    Around 90% CPU-Load might be a limit for the ECU.


Update 10.07.2013 to version 1.20:
Changes in ME7Logger v1.20:
- Read additional ecu characteristics file "my_<ecufile>" if it exists in same directory as <ecufile>.
  -> my_<ecufile> should be used to keep manually added definitions.
- Read additional log config file my_<ecu>_template.cfg from same directory as log config file.
  - my_<ecu>_template.cfg can be used to keep log entries for manually added definitions
- Optimization of logged data, e.g.:
    - logging multiple bitvariables which use the same byte will read only one byte from ecu.
    - logging two byte variables from neighbouring memory addresses will read only one merged
      word location from ecu.
    The limits are now:
      - up to 254 bytes,
      - up to 127 different memory locations (1 or 2 bytes),
      - up to 254 variables.

- Linux port added
   -> see "ME7Logger_Linux_DIST_10072013.tgz"
   Serial interfaces work using device /dev/ttyS*, as well as FTDI cables in serial mode
   using the kernel module ftdi_sio and device /dev/ttyUSB0.
   FTDI native mode is supported using libftdi1 and libusb1, both are already included
   in many Linux distributions.
   libftdi1: http://www.intra2net.com/en/developer/libftdi
   libusb1:  http://www.libusb.org/wiki/libusb-1.0

- Shared library (DLL) added (.so/.dll) for those who want to implement own logging solutions
   -> see directory "lib" in the ME7L .zip/.tgz files for description and example program.
   An example driver for WinLog (http://www.devtechnics.com/winlog.htm) using the ME7L shared library
   is available as well in ME7L_Winlog_driver.zip. Just copy ME7L_winlog.dll and libME7Logger.dll into
   the Winlog directory to make use of it.

Changes in ME7Info v1.20:
- Linux port added
- Internal cleanup work

https://s4wiki.com/wiki/Tuning#Logging_utilities
See http://nefariousmotorsports.com/forum/index.php?topic=4830.0title= for a GUI front end


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: carlossus on July 29, 2011, 05:32:34 AM
You are a legend for sharing this. Thank you!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: lulu2003 on July 29, 2011, 05:59:49 AM
thanks a lot.
will try soon and looking forward to the the first GUI ;)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: NOTORIOUS VR on July 29, 2011, 06:24:56 AM
This is pretty epic!  Thanks for sharing!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on July 29, 2011, 07:24:52 AM
Awesome tool setzi, thank you.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Matt Danger on July 29, 2011, 07:30:58 AM
Thanks for this, can't wait to try it out.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nehalem on July 29, 2011, 10:48:47 AM
dude.  this is epic.  100% complete and utterly epic.  now all we have to do is get a common list of what should be logged under most conditions!

just a quick suggestion / thought.

is there anyway you can add an option to do "synched timing".

this means if i enable / config the logger to use "synched timing", it will start the log exactly on the computer's clock second:  aka  11:05:10.0000 AM    like that?

this would greatly assist users to fuse multiple logging sources...  just a thought!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 29, 2011, 10:51:55 AM
Hell ya. screw GUIs.

Thank you so much setzi!



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 29, 2011, 10:52:43 AM
BTW i will be updating ECUxPlot to be able to read log files from this tool.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: vwaudiguy on July 29, 2011, 11:07:00 AM
Thank you!!!!!!!!!!!!!!!!!!!  ;D


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Matt Danger on July 29, 2011, 09:42:29 PM
BTW i will be updating ECUxPlot to be able to read log files from this tool.

Excellent


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: s4rmm on July 30, 2011, 10:46:45 AM
Anybody got it working with Ross-Tech USB cable?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on July 30, 2011, 11:05:19 AM
Anybody got it working with Ross-Tech USB cable?

If your cable works with NefMoto or ECUx, it should work no problem. You may have to set it to dumb mode. My blue KKL cable works perfectly.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Complacentsee on July 31, 2011, 01:23:44 PM
I know many people are used to seeing the logs displayed in Mark P format.
Here is my Mark P style logger configuration and excel sheet.

You will have to edit the config to reference your ecu config file "mybin.ecu". You may want to adjust the sample rate as I have selected 25.

Once you have logged you can simply copy the data you want, with the headers and it should auto populate the graphs. I made Mark P's template look for ME7Logger headers. Then I added in the unit conversions to make the graphs work correctly. If I recall these were the only data changes:

Convert time from seconds to milliseconds.
Convert Speed from kilometers per hour to miles per hour.
Convert Temperature from Celsius to F.
Convert Timing retard from negative to positive.

If someone is familiar with the how this worked with ecux you may want to verify the data I pulled matches the variable that ecux is logging. I think I matched them correctly, but I have never tuned, and never used ecux so I'm not sure.

If you find any errors, let me know and I'll update this post.
(I'm having trouble getting the files to upload at the moment)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 31, 2011, 02:15:06 PM
BTW i will be updating ECUxPlot to be able to read log files from this tool.

http://nyet.org/cars/ECUxPlot/

Please test it out, and send bug reports ;)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Jason on July 31, 2011, 03:19:31 PM
Complacentsee, line 40 needs a ; instead of a ,  (fr_w)

edit:  Also line 53


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Complacentsee on July 31, 2011, 03:27:49 PM
Thanks. I added those last minute and forgot to change it. The corrected file should be up now.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Jason on July 31, 2011, 04:02:32 PM
Is there any interest in an app that reads the stdout and combines it with values sampled from an innnovate LC-1?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 31, 2011, 04:15:19 PM
btw ECUxPlot will overlay zeitronix data on top of an existing log...

I could add innovate support, but I dont have log data to test with.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Jason on July 31, 2011, 04:18:37 PM
Are you just aligning the logs by looking at the narrowband values or does Zeitronix log RPM?  My issue is that I don't want to buy more innovate stuff just to log the wideband against RPM.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on July 31, 2011, 04:31:24 PM
Zeitronix ZT-2 logs wideband and RPM.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Jason on July 31, 2011, 05:01:27 PM
That is the problem with the innovate stuff... no RPM unless you add another box.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nehalem on July 31, 2011, 09:28:52 PM
I'd definitely want to see LC-1 support!  Thats a really good package...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 31, 2011, 09:39:00 PM
Ugh. not if there is no RPM support. forget it. Too hard to sync with other logs.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: s4rmm on August 01, 2011, 02:35:44 AM
Anybody got it working with Ross-Tech USB cable?

If your cable works with NefMoto or ECUx, it should work no problem. You may have to set it to dumb mode. My blue KKL cable works perfectly.
It works with NefMoto and with VCDS, it is in dumb mode. I created virtual comport (usb to serial), configured as COM2 or COM7, but did not manage to connect.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ElementalVoid on August 01, 2011, 07:23:21 AM
Ugh. not if there is no RPM support. forget it. Too hard to sync with other logs.

I went with the Innovate stuff but I did get the extra box required to do RPM, I didn't see a huge gain to getting wideband AFR without being able to correlate it to other log measurements.

When I get a log with both (missing a cable that didn't get shipped) I'll post it.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on August 01, 2011, 08:24:40 AM
just a quick suggestion / thought.

is there anyway you can add an option to do "synched timing".

this means if i enable / config the logger to use "synched timing", it will start the log exactly on the computer's clock second:  aka  11:05:10.0000 AM    like that?

this would greatly assist users to fuse multiple logging sources...  just a thought!
Is the timestamp really used to sync logs from different sources? From what I read here,
a synchronization would be made by comparing rpm data.
But yes, I could implement something like this. Also an option to get absolute timestamps
instead of relative time since start would be possible. Have to make some tests ....


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on August 01, 2011, 08:30:36 AM
It works with NefMoto and with VCDS, it is in dumb mode. I created virtual comport (usb to serial), configured as COM2 or COM7, but did not manage to connect.

What is the output? Just telling it can't connect or something more?
Are you referencing the right ecu characteristics file in your trace config?
If a wrong characteristics file is used, the logger could try to connect to a
wrong address.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on August 01, 2011, 08:34:29 AM
Anybody got it working with Ross-Tech USB cable?

If your cable works with NefMoto or ECUx, it should work no problem. You may have to set it to dumb mode. My blue KKL cable works perfectly.
It works with NefMoto and with VCDS, it is in dumb mode. I created virtual comport (usb to serial), configured as COM2 or COM7, but did not manage to connect.

The default is COM2 for the logger.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: infinkc on August 01, 2011, 08:57:08 AM
That is the problem with the innovate stuff... no RPM unless you add another box.

yea i landed up getting the ot2 to log the rpm with the innovate wideband, i figured that was easier than getting their other input box where you have to configure the rpm signal.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nehalem on August 01, 2011, 10:22:17 AM
just a quick suggestion / thought.

is there anyway you can add an option to do "synched timing".

this means if i enable / config the logger to use "synched timing", it will start the log exactly on the computer's clock second:  aka  11:05:10.0000 AM    like that?

this would greatly assist users to fuse multiple logging sources...  just a thought!
Is the timestamp really used to sync logs from different sources? From what I read here,
a synchronization would be made by comparing rpm data.
But yes, I could implement something like this. Also an option to get absolute timestamps
instead of relative time since start would be possible. Have to make some tests ....



Ha - I have to totally honest.  I don't know...  but it seemed like a decent-enough idea.  I suppose RPM would be better, but it might all be relative depending on the frequency of data-update.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nehalem on August 01, 2011, 10:23:29 AM
That is the problem with the innovate stuff... no RPM unless you add another box.

yea i landed up getting the ot2 to log the rpm with the innovate wideband, i figured that was easier than getting their other input box where you have to configure the rpm signal.

What do you think about it?  Have you had the chance to use the Wideband AFR matrix that does averaging?  I thought that looked really powerful.  Also, how are you going to log using this tool while using the OT-2?  Just wondering...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Jason on August 01, 2011, 10:55:35 AM
For me, I just thought about reading the data as it's being dumped out of the ME7Logger, and appending the wideband data from the Innovate SDK.  The max sample rate I could achieve with the MarkP layout was 33hz, so I think the results would be better than the current "educated guess" method of aligning the log based on throttle lift.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 01, 2011, 12:34:57 PM
fixed a few bugs in the last ecuxplot for setzi's ME7 logger.

please try this one instead :)

http://nyet.org/cars/files/ECUxPlot-0.9r3.0-setup.exe

other versions are always available here

http://nyet.org/cars/files/


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: RaraK on August 02, 2011, 07:50:46 AM
good stuff nyet, going to test it out tonight :)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: s4rmm on August 02, 2011, 08:51:09 AM
It works with NefMoto and with VCDS, it is in dumb mode. I created virtual comport (usb to serial), configured as COM2 or COM7, but did not manage to connect.

What is the output? Just telling it can't connect or something more?
Are you referencing the right ecu characteristics file in your trace config?
If a wrong characteristics file is used, the logger could try to connect to a
wrong address.

I'm referencing the characteristics file I created from my ECUs binary.
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x11
Communicate  = HM0
LogSpeed     = 57600
[Identification]
HWNumber           = "0261206776"
SWNumber           = "1037354123"
PartNumber         = "8D0907551G"
SWVersion          = "0001"
EngineId           = "2.7l V6/5VT"

Here's the output:
Logged data size is 101 bytes.
Start connecting to ECU at 02.08.2011 17:17:17.515
try connect slow(11)
try connect slow(11)
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: jibberjive on August 05, 2011, 11:55:07 PM
I just found this. Awesome work Setzi!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ThomasRS4 on August 06, 2011, 03:14:54 PM
Great work, thanks to share this awesome tool...

But I have a connecting problem with my RS4 8D0907551K.
My USB-Adapter works with Nefmoto, VAGCom and other diagnostic tools without problems.
The original 551K image is stored and the .ecu file is successfull generatet by ME7Info.exe.
A config file is also written.

Logged data size is 101 bytes.
Start connecting to ECU at 05.08.2011 20:01.22.111
try connect slow(11)
try connect slow(11)
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)...

At the beginning of a connection with VAGCom, you can here a short clicking in the instrumentcluster.
When I try to connect with ME7Logger there is no clicking.

Can anybody help?

Thanks

Tom


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 09, 2011, 05:51:10 PM
I love this tool. Simply amazing. thanks setzi!

one small bug complaint: you MUST use spaces to separate fields, you can't use tabs.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: dirtyr32 on August 09, 2011, 07:46:22 PM
First off, thank you for getting this tool out there, it's going to help a lot of people see whats going on under the hood.  :)

I have an '08 R32, and while I can log fairly quickly in vcds (getting ~10-12 samples/sec) I'd really like to open up my logging options with this tool. Not that I need to change much right now, but I love the data, and really want to verify some upcoming mods I'd like to do with some good information. Nothing else I've found supports these later ME7.1.1 ECU's, so I was hoping some small tweaks to yours would be all that is needed to work with these later ME7 ecu images properly. Right now it's not detecting any ram locations/variables at all:
Code:
C:\ME7Logger\bin>ME7Info.exe "..\images\VW Golf MK5 R32 0261201807 022906032KR 1037387913.bin"
read 1300 map entries
mapped 186 aliases
written 0 definitions
written output to file C:\ME7Logger\ecus\VW Golf MK5 R32 0261201807 022906032KR 1037387913.ecu

C:\ME7Logger\bin>

I've attached a bin from the same ECU.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: matchew on August 10, 2011, 02:54:19 AM
MK5 R32 is a completely different structure of code...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on August 10, 2011, 04:03:37 AM
Yes, this MK5 R32 image looks completely different to older R32 images
(which can be processed by ME7Info). I think this ECU is based on ST10 which is
C167 compatible, but the bootrom must be completely different.
So, no chance to get the info tool working for this MK5 R32 image  :'( and also
the logger will not run (hopefully it will detect this is a non-supported ecu).

Next update will allow TABs in config files, support sync to full second at logging
start, and optional absolute timestamps (for easier synchronization with other logs).
I will prepare this within the next days.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on August 10, 2011, 04:09:39 AM
And, I am looking into the connection problems reported by
s4rmm and ThomasRS4. Would be good to find out what is blocking there,
but currently I don't have a concrete hint what to change to get it connecting.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tobz on August 11, 2011, 06:16:42 PM
First off, I want to say: thank the fucking lord.  VCDS logging is god awful slow and I'm glad someone finally created a program so we don't have to pay for / deal with the bugginess of ECU Explorer.  I plan on creating a small .NET app that wraps ME7Info/ME7Logger to make it dead simple to generate your ECU definitions and then run the logger.

Anyways, having some issues...  I'm getting "Got error -8" while logging.  Lowering the baud rate/sample rate helped a little bit, but it always happens.  It'll say it about 8 - 10 times then the logger will exit with code 0x4.  Not sure what's going on, but VCDS works no problem and I'm using a blue KKL cable.

Any thoughts?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 11, 2011, 11:36:12 PM
One more minor thing: 2.7t mbox was missing zwbasar_4 and zwbasar_5


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on August 12, 2011, 07:50:39 AM
Anyways, having some issues...  I'm getting "Got error -8" while logging.  Lowering the baud rate/sample rate helped a little bit, but it always happens.  It'll say it about 8 - 10 times then the logger will exit with code 0x4.  Not sure what's going on, but VCDS works no problem and I'm using a blue KKL cable.

Any thoughts?

This error -8 means that there are no more data coming from the ecu, so the logger gets
a timeout. The logger tries 10 times to re-send the current request, but no further
response is seen, then it stops.
Similar communication problem exists in some cars, could be solved by adding a
separate wire from ECU to tester/logger without any other units on the K-line.
See this thread: http://nefariousmotorsports.com/forum/index.php/topic,366.0.html


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tobz on August 12, 2011, 07:55:37 AM
Anyways, having some issues...  I'm getting "Got error -8" while logging.  Lowering the baud rate/sample rate helped a little bit, but it always happens.  It'll say it about 8 - 10 times then the logger will exit with code 0x4.  Not sure what's going on, but VCDS works no problem and I'm using a blue KKL cable.

Any thoughts?

This error -8 means that there are no more data coming from the ecu, so the logger gets
a timeout. The logger tries 10 times to re-send the current request, but no further
response is seen, then it stops.
Similar communication problem exists in some cars, could be solved by adding a
separate wire from ECU to tester/logger without any other units on the K-line.
See this thread: http://nefariousmotorsports.com/forum/index.php/topic,366.0.html


Seems like that would not be such a good idea without knowing precisely what would not be talking on the K-line anymore and especially since I want to be able to drive my car to log stuff. :/

EDIT:  I'm gonna try and do the resistor mod to my KKL cable just to make sure it is working 100% and to hopefully reduce any noise / issues while logging.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on August 12, 2011, 07:57:41 AM
I have added an update to the initial post wich fixes some of the smaller problems/requests.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tobz on August 12, 2011, 08:08:54 AM
Also, just a thought... what's the minimum baud rate to use if I wanted to log around 5 samples/sec for 15 - 25 values?  Bumping the rates down seemed to have a positive effect, but  I'm just not sure how low I can put them.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on August 12, 2011, 08:09:33 AM
Seems like that would not be such a good idea without knowing precisely what would not be talking on the K-line anymore and especially since I want to be able to drive my car to log stuff. :/

The K-line is designed only for diagnosis. Car must be able to run without problems,
even if someone pulls the line down to ground or fixes it to +12V permanently
(I think this was the case with so called aftermarket radio problem).
Anyways, if you connect a tester to the ecu, the protocol allows to starve out any
other communication, making it impossible for other units to send anything.
If you log 25 samples/second, no one else besides the ECU and the logger can send
anything on the K-line  ;).
Therefore any sensitive communication takes place over CAN.

If it is possible for you, you could connect an logic analyzer to the K-line and watch
what is happening when the communication failures appear. I would be glad to hear
which unit is causing these problems, so we probably can finally find a way to stop this.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on August 12, 2011, 08:12:41 AM
Also, just a thought... what's the minimum baud rate to use if I wanted to log around 5 samples/sec for 15 - 25 values?  Bumping the rates down seemed to have a positive effect, but  I'm just not sure how low I can put them.

Just try with 10400baud, the logger will reduce the samplerate accordingly if it can't
keep up with the requested rate.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tobz on August 12, 2011, 09:10:40 AM
Seems like that would not be such a good idea without knowing precisely what would not be talking on the K-line anymore and especially since I want to be able to drive my car to log stuff. :/

The K-line is designed only for diagnosis. Car must be able to run without problems,
even if someone pulls the line down to ground or fixes it to +12V permanently
(I think this was the case with so called aftermarket radio problem).
Anyways, if you connect a tester to the ecu, the protocol allows to starve out any
other communication, making it impossible for other units to send anything.
If you log 25 samples/second, no one else besides the ECU and the logger can send
anything on the K-line  ;).
Therefore any sensitive communication takes place over CAN.

If it is possible for you, you could connect an logic analyzer to the K-line and watch
what is happening when the communication failures appear. I would be glad to hear
which unit is causing these problems, so we probably can finally find a way to stop this.


I'll have to do some digging first to see what devices hang off of the K-line before I go and start splicing anything, but you do make a convincing argument.  I have a 2004MY Jetta so I don't think I even have CAN-BUS, though.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Ur-S-Sex on August 15, 2011, 11:36:58 AM
Any chance this program will log the AEB 1.8t P box ECUs?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nehalem on August 16, 2011, 05:24:08 PM
Hi Setzi - I was wondering about some of the variables.

Block 032 is LTFT's in VCDS.  Do you happen to know what the four variables are in your nomenclature?  I believe the partial's might be FRA_W and FRA2_W.  Any idea?

Also, do you happen to know where STFT's are shown?  I think its block 033 / 034?


Cheers,
DB


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on August 16, 2011, 05:28:45 PM
Hi Setzi - I was wondering about some of the variables.

Block 032 is LTFT's in VCDS.  Do you happen to know what the four variables are in your nomenclature?  I believe the partial's might be FRA_W and FRA2_W.  Any idea?

Also, do you happen to know where STFT's are shown?  I think its block 033 / 034?


Cheers,
DB


Setzi posted a text file of the RAM variable associated to the different measuring blocks in VCDS. I am on my phone, otherwise I would help more.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TWiST on August 17, 2011, 10:26:33 PM
I have been gone for a while, looking forward to giving this a run soon.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ThomasRS4 on August 18, 2011, 08:45:09 AM
And, I am looking into the connection problems reported by
s4rmm and ThomasRS4. Would be good to find out what is blocking there,
but currently I don't have a concrete hint what to change to get it connecting.

Hi Setzi,

I am still searching for my connection problems with my RS4 8D0907551K ECU.
In my generatet ECU file, the connect parameter is set to "SLOW-0x11"

[Communication]
Connect      = SLOW-0x11    ; Possible values: SLOW-0x11, FAST-0x01
Communicate  = HM0          ; Possible values: HM0, HM2-0x01
LogSpeed     = 57600        ; Possible values: 10400, 14400, 19200, 38400, 56000, 57600, 125000

[Identification]
HWNumber          = {0261207001}
SWNumber          = {1037360387}
PartNumber        = {8D0907551K}
SWVersion         = {0001}
EngineId          = {2.7l V6/5VT}

But in the Connect overview of file "example.commdate" in the logs folder,
I cant find anything about the value "SLOW-0x11".
The optional possible value "FAST-0x01" is missing too.

slow (0x01)           -> KWP2000
slow (0x31)           -> KWP2000
slow (0x33)           -> SAE-J1979(KWP2000)
fast (HM2-phys(0x10)) -> KWP2000
fast (HM3-func(0x31)) -> KWP2000

KWP2000 communication:
HM0/none(----)
HM2/phys(0x10)
HM3/func(0x31)

Is this the problem?
Can you bring light into dark?

Thanks a lot...

Tom



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 18, 2011, 12:12:57 PM
Hi Setzi - I was wondering about some of the variables.

Block 032 is LTFT's in VCDS.  Do you happen to know what the four variables are in your nomenclature?  I believe the partial's might be FRA_W and FRA2_W.  Any idea?

Also, do you happen to know where STFT's are shown?  I think its block 033 / 034?


I would like to know this too :) I would guess STFTs are fr_w/fr2_w and/or frm_w/frm2_w

Additive LTFT (idle) is probably rkat or rkaz?

Also, setzi: zwbasar_4 and _5 still dont show up for Mbox in 1.07



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on August 18, 2011, 12:45:43 PM
Hi Setzi - I was wondering about some of the variables.

Block 032 is LTFT's in VCDS.  Do you happen to know what the four variables are in your nomenclature?  I believe the partial's might be FRA_W and FRA2_W.  Any idea?

Also, do you happen to know where STFT's are shown?  I think its block 033 / 034?


I would like to know this too :) I would guess STFTs are fr_w/fr2_w and/or frm_w/frm2_w

Additive LTFT (idle) is probably rkat or rkaz?

Also, setzi: zwbasar_4 and _5 still dont show up for Mbox in 1.07



Per the file posted by Setzi here:
http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=472.0;attach=583

LTFT
Group 032: 001F (      ), 0021 (fra_w), 0020 (        ), 0022 (fra2_w)

STFT
Group 033: 001C (fr_2), 0025 (usvk ), 001D (fr2_w), 0026 (usvk2 )


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 18, 2011, 06:25:23 PM
Also: a request

ldrkp
ldrki
ldrkd

:)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 18, 2011, 11:15:19 PM
New version of ECUxPlot. Lots of new ME7Logger compatibility fixes.

http://nyet.org/cars/files/ECUxPlot-0.9r3.0-setup.exe

note for setzi:

A few more translations required for ECUx compatibility:

BoostPressureSpecified -> BoostPressureDesired
AtmosphericPressure -> BaroPressure
AirFuelRatioRequired -> AirFuelRatioDesired
InjectionTime -> FuelInjectorOnTime
InjectionTimeBank2 -> FuelInjectorOnTimeBank2          


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nehalem on August 19, 2011, 11:25:07 AM
Hi Setzi - I was wondering about some of the variables.

Block 032 is LTFT's in VCDS.  Do you happen to know what the four variables are in your nomenclature?  I believe the partial's might be FRA_W and FRA2_W.  Any idea?

Also, do you happen to know where STFT's are shown?  I think its block 033 / 034?


I would like to know this too :) I would guess STFTs are fr_w/fr2_w and/or frm_w/frm2_w

Additive LTFT (idle) is probably rkat or rkaz?

Also, setzi: zwbasar_4 and _5 still dont show up for Mbox in 1.07



Per the file posted by Setzi here:
http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=472.0;attach=583

LTFT
Group 032: 001F (      ), 0021 (fra_w), 0020 (        ), 0022 (fra2_w)

STFT
Group 033: 001C (fr_2), 0025 (usvk ), 001D (fr2_w), 0026 (usvk2 )


How can we get 001F and 0020?  Does Setzi need to modify his code or is there something we can do to log these idle LTFTs?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 20, 2011, 09:28:19 PM
Hey. I forgot tony posted this

http://nyet.org/cars/files/8D0907551M_0002%20RAM%20Variables.txt

Code:
(Address=0x383D1A, DataType=INT16, Scale=(1.0 / 21.33), Offset=(0.0), Name="Bank 1 Long Term Idle Additive Fuel Trim", Units="%")
(Address=0x383D18, DataType=INT16, Scale=(1.0 / 21.33), Offset=(0.0), Name="Bank 2 Long Term Idle Additive Fuel Trim", Units="%")
(Address=0x3823E2, DataType=UINT16, Scale=(1.0 / 327.68), Offset=(-100), Name="Bank 1 Long Term Partial Load Multiplicative Fuel Trim", Units="%")
(Address=0x3823E0, DataType=UINT16, Scale=(1.0 / 327.68), Offset=(-100), Name="Bank 2 Long Term Partial Load Multiplicative Fuel Trim", Units="%")
(Address=0x3823E6, DataType=INT16, Scale=(1.0 / 21.33), Offset=(0.0), Name="Bank 1 Combined and Weighted Long Term Idle Additive Fuel Trim", Units="%")
(Address=0x3823E4, DataType=INT16, Scale=(1.0 / 21.33), Offset=(0.0), Name="Bank 2 Combined and Weighted Long Term Idle Additive Fuel Trim", Units="%")

and, even better

Code:
(Address=0x382754, DataType=INT16, Scale=(1.0 / 200.0), Offset=(0.0), Name="Wastegate PID Controller Duty Cycle Before Linearization", Units="%")
(Address=0x382752, DataType=INT16, Scale=(1.0 / 200.0), Offset=(0.0), Name="Wastegate PID Controller Duty Cycle After Linearization", Units="%")
(Address=0x382750, DataType=UINT16, Scale=(1.0 / 2000.0), Offset=(0.0), Name="Wastegate PID Controller P Minus D Scalar", Units="%/mbar")
(Address=0x382748, DataType=INT16, Scale=(1.0 / 200.0), Offset=(0.0), Name="Wastegate PID Controller P Minus D Result", Units="%")
(Address=0x38274E, DataType=UINT16, Scale=(1.0 / 2000.0), Offset=(0.0), Name="Wastegate PID Controller I Scalar", Units="%/mbar")
(Address=0x382756, DataType=UINT16, Scale=(1.0 / 25.6), Offset=(0.0), Name="Boost Pressure Reference Negative Offset From Specified Load For Load Pressure Control I Limit", Units="mbar")
(Address=0x382758, DataType=UINT16, Scale=(1.0 / 25.6), Offset=(0.0), Name="Boost Pressure Reference For Load Pressure Control I Limit", Units="mbar")
(Address=0x382742, DataType=INT16, Scale=(1.0 / 200.0), Offset=(0.0), Name="Wastegate PID Controller I Result Limit Base Adaptation Offset", Units="%")
(Address=0x382744, DataType=INT16, Scale=(1.0 / 200.0), Offset=(0.0), Name="Wastegate PID Controller I Result Limit Base", Units="%")
(Address=0x382740, DataType=INT16, Scale=(1.0 / 200.0), Offset=(0.0), Name="Wastegate PID Controller I Result Upper Limit", Units="%")
(Address=0x38273E, DataType=INT16, Scale=(1.0 / 200.0), Offset=(0.0), Name="Wastegate PID Controller I Result Lower Limit", Units="%")
(Address=0x382746, DataType=INT16, Scale=(1.0 / 200.0), Offset=(0.0), Name="Wastegate PID Controller I Result", Units="%")
(Address=0x38274C, DataType=UINT16, Scale=(1.0 / 2000.0), Offset=(0.0), Name="Wastegate PID Controller D Scalar", Units="%/mbar")
(Address=0x38274A, DataType=INT16, Scale=(1.0 / 200.0), Offset=(0.0), Name="Wastegate PID Controller D Result", Units="%")


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 20, 2011, 09:30:28 PM
And one more request for setzi :)

A command line argument that tells ME7L to take ONE sample, and quit.

For example, to read long term adaptation values :)

Thanks, setzi, your stuff rocks. I'm using it constantly now and I love it.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tobz on August 21, 2011, 09:55:06 AM
Indeed!  My issues with ECU not feeding data aside... this logger is friggin' awesome.  ;D

One issue, though: the definition file for my ECU doesn't have a field for intake air temperature.   I have my original BIN attached and hopefully setzi can figure out the issue. :D


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tkla on August 21, 2011, 09:24:03 PM
Thanks for this, can't wait to try it out.

+1 I will test it and compare the results vs Ecux, thanks for sharing!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: New2Tune on August 22, 2011, 12:01:32 PM
Having a connect issue, doesn't seem to be able to initialize.

=> Could not connect to ECU, exiting...
=> Logging Failed

exiting (cause 0x4)...

Any ideas?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 23, 2011, 06:07:58 PM
Also: a request

ldrkp
ldrki
ldrkd

:)

Err that should be

ldptv (0x382748?)
lditv_w (0x382746?)
ldrdtv (0x38274A?)




Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 23, 2011, 06:25:10 PM
Per the file posted by Setzi here:
http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=472.0;attach=583

LTFT
Group 032: 001F (      ), 0021 (fra_w), 0020 (        ), 0022 (fra2_w)

STFT
Group 033: 001C (fr_2), 0025 (usvk ), 001D (fr2_w), 0026 (usvk2 )

I'm going to guess that it is
Group 032: 001F (rkat_w), 0021 (fra_w), 0020 (rkat2_w), 0022 (fra2_w)

based on Tony's RAM locations.




Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on September 07, 2011, 02:10:34 AM
Any chance this program will log the AEB 1.8t P box ECUs?
If it has bootrom version 05.XX or 06.XX (can be seen with ME7Check),
it should be possible. If another bootrom version get's reported, then no chance.
Some people reported communication problems with compatible ECUs, so there
might be an additional blocking point for certain configurations.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on September 07, 2011, 02:31:31 AM
I am still searching for my connection problems with my RS4 8D0907551K ECU.
In my generatet ECU file, the connect parameter is set to "SLOW-0x11"

But in the Connect overview of file "example.commdate" in the logs folder,
I cant find anything about the value "SLOW-0x11".

Is this the problem?
Can you bring light into dark?
Unfortunately this is not the problem. The example.commdate is just for the binary
example.bin. If you run ME7Info -c <yourbinary> you will see the communication
data of your binary.
For the K-Box, the used address is the correct one. The connect problem must be
something else. Did you try with the experimental FTDI support? This might help
if it is a timing issue (if the FTDI support works at all).


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on September 09, 2011, 02:39:43 AM
An update was added to the first post, just minor requests + fixes were done.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tobz on September 09, 2011, 05:15:00 AM
An update was added to the first post, just minor requests + fixes were done.


Thank you thank you thank you for the update that gets me IAT!  Where do I send the beer?!  ;D

Also, if I sent you an FTDI cable to test with, do you think we'd be able to get some "better" FTDI support?  I've tried using the FTDI mode but it randomly craps out here and there and I know you mentioned not having a cable... so I figured I could donate to the cause and help you get one. :D


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on September 09, 2011, 08:57:36 AM
THANK YOU!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: cactuss4 on September 11, 2011, 05:56:09 PM
Nyet stated there were linux binaries available for Me7logger. Can I get the located for them? Trying to reduce the number of systems I have spread all over and if i could do this all under linux vs wind0ze, that would be fantastic

thanks
Tory


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on September 13, 2011, 09:35:02 AM
Also, if I sent you an FTDI cable to test with, do you think we'd be able to get some "better" FTDI support?  I've tried using the FTDI mode but it randomly craps out here and there and I know you mentioned not having a cable... so I figured I could donate to the cause and help you get one. :D
Thanks for the offer, but I just ordered one. Unfortunately it will take till october until it arives
(the shop maintainer is on vacation, this info appeared after buying the thing ...).

So you are saying with ftdi mode you could open your interface and connect to the ecu,
then connection breaks down during logging? That would be more than I had expected.
Do you have some logs of the screen output of such occurences? Also, is it working more
reliable when using the VCP driver or do you face the same instabilities?




Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on September 13, 2011, 09:42:04 AM
Nyet stated there were linux binaries available for Me7logger. Can I get the located for them? Trying to reduce the number of systems I have spread all over and if i could do this all under linux vs wind0ze, that would be fantastic

thanks
Tory
No, there exists currently no linux variant of the logger. A port is on the todo list,
but this will not be done in short time, sorry.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tobz on September 13, 2011, 12:43:05 PM
Also, if I sent you an FTDI cable to test with, do you think we'd be able to get some "better" FTDI support?  I've tried using the FTDI mode but it randomly craps out here and there and I know you mentioned not having a cable... so I figured I could donate to the cause and help you get one. :D
Thanks for the offer, but I just ordered one. Unfortunately it will take till october until it arives
(the shop maintainer is on vacation, this info appeared after buying the thing ...).

So you are saying with ftdi mode you could open your interface and connect to the ecu,
then connection breaks down during logging? That would be more than I had expected.
Do you have some logs of the screen output of such occurences? Also, is it working more
reliable when using the VCP driver or do you face the same instabilities?




In FTDI mode, it will commence logging... and just randomly die.  The little period "ticks" will stop ticking and I'll have to Ctrl-C and try again.  It's short of random but it almost always dies within 2 - 4 ticks.

In normal VCP mode it works fine aside from my "error -8" issues which I'll eventually try to address at some point.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ejg3855 on September 19, 2011, 07:58:58 PM
awesome work. Need a little guide DIY, I may write one if I get it to work well and some time.

GUI would be nice for simple use.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on October 17, 2011, 08:05:16 AM
In FTDI mode, it will commence logging... and just randomly die.  The little period "ticks" will stop ticking and I'll have to Ctrl-C and try again.  It's short of random but it almost always dies within 2 - 4 ticks.

In normal VCP mode it works fine aside from my "error -8" issues which I'll eventually try to address at some point.

I found a problem in the code for FTDI cables, this led to a blocked program if the ecu didn't
send any more data. I have attached just the updated ME7Logger executable with the fix.
Using this fix, the FTDI mode should behave like the VCP mode, so instead of a hanging program
you will now see also "error -8" (timeouts) if the ecu stops sending data.

The "error -8" (timeouts) are a second problem, which lies outside the logger itself in my opinion.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Tony@NefMoto on October 17, 2011, 12:28:57 PM
Are you setting the timeouts for the FTDI device for sending and receiving when you open the device?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: j2mc on October 18, 2011, 07:13:32 PM
Just an FYI, I couldn't get a connection at all using ftdi mode, but works great using the default comm mode.  Which made me curious, what is the advantage of ftdi vs vcp in this case? Sorrybif it's a dumb question, I'm still new at this.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on October 19, 2011, 05:59:58 AM
Are you setting the timeouts for the FTDI device for sending and receiving when you open the device?
The problem was I "forgot" that FT_Read is blocking and therefore the FTDI code
would have waited forever if no further data was coming.
I set the timeouts before reading now, so the FTDI code works same as the serial port code.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on October 19, 2011, 06:06:19 AM
Just an FYI, I couldn't get a connection at all using ftdi mode, but works great using the default comm mode.  Which made me curious, what is the advantage of ftdi vs vcp in this case? Sorrybif it's a dumb question, I'm still new at this.
I am not sure if the FTDI mode has big advantages compared to the VCP mode. I was hoping it
would give an enhancement regarding the reachable communication speed (in terms of delays,
not baudrate) over the VCP mode.
The FTDI mode makes it easier to locate the cable, you don't have to look up a com port number.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: j2mc on October 19, 2011, 05:05:28 PM
Just have to say excellent work setzi!  I just logged 40 variables at 20 samples per second for over 25 minutes...worked perfect, my csv log file is 14.5 MB!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: iznogoud on October 23, 2011, 08:03:15 PM
Wow! I am in awe. And I cannot wait to try it out. Many thanks setzi. Looking at the contents of the .zip file, it looks so unix, I find it surprising that you had not got it working on the linux side first!

Now all we have to do is convince Nye to make an ECUxPlot that works with Gnuplot and we are almost fully organic.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on October 23, 2011, 08:30:15 PM
What do you want to do with gnuplot?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: iznogoud on October 23, 2011, 08:37:21 PM
What do you want to do with gnuplot?

Make a data extractor and manipulator that will drop graphs immediatelly with gnuplot scripts. Like what happens with excel and the usual logs that we see posted all the time.

I use gnuplot all the time and the ability to create plots with a script and drop the files in any format I want (from within the script) is great.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on October 23, 2011, 11:04:22 PM
Ah. I can probably do that.

Thing is, it would be easier to just have ECUxPlot automatically drop a series of graphs... also, not a lot of people use gnuplot.

But i'll think about the gnuplot idea, its a good one.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: iznogoud on October 24, 2011, 08:27:15 PM
Happy to report this things is working extremely well. This is huge for the community. I will do what I can to provide feedback and improvements.

Found a little problem with it. When invoked the first time it logs fine. Keeping the ignition on and trying to start a new logging session does not initialize properly and logging does not start. Although it is not really a problem to turn the engine off and on, which makes it work fine again, I thought setzi would like to know.

The errors I encountered were: "Read ECU ID's ....failed" The one-time error of failing to connect with an appropriate timeout may have been unrelated.

My setup for this test was: WindowsXP untouched since 2006, Cygwin untouched since 2006, Abox on MY2000 (late model) in which I had flashed the Abox file ending in 345 (from the stock ECU files of Nefmoto). I will try to run it from the linux side with Wine.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: julex on October 25, 2011, 06:14:38 AM
I am happy to report that the logger works for me superbly.

Zero issues, no time outs, nada. No issues with multiple reconnects without shutting car off like reported above. It must be A-box software/hardware isssue.

I am 02 A6 ECU with M-box S4 file on it, if that helps.



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on October 26, 2011, 09:51:33 AM
Found a little problem with it. When invoked the first time it logs fine. Keeping the ignition on and trying to start a new logging session does not initialize properly and logging does not start. Although it is not really a problem to turn the engine off and on, which makes it work fine again, I thought setzi would like to know.

My setup for this test was: .... Abox on MY2000 (late model) in which I had flashed the Abox file ending in 345 (from the stock ECU files of Nefmoto).

I can confirm that this is a software problem with the Abox image (both 0002 and 0003 are affected).
These ecu images don't re-initialize some variables when a new K-Line connection is set up.
I think about how to implement a workaround.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: iznogoud on October 26, 2011, 09:52:45 AM
Just looked at my first logging data that I acquired a day ago with the ME7Logger. One word: fantastic.

Here is a request. Can we attach a thread to this that spits out data on a UDP socket? Or just have the main thread that does the recording drop the data to a UDP socket. I think we can make a graphical real-time plotting program that can work alongside the logger. By throwing data at a UDP socket, setzi does not have to release code and make this monolithic.

I can probably code that part on the linux side, which means it can probably be ported to Cygwin pretty easily. I do not think I can get away from X11 for the windowing aspect. someone with a strong Windows background may want to do this. Something to think about.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on October 26, 2011, 10:04:38 AM
I agree. it would be fantastic.

Of course, if he released code, anybody could actually add this functionality as well.

Or at least if he released libraries and an api...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: julex on October 28, 2011, 06:27:19 AM
UDP spit out would be great unless current "real time" output already writes to a file in real time and it could be read off immediately by graphing utility. Knowing windows though it is not guaranteed though.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: j2mc on October 28, 2011, 09:40:29 AM
Right now i'm working on a simple bar gauge style display that will read the real time output of the log file...it will be slightly delayed and I'm still not sure how quickly I can read the log(so you may only get 2-5 updates per second), but better than nothing.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: j2mc on October 28, 2011, 03:46:26 PM
Here is what my gauge app looks like right now(see attached), it takes all the variables you are logging and asks you to set the minimums and maximums of each gauge.  I can't tell how fast it is updating right now, but it is looking like at least 20 times per second...but as the log file gets bigger it will slow down since it has to reopen the file everytime it updates.  Currently using 24% cpu and right around 1MB of memory.

I have a few more things to do along with some testing, then I would like to integrate this into the GUI I created...Might have it done this weekend but most likely it will be available Monday.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: iznogoud on October 28, 2011, 04:09:19 PM
Good work.

You certainly do not want to re-read the whole file all the time. Two ways of approaching it:

1) knowing the amount of data the files gets when it is written (each time) and assuming that it is always the same, you 'seek()" into the file and do your reads only of new data. This is _much_ faster than having to re-read it. You monitor the file for an updated state and you do the reading when it happens.

2. keep the file open and continue to read from where you left off. Again, you need monitoring of the file.

I wish I could tell you how to do this in Windows. If this were under Cygwin, I'd have a better chance.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on October 28, 2011, 04:36:45 PM
I wish I could tell you how to do this in Windows. If this were under Cygwin, I'd have a better chance.

is there an option to run the logger output to stdout?

i'm pretty sure windows can do the equivalent of popen()

let me guess, you can't make a named pipe in win7?

again, I'm a unix guy, so ... who knows.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: j2mc on October 28, 2011, 08:56:48 PM
Unfortunately I'm taking the cheap way out using autohotkey to do this, while it allows me to do this quick and easy(right now it's only about 20-30 lines total) i'm pretty limited on what I can do.  I'll do some longer tests this weekend and see how it runs, so far it doesn't look like it's going to be a problem(except maybe on old machines).


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Jason on October 30, 2011, 08:00:56 AM
I just read from the stdout.  Use the -R switch to invoke writing to stdout (it will still write the log file).


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: j2mc on October 30, 2011, 10:30:45 AM
Just wanted to be more specific for you:

1) I actually don't re-read the entire file each time, I open it, find the last line and read that, as the file gets bigger it might take slightly longer to find the last line(but from my tests we're talking microseconds).

2)I thought about that, but thought there is a possibility that my reads could be slower than the logger's writes..the reads could end up a few lines behind and get worse as time goes on.  If I just read the last line like i'm doing now I don't care if I missed a row of data here and there as long as what's displayed is current.

Good work.

You certainly do not want to re-read the whole file all the time. Two ways of approaching it:

1) knowing the amount of data the files gets when it is written (each time) and assuming that it is always the same, you 'seek()" into the file and do your reads only of new data. This is _much_ faster than having to re-read it. You monitor the file for an updated state and you do the reading when it happens.

2. keep the file open and continue to read from where you left off. Again, you need monitoring of the file.

I wish I could tell you how to do this in Windows. If this were under Cygwin, I'd have a better chance.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Jason on October 30, 2011, 11:51:22 AM
Are you using .net?  If so it's easy to quickly and efficiently read the stdout with a StreamReader.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: okkim on November 01, 2011, 04:03:02 AM
Thanks for the great program!

I'm trying to find out the EGT enrichment variables, but no luck.  Those that are on block 112 on VCDS.

Does anyone know what those are?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Tony@NefMoto on November 01, 2011, 05:13:03 PM
Just a quick note to all the guys working on adding a GUI to this program.

I'm hopefully going to release the NefMoto data logger with a full graphical UI in the next week...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: iznogoud on November 01, 2011, 06:51:08 PM
Just a quick note to all the guys working on adding a GUI to this program.

I'm hopefully going to release the NefMoto data logger with a full graphical UI in the next week...

I live on command-line. But good, and thanks.

Please make it configurable, and with freeze-frame hotkey, and with a shadow needle on the dials for "dial history" (sort of like seen where the average of the last 20 samples was in addition to the quickly fluctuating instantaneous measurement).


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on November 02, 2011, 10:15:11 AM
Thanks for the great program!

I'm trying to find out the EGT enrichment variables, but no luck.  Those that are on block 112 on VCDS.

Does anyone know what those are?

ME7Info -g ../bins/mbox.bin | grep 112
measgroup 112: 0098(tats_w              ), 00C4(dlamatr_w           ), 0099(tats2_w             ), 00C5(dlamatr2_w          )

-> Should be dlamatr_w and dlamatr2_w which you are searching for.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: julex on November 03, 2011, 10:38:33 AM
Just a quick note to all the guys working on adding a GUI to this program.

I'm hopefully going to release the NefMoto data logger with a full graphical UI in the next week...

Awesome.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: okkim on November 06, 2011, 08:44:34 AM
I'm having a trouble to import the data to the MS Excel or Open office. There are space before the values, or many after it after the import. Also some columns have "' ' " marks berfore the value.

The charts are not shown because of those spaces or marks. It is very difficult to clean those manually. Am I doing something wrong, or could I open the data differently?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Jason on November 06, 2011, 09:50:20 AM
What version of excel?

rename the log to log.csv, and then open the csv file - excel should strip the whitespace.

Worst case, you could always import the data into a worksheet using the text to columns feature, and then change the cell data type.

I haven't had that problem when opening the log as a .csv before though.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: okkim on November 06, 2011, 11:39:27 AM
Excel is 2010, Open office calc is 3.3.0. Excel opens the csv-files ok, but didn't remove the whitespaces. It seemed that the values were text, not numbers.

I changed the system settings so that the decimal value is ".", and not "," as it was. Now the excel works right, and removes the whitespaces and understands the numbers. But still the Open office doesn't work.

I would like to use Open office, but now I cant.

I'm not sure that if this problem is also with ECUxPLOT, because it doesn't show any graphs. It can open the cvs, and can select the variables, but is doesn't plot any lines.

Ok, I found the "fault" with ECUxPLOT. I had the "filter data" option on, and with it most of the logs didn't show nothing. So now I have only the Open office problem :)


Title: Question on FRAO, FRAU, FRA o2 corrections ME7 Logger vs RossTech VCDS values
Post by: julex on December 09, 2011, 07:22:26 AM
So I compared what VCDS and Me7 loggers show for idle, low and high range o2 LTFT adaptation values and it seems like they differ quite a lot.

For example:

Idle: VCDS shows -2.8% (0.972 multiplier?) for bank1 on idle, ME7 logger shows 0.987824 or -1.4%
Part Throttle: VCDS shows -1.6% (0.984 multiplier?) for bank1 on low range, ME7 logger shows 0.988282 or -1.2%
Full Throttle: VCDS shows -0.8% (0.992 multiplier?) for bank1 on low range, ME7 logger shows 0.999696

Keep in mind VCDS pulls data from Channel 032 while ME7 gets it from ECU memory. In addition it would appear that VCDS is stepping the corrections in 0.4% increments and is rounding numbers. Since it is stepping in 0.4% increments, I am gonna assume that this is somehow tied into a multiplier VCDS is using...

I don't know what to make out of it.... who should I trust more?

Let's hope somebody could shed some light on this, especially if you know what multiplier is VCDS using (ME7 logger is using 3.05176e-005) as it would explain why the data is off if they are using wrong values :)


Title: Re: Question on FRAO, FRAU, FRA o2 corrections ME7 Logger vs RossTech VCDS values
Post by: setzi62 on December 10, 2011, 04:08:04 AM
Let's hope somebody could shed some light on this, especially if you know what multiplier is VCDS using (ME7 logger is using 3.05176e-005) as it would explain why the data is off if they are using wrong values :)

The data you see from ME7Logger are the most accurate values you will get in this case  :).
Variables fra_w, frao_w, frau_w are stored as unsigned word (16bit) in the ecu.
Damos specifies the conversion from internal to physical value for these:
PHYS = INT / 32768, this returns values in range 0.0 to 1.99997 (a factor without unit).
The conversion factor which ME7L uses is therefore 1/32768, which is just 3.05176e-005.

Now, when you log with VCDS, the ECU processes each variable and performs an internal
conversion, then delivers for each variable three bytes (a, b, c) to VCDS.
Byte c is a conversion formula number
(see here: http://nefariousmotorsports.com/forum/index.php/topic,22.msg22.html#msg22),
bytes a and b are data values used in the conversion formula.
VCDS takes a and b, then converts again using the formula and presents you the result.

In case of fra_w, frao_w, frau_w, the ecu always sets c = 20, so the formula for VCDS is:
a*(b-128)/128  [in %].
The ecu sets a=50 and b to result from a conversion of the original 16bit value.
You can see, that VCDS can compute the final percentage result with a resolution
of 50/128 = 0.390625% in a range of -50% .. +50% (b can be 0 ..255).

Be aware, when you log via KWP1285 (as VCDS does), the ecu alway processes variables
internally before delivering data and you probably loose accuracy.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: julex on December 10, 2011, 09:08:16 AM
Thanks for the explanation, it makes total sense now!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TTQS on December 26, 2011, 09:29:24 AM
I've only just started to look into using this tool. I see that

"The stock binary is sufficient (as long as you don't change variable addresses in the code, which is normally NOT done)".

I have my stock binary file, but my car has a Revo Stage II remap. What is the likelihood of me being able to implement ME7logger successfully given what is generally known about Revo code (i.e. read over OBDII disabled, extra maps, information moved around? Etc.)

Advice would be gratefully received. I thought this might have been a way of, ahem, understanding the remap better, but I'm reluctant to embark if isn't likely to work.

TTQS


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on December 26, 2011, 10:56:45 AM
I've only just started to look into using this tool. I see that

"The stock binary is sufficient (as long as you don't change variable addresses in the code, which is normally NOT done)".

I have my stock binary file, but my car has a Revo Stage II remap. What is the likelihood of me being able to implement ME7logger successfully given what is generally known about Revo code (i.e. read over OBDII disabled, extra maps, information moved around? Etc.)

Advice would be gratefully received. I thought this might have been a way of, ahem, understanding the remap better, but I'm reluctant to embark if isn't likely to work.

TTQS

You should have no problem logging with this tool.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TTQS on December 26, 2011, 12:52:48 PM
Super. I've created a template and had a browse through the available variables.

Thanks.

TTQS


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: iznogoud on December 27, 2011, 12:17:19 PM
I'd be interested to know if you can successfully read out the flash from the Revo flashed ECU. This becasue Revo and APR sued to be the same company before the fallout (Euro and US) and I know for a fact that I could not pull out the APR trial file when I tried with the Nefmoto ME flasher tool.

Addresses for log variables are usually not changed -- I do not see why. So whether you can pull out the flash or not should not affect the ability to log in this case. Somebody with more intimate knowledge of the internals of the flash may be able to explain in detail if needed.

And.... ME7Logger rawks.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TTQS on December 28, 2011, 01:17:04 PM
Looks fine up to now. I created a definition file with 127 of the choicest variables ready to try some logging but I'm falling at the first hurdle when trying to connect over USB with a genuine Ross-Tech interface set to boot in dumb mode. It fires through all the variables o.k. on the command line window but then returns the failed to connect error. Which port should I be selecting for this or do I require a VCP driver? It's a dumbass noob question I know, but any ideas...?

TTQS


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on December 28, 2011, 01:59:29 PM
Looks fine up to now. I created a definition file with 127 of the choices variables ready to try some logging but I'm falling at the first hurdle when trying to connect over USB with a genuine Ross-Tech interface set to boot in dumb mode. It fires through all the variables o.k. on the command line window but then returns the failed to connect error. Which port should I be selecting for this or do I require a VCP driver? It's a dumbass noob question I know, but any ideas...?

TTQS

Default is COM port 2 IIRC, but it is an accepted argument.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TTQS on December 28, 2011, 02:32:42 PM
Default is COM port 2 IIRC, but it is an accepted argument.

It was selected USB in VCDS when I unchecked boot in intelligent mode, but I guess I could try selecting COM2 in VCDS. I'm using the GUI and I did try typing USB into the COM port box but that didn't work either.

I've just ordered a normal, cheap 409.1 KKL VAG cable from eBay to avoid any future complications with the genuine Ross Tech interface. Maybe that might help.

TTQS


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on December 28, 2011, 06:22:47 PM
Default is COM port 2 IIRC, but it is an accepted argument.

It was selected USB in VCDS when I unchecked boot in intelligent mode, but I guess I could try selecting COM2 in VCDS. I'm using the GUI and I did try typing USB into the COM port box but that didn't work either.

I've just ordered a normal, cheap 409.1 KKL VAG cable from eBay to avoid any future complications with the genuine Ross Tech interface. Maybe that might help.

TTQS

You need to open Device Manager from the Window's Control Panel and expand the Ports tree. You should have a USB serial port with the current COM port displayed. You can assign it to a different port by double clicking it to bring up the properties window. Then, click the Port Settings tab and select the Advanced button.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TTQS on December 29, 2011, 02:37:50 AM
You need to open Device Manager from the Window's Control Panel and expand the Ports tree. You should have a USB serial port with the current COM port displayed. You can assign it to a different port by double clicking it to bring up the properties window. Then, click the Port Settings tab and select the Advanced button.

Thanks. Makes sense, I'll try that.

TTQS


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: lezsi on January 04, 2012, 11:45:32 AM
This logger is awesome!

Unfortunately my car (seat leon 1.8t AUQ) seems to have the busy K-line problem, it drops connection after a few seconds when ignition is on. (It's fine when ignition is off).

How others cured this problem? Do you have some details where/how to route a "dedicated" K-line from the ECU if necessary?

Thanks


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: carlossus on January 04, 2012, 12:24:59 PM
Unfortunately my car (seat leon 1.8t AUQ) seems to have the busy K-line problem, it drops connection after a few seconds when ignition is on. (It's fine when ignition is off).

How others cured this problem? Do you have some details where/how to route a "dedicated" K-line from the ECU if necessary?

I take it you read my Leon thread http://nefariousmotorsports.com/forum/index.php?topic=1021.msg10463#msg10463 here?

For me it's fine if I keep the "Log packet size: 36 bytes" or less which gives me 24 variables to log
which is enough for me for most of my tinkering. I regularly log my 25minute journey to work without a timeout.

You can maximise the number of vars by choosing the single byte versions where you have a choice.

Out of interest, what's your ECU version? It might be better to post in the thread above to keep these issues together.




Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tkla on January 08, 2012, 03:24:16 PM
cool!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: All_Euro on January 09, 2012, 09:21:02 PM
Finally had a chance to start using the Me7Logger - awesome stuff!

Question: has anyone else noticed their correction factors to be completely different than what VCDS logs? I'm trusting the Me7Logger values but still curious.

Thanks


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TTQS on January 10, 2012, 08:31:35 AM
Finally had a chance to start using the Me7Logger - awesome stuff!

Question: has anyone else noticed their correction factors to be completely different than what VCDS logs? I'm trusting the Me7Logger values but still curious.

Thanks

Is that because of this (from the previous page on this post)?

http://nefariousmotorsports.com/forum/index.php?topic=837.msg11613#msg11613

TTQS


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: All_Euro on January 10, 2012, 12:25:36 PM
Is that because of this (from the previous page on this post)?

http://nefariousmotorsports.com/forum/index.php?topic=837.msg11613#msg11613

TTQS

I'm just realizing my question was pretty vague... in VCDS I show a fair amount of ignition timing pull in cyl#4 & with Me7Logger I rarely get any from that cylinder - I'm surprised at how much of a difference there is.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on January 10, 2012, 12:28:01 PM
I'm just realizing my question was pretty vague... in VCDS I show a fair amount of ignition timing pull in cyl#4 & with Me7Logger I rarely get any from that cylinder - I'm surprised at how much of a difference there is.

I haven't seen that variation.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Tony@NefMoto on January 10, 2012, 12:57:59 PM
The one possibility I could think of, is that the ECU clears that variable each cycle, and then sets it to a new value. It is possible the ME7Logger is ready the value after it has been cleared, but before it is set. This is just a guess though.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Lobuziak on January 15, 2012, 02:33:03 PM
Hello.

I'm new to that great knowledgeable forum but have a request/question.

What would be needed to add different Motronic ECU support for ME7logger? How can I get RAM variables addresses?

My cars ECU is Me1.5.5 it has 512KB data file. The car is Opel Astra Coupe 2.0T. I have a damos for it and it looks similar to ME7.1
Tried use the tool and make some logs - "written 13 definitions" - but didn't want to make logs because of the unknown bootrom.

edit: if that helps WinOLS Demo shows processor: Siemens C167CR

Regards
Lobuziak


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on January 20, 2012, 08:45:02 AM
The ME1.5.5 might be same CPU and contain same maps as the ME7, but the basic software
is completely different. Since the ME7Logger depends definitely on the bootrom of the ME7,
it is not possible to port it easily to another ECU type. Same is true for the ME7Info tool.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Lobuziak on January 20, 2012, 11:34:20 AM
The ME1.5.5 might be same CPU and contain same maps as the ME7, but the basic software
is completely different. Since the ME7Logger depends definitely on the bootrom of the ME7,
it is not possible to port it easily to another ECU type. Same is true for the ME7Info tool.

So to get it working someone should get the bootrom with minimon, disassemble it, disassemble flash rom correlate it with damos and make some more testing...
If there was a good working logger that would help with tuning of the car. There is some how working op-com but I don't get any knock control action, air mass and load is wrongly calculated... Anyway thanks.

Regards
Lobuziak


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on January 22, 2012, 03:53:14 PM
Has anyone with an Euro 2.7 gotten this to work?
I get this:
Code:
Logged data size is 72 bytes.
Start connecting to ECU at 23.01.2012 00:38:51.109
try connect slow(11)
try connect slow(11)
Could not connect
try connect slow(11)
22:38:56.656-252,0 os_setspeed(speed=10400)
22:38:56.963-321,4 os_receiver_off()
22:38:56.963-586,3 os_setbreak()
22:38:57.164-499,2 os_clrbreak()
22:38:57.365-932,4 os_setbreak()
22:38:57.566-520,4 os_setbreak()
22:38:57.767-140,4 os_setbreak()
22:38:57.968-995,3 os_clrbreak()
22:38:58.170-738,3 os_setbreak()
22:38:58.372-139,3 os_setbreak()
22:38:58.572-750,3 os_setbreak()
22:38:58.773-447,3 os_clrbreak()
22:38:58.775-066,5 os_receiver_on()
22:38:59.278-435,8 os_rcvbyte(timeout=500) -> TIMEOUT
try connect slow(11)
22:38:59.278-975,8 os_setspeed(speed=10400)
22:38:59.585-279,8 os_receiver_off()
22:38:59.585-555,8 os_setbreak()
22:38:59.787-078,9 os_clrbreak()
22:38:59.988-297,8 os_setbreak()
22:39:00.189-228,9 os_setbreak()
22:39:00.390-282,7 os_setbreak()
22:39:00.591-733,7 os_clrbreak()
22:39:00.792-797,8 os_setbreak()
22:39:00.994-333,8 os_setbreak()
22:39:01.195-425,8 os_setbreak()
22:39:01.396-525,9 os_clrbreak()
22:39:01.398-050,7 os_receiver_on()
22:39:01.901-669,2 os_rcvbyte(timeout=500) -> TIMEOUT
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)...
VCDS Lite connects just fine using the same cable...

I have immo on the car, and what I notice is, a relay in the cluster makes a "click" when VCDS Lite connects, but not when ME7Logger connects.
On older motronics to use fast diag, the immo had to be bypassed.

Am I right in thinking, that I need to run a direct K-Line from the ECU into the diagnostic port for this to work?
Otherwise the immo is blocking all communication?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on January 23, 2012, 02:24:54 AM
I think you are in the same boat as user s4rmm. He also can't connect to 0x11 while instruments cluster
turned on.
If I ever find the time, I will add a new connection method " double slowinit to 0x01" to the ME7L.
This is a connection method that should always work. The drawback of this is, it is only possible while
the engine is not running on most ecus. But I think it is possible to patch the image so this check is no
longer present and then it should be possible to connect using "double slowinit" even while the engine is running.

If you have access to the cables and dont fear the work, direkt K-line should also be a solution.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on January 23, 2012, 05:17:00 AM
s4rmm actually lives in my little town :D
He has a K04 S4, I have RS4.

In older cars, when I wrote fast logging for the ECU (custom protocol), the immo shorted K-Line to ground.
Basically I sent it 5 baud init, then it let through a little bit of data and shut it down again.
I think it's actively monitoring communications and if it sees something it does not like, it shuts down the line in older ECU's.

Do you think the cluster is also shorting K-line to ground? Because if it is, then I will not only need to add a direct K-Line, I will also need to add a switch, which will switch between the normal K-Line and direct K-Line, if I want to log anything else.
Or do you think just bridging the lines will be enough? (that didn't work on older cars for me with Immo 1).

Also, you are saying that engine has to be off - if it is off, and you connect, will it stay connected after you start the engine? If yes, then it's not a problem...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on January 23, 2012, 05:27:33 AM
Oh yes, sorry, forgot that you will need a switch to separate ecu from regular K-line.
I did it using a relais which disconnects the bus from ecu when activated.
When I plug in my diag cable to the new direct-ecu-connector, a bridge between
two otherwise unused pins in the plug activates this relais and I just communicate with the ecu.
If the bridge is not set in the plug, the relais stays released and I can e.g. monitor
the traffic on the K-line at ecu side.

I have made some logic analyzer traces of the diag connector and same time of the ecu
while instrument cluster is on. You can nicely see how the instrument cluster "disturbs"
the line!! I'll prepare them and post in the communication protocols section soon.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on January 23, 2012, 07:45:06 AM
Okay, so...
I cut the K-line coming from ECU. Then I put a relay on there (or a three pole), I then connect the ECU to one pole, then to one switched pole I connect the K-line wire that I cut, and to the other switched pole I connect a new K-Line wire.

I then run the new K-Line to the OBD II connector.

Will it work then? Or do I also need to disconnect the cluster from the OBD II connector?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on January 23, 2012, 10:16:27 AM

I just did the following:
                         ( whatever )   Switch       +-----+
  OBD-Connector O--------( is in    )---o____O---+---| ECU |
                         ( the line )            |   +-----+
                                                 |
  NEW-Connector O--------------------------------'


Switch open   -> NEW connector can be used to communicate with ECU.
                       ORIG connector can be used to communicate with all other devices.

Switch closed -> ORIG connector can be used as previously.
                        NEW connector can be used for MONITORING the bus at ecu side.


If you want to use just the original ODB-Connector, you should
disconnect also the original K-line at the connector side.
You need a BYPASS of whatever is in the line between OBD-connector and ECU:

                    Switch    ( whatever )    Switch
                         o----( is in    )----o           +-----+
 OBD-Connector O-----O--__    ( the line )    __--O-------| ECU |
                         o-.                .-o           +-----+
                           |                |         
                           '----------------'         



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on January 23, 2012, 04:59:26 PM
Ok, I understand, you added a whole separate connector.
Pretty good idea with the relay also, I like that.

I think I will take a 2x2 adapter cable I have, gut it and run the K-Line and power to it, as well as the relay positive voltage or ground.
That should work just fine. I guess I need to start the car first (so immo can talk to ECU), then plug in the connector, and I can log.

Thank you...
Now if you only could add some sort of instant output mode to the logger, so I wouldn't have to hook it to get the data in real time ... but I guess not all wishes can be fulfilled.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Jason on January 24, 2012, 04:54:40 PM
Slightly off-topic but my ECU rebooted while logging tonight exactly when "The Application Experience service entered the stopped state." showed up in the event log.

I'm guessing the ECU was waiting for a message or got an incomplete transmission and decided to reboot?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TTQS on January 29, 2012, 04:36:25 AM
Any chance that lamfawkr_w can be added to the main list, or can somebody post the address for it?

I want to see if lamfaw-lamkr is being used to enrich below lean best torque at WOT instead of lambts on my tune.

Thanks in advance

TTQS


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: julex on February 15, 2012, 11:39:07 AM
I believe that all that needs to be done to successfully use MarkP templates (and others) are some changes to ME7 .ECU/.CFG files and any ECUX template should work without any changes to template itself (which is preferable):

1) Activate [Alias] columns for the .CFG file by removing ";" sign in front of them. This will force logger to use column names from CFG files not .ECU file. Useful for people who want to use one .ECU with multiple .CFG files and not necessarily having mtaching column names, like me...

2) If you want to preserve original vfil_w in km/s:
   Make a copy of vfil_w file in .ECU file, call it vfil_w_miles, and modify "A" column to "0.0048555" (which is a product of original 0.0078125 divided by 1.609 - how many kms in a mile)
   Modify vfil_w line in .CFG file to say vfil_w_miles. You will now log speed in miles
  
   If you don't want to preserve original value, just modify the A column for vfil_w and you're done.

3) IATs. Do the same as in #2 if you want to preserve original variable in Cs. Regardless, the formula changes to A= 1.35, B = - 54.4 and you now log in F.
  Don't ask me in detail how I arrived at that. It takes just a little bit of arithmetic, use two formulas for C to F and the one used in logger and a bit of shuffling stuff around and here it is.

4) Timing retard: Modify dwkrz_0 - dwkrz_5's column A to "-0.75". Retard will now be positive in the logs as originally it is a signed value and is negative.


This leaves one outstanding thing which is timestamps. I will ask Setzi for an option to output EcuX style time stamps in a format "mmm" instead of current "s:mmm". Regardless, a simple replace of "." with "" in excel takes care of this.

Enjoy.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on February 15, 2012, 11:51:23 AM
btw ECUxPlot can take care of whatever translations you need (including unit conversions), just email me and i'll try to add them.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: julex on February 16, 2012, 09:08:01 AM
Ok, I have a .CFG/.ECU combo file that works with any EcuX tool sans the timestamps which would have to be modified by hand. If anybody is interested, give me a word and I will share.

Thanks.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: jibberjive on February 16, 2012, 09:28:08 AM
If only I would've known you were making that last night lol. I've got my own as of a few hours ago.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: julex on February 16, 2012, 09:33:13 AM
One correction though, tans (IAT) calculation requires: A = 1.35 and B = 54.4 NOT B = -54.4 as I originally posted.

Thanks.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: rkam on February 16, 2012, 02:13:04 PM
I'm not sure if this is supposed to work, but I just tried it on a Volvo ME7 with limited success.

The program was unable to open COM1 where I had a real RS232 to KKL interface.  (-p 1)
serialOpen - Unable to open port (error=2)
can't open serial port 1
Initialization failed, exiting ...
exiting (cause=0x1)...

USB KKL at COM3 gave the same error.

But with -f option I was able to use the USB version.

57600:
INIT Slow 0x11

IN 55 ef 8f

OUT 70
IN  ee

OUT 02 1a 94 b0
IN  0a 5a 94 45 32 45 4e 43 47 57 43 26 (E2ENCGWC) SWNumber

OUT 03 10 86 64 fd
IN  03 50 86 64 3d

OUT 07 83 03 00 01 00 14 00 a2
IN  02 c3 03 c8

OUT 02 1a 81 9d
IN  13 5a 81 04 91 0f 01 03 92 6a 03 93 6a 03 94 68 03 95 68 ff 90

OUT 02 1a 91 ad
IN  12 5a 91 00 00 00 00 00 10 32 22 00 00 00 00 09 47 07 38 f0 (Serial No.103222 , Part No. 09470738)

OUT 02 1a 92 ae
IN  0c 5a 92 30 32 36 31 32 30 34 35 35 39 fa (0261204559) HWNumber

OUT 02 1a 93 af
IN  0c 5a 93 31 30 33 37 33 35 39 34 36 32 01 (1037359462)

OUT 02 1a 94 b0
IN  0a 5a 94 45 32 45 4e 43 47 57 43 26 (E2ENCGWC) SWNumber

OUT 02 1a 95 b1
IN  0a 5a 95 37 30 31 39 37 45 39 5a d9 (70197E9Z)

OUT 05 23 00 e1 b0 04 bd
IN  05 63 00 00 00 00 68


Start connecting to ECU at 16.02.2012 21:58:35.843
try connect slow(11)
=> FLASH (slowinit)
ecuid reports software version
Started session86, speed=57600
-> Read ECU ID's .... done
-> Checked ECU ID's
unknown bootromversion found
=> Logging failed
exiting (cause=0x4)...



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phils8 on March 02, 2012, 08:29:59 PM
I have a RossTech KII-USB cable. Works fine with NefMoto Flasher. Was wondering if ME7Logger can work with this USB cable or just the ebay USB cables?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on March 05, 2012, 09:25:07 AM
I'm not sure if this is supposed to work, but I just tried it on a Volvo ME7 with limited success.

Sorry, but that is the expected outcome. The Volvo ME7 is not compatible with ME7L.
A custom protocol is used for logging which depends on the bootrom in ME7 found in
VAG cars (VW,Audi,Seat,Skoda).


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on March 05, 2012, 09:33:15 AM
I have a RossTech KII-USB cable. Works fine with NefMoto Flasher. Was wondering if ME7Logger can work with this USB cable or just the ebay USB cables?
If Nefmoto works with this cable, also ME7L should be able to do.
It just needs to be a "dumb" cable with FTDI chip.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: speed51133 on March 27, 2012, 05:59:07 AM
-> Reading log config file C:\Users\Speed51133\Downloads\me7logger\logs\my 1st.c
fg .... done
-> Reading ecu characteristics file C:\Users\Speed51133\Downloads\me7logger\ecus
\example.ecu .... done
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x01
Communicate  = HM0
LogSpeed     = 56000

[Identification]
HWNumber           = "0261207931"
SWNumber           = "1037366920"
PartNumber         = "4B0906018DA"
SWVersion          = "0006"
EngineId           = "1.8L R4/5VT"

Logged variables are:
#no.: name                , alias                           , addr  ,sz, bitm, S
, I,  A         ,   B, unit
#069: tmot                , CoolantTemperature              , 380A63, 1, 0000, 0
, 0,        0.75,  48, '░C'
#070: tmotlin             , CoolantTemperature              , 3848B5, 1, 0000, 0
, 0,        0.75,  48, '░C'
#071: tmotsoll            , CoolantTemperatureRequested     , 384969, 1, 0000, 0
, 0,        0.75,  48, '░C'
#072: tmst                , EngineStartTemperature          , 3848BB, 1, 0000, 0
, 0,        0.75,  48, '░C'
#073: tnst_w              , TimeSinceStart                  , 382C14, 2, 0000, 0
, 0,        0.01,   0, 's'
Logged data size is 124 bytes.
Start connecting to ECU at 26.03.2012 22:36:07.154
try connect slow(01)
received wrong inverted address 0x0F (expected 0xFE)
try connect slow(01)
received wrong inverted address 0x0F (expected 0xFE)
Could not connect
try connect slow(01)
02:36:12.473-756,1 os_setspeed(speed=10400)
02:36:12.788-569,9 os_receiver_off()
02:36:12.789-426,2 os_setbreak()
02:36:12.993-594,5 os_clrbreak()
02:36:13.196-619,7 os_setbreak()
02:36:13.399-628,3 os_setbreak()
02:36:13.603-799,1 os_setbreak()
02:36:13.806-637,0 os_setbreak()
02:36:14.009-659,7 os_setbreak()
02:36:14.212-651,5 os_setbreak()
02:36:14.415-705,6 os_setbreak()
02:36:14.618-663,5 os_clrbreak()
02:36:14.621-645,5 os_receiver_on()
02:36:14.889-692,2 os_rcvbyte(timeout=500) -> 55
02:36:14.900-123,1 os_rcvbyte(timeout=100) -> 01
02:36:14.909-663,7 os_rcvbyte(timeout=100) -> 8A
02:36:14.935-488,9 os_sendbyte(data=75)
02:36:14.969-662,8 os_rcvbyte(timeout=100) -> 0F
received wrong inverted address 0x0F (expected 0xFE)
try connect slow(01)
02:36:14.975-568,4 os_setspeed(speed=10400)
02:36:15.291-652,3 os_receiver_off()
02:36:15.292-527,2 os_setbreak()
02:36:15.496-680,1 os_clrbreak()
02:36:15.700-667,4 os_setbreak()
02:36:15.903-716,4 os_setbreak()
02:36:16.106-733,3 os_setbreak()
02:36:16.309-709,8 os_setbreak()
02:36:16.512-710,6 os_setbreak()
02:36:16.715-735,8 os_setbreak()
02:36:16.918-766,2 os_setbreak()
02:36:17.121-733,7 os_clrbreak()
02:36:17.124-729,8 os_receiver_on()
02:36:17.393-778,4 os_rcvbyte(timeout=500) -> 55
02:36:17.403-823,2 os_rcvbyte(timeout=100) -> 01
02:36:17.413-825,0 os_rcvbyte(timeout=100) -> 8A
02:36:17.440-131,2 os_sendbyte(data=75)
02:36:17.473-754,2 os_rcvbyte(timeout=100) -> 0F
received wrong inverted address 0x0F (expected 0xFE)
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)...

C:\Users\Speed51133\Downloads\me7logger>


the above is all i can get to happen. i can log fine with vcds and EVEN WITH ECUX! I would like to try this out, but i have seen others with the same errors, and no solutions.

using a real vcds cable set it to NOT intelligent. no com port works, have to use that other selection.

any help?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on March 29, 2012, 07:07:21 AM
the above is all i can get to happen. i can log fine with vcds and EVEN WITH ECUX! I would like to try this out, but i have seen others with the same errors, and no solutions.

using a real vcds cable set it to NOT intelligent. no com port works, have to use that other selection.

any help?

You are using the example.ecu file, which matches the 4B0906018DA, 0006 image.
This image allows connection to KWP2000 with slowinit to 0x01,
but on your car/ecu you get a KWP1285 connection on the address 0x01.

I don't think your ecu has the image file 018DA inside! You need to follow
the instructions in the README and generate your own .ecu file that matches your image.
To do this, you will need to read out the image of your ecu first
or you can try find an original file with matching ecu ID's somewhere on the forum.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: speed51133 on March 29, 2012, 11:27:53 AM
I did not even know there was a README. I found it buried in the DOC folder.

So i need my ecu's binary. It says to "get it" or find someone that has it.

So how do I get it?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on April 02, 2012, 04:43:23 AM
Read the image out of the ecu with the Nefmoto ECU flasher
http://nefariousmotorsports.com/forum/index.php?topic=1686.0title=


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on April 02, 2012, 05:05:36 AM
Finally I was able to put together a "cleanup" build of ME7Logger
with all the small changes that have piled up over the time.
Find an updated version 1.17 of ME7Logger and ME7Info in the first post.

Roughly the changes in ME7Logger:
- Reworked general timing calculations, timestamps, sync to full second
- Fixed local time in absolute timestamps (option -a)
- Supress logfile writing when output goes to stdout (option -R)
  useful if output is piped to external evaluation tool/filter
- Added option -m: Timestamp format milliseconds
- Added option -h: supress printing header information in logfiles
- Added option -b: set logging baudrate for communication,
                   overrides baudrate from ecu file
- connection method "double slowinit" added (helps with "instrument cluster" problem)
  To use double slowinit set in the [Communication] section of the .ecu file:
    Connect      = SLOW-0x00
    DoubleDelay  = 12           ; Possible values 1 .. 100 (delay in 100ms)
  This allows to connect only while engine not yet started.

And the changes in ME7Info:
- Reverted back to zwbasar_0 .. zwbasar_3
  (Array size NOT dependent on number of cylinders)
- Some variables added:
 + zwoutar_0 .. zwoutar_3
 + zwsol
 + redist / evz_austot
 + lamfaws_w / lamfawkr_w / lamfaw_w / lamfwl_w / lamrlmn_w
 + perffilt_w / perfmax_w   => This is CPU-Load
    It helps in finding out the max. logging capabilities of your ECU.
    Around 90% CPU-Load might be a limit for the ECU.

I think it would be useful if you put perffilt_w (CPU load) into your logging profiles and
make some tests to see how you ECU performs underr different logging conditions (sample rate/#variables).
My ECU is 32MHz, so I have plenty of headroom for wildest logging. But most ECUs run at 24MHz and some
even have only 20MHz, so these could probably suffer from excessive logging.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on April 02, 2012, 09:53:21 AM
THANK YOU!

BTW, seeing as I am attempting to debug torque monitoring issues in my ECU, can you add:

dzws
etazws
wkrdy
zaldy
B_krldya
B_krldyv

thanks!

I have them in my ecu defs, but they get overwritten when i dload a new version from you, and i have to hand patch them back :)

Or, alternately, have some sort of file that you read that has custom values to automatically add to .ecu and the template.cfg?

i just cat them on, but i have to remember to do so :)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: -SlowSilverTIPJason- on April 02, 2012, 01:08:39 PM
Nice!  TY setzi!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: lulu2003 on April 03, 2012, 12:42:16 PM
seems the default paths to /def is not working as before?

getting "can't open map file defs\me7_std.map"
and
"can't open alias file defs\me7_alias.map"
and
"can't open output file ecus\xy.ecu"

it works when I specify the pathes.....



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on April 04, 2012, 12:20:46 AM
seems the default paths to /def is not working as before?

getting "can't open map file defs\me7_std.map"
and "can't open alias file defs\me7_alias.map"
and "can't open output file ecus\xy.ecu"

it works when I specify the pathes.....

Sorry, that was a build error, so it worked only under cygwin but not in DOS shell.
I fixed this and updated the .zip in the first post, please download this again,
it contains an updated ME7Info.exe


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: lulu2003 on April 04, 2012, 01:13:15 AM
thx, it works again  :D


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: lulu2003 on April 04, 2012, 02:27:27 AM
thx, it works again  :D

first test of the logger on a ME7.8:

Quote
try connect slow(11)
=> FLASH (slowinit)
ecuid reports software version
Started session86, speed=56000
-> Read ECU ID's .... done
-> Checked ECU ID's
Found bootrom version 05.12/05.32 via readmem
Read pointer ... done
Store handler ... writemem failed, got error: 0x12
=> Logging failed
exiting (cause=0x4)...

any idea?
(more details provided in PM)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on April 04, 2012, 09:37:32 AM
Sorry, that was a build error, so it worked only under cygwin but not in DOS shell.
I fixed this and updated the .zip in the first post, please download this again,
it contains an updated ME7Info.exe


ha ha. glad I use cygwin :)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: elRey on April 04, 2012, 11:35:01 PM
request fupsrl_w


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: udcc11 on April 24, 2012, 06:07:47 PM
 I am getting an echo failure and to check the connection and make sure the ignition is on, which they both are.
I am using the ross-tech cable and put it in dumb mode.
I'm not sure what is going on here. I searched and didn't see this mentioned.  Thanks for the help.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on April 27, 2012, 07:39:32 AM
The echo check just checks wether communication works and the K-line is powered.
If you don't get an echo while connected and ignition on, one possibility is
that the wrong serial port is selected (default is COM2), use option -p <COMPORT>
for the correct com port. Or you need to specify option -f (to use an FTDI based cable).


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: jibberjive on April 28, 2012, 12:51:53 AM
When I tried to log with the newest version, I got an error that said something like "too many variables."  Does the new version have a limit on how many variable you can log?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: udcc11 on May 03, 2012, 09:56:49 PM
The echo check just checks wether communication works and the K-line is powered.
If you don't get an echo while connected and ignition on, one possibility is
that the wrong serial port is selected (default is COM2), use option -p <COMPORT>
for the correct com port. Or you need to specify option -f (to use an FTDI based cable).

I thought I went through all the ports one by one but my water pump crapped on me right after I tried. I'll have to wait til I finish my stage 3 build to try again.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: NOTORIOUS VR on May 04, 2012, 02:21:31 PM
So what is needed to make this work with a Porsche 996T ECU? :)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Vitruvian Engineering on May 04, 2012, 05:45:58 PM
So what is needed to make this work with a Porsche 996T ECU? :)
I've been looking down this road myself;)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: azaiats on May 19, 2012, 07:30:07 AM
For those who are having error -8 issues, like me was a while ago, I found that the problem was my notebook. It is a IBM Thinkpad which cames with an accelerometer and a technology to protect your HD when the notebook get shockes... When it's "on" and you're trying to log data from your car, the me7logger will stop random because your car shakes too much :)

Who have IBM/Lenovo notebook's go to: http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-53150 and install the application. When installed, you can disable APS protection and have fun with your logging :)

This drove me crazy for like 2 days without logging success... hope this can help someone too.

[]s


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: masterj on May 20, 2012, 12:46:04 PM
Could someone help me to locate memory addreses for these variables? (for logging, since me7 logger can't find them)

B_CDAGR
B_CDAGRL
B_CDATR
B_CDATS
B_CDBKVP
B_CDDSBKV
B_CDDST
B_CDEGFE
B_CDEHFM
B_CDFST
B_CDGTS
B_CDHRLSU
B_CDHRLSUE
B_CDHSH
B_CDHSV
B_CDHSVSA
B_CDKAT
B_CDKATSP
B_CDKATSPT
B_CDKVS
B_CDLASH
B_CDLATP
B_CDLATV
B_CDLDP
B_CDLLR
B_CDLSH
B_CDLSHV
B_CDLSV
B_CDLSVV
B_CDMD
B_CDNWS
B_CDSLS
B_CDSLSE
B_CDSWE
B_CDTANKL
B_CDTES

These are from prokonal bits section... :)


Title: Works perfekt with a RS4 B5 8D0907551K ECU
Post by: RS4boost on May 22, 2012, 11:59:16 AM
Hi,

absolutly great tool. :)

Works perfect for a RS4 B5 with 8D0 907 551K ECU, in connection method "double slowinit".
In older versions without this option there is no chance to connect with this car.
But now it runs stable and fast.
I use it with a AVG4000 cable in transparent mode.

It is a dream to log realtime values with this tool...
There is a great chance to fine tune many things in the ECU.

Tom


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on May 28, 2012, 01:07:30 PM
For those who are having error -8 issues, like me was a while ago, I found that the problem was my notebook. It is a IBM Thinkpad which cames with an accelerometer and a technology to protect your HD when the notebook get shockes... When it's "on" and you're trying to log data from your car, the me7logger will stop random because your car shakes too much :)

Who have IBM/Lenovo notebook's go to: http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-53150 and install the application. When installed, you can disable APS protection and have fun with your logging :)

This drove me crazy for like 2 days without logging success... hope this can help someone too.

Hey, great. Thanks for this tip!
I checked the APS application in the Thinkpad now and it is really often disabling the harddisk.
I will try with disabled APS if I get more stable logging also.
As alternative, I will also try to log onto a Ramdisk.
Must think about decoupling the logger from the writing to harddisk a little bit more to avoid such problems.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: julex on May 29, 2012, 08:37:01 AM
Hey, great. Thanks for this tip!
I checked the APS application in the Thinkpad now and it is really often disabling the harddisk.
I will try with disabled APS if I get more stable logging also.
As alternative, I will also try to log onto a Ramdisk.
Must think about decoupling the logger from the writing to harddisk a little bit more to avoid such problems.

I had the same problem back in days with Eurodyne logger. Eventually figured it out and disabled the protection...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: fykus on June 07, 2012, 02:37:55 PM
Pushing a little bit forward on the logging front ...
Here is my ME7Logger package now available for everybody,
has been tested successfully on different cars.

It consists of two tools: one to generate ecu characteristics files
(similar to properties) out of ecu images, second to log data.
No GUI for klicky guys, no graphics, just console programs.

/sales_mode=on  ;)
Will outperform commercially available tools on speed & flexibility:
 - Up to 50 samples per second possible.
 - Up to 127 independent variables can be logged at same time.
 - Open for expansions: whatever you want to log, you can define it.
 - No fiddling with licenses/hacked programs needed.
/sales_mode=off

- It's free for hobby use,
- It's NOT for noobs. Not a connect-and-log tool,
  before logging you should have your ecu image available.

Last but not least: buy a commercial program if you want
to make someone liable for damages/not working logging tools  :)

Update 12.08.2011, some fixes/changes done:
- Experimental FTDI native driver support added, option -f
- Logger start time synchronization added, option -t
- Logger absolute timestamp added, option -a
- Allow TAB's also in trace config files
- Variables zwbasar_<xx> for all available cylinders
- Variables wkraa_<xx> limited to available cylinders
- Minor changes, some variables added

Update 09.09.2011, some of the requested changes/fixes done:
- Single sample option added (result is output just to the window)
- More variables determined for images with code variant (missing tans(IAT) for one image)
- zwbasar_<xx> now really available for all available cylinders
- Some more variables added
- Some alias names added, some changed


Update 02.04.2012 to version 1.17:
(Updated 04.04.2012 the ME7Info in the .zip, fixed path error)
Changes in ME7Logger:
- Reworked general timing calculations, timestamps, sync to full second
- Fixed local time in absolute timestamps (option -a)
- Supress logfile writing when output goes to stdout (option -R)
  useful if output is piped to external evaluation tool/filter
- Added option -m: Timestamp format milliseconds
- Added option -h: supress printing header information in logfiles
- Added option -b: set logging baudrate for communication,
                   override baudrate from ecu file
- connection method "double slowinit" added (helps with "instrument cluster" problem)
  To use double slowinit set in the [Communication] section of the .ecu file:
    Connect      = SLOW-0x00
    DoubleDelay  = 12           ; Possible values 1 .. 100 (delay in 100ms)
  This only allows to connect while engine not yet started.

Changes in ME7Info:
- Reverted back to zwbasar_0 .. zwbasar_3
  (Array size NOT dependent on number of cylinders)
- Some variables added:
 + zwoutar_0 .. zwoutar_3
 + zwsol
 + redist / evz_austot
 + lamfaws_w / lamfawkr_w / lamfaw_w / lamfwl_w / lamrlmn_w
 + perffilt_w / perfmax_w   => This is CPU-Load
    It helps in finding out the max. logging capabilities of your ECU.
    Around 90% CPU-Load might be a limit for the ECU.

i really cant seem to figure out to open the file dowmloaded all of them any help//


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: boomerro on July 20, 2012, 12:09:07 AM
EDIT.  never mind, im an idiot... lol.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: AndiS4 on July 30, 2012, 12:30:56 PM
Logger is really fine. everything visuable with a great resolution! Absolutely great!

But its strange, that the airmass on my 8d0907551d seems to be shown with an offset of about 55 g/s (idle airmass is about 60 g/s).
The rest works really well in double slow init. I wish I could connect in another init, to be able to start logging during the engine running.

Thanks for this great tool!



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: gremlin on August 04, 2012, 05:49:26 PM
I've found some problems with some ME7.5 ECUs 2004...2005MY
For example ECU Numbers:
8E0909518BC 0010 0020 0040
4B0906018DQ 0040 0060
ME7Info.exe can't recognize most of definitions.
Error messages list is in attachment.
Any ideas?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: A6turbofrance on August 05, 2012, 04:35:13 AM
i thinks i have found my problem i can't connect with any logger
i have see on audizine that an aftermarket radio can cause kline interferance
i wanna try it without my rns-e for see...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Michel94 on August 15, 2012, 06:46:30 AM
Hi, i'have problem to connect and test me7logger to a F-box:
If someone have an idea? thx


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Michel94 on August 15, 2012, 07:02:32 AM
i saw the cause of my problem, i must connect in ''double slowinit" , now i have a new problem!

(http://img594.imageshack.us/img594/4015/erro2m.jpg) (http://imageshack.us/photo/my-images/594/erro2m.jpg/)






Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on August 16, 2012, 06:03:52 AM
Flash your ECU to K-Box.
F-Box is bad anyway, it does not have ignition misfire checking and other things.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: professor on August 19, 2012, 01:47:07 PM
Guys owning a original vcds usb cable what cmd should use to play?
me7_logger -f my_log.cfg dont work
and for
me7_logger -L<> my_log.cfg i cant find the HEX address of my usb.

Any advice or this too noobish to answer  ::) ?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on August 20, 2012, 01:38:20 AM
Set it to dumb mode and install the Ross Tech driver which creates a COM port.
Then uncheck "boot in intelligent mode".

After this connect using the created COM port.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: professor on August 20, 2012, 01:36:23 PM
Set it to dumb mode and install the Ross Tech driver which creates a COM port.
Then uncheck "boot in intelligent mode".

After this connect using the created COM port.

It works via cmd -f.

Thank you.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Gonzo on August 21, 2012, 07:50:24 PM
I love this logger but I can never get it to log over 15 samples/sec without pulling the cluster fuse or it will give me timeout errors :(


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nehalem on August 21, 2012, 08:45:33 PM
I love this logger but I can never get it to log over 15 samples/sec without pulling the cluster fuse or it will give me timeout errors :(

Believe it or not, I keep it at 10 Hz...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on August 22, 2012, 03:08:16 AM
I log at 20hz on all cars and no timeout errors.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 22, 2012, 09:41:12 AM
I log at 20hz on all cars and no timeout errors.

I find it works a lot better in USB mode, not COM port mode.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on August 22, 2012, 11:43:48 AM
I run COM port mode and an el cheapo KKL cable. Never had any issues...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: RS4boost on August 22, 2012, 01:07:49 PM
Flash your ECU to K-Box.
F-Box is bad anyway, it does not have ignition misfire checking and other things.

@prj
Have you ever done this with success?
I mean RS4 551F to 551K...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Gonzo on August 22, 2012, 01:40:17 PM
I find it works a lot better in USB mode, not COM port mode.
USB just hangs at connection for me  :-\


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on August 22, 2012, 02:02:05 PM
@prj
Have you ever done this with success?

Yes, on this car:
http://prj-tuning.com/?p=253 (http://prj-tuning.com/?p=253)

Flashing must be done in boot mode. OBD bricks the ECU.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: RS4boost on August 22, 2012, 02:05:24 PM
Yes, on this car:
http://prj-tuning.com/?p=253 (http://prj-tuning.com/?p=253)

Flashing must be done in boot mode. OBD bricks the ECU.

Ok very interesting.

Only flashed in bootmode and done?
And the car runs without problems?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on August 22, 2012, 02:29:14 PM
Ok very interesting.

Only flashed in bootmode and done?
And the car runs without problems?

Yes...
After you flash to 551K in boot mode you can flash over OBD.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: RS4boost on August 22, 2012, 11:23:10 PM
Yes...
After you flash to 551K in boot mode you can flash over OBD.

Thank you for sharing this info... ;)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: professor on August 31, 2012, 10:48:18 AM
.Got error -8

What it mean guys?



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Michel94 on September 01, 2012, 01:46:07 AM
Thank you for sharing this info... ;)

And K-box flash with F file works ?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on September 01, 2012, 02:33:56 AM
And K-box flash with F file works ?

Most likely, but I would not do this, because F does not have misfire recognition while K does.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Il Signor Zetec on September 16, 2012, 01:56:27 PM
- connection method "double slowinit" added (helps with "instrument cluster" problem)
  To use double slowinit set in the [Communication] section of the .ecu file:
    Connect      = SLOW-0x00
    DoubleDelay  = 12           ; Possible values 1 .. 100 (delay in 100ms)
  This allows to connect only while engine not yet started.

hello Setzi, thank you for your useful tool. I had the same problem described here:

http://nefariousmotorsports.com/forum/index.php?topic=837.msg16551#msg16551

I used a particular charateristics file for my ecu (8N0906018J) with slow init.
During the mods on the .ecu file I didn't find a row to mod the double delay time. Also changing the whole rows in [connection] with your

    Connect      = SLOW-0x00
    DoubleDelay  = 12           ; Possible values 1 .. 100 (delay in 100ms)

I can't connect to the ecu (error = cause<0x04> )
Then the solution is to put a dedicated K line from ecu? Can I do any other test?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Il Signor Zetec on September 23, 2012, 03:09:31 AM
I used a directly connect K line cable. Now all work good


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Milka on September 27, 2012, 04:58:21 AM
Really great tool, worked first time I tried it on an RS6.

I do have a request is it possible to get modified Defs so that ME7Info can map dual MAFs?  Currently I have the following:
 msdk_w        mshfm_w       uhfm_w   

From what I can tell the first 2 are combined values but the last one is voltage and I think is for an individual sensor?  I would love to have voltage and g/s for each MAF.

Thanks


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on September 27, 2012, 05:56:34 AM
You can get them by disassembly ;)

Does VAG-COM support showing the mass flow over each MAF?
If yes, try printing the measuring block info with me7logger and seeing what it reports.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on September 27, 2012, 06:02:23 AM
It will almost definitely be located directly before or after in RAM.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Milka on September 27, 2012, 07:01:49 AM
Thanks guys.  Yep, through VCDS I have a combined g/s which maxes out at 364 while the individual MAF values continue to rise.  I will try to get the info and post it tomorrow (Aus time).

prj, I'm still working on clutch switch wiring, will be in contact very soon


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on September 27, 2012, 07:25:58 AM
My question was not because you should log with VCDS.
My question was because if you can see this with VCDS, then use ME7Info-s functionality to print information about measuring blocks.

This will yield the addresses most likely, IF it is possible to log them with VCDS.

Now you see where I was going with this :)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Milka on September 27, 2012, 07:57:35 AM
Yep I realised that, was just stating what VCDS has.  I did not know that ME7Info had that option (probably should check the options)

Just ran it with -g option, then looked up measuring block 2

measgroup 002: 0001(nmot                )    0002(rl                  )    0394(                    )    0395(                    )

Not sure how I log these in ME7Logger yet, will try and figure it out.

Last 2 are the individual MAF readings g/s, there is no MAF voltage in the measuring blocks but I think I have one of those mapped already in the full .ecu file (just to see when I get close to maxing out the MAFs)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on September 27, 2012, 08:42:16 AM
Ha, it seems empty in ME7Logger. Maybe something for setzi to work on.
But it's pretty easy to find in ASM if it's in the measuring blocks.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Milka on September 27, 2012, 03:25:55 PM
Ok how would I find it in ASM?  it's the last 2 measuring blocks in measuring group 2 I need


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: matchew on September 27, 2012, 05:39:59 PM
F94E and F950 are added together to make F954 (mshfm_w)

I believe the MAF voltages are 0x380ABA and 0x380AB8

 


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Milka on September 27, 2012, 06:58:07 PM
Thanks I will do a quick log and check.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Milka on September 28, 2012, 05:30:24 AM
Thanks Matchew!

0x00F94E and 0x00F950 were correct

One of the MAF voltages 0x380ABA was correct but the other one was something else. The second one was 0x380ABC.

For anyone that wants to map these on an RS6 here are the entries I added to the .ecu file, the nht is just my initials so I know which ones I added manually

mshfm1_nht   , {MassAirFlow Bank 1}          , 0x00F94E,  2,  0x0000, {g/s}     , 0, 0,    0.0277778,      0, {Massenstrom HFM Bank1}
mshfm2_nht   , {MassAirFlow Bank 2}          , 0x00F950,  2,  0x0000, {g/s}     , 0, 0,    0.0277778,      0, {Massenstrom HFM Bank2}
uhfm_w1_nht     , {MassAirFlow Voltage Bank 1}       , 0x380ABA,  2,  0x0000, {V}       , 0, 0,   0.00488281,      0, {Spannung HFM Bank1}
uhfm_w2_nht     , {MassAirFlow Voltage Bank 2}       , 0x380ABC,  2,  0x0000, {V}       , 0, 0,   0.00488281,      0, {Spannung HFM Bank2}


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on September 28, 2012, 09:20:49 AM
Well done guys.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: matchew on September 28, 2012, 09:49:15 AM
Thanks Matchew!

0x00F94E and 0x00F950 were correct

One of the MAF voltages 0x380ABA was correct but the other one was something else. The second one was 0x380ABC.

No probs, I musta been tired when I looked at this. Atleast it gave you the lead you needed and figured it out your self :)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: jooo on October 20, 2012, 02:30:40 PM
Is ME7logger (and ecux) always safe to use or can there be ecu problems with codes or eeprom or something like that? Don't want to kill friends ecu who has an unknown tune.
But I suspect it is an APR or Revo tune.
Does it use the same ME7.x functions/commands as when flashing and therefore could be blocked by tuner or does ME7logger always work if you have a correct .ecu file?

I'm asking since I recall reading about problems after using nefmoto software even though they have only tried reading their box.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: melodic on October 23, 2012, 08:31:40 AM
Is it possible to log MED9.1 ECUs or it has different protocol?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: bbernd on November 24, 2012, 03:22:25 AM
Thanks Matchew!

0x00F94E and 0x00F950 were correct

One of the MAF voltages 0x380ABA was correct but the other one was something else. The second one was 0x380ABC.

For anyone that wants to map these on an RS6 here are the entries I added to the .ecu file, the nht is just my initials so I know which ones I added manually

mshfm1_nht   , {MassAirFlow Bank 1}          , 0x00F94E,  2,  0x0000, {g/s}     , 0, 0,    0.0277778,      0, {Massenstrom HFM Bank1}
mshfm2_nht   , {MassAirFlow Bank 2}          , 0x00F950,  2,  0x0000, {g/s}     , 0, 0,    0.0277778,      0, {Massenstrom HFM Bank2}
uhfm_w1_nht     , {MassAirFlow Voltage Bank 1}       , 0x380ABA,  2,  0x0000, {V}       , 0, 0,   0.00488281,      0, {Spannung HFM Bank1}
uhfm_w2_nht     , {MassAirFlow Voltage Bank 2}       , 0x380ABC,  2,  0x0000, {V}       , 0, 0,   0.00488281,      0, {Spannung HFM Bank2}

Hm... am I not smart enough??  I added this to the ecu file and started to create a new Template (config) with ME7Logger GUI (Create Template file) but the four variables are not in the new config... ??  Am I doing wrong??


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Milka on November 24, 2012, 04:40:50 AM
Hm... am I not smart enough??  I added this to the ecu file and started to create a new Template (config) with ME7Logger GUI (Create Template file) but the four variables are not in the new config... ??  Am I doing wrong??

Did you add entries into both the .ecu and the .cfg files you are using?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on November 25, 2012, 06:54:45 AM
and started to create a new Template (config) with ME7Logger GUI (Create Template file)

There is your mistake. The template is created from the file, not from the .ecu.
So you will have to create a template and then manually add the entires to the template.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: bbernd on November 29, 2012, 04:29:07 AM
There is your mistake. The template is created from the file, not from the .ecu.
So you will have to create a template and then manually add the entires to the template.

thx ...  thats what I want so hear...  I went in the wrong direction because it was written "add it to your ecu file" and so it has to be "add it to your ecu and to your temp file"...

so thanks a lot for advice...


Title: Re: Logging ME7 fast and flexible => ME7Logger - win7 64bit help needed
Post by: vtraudt on December 05, 2012, 07:55:00 AM
I need help installing the logger on my win7 64bit.
is someone willing to give me a hand, walk me through (email/txt/phone) based on a good detailed guide?
Or in person (I am in the Lansing/Ann Arbor/Detroit area)?

Really would like to use the logger and get rid of ECUx logger; VAGcom just too slow and limited.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nicetry on January 19, 2013, 06:17:28 PM
I'm having some troubles getting this to run, has anyone seen these errors before?

-> Reading log config file C:\Users\Rob\Downloads\ME7Logger_DIST_02042012_v1.17\
logs\Audi S4 2.7T 2001.5 6speed 8D0907551M 0261207143 1037354837 001_template.cf
g .... done
-> Reading ecu characteristics file C:\Users\Rob\Downloads\ME7Logger_DIST_020420
12_v1.17\ecus\Audi S4 2.7T 2001.5 6speed 8D0907551M 0261207143 1037354837 001.ec
u .... done
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x11
Communicate  = HM0
LogSpeed     = 56000

[Identification]
HWNumber           = "0261207143"
SWNumber           = "1037354837"
PartNumber         = "8D0907551M"
SWVersion          = "0001"
EngineId           = "2.7l V6/5VT"

Logged variables are:
#no.: name                , alias                           , addr  ,sz, bitm, S
, I,  A         ,   B, unit
#-------------------------------------------------------------------------------
-----------------------------
#001: dwkrz_0             , IgnitionRetardCyl1              , 380C2B, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#002: dwkrz_1             , IgnitionRetardCyl5              , 380C2C, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#003: dwkrz_2             , IgnitionRetardCyl3              , 380C2D, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#004: dwkrz_3             , IgnitionRetardCyl2              , 380C2E, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#005: dwkrz_4             , IgnitionRetardCyl6              , 380C2F, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#006: dwkrz_5             , IgnitionRetardCyl4              , 380C30, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#007: fr_w                , LambdaControl                   , 382E3A, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#008: fra2_w              , AdaptationPartialBank2          , 3823E0, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#009: fra_w               , AdaptationPartial               , 3823E2, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#010: frm2_w              , LambdaControlAvgBank2           , 382E2A, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#011: frm_w               , LambdaControlAvg                , 382E34, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#012: gangi               , SelectedGear                    , 380AF8, 1, 0000, 0
, 0,           1,   0, 'gear'
#013: lamsbg_w            , AirFuelRatioDesired             , 3823C4, 2, 0000, 0
, 0, 0.000244141,   0, '-'
#014: ldtvm               , WastegateDutyCycle              , 380C76, 1, 0000, 0
, 0,    0.390625,   0, '%'
#015: mshfm_w             , MassAirFlow                     , 00F97C, 2, 0000, 0
, 0,   0.0277778,   0, 'g/s'
#016: nmot_w              , EngineSpeed                     , 00F87A, 2, 0000, 0
, 0,        0.25,   0, 'rpm'
#017: plsol_w             , BoostPressureDesired            , 382284, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#018: pus_w               , BaroPressure                    , 382206, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#019: pvdkds_w            , BoostPressureActual             , 382216, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#020: rkat2_w             , AdaptationIdleBank2             , 383D18, 2, 0000, 1
, 0,    0.046875,   0, '%'
#021: rkat_w              , AdaptationIdle                  , 383D1A, 2, 0000, 1
, 0,    0.046875,   0, '%'
#022: rkrn_w_0            , KnockVoltageCyl1                , 382646, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#023: rkrn_w_1            , KnockVoltageCyl5                , 382648, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#024: rkrn_w_2            , KnockVoltageCyl3                , 38264A, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#025: rkrn_w_3            , KnockVoltageCyl2                , 38264C, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#026: rkrn_w_4            , KnockVoltageCyl6                , 38264E, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#027: rkrn_w_5            , KnockVoltageCyl4                , 382650, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#028: rl_w                , EngineLoad                      , 00F990, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#029: rlmax_w             , EngineLoadCorrected             , 38277E, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#030: rlmx_w              , EngineLoadSpecified             , 382782, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#031: rlsol_w             , EngineLoadRequested             , 3822D8, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#032: tabgm               , EGTModelBeforeCat               , 380A81, 1, 0000, 0
, 0,           5,  50, '░C'
#033: tabgm2              , EGTModelBeforeCatBank2          , 380A82, 1, 0000, 0
, 0,           5,  50, '░C'
#034: tans                , IntakeAirTemperature            , 380BBF, 1, 0000, 0
, 0,        0.75,  48, '░C'
#035: tats2_w             , EGTSensorBank2                  , 3824EE, 2, 0000, 0
, 0,   0.0195312,  50, '░C'
#036: tats_w              , EGTSensor                       , 3824F0, 2, 0000, 0
, 0,   0.0195312,  50, '░C'
#037: ti_b1               , FuelInjectorOnTime              , 38238E, 2, 0000, 0
, 0,  0.00266667,   0, 'ms'
#038: usvk                , O2SVoltageSensor1               , 380AA6, 1, 0000, 0
, 0,  0.00521569, 0.2, 'V'
#039: usvk2               , O2SVoltageSensor1Bank2          , 380AA7, 1, 0000, 0
, 0,  0.00521569, 0.2, 'V'
#040: vfil_w              , VehicleSpeed                    , 380E40, 2, 0000, 0
, 0,   0.0078125,   0, 'km/h'
#041: wdkba               , ThrottlePlateAngle              , 380B13, 1, 0000, 0
, 0,    0.392157,   0, '% DK'
#042: wped_w              , AccelPedalPosition              , 381FA4, 2, 0000, 0
, 0,   0.0015259,   0, '% PED'
#043: zwout               , IgnitionTimingAngleOverall      , 00F9FC, 1, 0000, 1
, 0,        0.75,   0, '░KW'
Logged data size is 71 bytes.
can't locate function FT_GetLibraryVersion in dll
Initialization failed, exiting ...
exiting (cause=0x1)...

C:\Users\Rob\Downloads\ME7Logger_DIST_02042012_v1.17>


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: vagenwerk on January 25, 2013, 07:31:17 AM
I logg with succes few days ago.
Today i try to log and result :

"Logged data size is 20 bytes.
can't locate function FT_GetLibraryVersion in dll
Initialization failed, exiting ...
exiting (cause=0x1)..."


what is going on ?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: vagenwerk on January 26, 2013, 04:23:07 AM
anyone ?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on January 26, 2013, 06:34:00 AM
Your install is probably corrupted due to a virus or similar, re-install it.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: vagenwerk on January 26, 2013, 04:13:11 PM
i re-download gui + logger re-install it there is still error

'Logged data size is 2 bytes.
can't locate function FT_GetLibraryVersion in dll
Initialization failed, exiting ...
exiting (cause=0x1)..."


i try many options but without succes

work like a charm and suddenly stopped after few days ?  any hints ?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on January 26, 2013, 04:43:25 PM
That's an FTDI function.

Try reinstalling the driver.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: sweegie on January 26, 2013, 05:27:59 PM
Pull new FTDI drivers down and put ftd2xx.dll from the driver package into the me7logger bin directory. This should fix your issue.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on January 26, 2013, 07:55:55 PM
Pull new FTDI drivers down and put ftd2xx.dll from the driver package into the me7logger bin directory. This should fix your issue.

I wouldn't do this unless you really know what you are doing (i.e remember to delete the dll the next time you reinstall the drivers). Windows is really dumb with .dlls. You only need one wayward dll in yoru system and eveything can get screwed up.

Hell, i bet the poster's problem is due to something similar (a usb/serial dll floating around where it shouldnt).


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: sweegie on January 27, 2013, 11:52:16 AM
Hell, i bet the poster's problem is due to something similar (a usb/serial dll floating around where it shouldnt).

Yep, I agree it sounds like it. Windows *should* pick up a library dll in the same directory as the executable first, before attempting to locate it in system32 etc etc, but i dont trust it too much to behave like it's supposed to either....


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on January 27, 2013, 12:38:07 PM
Its worse than that. Once that DLL is loaded in memory it *STAYS THERE * until the system is rebooted - and every app is forced to use it unless it deliberately tries to load a different dll. Absolutely retarded behavior, but thats windows for you.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: lsalt100 on January 28, 2013, 04:53:07 PM
Thanx for great tool!!

I've got some problems to connect, but reading this forum help much.
Now I use KKL pass through cable (blue one-china made-some ch340 chip inside).
"SLOW-0x00" in ecu settings file, and starting LOGGER before starting engine.
Everything works fine.

so once again thanx for very useful tool!!!



now is time to analyze logs ;-)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: temanuele on March 05, 2013, 08:52:58 PM
Been having some issues connecting lately, so I'm wondering if I am doing something obviously wrong. I have used this same computer, cable and car for all my previous logging, so I'm not sure what happened. I have also tried both M-box 001 and 001 bin files. I have also tried different computers, cables and cars and get the same error so I'm guessing it is user error. If anyone could help me out, it would be greatly appreciated. I keep getting this error message:

-> Reading log config file C:\Users\Chuck\Desktop\ME7Logger_DIST_02042012_v1.17\
logs\2001.5 Audi S4 8D0907551M 0261207143_template.cfg .... done
-> Reading ecu characteristics file C:\Users\Chuck\Desktop\ME7Logger_DIST_020420
12_v1.17\ecus\2001.5 Audi S4 8D0907551M 0261207143.ecu .... done
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x11
Communicate  = HM0
LogSpeed     = 56000

[Identification]
HWNumber           = "0261207143"
SWNumber           = "1037360857"
PartNumber         = "8D0907551M"
SWVersion          = "0002"
EngineId           = "2.7l V6/5VT"

Logged variables are:
#no.: name                , alias                           , addr  ,sz, bitm, S
, I,  A         ,   B, unit
#-------------------------------------------------------------------------------
-----------------------------
#001: dwkrz_0             , IgnitionRetardCyl1              , 380C2B, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#002: dwkrz_1             , IgnitionRetardCyl5              , 380C2C, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#003: dwkrz_2             , IgnitionRetardCyl3              , 380C2D, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#004: dwkrz_3             , IgnitionRetardCyl2              , 380C2E, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#005: dwkrz_4             , IgnitionRetardCyl6              , 380C2F, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#006: dwkrz_5             , IgnitionRetardCyl4              , 380C30, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#007: fr2_w               , LambdaControlBank2              , 382E1C, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#008: fr_w                , LambdaControl                   , 382E3A, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#009: frm2_w              , LambdaControlAvgBank2           , 382E2A, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#010: frm_w               , LambdaControlAvg                , 382E34, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#011: gangi               , SelectedGear                    , 380AF8, 1, 0000, 0
, 0,           1,   0, 'gear'
#012: ldtvm               , WastegateDutyCycle              , 380C76, 1, 0000, 0
, 0,    0.390625,   0, '%'
#013: mshfm_w             , MassAirFlow                     , 00F97C, 2, 0000, 0
, 0,   0.0277778,   0, 'g/s'
#014: nmot_w              , EngineSpeed                     , 00F87A, 2, 0000, 0
, 0,        0.25,   0, 'rpm'
#015: plsol_w             , BoostPressureDesired            , 382284, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#016: pvdkds_w            , BoostPressureActual             , 382216, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#017: tabgm               , EGTModelBeforeCat               , 380A81, 1, 0000, 0
, 0,           5,  50, '░C'
#018: tabgm2              , EGTModelBeforeCatBank2          , 380A82, 1, 0000, 0
, 0,           5,  50, '░C'
#019: tans                , IntakeAirTemperature            , 380BBF, 1, 0000, 0
, 0,        0.75,  48, '░C'
#020: tats2_w             , EGTSensorBank2                  , 3824EE, 2, 0000, 0
, 0,   0.0195312,  50, '░C'
#021: tats_w              , EGTSensor                       , 3824F0, 2, 0000, 0
, 0,   0.0195312,  50, '░C'
#022: ti_b1               , FuelInjectorOnTime              , 38238E, 2, 0000, 0
, 0,  0.00266667,   0, 'ms'
#023: zwout               , IgnitionTimingAngleOverall      , 00F9FC, 1, 0000, 1
, 0,        0.75,   0, '░KW'
Logged data size is 34 bytes.
Start connecting to ECU at 05.03.2013 19:47:04.823
try connect slow(11)
try connect slow(11)
Could not connect
try connect slow(11)
19:47:10.339-685,5 os_setspeed(speed=10400)
19:47:10.343-260,4 os_receiver_off()
19:47:10.645-914,5 os_setbreak()
19:47:10.846-457,4 os_clrbreak()
19:47:11.047-789,0 os_setbreak()
19:47:11.249-928,6 os_setbreak()
19:47:11.451-221,1 os_setbreak()
19:47:11.652-221,4 os_clrbreak()
19:47:11.854-187,9 os_setbreak()
19:47:12.055-344,1 os_setbreak()
19:47:12.256-471,5 os_setbreak()
19:47:12.459-360,7 os_clrbreak()
19:47:12.460-347,4 os_receiver_on()
19:47:12.963-062,5 os_rcvbyte(timeout=500) -> TIMEOUT
try connect slow(11)
19:47:12.964-320,5 os_setspeed(speed=10400)
19:47:12.966-048,6 os_receiver_off()
19:47:13.266-327,5 os_setbreak()
19:47:13.468-035,0 os_clrbreak()
19:47:13.669-590,0 os_setbreak()
19:47:13.870-260,9 os_setbreak()
19:47:14.070-736,3 os_setbreak()
19:47:14.271-852,4 os_clrbreak()
19:47:14.472-500,9 os_setbreak()
19:47:14.673-677,6 os_setbreak()
19:47:14.875-164,2 os_setbreak()
19:47:15.075-872,2 os_clrbreak()
19:47:15.077-718,1 os_receiver_on()
19:47:15.580-403,9 os_rcvbyte(timeout=500) -> TIMEOUT
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)...

C:\Users\Chuck\Desktop\ME7Logger_DIST_02042012_v1.17>


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on March 05, 2013, 09:53:39 PM
If you are who I think you are, shouldn't you have access to some proprietary logging software?

And aren't you part of that anti-Nefmoto tribe?

All that aside, there is nothing obvious there.

Does VCDS and/or ECUx function as expected?

The only time that I've seen that is when the file on the ECU is bad and connection isn't possible.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on March 05, 2013, 10:33:43 PM
i've seen that on occasion.

rebooting the ECU seems to help sometimes, or unplugging the usb port on my cable and plugging it back in


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: temanuele on March 06, 2013, 12:20:35 AM
If you are who I think you are, shouldn't you have access to some proprietary logging software?

And aren't you part of that anti-Nefmoto tribe?

All that aside, there is nothing obvious there.

Does VCDS and/or ECUx function as expected?

The only time that I've seen that is when the file on the ECU is bad and connection isn't possible.

Anti-Nefmoto tribe? I've never said a bad thing about this forum or its users so I'm not sure where this is coming from.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: temanuele on March 06, 2013, 12:25:08 AM
Thanks for the answers.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: CoupedUp on March 13, 2013, 12:46:24 PM
No, there exists currently no linux variant of the logger. A port is on the todo list,
but this will not be done in short time, sorry.

Any word on this? Would be sweet to get a raspberry pi in a car to start logging based off of a switch and not need a computer in the car.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: AudiSportB5S4 on March 16, 2013, 12:29:33 PM
I've spent the past couple days reading this and first off... Thanks to all the people who put so much work into this. I actually love how raw it is in comparison to ECUx. The GUI is also great..

My questions.. I did read this thread too, so if someone wouldn't mind helping I'd appreciate it. They're basic.

I'm deleting only the semicolon in front of each variable, correct? I think I did that part right... I have the variables I want to look at. Now when I go to use my VCDS hex/can cable, it's runs through the command prompt and then says COM error 2, or something right along those lines. Has it been figured out what settings you want to shoot for with the VCDS cable, or should I get the other cable from ebay?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on March 16, 2013, 12:45:06 PM
ME7L can use the FDTI USB method or the COM port method.

If you don't install the RossTech VCP driver, the ross tech cable will not get a COM port allocated to it, and you have to tell ME7L to use the USB method.

Which method is better depends on your laptop/OS/cable.. I generally use USB when possible.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: AudiSportB5S4 on March 16, 2013, 01:39:21 PM
ME7L can use the FDTI USB method or the COM port method.

If you don't install the RossTech VCP driver, the ross tech cable will not get a COM port allocated to it, and you have to tell ME7L to use the USB method.

Which method is better depends on your laptop/OS/cable.. I generally use USB when possible.

Nye... Thanks a lot man. What is the RossTech "vcp" driver? The driver is installed for the cable for VCDS use and it connects to ECUx fine, but I have this netbook now and I want it to be my logging machine... ECUx seems too outdated now, so I'm determined to get this to work!

Also side question since everyone on this site is near genius... The netbook I'm running this on is an Acer Aspire one with an Intel Atom dual core 1.6 processor. It has 1gig of RAM which I've already bought the 2gig stick for, since Win7 starter takes a bunch of the physical memory just to run. I have stripped the netbook of anything but Firefox, and the logging tools and VCDS. This should be sufficient for logging with Me7, yes?

Thanks again Nye!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ddillenger on March 16, 2013, 01:42:58 PM
Nye... Thanks a lot man. What is the RossTech "vcp" driver? The driver is installed for the cable for VCDS use and it connects to ECUx fine, but I have this netbook now and I want it to be my logging machine... ECUx seems too outdated now, so I'm determined to get this to work!

Also side question since everyone on this site is near genius... The netbook I'm running this on is an Acer Aspire one with an Intel Atom dual core 1.6 processor. It has 1gig of RAM which I've already bought the 2gig stick for, since Win7 starter takes a bunch of the physical memory just to run. I have stripped the netbook of anything but Firefox, and the logging tools and VCDS. This should be sufficient for logging with Me7, yes?

Thanks again Nye!

I use an acer aspire one, works great. I didn't even bother to upgrade the memory.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on March 16, 2013, 01:47:42 PM
"VCP" stands for "virtual com port", which you should only need for software that expects to see the KKL interface on a com port, rather that directly on a USB port.

ME7L, galletto, and VCDS do not need the VCP driver.. so unless you are having lots of problems talking directly to USB, you shouldn't need it.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: AudiSportB5S4 on March 17, 2013, 04:38:24 AM
I use an acer aspire one, works great. I didn't even bother to upgrade the memory.

Oh, good to know!

"VCP" stands for "virtual com port", which you should only need for software that expects to see the KKL interface on a com port, rather that directly on a USB port.

ME7L, galletto, and VCDS do not need the VCP driver.. so unless you are having lots of problems talking directly to USB, you shouldn't need it.

Oh okay, thanks for the info. So in the GUI (I read you're not a fan lol) am I changing that "Specify Com Port" to read "USB" or just selecting use FTDI?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Timtheguru on March 19, 2013, 02:46:29 PM
Is ME7Logger written in C? I'd love to get this ported over to Android and use BT or the Beta FTDI Android driver. Would be sweet to attach my cell phone or tablet to gather logs.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on March 19, 2013, 02:49:12 PM
Unfortunately, it is binary only. No source :(


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Timtheguru on March 19, 2013, 02:55:19 PM
Darn! Heh, I've been playing around with emulators on my rooted Kindle Fire HD to get Win95/98/XP etc and run ME7Logger in there, so far all of the emulators suck, or maybe it's just the Kindle not allowing me to host the USB device (so I'll be getting a different Tablet soon) and try this out some more. If I knew how to write a program that did what all of this does I would make a native one for Android... maybe one day. Although, Java would be cool, and could be across all platforms.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: AudiSportB5S4 on March 23, 2013, 06:56:47 AM
My buddy who is on here also came over last night and got it working! He had to download the VCP for the cable I have (Rosstech Hex/Can). Then he was still hitting a speed bump, which was that my file name was edited from the stock 2.7 blah blah thing you read in the engine channel in VCDS. Once he changed it to to what mine reads, it worked!!!

Tested it out and it's great. Big thanks!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aysix on April 13, 2013, 09:37:03 PM
I've found some problems with some ME7.5 ECUs 2004...2005MY
For example ECU Numbers:
8E0909518BC 0010 0020 0040
4B0906018DQ 0040 0060
ME7Info.exe can't recognize most of definitions.
Error messages list is in attachment.
Any ideas?



Was this resolved? Is there a solution? Same issue over here. Trying this out on an 04 Passat and upon trying to create a template file with the stock, or modded bin I get this. This only happens with this specific bin, and i'm not sure where to start troubleshooting.

(http://img405.imageshack.us/img405/6916/loledi.png)

Any insight would be great.

Thanks!



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Timtheguru on April 16, 2013, 08:57:44 AM
OOo, Microsoft is going to put out a tablet that competes with the 7" crowd. That would be perfect for this logging tool. :)

http://www.fool.com/investing/general/2013/04/15/ipad-minis-latest-challenger.aspx (http://www.fool.com/investing/general/2013/04/15/ipad-minis-latest-challenger.aspx)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on April 16, 2013, 11:20:06 AM
What would be perfect would be source code so it can be ported :)

setzi already published binaries for linux..


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on April 16, 2013, 11:27:29 AM
What would be perfect would be source code so it can be ported :)

setzi already published binaries for linux..

Written to interface directly with Tunerpro for map tracing along with a real time dashboard ;D

Gratefully submitted.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: jibberjive on April 16, 2013, 01:29:59 PM
Agreed with the above, the source would be awesome :)



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: udcc11 on April 24, 2013, 11:14:31 AM
I'm stumped with the same problem I had a year ago when my water pump went out. I am having an Echo test failed, check cable is connected and ignition is on message on com3. Any other com I get can't open serial port com1,2,4 etc.

I'm using a newer vag com cable with it in dumb mode on a Windows 7 64 bit. Car is a 2000 S4 six-speed. Ignition is on and the light on the cable is on.

In Windows the Ross-Tech cable is labeled at this:
Location 0 (Port_#0004.Hub_#0001) (I don't know if this helps I'm just supplying the information.

What is going on with this that I can't figure out? Thanks for any help. I need this tune revisioned ASAP.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: udcc11 on April 24, 2013, 12:56:13 PM
After a suggestion on Audizine I downloaded and installed this:
http://www.ross-tech.com/vag-com/usb/virtual-com-port.html

Now I try to run it FTDI as he suggested and am getting the echo test failed again on that now.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: udcc11 on April 25, 2013, 03:57:04 PM
Any suggestions would be appreciated :(


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on April 25, 2013, 04:03:30 PM
If you didn't have the vcp installed AND enabled, it is unlikely that com3 is correct.


For me7l, and the ross-tech cable in dumb mode, you should use the -f option.

Please paste the output of what you are trying to do (no screen shot, just copy/paste the text from the cmd.exe box)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: udcc11 on April 25, 2013, 08:00:27 PM
-> Reading log config file C:\ME7Logger\logs\Audi B5 S4 2.7T APB 250HP 026120611
0 1037352741.bin_template.cfg .... done
-> Reading ecu characteristics file C:\ME7Logger\ecus\Audi B5 S4 2.7T APB 250HP
0261206110 1037352741.bin.ecu .... done
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x11
Communicate  = HM0
LogSpeed     = 56000

[Identification]
HWNumber           = "0261206110"
SWNumber           = "1037352741"
PartNumber         = "8D0907551A"
SWVersion          = "0003"
EngineId           = "2.7l V6/5VT"

Logged variables are:
#no.: name                , alias                           , addr  ,sz, bitm, S
, I,  A         ,   B, unit
#-------------------------------------------------------------------------------
-----------------------------
#001: dwkrz_0             , IgnitionRetardCyl1              , 380C17, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#002: dwkrz_1             , IgnitionRetardCyl5              , 380C18, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#003: dwkrz_2             , IgnitionRetardCyl3              , 380C19, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#004: dwkrz_3             , IgnitionRetardCyl2              , 380C1A, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#005: dwkrz_4             , IgnitionRetardCyl6              , 380C1B, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#006: dwkrz_5             , IgnitionRetardCyl4              , 380C1C, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#007: fr_w                , LambdaControl                   , 382CC8, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#008: fra2_w              , AdaptationPartialBank2          , 3822BC, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#009: fra_w               , AdaptationPartial               , 3822BE, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#010: frm2_w              , LambdaControlAvgBank2           , 382CB8, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#011: frm_w               , LambdaControlAvg                , 382CC2, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#012: gangi               , SelectedGear                    , 380AF7, 1, 0000, 0
, 0,           1,   0, 'gear'
#013: lamsbg_w            , AirFuelRatioDesired             , 38229E, 2, 0000, 0
, 0, 0.000244141,   0, '-'
#014: ldtvm               , WastegateDutyCycle              , 380C62, 1, 0000, 0
, 0,    0.390625,   0, '%'
#015: mshfm_w             , MassAirFlow                     , 00F97A, 2, 0000, 0
, 0,   0.0277778,   0, 'g/s'
#016: nmot_w              , EngineSpeed                     , 00F878, 2, 0000, 0
, 0,        0.25,   0, 'rpm'
#017: plsol_w             , BoostPressureDesired            , 38219E, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#018: pus_w               , BaroPressure                    , 3820FE, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#019: pvdkds_w            , BoostPressureActual             , 38210E, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#020: rkat2_w             , AdaptationIdleBank2             , 383D04, 2, 0000, 1
, 0,    0.046875,   0, '%'
#021: rkat_w              , AdaptationIdle                  , 383D06, 2, 0000, 1
, 0,    0.046875,   0, '%'
#022: rkrn_w_0            , KnockVoltageCyl1                , 382550, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#023: rkrn_w_1            , KnockVoltageCyl5                , 382552, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#024: rkrn_w_2            , KnockVoltageCyl3                , 382554, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#025: rkrn_w_3            , KnockVoltageCyl2                , 382556, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#026: rkrn_w_4            , KnockVoltageCyl6                , 382558, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#027: rkrn_w_5            , KnockVoltageCyl4                , 38255A, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#028: rl_w                , EngineLoad                      , 00F98E, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#029: rlmax_w             , EngineLoadCorrected             , 38266C, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#030: rlmx_w              , EngineLoadSpecified             , 382670, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#031: rlsol_w             , EngineLoadRequested             , 3821D2, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#032: tabgm               , EGTModelBeforeCat               , 380A81, 1, 0000, 0
, 0,           5,  50, '░C'
#033: tabgm2              , EGTModelBeforeCatBank2          , 380A82, 1, 0000, 0
, 0,           5,  50, '░C'
#034: tans                , IntakeAirTemperature            , 380BAD, 1, 0000, 0
, 0,        0.75,  48, '░C'
#035: tats2_w             , EGTSensorBank2                  , 3823B2, 2, 0000, 0
, 0,   0.0195312,  50, '░C'
#036: tats_w              , EGTSensor                       , 3823B4, 2, 0000, 0
, 0,   0.0195312,  50, '░C'
#037: ti_b1               , FuelInjectorOnTime              , 382272, 2, 0000, 0
, 0,  0.00266667,   0, 'ms'
#038: usvk                , O2SVoltageSensor1               , 380AA4, 1, 0000, 0
, 0,  0.00521569, 0.2, 'V'
#039: usvk2               , O2SVoltageSensor1Bank2          , 380AA5, 1, 0000, 0
, 0,  0.00521569, 0.2, 'V'
#040: vfil_w              , VehicleSpeed                    , 380E10, 2, 0000, 0
, 0,   0.0078125,   0, 'km/h'
#041: wdkba               , ThrottlePlateAngle              , 380B0D, 1, 0000, 0
, 0,    0.392157,   0, '% DK'
#042: wped_w              , AccelPedalPosition              , 381EBA, 2, 0000, 0
, 0,   0.0015259,   0, '% PED'
#043: zwout               , IgnitionTimingAngleOverall      , 00F9F6, 1, 0000, 1
, 0,        0.75,   0, '░KW'
Logged data size is 71 bytes.
FTDI library version 30118
Echo test failed, check cable is connected and ignition is on
Initialization failed, exiting ...
exiting (cause=0x1)...

Is the -f the FTDI option or am I missing something?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on April 25, 2013, 09:57:57 PM
yes. you omitted the most important part: what options you are passing to me7l


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: udcc11 on April 26, 2013, 01:29:46 AM
yes. you omitted the most important part: what options you are passing to me7l

What do I need to edit or change then? I can't seem to figure out what is missing that you see.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on April 26, 2013, 09:34:00 AM
No idea. You didn't include the actual command in your copy/paste.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: DMVDUB on April 26, 2013, 06:28:52 PM
Could someone give me a screenshot of how to setup the .txt file so it will log variables. I feel like I've tried it all, but everytime I delete the comment it just comes back to the same thing.... No variables selected.

If I had an example of what it looks like I'd be golden!

Please n thank you!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: DMVDUB on April 26, 2013, 06:54:26 PM
Nevermind I figured it out  ::) Duh.....


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: iznogoud on April 28, 2013, 06:19:18 PM
Nevermind I figured it out  ::) Duh.....

Yeah, must have been something obvious that was overlooked. When I first used it, years ago now (wow!), it worked essentially out of the box on the same A-box ECU that you have.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on May 10, 2013, 06:47:21 PM
Here are my 2.7t 551M (ME7.1) extras

Torque variables (from phila? not sure who i got it from)

https://raw.github.com/nyetwurk/ME7L/master/ecus/torque.ecu

Stuff I also log not included above:

https://raw.github.com/nyetwurk/ME7L/master/ecus/extras.ecu


Title: ME7Info Error
Post by: TCSTigersClaw on May 25, 2013, 02:11:48 PM
Hello there ! I am trying to finally inpuy ALS and LC to my Cupra but I am having trouble with ME7info tool to id all the adressess.

I got the following error  " restypes 058x ->JMP not found in 2nd stage selector <889232> .
( also attached an image )

I tried various original ME7.5 files ,but no luck the same thing.

The file.ecu is made , but lots of adresses are missing , so I have only found a few to proceed with my project.

Does anyone know what is this error and how to fix ? I cant seem to find anything .

Thank you   

EDIT: I have trouble right now uploading the .png for some reason I will upload later , the error is exactly as I quoted


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: boomerro on June 03, 2013, 03:13:49 PM
I logg with succes few days ago.
Today i try to log and result :

"Logged data size is 20 bytes.
can't locate function FT_GetLibraryVersion in dll
Initialization failed, exiting ...
exiting (cause=0x1)..."


what is going on ?

I am getting this same issue, no idea whats going on with the DLL, is something messed up with my drivers? vag-com and ecux work great though...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: boomerro on June 05, 2013, 02:29:02 PM
Figured it out. Got the rosstech dll for the vcp and put it in the bin folder for the logger. Works great.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on June 05, 2013, 02:40:51 PM
Figured it out. Got the rosstech dll for the vcp and put it in the bin folder for the logger. Works great.

thats not a good sign. that means there is a bad rosstech dll floating around your system.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: chrisp on June 06, 2013, 05:56:20 AM
Figured it out. Got the rosstech dll for the vcp and put it in the bin folder for the logger. Works great.

Same error here. After copying the vcp drivers to bin, me7l at least found the ftdi drivers. But now I get the following error:


I'm stumped with the same problem I had a year ago when my water pump went out. I am having an Echo test failed, check cable is connected and ignition is on message on com3. Any other com I get can't open serial port com1,2,4 etc.

Did anyone meanwhile figure out how to fix it?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on June 06, 2013, 09:23:25 AM
GUYS DO NOT blindly copy dlls around. You are only asking for future trouble.

You need to find the offending DLL *and remove it*


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: professor on June 16, 2013, 02:45:33 AM
Code:
Logged data size is 63 bytes.
Start connecting to ECU at 02.06.2013 13:21:29.703
try connect slow(11)
try connect slow(11)
=> FLASH (slowinit)
ecuid reports software version
Started session86, speed=56000
-> Read ECU ID's .... done
-> Checked ECU ID's
Found bootrom version 05.12/05.32 via readmem
Read pointer ... done
Store handler ... done
Verify handler ... done
Redirect pointer ... done
Test handler ... done
Opened logfile C:\ME7_logger_1.17\logs\log_20130602_132135.csv
-> Start logging (logdata size=63, 10 samples/second, 56000 baud) at 02.06.2013
13:21:35.429
Press ^C to stop logging
.Got error -8
13:21:36.743-604,5 os_sendbuf(len=3, data= 01 B7 B8)
13:21:36.746-777,8 os_rcvbyte(timeout=100) -> 01
13:21:36.748-428,8 os_rcvbyte(timeout=100) -> B7
13:21:36.750-108,9 os_rcvbyte(timeout=100) -> B8
13:21:36.903-245,6 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
13:21:36.961-374,5 os_sendbuf(len=3, data= 01 B7 B8)
13:21:36.964-819,5 os_rcvbyte(timeout=100) -> 01
13:21:36.966-472,4 os_rcvbyte(timeout=100) -> B7
13:21:36.968-209,4 os_rcvbyte(timeout=100) -> B8
13:21:37.121-391,3 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
13:21:37.179-558,1 os_sendbuf(len=3, data= 01 B7 B8)
13:21:37.182-781,7 os_rcvbyte(timeout=100) -> 01
13:21:37.184-436,1 os_rcvbyte(timeout=100) -> B7
13:21:37.186-165,1 os_rcvbyte(timeout=100) -> B8
13:21:37.339-337,0 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
13:21:37.397-448,7 os_sendbuf(len=3, data= 01 B7 B8)
13:21:37.400-796,9 os_rcvbyte(timeout=100) -> 01
13:21:37.402-446,0 os_rcvbyte(timeout=100) -> B7
13:21:37.404-167,5 os_rcvbyte(timeout=100) -> B8
13:21:37.557-367,1 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
13:21:37.615-509,2 os_sendbuf(len=3, data= 01 B7 B8)
13:21:37.618-791,2 os_rcvbyte(timeout=100) -> 01
13:21:37.620-446,5 os_rcvbyte(timeout=100) -> B7
13:21:37.622-175,3 os_rcvbyte(timeout=100) -> B8
13:21:37.775-349,6 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
13:21:37.833-474,1 os_sendbuf(len=3, data= 01 B7 B8)
13:21:37.836-783,0 os_rcvbyte(timeout=100) -> 01
13:21:37.838-435,8 os_rcvbyte(timeout=100) -> B7
13:21:37.840-198,1 os_rcvbyte(timeout=100) -> B8
13:21:37.993-378,7 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
13:21:38.051-468,8 os_sendbuf(len=3, data= 01 B7 B8)
13:21:38.055-802,0 os_rcvbyte(timeout=100) -> 01
13:21:38.057-546,5 os_rcvbyte(timeout=100) -> B7
13:21:38.059-278,7 os_rcvbyte(timeout=100) -> B8
13:21:38.212-497,5 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
13:21:38.270-675,3 os_sendbuf(len=3, data= 01 B7 B8)
13:21:38.274-760,5 os_rcvbyte(timeout=100) -> 01
13:21:38.276-420,0 os_rcvbyte(timeout=100) -> B7
13:21:38.278-154,5 os_rcvbyte(timeout=100) -> B8
13:21:38.431-564,9 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
13:21:38.489-826,4 os_sendbuf(len=3, data= 01 B7 B8)
13:21:38.493-756,5 os_rcvbyte(timeout=100) -> 01
13:21:38.495-509,8 os_rcvbyte(timeout=100) -> B7
13:21:38.497-345,7 os_rcvbyte(timeout=100) -> B8
13:21:38.650-909,8 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
13:21:38.709-089,2 os_sendbuf(len=3, data= 01 B7 B8)
13:21:38.712-745,7 os_rcvbyte(timeout=100) -> 01
13:21:38.714-407,1 os_rcvbyte(timeout=100) -> B7
13:21:38.716-305,5 os_rcvbyte(timeout=100) -> B8
13:21:38.869-463,3 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
=> Logging failed
[b]exiting (cause=0x4)[/b]...

I ve tried different baud and sample rates, communication types inside ecu file, all usb ports, different laptops, with ignition off/on engine running or not.
Sometimes it starts with  low baud rate and 5 samples/sec but it throw this error after 1-2' minutes.
This happens only so far with seat leon cupra:
Code:
HWNumber           = "0261208221"
SWNumber           = "1037367220"
PartNumber         = "1ML906032A"
SWVersion          = "0001"
EngineId           = "1.8l R4/5VT"

Any suggestions?

Thank you.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Malinovsky on June 23, 2013, 01:29:12 PM
Hey. I forgot tony posted this

http://nyet.org/cars/files/8D0907551M_0002%20RAM%20Variables.txt


is it still possible to get this .txt ?
or will I find on forum any other full translation file from vag-com to me7logger variables?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Axis on June 23, 2013, 02:07:19 PM
is it still possible to get this .txt ?
or will I find on forum any other full translation file from vag-com to me7logger variables?
http://nyet.org/cars/files/defs/8D0907551M_0002%20RAM%20Variables.txt


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on June 23, 2013, 05:33:39 PM

https://raw.github.com/nyetwurk/ME7L/master/ecus/torque.ecu
https://raw.github.com/nyetwurk/ME7L/master/ecus/extras.ecu


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Malinovsky on June 25, 2013, 06:32:39 AM
thanks :)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: kaross on July 02, 2013, 01:02:00 PM
I got problem with using this logger.
I tryed with old blue kkl cable and used even original ross-tech usb-hex cable but can't get it working.
Where could be problem?
I am using ME7logger GUI version. Because I don't know how to start logging with this version.
I know it will sound stupid but I don't know how to properly run these commands. I have tryed in many ways but mostly I got some errors or nothing is happening. Is there should be any message about for example logging speed (sample rate) when I change it?
I am writing C:\ME7\bin>me7logger 20 s
right?
But main thing right now is how to communicate with car.
(http://content3-foto.inbox.lv/albums/e/eddix/12-09-2012/me7logger.png?1372794888)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ddillenger on July 02, 2013, 01:05:48 PM
kaross:

You have a very early car, the clusters in those are notorious for preventing and terminating k-line communication. You should run a new wire to the ecu k-line from the OBD port to allow flashing and logging.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: kaross on July 02, 2013, 01:11:54 PM
o.k. That explains some things. I wasn't able to flash it also.
And how about this command line. After starting GUI version + first communication command line is back to C:\ME7\bin. How to start communication again? or how to change for example baud rate? I am complete noob in this. :(


Title: Windows 8?
Post by: Jrw0215 on July 02, 2013, 01:37:41 PM
Sorry if this has been covered in previous posts, with 19 pages I managed the first 3 skipped to page 19 and read backwards to 14 and hadn't found an answer yet!

I'm currently running windows 8 on my netbook and am really interested in getting this program to operate, I have saved the .zip file and extracted using 7-zip and when I open the application icon there is a brief black box that appears and then nothing. I am not entirely advanced when it comes to software but I can manage.

Any help is much appreciated and again if this has been covered I apologize.


Title: Re: Windows 8?
Post by: nyet on July 02, 2013, 01:48:14 PM
when I open the application icon there is a brief black box that appears and then nothing. I am not entirely advanced when it comes to software but I can manage.

It is a command line program, not a GUI based app.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Jrw0215 on July 02, 2013, 01:58:44 PM
Thank you for the response so quickly, I guess I should have picked up on that. Guess when I get home from work tonight its going to be a brush up on command prompts.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 02, 2013, 02:09:36 PM
btw cygwin bash is much better than the cosmic joke that is "cmd.exe"


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ddillenger on July 02, 2013, 02:14:19 PM
There's a GUI for the program, makes it much safer to log and drive.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aysix on July 02, 2013, 10:50:53 PM
kaross:

You have a very early car, the clusters in those are notorious for preventing and terminating k-line communication. You should run a new wire to the ecu k-line from the OBD port to allow flashing and logging.

I think this will help for the later ME7.5 passat and such, going to be trying this out.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: kaross on July 03, 2013, 01:54:29 AM
btw cygwin bash is much better than the cosmic joke that is "cmd.exe"

ohh.. it is somekind of Linux soft for Windows?

By the way, can you answer short to this?
o.k. That explains some things. I wasn't able to flash it also.
And how about this command line. After starting GUI version + first communication command line is back to C:\ME7\bin. How to start communication again? or how to change for example baud rate? I am complete noob in this. :(


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on July 10, 2013, 07:42:58 AM
Hi there,

after a long period I found now a little spare time to contribute something here.
Had planned for an update of ME7L to be ready in march, but this didn't get finalized
due to "little" problems here and there as well as massive lack of time.
Now four additional months have passed by,  but finally I could finish what I had in mind so far.
So, the first post of this thread is refreshed with the most recent update of ME7Logger V1.20.

The logging functionality itself has only small changes, there are some fixes/enhancements.
The two major changes to be mentioned are:
1. the Linux port is available now (currently compiled for i386, other systems to follow).
2. a shared library of ME7Logger is available, for those who want to implement
   their own (non-commercial) logging solutions.

I provided a basic driver implementation for WinLog (http://www.devtechnics.com/winlog.htm),
it is contained in ME7L_Winlog_driver.zip also in the first post. A short video showing it at work is attached.

This is just an example, using the shared library there are many possibilities to integrate ME7L into your applications.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on July 10, 2013, 08:00:53 AM
 :o


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ddillenger on July 10, 2013, 08:57:26 AM
:o

My thoughts exactly. Setzi's back!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Axis on July 10, 2013, 09:40:19 AM
D*mn, what a suprise.  :o  ;D   I hope we in future can see support for the later versions of me7.1.1 with ST10 cpu's (variant of c16x). I don't care about the detection routines in Me7Info but to be able to log would be very nice. Variables and bits can be found manually in ida pro without the info tool.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 10, 2013, 10:06:21 AM
Setzi: thank you!

One feature request, while I have your attention.. thing is, i dont know how to explain it.. let alone the best way to implement it.

I have a bunch of additional ecu variables I like to log that are not automatically detected and written out... so when i create a template config file from an ecu file, it requires a bit of work (concatenating various things) etc.

I have a bunch of scripts that take care of this, including one that uncomments/comments lines from the generated config file.

Have you given any thought to making a way to streamline this workflow?

my additional variables (mbox)

https://raw.github.com/nyetwurk/ME7L/master/ecus/torque.ecu
https://raw.github.com/nyetwurk/ME7L/master/ecus/extras.ecu

the scripts are here:

https://github.com/nyetwurk/ME7L/tree/master/logs
https://github.com/nyetwurk/ME7L/tree/master/ecus

Also, while I have your attention, if there is any possible way you can guide me into fixing up ME7Sum, i'd appreciate it... i have run into a few things I simply can't figure out.

http://nefariousmotorsports.com/forum/index.php?topic=3347.0
http://nefariousmotorsports.com/forum/index.php?topic=3347.msg32324#msg32324



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: jooo on July 10, 2013, 10:13:56 AM
Is there a way to get hex (or even binary) output in the log file?  That would be very handy when debugging custom code in ECU.

btw. Thank you for your incredibly useful software.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 10, 2013, 10:17:15 AM
Is there a way to get hex (or even binary) output in the log file?

What kind of binary output? You can easily write a script to monitor the output and reformat it.


Title: Re: Re: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Axis on July 10, 2013, 10:25:36 AM
What kind of binary output? You can easily write a script to monitor the output and reformat it.
I know.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: B234R on July 10, 2013, 11:14:06 AM
Massive!

Thanks a lot for all the impressive work and continued updates!
Makes me wanna buy a ME7 powered car  ::)

Although I prolly should torture my brain for the rest of my lifetime and figure something out for MED9  ;D


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: NOTORIOUS VR on July 10, 2013, 12:19:17 PM
This is amazing!  Thanks Setzi!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: trichard3000 on July 10, 2013, 12:28:24 PM
Very cool!  I can't wait to take a look!  A couple of weeks earlier and you might have saved me a bunch of work trying to clone ME7L.  :)  Are you opening the source for these?

Thanks again for all of your contributions! 


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Axis on July 10, 2013, 12:58:45 PM
Who will be first to publish a ME7 .dsh dashboard file for winlog?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: jibberjive on July 10, 2013, 01:22:44 PM
Wow, when I saw an explosion in the thread, I didn't necessarily expect this.  Awesome work Setzi!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: s4rmm on July 11, 2013, 05:29:08 AM
I provided a basic driver implementation for WinLog (http://www.devtechnics.com/winlog.htm),
it is contained in ME7L_Winlog_driver.zip also in the first post. A short video showing it at work is attached.
Thank you!

I tried to add new device to winlog (copied the dll into winlog folder), but after selecting the dll I get
"Error: This does not appear to be a valid WinLog driver file"

Tested on Win7x64 and (virtual) XP SP3
Anybody got it working?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Axis on July 11, 2013, 05:51:36 AM
Thank you!

I tried to add new device to winlog (copied the dll into winlog folder), but after selecting the dll I get
"Error: This does not appear to be a valid WinLog driver file"

Tested on Win7x64 and (virtual) XP SP3
Anybody got it working?

libME7Logger.dll also need to be in Winlog directory. I had the same problem to begin with.

Quote
Just copy ME7L_winlog.dll and libME7Logger.dll into the Winlog directory to make use of it.

Anyone who's done a nice Dashboard yet? Or perhaps Setzi62 wouln't mind sharing the .dsh which is shown in the .avi?
It is possible to have two winlog windows open and copy paste from a BIG library dashboard with ME7 suited meters.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on July 11, 2013, 01:34:17 PM
I have to take a look at this.

Setzi, how did you get around 64 variable limit in winlog and the fact that it is not refreshing the variables until you remove and re-add the driver?
I made a logger a long time ago for winlog, but it was not very nice to use because of these problems, so never released it.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on July 13, 2013, 07:47:21 PM
I have to take a look at this.

Setzi, how did you get around 64 variable limit in winlog and the fact that it is not refreshing the variables until you remove and re-add the driver?
I made a logger a long time ago for winlog, but it was not very nice to use because of these problems, so never released it.

WinLog crashes for me above 69 variables.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 13, 2013, 07:52:28 PM
God I hate proprietary software. Fucking useless.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on July 14, 2013, 03:51:08 AM
WinLog crashes for me above 69 variables.

As expected.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: lulu2003 on July 14, 2013, 04:31:49 AM
WinLog crashes for me above 69 variables.

good opportunity to consolidate your amount of varables ;)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on July 14, 2013, 05:16:06 AM
As expected.

Is this different than the 64 variable limit that you were asking about?

good opportunity to consolidate your amount of varables ;)

But there's so much to see ...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: hammersword on July 15, 2013, 04:46:36 AM
Hi,

why my laptop cannot open ME7info?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TCSTigersClaw on July 15, 2013, 08:25:44 AM
how are you trying to open it ?   ;D


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: hammersword on July 15, 2013, 10:12:36 AM
I should open it via DOS?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 15, 2013, 10:14:01 AM
you mean cmd.exe.

Yes.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: hammersword on July 15, 2013, 10:54:16 AM
I did it work and I stuck here

http://prntscr.com/1fkukr (http://prntscr.com/1fkukr)

The problem is that the readme.txt isn't easy read and I can't understand anything at all!

I need a hand on this


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 15, 2013, 11:00:14 AM
Thats not stuck. That is telling you what you should type.

And why did you take a screen shot? Why not post the actual output? You can cut and paste text directly from a cmd window.

ME7Info v1.17 (c) mki, 11/2010-03/2012
Usage: ME7Info [-c | -g | -t]  [-n] [-m <mapfile>] [-a <aliasfile>] [-o <outfile>]  <binfile>

Options:
  -c              : generate communication parameters overview on stdout
  -g              : generate measgroup variables overview on stdout
  -t              : generate logging config template in logs-directory

  -n              : sort characteristics file numerically (by address),
                    default is to sort by variable name
  -m <mapfile>    : map file to use, default is me7_std.map out of defs-directory
  -a <aliasfile>  : alias file to use, default is me7_alias.map out of defs-directory
  -o <outfile>    : output file to generate,
                    default is to create <binfile>.ecu in ecus-directory
                    or <binfile>.cfg in logs-directory when creating a logging config template (-t)

  <binfile>       : the input file, a ME7 image

Finally, did you look at this

http://s4wiki.com/wiki/Tuning#Logging_utilities

which refers to this

http://www.audizine.com/forum/showthread.php/479416-****-Complete-Guide-on-How-to-Take-and-Graph-Logs-****


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on July 15, 2013, 01:18:23 PM
I have a bunch of additional ecu variables I like to log that are not automatically detected and written out... so when i create a template config file from an ecu file, it requires a bit of work (concatenating various things) etc.

I have a bunch of scripts that take care of this, including one that uncomments/comments lines from the generated config file.

Have you given any thought to making a way to streamline this workflow?

I'm not sure I got fully what functionality you need, but probably the "my_XXX" files can be used for this task.
If you use an ecu file "8D0907551M.ecu", then also the file "my_8D0907551M.ecu" is read by the logger if it exists.
You could store your manually added variables in this file. Same thing for the logger config, a file "my_8D0907551M_template.cfg"
will be read by the logger if it exists.

For the checksums topic, I have to read and look up some things at first.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on July 15, 2013, 01:23:15 PM
Who will be first to publish a ME7 .dsh dashboard file for winlog?

Here is the dashboard I used for the video and the logger config file if you want to use it.
The usefulness of the logged things is debatable  ;), just a collection of gauges and numbers
that move/change while you drive...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on July 15, 2013, 01:30:20 PM
I have to take a look at this.

Setzi, how did you get around 64 variable limit in winlog and the fact that it is not refreshing the variables until you remove and re-add the driver?
I made a logger a long time ago for winlog, but it was not very nice to use because of these problems, so never released it.

I did NOT get around the 64 variable limit. The driver is just a basic example, I must even have forgotten to protect against that limit in Winlog.
But if you are logging variables for graphical display, I wonder if anybody can watch 64 things simultaneously.

The Winlog driver was just the best example to show how ME7L could be integrated into other programs using the shared library.
There will be lots of possibilities to integrate ME7L into your own applications, e.g. remote control of logging and streaming
of log data over network, merging log data with results from other sources, .... I'm looking forward to see what will show up.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 15, 2013, 03:03:49 PM
If you use an ecu file "8D0907551M.ecu", then also the file "my_8D0907551M.ecu" is read by the logger if it exists.

Oh wow! I think that solves my workflow issue. Thanks, as usual, setzi. You're my hero.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Axis on July 15, 2013, 04:54:56 PM
But I think it is possible to patch the image so this check is no
longer present and then it should be possible to connect using "double slowinit" even while the engine is running.
I would be happy to look at the code if  I could get some hints of what to look for in IDA pro.
Somehow the need to connect without engine running is even more annoying when using Winlog.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on July 16, 2013, 02:07:47 AM
I did NOT get around the 64 variable limit. The driver is just a basic example, I must even have forgotten to protect against that limit in Winlog.
But if you are logging variables for graphical display, I wonder if anybody can watch 64 things simultaneously.

WinLog has it's own logging - you can make a datalog, and then you can review this datalog with WinLogView. That's why you might want to log everything.
Quote
The Winlog driver was just the best example to show how ME7L could be integrated into other programs using the shared library.
There will be lots of possibilities to integrate ME7L into your own applications, e.g. remote control of logging and streaming
of log data over network, merging log data with results from other sources, .... I'm looking forward to see what will show up.

I'll rewrite my driver to use the library, and will work with the WinLog author further to lift some limits.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on July 16, 2013, 08:21:18 AM
I would be happy to look at the code if  I could get some hints of what to look for in IDA pro.
Somehow the need to connect without engine running is even more annoying when using Winlog.

To have double slowinit work while engine is running, I had to patch three locations.
In the image 8D0907551G, 0001, 1037354123, 0261206776 these locations were
found at following fileoffsets:
02B8BC:   3D04 -> CC00    // Replace JMPR by NOP
067026:   3D08 -> CC00    // Replace JMPR by NOP
067EF8:   3D03 -> CC00    // Replace JMPR by NOP

At all three locations it is checked if nmot_w is zero:
82'B8B8: F2F47AF8       MOV     R4, [nmot_w]
82'B8BC: 3D04           JMPR    cc_NZ/NE, L_82B8C6 (82'B8C6)        ; PATCH: NOP

86'7022: F2F47AF8       MOV     R4, [nmot_w]
86'7026: 3D08           JMPR    cc_NZ/NE, L_867038 (86'7038)        ; PATCH: NOP

86'7EF4: F2F47AF8       MOV     R4, [nmot_w]
86'7EF8: 3D03           JMPR    cc_NZ/NE, L_867F00 (86'7F00)        ; PATCH: NOP

If you disassemble the 551G image, you can hopefully determine some code patterns
around the mentioned locations that you can then find also in your image.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: setzi62 on July 16, 2013, 08:26:59 AM
I'll rewrite my driver to use the library, and will work with the WinLog author further to lift some limits.

That's great, I'm curious to hear what will be the outcome of your work then.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Axis on July 16, 2013, 12:07:02 PM
If you disassemble the 551G image, you can hopefully determine some code patterns
around the mentioned locations that you can then find also in your image.
You gave all I needed, almost too easy.  :)
Thank you VERY much!

I'll help those who work with 551M.

Code:
0x2B8BC   3D04 -> CC00    // Replace JMPR by NOP
0x64422   3D08 -> CC00    // Replace JMPR by NOP
0x652C8   3D03 -> CC00    // Replace JMPR by NOP

Not double checked or tested in car, but everything should be ok.

edit:
This 3 position patch worked very well, really nice. Thank you setzi62!  I've not tested the 551M but the same patch in another bin.
From what I can gather I cannot see any problem making this patch permanent.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on July 16, 2013, 07:07:46 PM
You gave all I needed, almost too easy.  :)
Thank you VERY much!

I'll help those who work with 551M.

Code:
0x2B8BC   3D04 -> CC00    // Replace JMPR by NOP
0x64422   3D08 -> CC00    // Replace JMPR by NOP
0x652C8   3D03 -> CC00    // Replace JMPR by NOP

Not double checked or tested in car, but everything should be ok.

edit:
This 3 position patch worked very well, really nice. Thank you setzi62!  I've not tested the 551M but the same patch in another bin.
From what I can gather I cannot see any problem making this patch permanent.

This is not an issue on the S4 M box.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Axis on July 16, 2013, 08:32:38 PM
This is not an issue on the S4 M box.
I thought it was a cluster issue and since mbox binary is widely spread I assumed some would have connection trouble without double-slow.
Ohh well, good thing it only took 5min to find 'em.  8)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on July 16, 2013, 08:39:26 PM
I thought it was a cluster issue and since mbox binary is widely spread I assumed some would have connection trouble without double-slow.
Ohh well, good thing it only took 5min to find 'em.  8)

You're right in that aspect. I didn't think of it from that angle, so I guess it could be useful to some cross-flashing.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on July 21, 2013, 10:55:06 AM
The  -p switch for comport selection doesn't work for me.

I get "unable to open port error" when trying to use any port other than the port 2 default.

I have no problem keeping my cable on port 2, but I thought that I would share. This particular laptop has never run any previous version of ME7L, so I can't confirm that the issue is with the update and not something else.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 21, 2013, 09:27:13 PM
com port is too tightly bound with stupid random device driver settings... i prefer using the native ftdi interface (-f)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 21, 2013, 10:02:41 PM
If you use an ecu file "8D0907551M.ecu", then also the file "my_8D0907551M.ecu" is read by the logger if it exists.

However, ME7Info doesn't read the my_XXX.ecu automatically? And it will not create a my_XXX-template.cfg automatically?

Quote
You could store your manually added variables in this file. Same thing for the logger config, a file "my_8D0907551M_template.cfg"
will be read by the logger if it exists.

You mean if you specifiy "MELogger logconfig.cfg" it will automatically also read my_logconfig.cfg?

I assume the my_XXX.config doesn't need all the header stuff, just a plain list of additional variables?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: NOTORIOUS VR on July 22, 2013, 01:46:24 PM
com port is too tightly bound with stupid random device driver settings... i prefer using the native ftdi interface (-f)

just an FYI... Strangely enough I seem to have less issues with connection stability using the COM port instead of direct via FTDI.

Also another question for anyone that knows.

Sometimes the logger window shows the logging progress a dots, sometimes it's as a small o and sometimes it's a mix of small o and big O.

eg:

Code:
|........................................|

or

|ooooooooooooooooooooooooo|

or

|ooooOoooooooOOoooooooooO|

What's the difference?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on July 22, 2013, 01:54:05 PM
I forget the details exactly, but it's in the readme.

IME, you want to adjust the number of variables logged or samples per second to have all dots. The data gets wacky when you get o's. IIRC it progresses from small o's to big O's and finally to exclamation points depending on severity.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: NOTORIOUS VR on July 23, 2013, 07:57:49 AM
ah alright, good to know thanks!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: grey on August 04, 2013, 03:17:09 AM
I'm looking a solution for Got error -8
4B0 906 018 DH

Any idea?



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: professor on August 04, 2013, 05:33:08 AM
I'm looking a solution for Got error -8
4B0 906 018 DH

Any idea?


Test all baud rates inside .ecu.
On some cars works as is, on others works on 19200 or even 125000 (same cars).
For easier start stick on 5-10 samples/sec.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: grey on August 04, 2013, 12:27:17 PM
Test all baud rates inside .ecu.
On some cars works as is, on others works on 19200 or even 125000 (same cars).
For easier start stick on 5-10 samples/sec.


All tested as 10400, 14400, 19200, 38400, 56000, 76800, 125000
but i have got error -8
Where I'm doing wrong?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: professor on August 04, 2013, 01:33:39 PM
All tested as 10400, 14400, 19200, 38400, 56000, 76800, 125000
but i have got error -8
Where I'm doing wrong?
Using windows 7, give to me7logger.exe admin rights and try again.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: grey on August 08, 2013, 04:53:23 AM
Using windows 7, give to me7logger.exe admin rights and try again.

Whatever I did,it not working  >:(
Any idea?

-> Reading log config file C:\ME7Logger\logs\log_4cyl_basic.cfg .... done
-> Reading ecu characteristics file C:\ME7Logger\ecus\4B0906018DH.ecu .... done
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x11
Communicate  = HM0
LogSpeed     = 19200

[Identification]
HWNumber           = "0261207928"
SWNumber           = "1037366497"
PartNumber         = "4B0906018DH"
SWVersion          = "0004"
EngineId           = "1.8L R4/5VT"

Logged variables are:
#no.: name                , alias                           , addr  ,sz, bitm, S
, I,  A         ,   B, unit
#-------------------------------------------------------------------------------
-----------------------------
#001: nmot_w              , EngineSpeed                     , 00F89E, 2, 0000, 0
, 0,        0.25,   0, 'rpm'
#002: gangi               , SelectedGear                    , 3809B6, 1, 0000, 0
, 0,           1,   0, 'gear'
#003: vfil_w              , VehicleSpeed                    , 381D5A, 2, 0000, 0
, 0,   0.0078125,   0, 'km/h'
#004: wub                 , BatteryVoltage                  , 3808BC, 1, 0000, 0
, 0,      0.0704,   0, 'V'
#005: tmotlin             , CoolantTemperature              , 3848B2, 1, 0000, 0
, 0,        0.75,  48, '¦C'
#006: tanslin             , IntakeAirTemperature            , 3848A8, 1, 0000, 0
, 0,        0.75,  48, '¦C'
#007: wped_w              , AccelPedalPosition              , 381D94, 2, 0000, 0
, 0,   0.0015259,   0, '% PED'
#008: wdkba               , ThrottlePlateAngle              , 3809D4, 1, 0000, 0
, 0,    0.392157,   0, '% DK'
#009: ti_b1               , FuelInjectorOnTime              , 38214A, 2, 0000, 0
, 0,       0.004,   0, 'ms'
#010: te_w                , EffInjectionTime                , 382148, 2, 0000, 0
, 0,       0.004,   0, 'ms'
#011: zwist               , IgnitionTimingAngle             , 00FA34, 1, 0000, 1
, 0,        0.75,   0, '¦KW'
#012: dwkrz_0             , IgnitionRetardCyl1              , 380AA6, 1, 0000, 1
, 0,        0.75,   0, '¦KW'
#013: dwkrz_1             , IgnitionRetardCyl4              , 380AA7, 1, 0000, 1
, 0,        0.75,   0, '¦KW'
#014: dwkrz_2             , IgnitionRetardCyl2              , 380AA8, 1, 0000, 1
, 0,        0.75,   0, '¦KW'
#015: dwkrz_3             , IgnitionRetardCyl3              , 380AA9, 1, 0000, 1
, 0,        0.75,   0, '¦KW'
#016: wkrm                , AvgIgnitionRetardKnockControl   , 00F9DC, 1, 0000, 0
, 0,       -0.75,   0, '¦KW'
#017: rkrn_w_0            , KnockVoltageCyl1                , 384C30, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#018: rkrn_w_1            , KnockVoltageCyl4                , 384C32, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#019: rkrn_w_2            , KnockVoltageCyl2                , 384C34, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#020: rkrn_w_3            , KnockVoltageCyl3                , 384C36, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#021: fzabg_w_0           , CountMisfireCyl1                , 38189E, 2, 0000, 0
, 0,           1,   0, '#'
#022: fzabg_w_1           , CountMisfireCyl4                , 3818A0, 2, 0000, 0
, 0,           1,   0, '#'
#023: fzabg_w_2           , CountMisfireCyl2                , 3818A2, 2, 0000, 0
, 0,           1,   0, '#'
#024: fzabg_w_3           , CountMisfireCyl3                , 3818A4, 2, 0000, 0
, 0,           1,   0, '#'
#025: fzabgs_w            , CountMisfireTotal               , 38189C, 2, 0000, 0
, 0,           1,   0, '#'
#026: fr_w                , LambdaControl                   , 382A2E, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#027: fra_w               , AdaptationPartial               , 38218C, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#028: frm_w               , LambdaControlAvg                , 382A2A, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#029: lamfa_w             , TargetAFRDriverRequest          , 384BA0, 2, 0000, 0
, 0, 0.000244141,   0, '-'
#030: lamsbg_w            , AirFuelRatioDesired             , 38217C, 2, 0000, 0
, 0, 0.000244141,   0, '-'
#031: lamsoni_w           , AirFuelRatioCurrent             , 381BBC, 2, 0000, 0
, 0, 0.000244141,   0, '-'
#032: pu_w                , BaroPressure                    , 384B2C, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#033: fho_w               , AltitudeCorrectionFactor        , 384B24, 2, 0000, 0
, 0, 6.10352e-005,   0, '-'
#034: ldtvm               , WastegateDutyCycle              , 380AE8, 1, 0000, 0
, 0,    0.390625,   0, '%'
#035: mshfm_w             , MassAirFlow                     , 00F9A8, 2, 0000, 0
, 0,   0.0277778,   0, 'g/s'
#036: plsol_w             , BoostPressureDesired            , 382086, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#037: pvdks_w             , BoostPressureActual             , 382014, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#038: rl_w                , EngineLoad                      , 00F9BC, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#039: rlmax_w             , EngineLoadCorrected             , 384B42, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#040: rlmx_w              , EngineLoadSpecified             , 384C68, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#041: rlsol_w             , EngineLoadRequested             , 3820DE, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#042: tabgm_w             , EGTModelBeforeCat               , 384A8A, 2, 0000, 0
, 0,   0.0195312,  50, '¦C'
Logged data size is 72 bytes.
Really logged are 40 entries with 72 bytes.
Start connecting to ECU at 08.08.2013 04:39:03.500
try connect slow(11)
try connect slow(11)
=> FLASH (slowinit)
ecuid reports software version
Started session86, speed=19200
-> Read ECU ID's .... done
-> Checked ECU ID's
Found bootrom version 06.02/06.05 via readmem
Read pointer ... done
Store handler ... done
Verify handler ... done
Redirect pointer ... done
Test handler ... done
Opened logfile C:\ME7Logger\logs\log_4cyl_basic_20130808_043910.csv
-> Start logging (logdata size=72, 20 samples/second, 19200 baud) at 08.08.2013
04:39:10.410
Press ^C to stop logging
Got error -8
04:39:11.575-050,6 os_sendbuf(len=3, data= 01 B7 B8)
04:39:11.616-541,6 os_rcvbyte(timeout=100) -> 01
04:39:11.642-394,1 os_rcvbyte(timeout=100) -> B7
04:39:11.667-232,4 os_rcvbyte(timeout=100) -> B8
04:39:11.843-285,8 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
04:39:11.947-729,3 os_sendbuf(len=3, data= 01 B7 B8)
04:39:11.984-450,7 os_rcvbyte(timeout=100) -> 01
04:39:12.008-861,9 os_rcvbyte(timeout=100) -> B7
04:39:12.033-732,6 os_rcvbyte(timeout=100) -> B8
04:39:12.209-823,5 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
04:39:12.314-135,6 os_sendbuf(len=3, data= 01 B7 B8)
04:39:12.352-483,2 os_rcvbyte(timeout=100) -> 01
04:39:12.377-274,6 os_rcvbyte(timeout=100) -> B7
04:39:12.401-231,6 os_rcvbyte(timeout=100) -> B8
04:39:12.577-789,8 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
04:39:12.683-415,2 os_sendbuf(len=3, data= 01 B7 B8)
04:39:12.720-452,6 os_rcvbyte(timeout=100) -> 01
04:39:12.745-032,0 os_rcvbyte(timeout=100) -> B7
04:39:12.769-913,4 os_rcvbyte(timeout=100) -> B8
04:39:12.945-825,1 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
04:39:13.048-443,2 os_sendbuf(len=3, data= 01 B7 B8)
04:39:13.088-480,7 os_rcvbyte(timeout=100) -> 01
04:39:13.113-126,2 os_rcvbyte(timeout=100) -> B7
04:39:13.137-940,9 os_rcvbyte(timeout=100) -> B8
04:39:13.313-912,1 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
04:39:13.418-156,6 os_sendbuf(len=3, data= 01 B7 B8)
04:39:13.456-462,1 os_rcvbyte(timeout=100) -> 01
04:39:13.481-126,4 os_rcvbyte(timeout=100) -> B7
04:39:13.505-990,7 os_rcvbyte(timeout=100) -> B8
04:39:13.682-024,5 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
04:39:13.786-522,7 os_sendbuf(len=3, data= 01 B7 B8)
04:39:13.824-467,8 os_rcvbyte(timeout=100) -> 01
04:39:13.848-929,5 os_rcvbyte(timeout=100) -> B7
04:39:13.873-835,5 os_rcvbyte(timeout=100) -> B8
04:39:14.049-863,7 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
04:39:14.154-151,3 os_sendbuf(len=3, data= 01 B7 B8)
04:39:14.192-465,9 os_rcvbyte(timeout=100) -> 01
04:39:14.217-185,0 os_rcvbyte(timeout=100) -> B7
04:39:14.241-978,1 os_rcvbyte(timeout=100) -> B8
04:39:14.418-235,1 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
04:39:14.523-630,7 os_sendbuf(len=3, data= 01 B7 B8)
04:39:14.560-450,7 os_rcvbyte(timeout=100) -> 01
04:39:14.585-022,3 os_rcvbyte(timeout=100) -> B7
04:39:14.609-838,5 os_rcvbyte(timeout=100) -> B8
04:39:14.787-182,0 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
04:39:14.891-779,1 os_sendbuf(len=3, data= 01 B7 B8)
04:39:14.928-450,8 os_rcvbyte(timeout=100) -> 01
04:39:14.953-108,1 os_rcvbyte(timeout=100) -> B7
04:39:14.977-934,5 os_rcvbyte(timeout=100) -> B8
04:39:15.153-979,2 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
=> Logging failed
exiting (cause=0x4)...

C:\ME7Logger>


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aysix on August 16, 2013, 10:10:34 AM

Was this resolved? Is there a solution? Same issue over here. Trying this out on an 04 Passat and upon trying to create a template file with the stock, or modded bin I get this. This only happens with this specific bin, and i'm not sure where to start troubleshooting.

(http://img405.imageshack.us/img405/6916/loledi.png)

Any insight would be great.

Thanks!



Updated ME7L and this now works for anyone wondering.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: skinnytirez on August 18, 2013, 10:54:34 PM
I had ECUx decide to quit working so i figured now was as good a time as any to get ME7 logger going. Thanks to all that played a  part in it's creation!
anyway- Running into an issue when i try and start logging: Has anyone encountered this before?

-> Reading log config file C:\Users\Dell Campus Rep\Desktop\ME7Logger\logs\(Audi
 S4 (Alex J - Rev 6) - 360857)_template.cfg .... done
-> Reading ecu characteristics file C:\Users\Dell Campus Rep\Desktop\ME7Logger\e
cus\(Audi S4 (Alex J - Rev 6) - 360857).ecu .... done
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x11
Communicate  = HM0
LogSpeed     = 56000

[Identification]
HWNumber           = "0261207143"
SWNumber           = "1037360857"
PartNumber         = "JFonz Tuning"
SWVersion          = "0002"
EngineId           = "2.7tt /5VT"

Logged variables are:
#no.: name                , alias                           , addr  ,sz, bitm, S
, I,  A         ,   B, unit
#-------------------------------------------------------------------------------
-----------------------------
#001: dwkrz_0             , IgnitionRetardCyl1              , 380C2B, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#002: dwkrz_1             , IgnitionRetardCyl5              , 380C2C, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#003: dwkrz_2             , IgnitionRetardCyl3              , 380C2D, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#004: dwkrz_3             , IgnitionRetardCyl2              , 380C2E, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#005: dwkrz_4             , IgnitionRetardCyl6              , 380C2F, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#006: dwkrz_5             , IgnitionRetardCyl4              , 380C30, 1, 0000, 1
, 0,        0.75,   0, '░KW'
#007: fr_w                , LambdaControl                   , 382E3A, 2, 0000, 0
, 0, 3.05176e-005,   0, '-'
#008: gangi               , SelectedGear                    , 380AF8, 1, 0000, 0
, 0,           1,   0, 'gear'
#009: lamsbg_w            , AirFuelRatioDesired             , 3823C4, 2, 0000, 0
, 0, 0.000244141,   0, '-'
#010: ldtvm               , WastegateDutyCycle              , 380C76, 1, 0000, 0
, 0,    0.390625,   0, '%'
#011: mshfm_w             , MassAirFlow                     , 00F97C, 2, 0000, 0
, 0,   0.0277778,   0, 'g/s'
#012: nmot_w              , EngineSpeed                     , 00F87A, 2, 0000, 0
, 0,        0.25,   0, 'rpm'
#013: plsol_w             , BoostPressureDesired            , 382284, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#014: pus_w               , BaroPressure                    , 382206, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#015: pvdkds_w            , BoostPressureActual             , 382216, 2, 0000, 0
, 0,   0.0390625,   0, 'mbar'
#016: rkrn_w_0            , KnockVoltageCyl1                , 382646, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#017: rkrn_w_1            , KnockVoltageCyl5                , 382648, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#018: rkrn_w_2            , KnockVoltageCyl3                , 38264A, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#019: rkrn_w_3            , KnockVoltageCyl2                , 38264C, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#020: rkrn_w_4            , KnockVoltageCyl6                , 38264E, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#021: rkrn_w_5            , KnockVoltageCyl4                , 382650, 2, 0000, 0
, 0,   0.0195313,   0, 'V'
#022: rl_w                , EngineLoad                      , 00F990, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#023: rlmax_w             , EngineLoadCorrected             , 38277E, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#024: rlmx_w              , EngineLoadSpecified             , 382782, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#025: rlsol_w             , EngineLoadRequested             , 3822D8, 2, 0000, 0
, 0,   0.0234375,   0, '%'
#026: tabgm               , EGTModelBeforeCat               , 380A81, 1, 0000, 0
, 0,           5,  50, '░C'
#027: tabgm2              , EGTModelBeforeCatBank2          , 380A82, 1, 0000, 0
, 0,           5,  50, '░C'
#028: tans                , IntakeAirTemperature            , 380BBF, 1, 0000, 0
, 0,        0.75,  48, '░C'
#029: tats2_w             , EGTSensorBank2                  , 3824EE, 2, 0000, 0
, 0,   0.0195312,  50, '░C'
#030: tats_w              , EGTSensor                       , 3824F0, 2, 0000, 0
, 0,   0.0195312,  50, '░C'
#031: ti_b1               , FuelInjectorOnTime              , 38238E, 2, 0000, 0
, 0,  0.00266667,   0, 'ms'
#032: usvk                , O2SVoltageSensor1               , 380AA6, 1, 0000, 0
, 0,  0.00521569, 0.2, 'V'
#033: usvk2               , O2SVoltageSensor1Bank2          , 380AA7, 1, 0000, 0
, 0,  0.00521569, 0.2, 'V'
#034: vfil_w              , VehicleSpeed                    , 380E40, 2, 0000, 0
, 0,   0.0078125,   0, 'km/h'
#035: wdkba               , ThrottlePlateAngle              , 380B13, 1, 0000, 0
, 0,    0.392157,   0, '% DK'
#036: wped_w              , AccelPedalPosition              , 381FA4, 2, 0000, 0
, 0,   0.0015259,   0, '% PED'
#037: zwopt               ,                                 , 380CB6, 1, 0000, 1
, 0,        0.75,   0, '░KW'
Logged data size is 59 bytes.
Really logged are 32 entries with 59 bytes.
can't locate function FT_GetLibraryVersion in dll
Initialization failed, exiting ...
exiting (cause=0x1)...


C:\Users\Dell Campus Rep\Desktop\ME7Logger>

Any insight would be great! P.S. im using an authentic ross tech Vag-Com cable for this...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aysix on August 21, 2013, 02:43:38 PM
It looks like you are missing a file, see if you are missing anything from the .rar


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ddillenger on August 21, 2013, 03:02:43 PM
Turn off your antivirus before unzipping.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: dantt on August 22, 2013, 01:55:15 AM
who can help me to edit costant for my TT mk1?

what is coefficent of drag or driveline loss?
what is maf offset??

thanks


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: malec on August 31, 2013, 12:22:18 PM
Hi everybody!

First of all big thanks to this forum! I'm new and try to learn as many as I can from all this good information I can find on this forum.

I have an Audi S3 from 2001 engine AMK. I found out about this logger and really wanted to use it but on my car I could not connect if the ignition was on. I read all this posts and found out that a solution is to route the K line from ECU directly to OBD port. I didn't want to cut the wires and add a switch so I started to check the wires diagram in ElsaWin.  There I found out that the diagnostic wire (K-wire) from ECU is routed through dash panel and this is connected by the immobilizer, I always could connect with VagCom but not with ME7Logger, so while I was in my garage it was very silent and I could hear a relay in the dash that was clicking when I was connecting with VagCom.
So I found out in ElsaWin that K wire from ECU is in fact on the 32 pins green connector on pin number 5 and K line that is connected to the OBD port is pin 28, so I connected pin 28 with pin 5 and here it goes, ME7Logger works perfect now. I guess VagCom sends a special command to dash panel in order to connect the ECU K line to the diagnostic K line which is actually connected with all the other modules in the car. I think this was somehow a protection so that you can't access the ECU without a key with valid immobilizer.

Hope this post helps other people.  Please let me know if you need me to check the wiring diagrams for other cars.

Best regards!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tweetss4estate on September 06, 2013, 10:27:39 AM
I'm getting a -19 code. its logging, then when I hit Cntrl C it gives me an error 19 code. Any ideas?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: professor on September 06, 2013, 11:52:28 AM
I'm getting a -19 code. its logging, then when I hit Cntrl C it gives me an error 19 code. Any ideas?
Log is saved, isn't?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: grey on September 06, 2013, 12:06:06 PM
Using windows 7, give to me7logger.exe admin rights and try again.

Thank you for everything  ;)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: cactusgreens4 on September 17, 2013, 08:05:35 PM
Little help here please... I downloaded and installed winlog. I coppied the ME7L_winlog.dll and libME7Logger.dll into the Winlog directory. i opened up winlog and went to device configuration and set everything up just like in the video... 56000 baudrate 10 samplerate absolute timestamps. i even used the cfg file and dsh file provided by stetzi however when i try to load winlog it pops up and says "error initializing device: ME7logger winlog driver. Would you like to retry" also i noticed when i go to the device configuration like setzi does in the video i do not have a little plus next to the "me7logger winlog driver" that drops down all the variables being logged... can someone maybe help me figure out what i am doing wrong here?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: lulu2003 on September 27, 2013, 01:23:34 AM
got strange behavior of me7logger when trying to log C-Box S4.
Log in with settings like rs4 works but then even lowest baud settings only work for some seconds and then abort...

any idea / experience?



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Ptyrell on October 06, 2013, 11:33:47 PM
I cant even connect my D box S4 at all. My TT setup works 100% on same laptop


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Ptyrell on October 07, 2013, 09:46:53 PM
If I read the cluster eeprom with VAG EEPROM programmer , then run ME7logger it runs fine. Its the stupid cluster immobilizer, unfortunately I removed all 3 fuses to do with the cluster and it did nothing. Unplugged ABS and removed all ABS fuses also


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: MIL_on on November 03, 2013, 04:06:09 PM
Hey Guys,
at first: Setzi you are great! What a fine piece of software!

Thats what i can say after a few hours hazzling around with the car and the problem, that i shared with a crowd of you:
i am using it on a 2004 euro 1.8t ME7.5 (225hp) and with nearly every setting it was logging for a few seconds and then got a timeout. i also think that this is a problem with another participant on the k-line.  Screenshot of the error in attachment!


So here comes my solution:

Notice: This works with my blue KKL Cable (so old, it doesnt even have the FT232R Chip, but FT232B orso)

change the connection settings in your ecu file to:
Code:
[Communication]
Connect      = SLOW-0x11    ; Possible values: SLOW-0x11, FAST-0x10
Communicate  = HM2-0x10          ; Possible values: HM0, HM2-0x10
LogSpeed     = 125000        ; Possible values: 10400, 14400, 19200, 38400, 56000, 57600, 125000

this is how it works fine for me. I even can connect to the ECU during a driving cycle/ with running engine!
tested it today up to 50 Hz sampling with a few variables :)

i think the most important setting is the 125k baud, so that the whole bandwidth of the k-line is used and no other participant can interrupt.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on November 03, 2013, 04:09:12 PM
i think the most important setting is the 125k baud, so that the whole bandwidth of the k-line is used and no other participant can interrupt.

Interesting theory! I like it.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: MIL_on on November 04, 2013, 03:47:19 PM
some more info to me 7.5 logging based on todays experience  :)
i logged 40-50 samples. lower sample rates tend to create early timeouts, same for baudrates less than 125k !
i started with 116 variables to check the capability of the whole system and did a few pulls in several gears.....better said i tried to...it seems that it was all a bit too much for the ecu, so it decided to do a reboot@ 5000-6000 rpm  ;D the only way to solve that problem was to reduce the number of labels to log. 67 still produced timeouts@high rpm in low gears.
i ended with 31 labels to log. i think round about 40-45 should be possible, but i didnt want to stress the engine too heavy, because those re-boots also mean that it controls exactly nothing for 0.5 seconds orso and its a heavy hit in the car and the pants :D


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: titi65 on December 08, 2013, 05:59:08 AM
Tried this soft on my ME7.4.6 on Peugeot V6, not working.
Error at connection (reason=4) . . .

Cheer ;)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Aurélien on December 09, 2013, 02:11:56 AM
It will not work on peugeot.

1st security login is not the same.
2nd I guess setzi is not using KWP2000 but something specific to VAG ?
3rd does the ram analysing works with ME7.4.6 with ME7 info ?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: dantt on December 15, 2013, 02:02:45 AM
hi setzi62,
is me7logger hard to comple for old windows mobile??
i'd like to log with my ppc. can you help me?
thank you!

Pushing a little bit forward on the logging front ...
Here is my ME7Logger package now available for everybody,
has been tested successfully on different cars.

It consists of two tools: one to generate ecu characteristics files
(similar to properties) out of ecu images, second to log data.
No GUI for klicky guys, no graphics, just console programs.

/sales_mode=on  ;)
Will outperform commercially available tools on speed & flexibility:
 - Up to 50 samples per second possible.
 - Up to 127 independent variables can be logged at same time.
 - Open for expansions: whatever you want to log, you can define it.
 - No fiddling with licenses/hacked programs needed.
/sales_mode=off

- It's free for hobby use,
- It's NOT for noobs. Not a connect-and-log tool,
  before logging you should have your ecu image available.

Last but not least: buy a commercial program if you want
to make someone liable for damages/not working logging tools  :)

Update 12.08.2011, some fixes/changes done:
- Experimental FTDI native driver support added, option -f
- Logger start time synchronization added, option -t
- Logger absolute timestamp added, option -a
- Allow TAB's also in trace config files
- Variables zwbasar_<xx> for all available cylinders
- Variables wkraa_<xx> limited to available cylinders
- Minor changes, some variables added

Update 09.09.2011, some of the requested changes/fixes done:
- Single sample option added (result is output just to the window)
- More variables determined for images with code variant (missing tans(IAT) for one image)
- zwbasar_<xx> now really available for all available cylinders
- Some more variables added
- Some alias names added, some changed


Update 02.04.2012 to version 1.17:
(Updated 04.04.2012 the ME7Info in the .zip, fixed path error)
Changes in ME7Logger:
- Reworked general timing calculations, timestamps, sync to full second
- Fixed local time in absolute timestamps (option -a)
- Supress logfile writing when output goes to stdout (option -R)
  useful if output is piped to external evaluation tool/filter
- Added option -m: Timestamp format milliseconds
- Added option -h: supress printing header information in logfiles
- Added option -b: set logging baudrate for communication,
                   override baudrate from ecu file
- connection method "double slowinit" added (helps with "instrument cluster" problem)
  To use double slowinit set in the [Communication] section of the .ecu file:
    Connect      = SLOW-0x00
    DoubleDelay  = 12           ; Possible values 1 .. 100 (delay in 100ms)
  This only allows to connect while engine not yet started.

Changes in ME7Info:
- Reverted back to zwbasar_0 .. zwbasar_3
  (Array size NOT dependent on number of cylinders)
- Some variables added:
 + zwoutar_0 .. zwoutar_3
 + zwsol
 + redist / evz_austot
 + lamfaws_w / lamfawkr_w / lamfaw_w / lamfwl_w / lamrlmn_w
 + perffilt_w / perfmax_w   => This is CPU-Load
    It helps in finding out the max. logging capabilities of your ECU.
    Around 90% CPU-Load might be a limit for the ECU.


Update 10.07.2013 to version 1.20:
Changes in ME7Logger v1.20:
- Read additional ecu characteristics file "my_<ecufile>" if it exists in same directory as <ecufile>.
  -> my_<ecufile> should be used to keep manually added definitions.
- Read additional log config file my_<ecu>_template.cfg from same directory as log config file.
  - my_<ecu>_template.cfg can be used to keep log entries for manually added definitions
- Optimization of logged data, e.g.:
    - logging multiple bitvariables which use the same byte will read only one byte from ecu.
    - logging two byte variables from neighbouring memory addresses will read only one merged
      word location from ecu.
    The limits are now:
      - up to 254 bytes,
      - up to 127 different memory locations (1 or 2 bytes),
      - up to 254 variables.

- Linux port added
   -> see "ME7Logger_Linux_DIST_10072013.tgz"
   Serial interfaces work using device /dev/ttyS*, as well as FTDI cables in serial mode
   using the kernel module ftdi_sio and device /dev/ttyUSB0.
   FTDI native mode is supported using libftdi1 and libusb1, both are already included
   in many Linux distributions.
   libftdi1: http://www.intra2net.com/en/developer/libftdi
   libusb1:  http://www.libusb.org/wiki/libusb-1.0

- Shared library (DLL) added (.so/.dll) for those who want to implement own logging solutions
   -> see directory "lib" in the ME7L .zip/.tgz files for description and example program.
   An example driver for WinLog (http://www.devtechnics.com/winlog.htm) using the ME7L shared library
   is available as well in ME7L_Winlog_driver.zip. Just copy ME7L_winlog.dll and libME7Logger.dll into
   the Winlog directory to make use of it.

Changes in ME7Info v1.20:
- Linux port added
- Internal cleanup work




Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: titi65 on January 16, 2014, 05:20:46 AM
It will not work on peugeot.

1st security login is not the same.
2nd I guess setzi is not using KWP2000 but something specific to VAG ?
3rd does the ram analysing works with ME7.4.6 with ME7 info ?
Thanks for the reply !

1) sure,but don't know.
2) I don't know . . .PSA seem using KWP2000 . . .
3) Don't know, but, if it's the only problem i have, I'll try to figure it out .


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: automan001 on February 11, 2014, 02:12:42 AM
ME7Logger is the greatest! 8)
Is there possibility to define variables without a factor and log them as raw values in hex or binary format (in other words just dump the memory)? For example i would like to define a variable bunch_of_bits_w and see its values in log like FFFEh or better 11111111111111111110b. I thought there should be some system unit (hex, bin) which defines this output format.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: terminator on February 11, 2014, 06:23:50 AM
I'm trying with blue cable, but there is no echo from FTDI or the cable.  :( And it doesnt matter its connected to the car or not.
I have also tried ELM, Vag-com and even open port, always the same thing. FTDI driver is installed, OS is Windows 7 x64, ECU is ME7.1.1
The same thing with nefmoto logger...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: phila_dot on February 11, 2014, 07:47:21 AM
ME7Logger is the greatest! 8)
Is there possibility to define variables without a factor and log them as raw values in hex or binary format (in other words just dump the memory)? For example i would like to define a variable bunch_of_bits_w and see its values in log like FFFEh or better 11111111111111111110b. I thought there should be some system unit (hex, bin) which defines this output format.

No, log with factor of 1, then convert from decimal to hex or binary


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: terminator on February 13, 2014, 04:08:08 AM
Solved. The problem was chinese KKL cable.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: carsey on April 26, 2014, 12:06:55 PM
Anyone know why mine keeps failing to log?

Itll connect to the ECU then a few seconds later itll scroll through some text and give a error code -8 and stop logging.   Ive tried new ECU and config files and also pulling the dash/cluster fuse (11) and still no joy.

Really cant get very far with VCDS either as it doesnt log enough samples to see whats going on


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: littco on April 26, 2014, 06:48:05 PM
Anyone know why mine keeps failing to log?

Itll connect to the ECU then a few seconds later itll scroll through some text and give a error code -8 and stop logging.   Ive tried new ECU and config files and also pulling the dash/cluster fuse (11) and still no joy.

Really cant get very far with VCDS either as it doesnt log enough samples to see whats going on
try pulling both dash fuses..

Or run a wire direct from Ecu to obd port and cut the original Kline out( or put a switch in )


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: carsey on April 27, 2014, 03:13:20 AM
Which one is the 2nd dash fuse?   Ive pulled fuse 11 but unsure what the other is.   Daft how it works fine then it all of a sudden decides to stop working.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: SB_GLI on May 05, 2014, 06:16:08 PM
Anyone know why mine keeps failing to log?

Itll connect to the ECU then a few seconds later itll scroll through some text and give a error code -8 and stop logging.   Ive tried new ECU and config files and also pulling the dash/cluster fuse (11) and still no joy.

Really cant get very far with VCDS either as it doesnt log enough samples to see whats going on

Try specifying a lower sample rate.  Sometimes I can only get 5-6 samples a second out of my jetta, otherwise it will error out while other times is will sample 10+ per second without issue.  Also, try using VisualME7Logger as it has a nice friendly GUI that might make it easier to find configuration that works for your car.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ddillenger on May 05, 2014, 06:18:49 PM
Which one is the 2nd dash fuse?   Ive pulled fuse 11 but unsure what the other is.   Daft how it works fine then it all of a sudden decides to stop working.

Star the log when you are in 3rd gear, ready to go WOT. Wait until it says press C to stop logging, then just take the log. Does it stop within seconds?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TLS on July 31, 2014, 06:13:35 PM
Anyone know why mine keeps failing to log?

Itll connect to the ECU then a few seconds later itll scroll through some text and give a error code -8 and stop logging.   Ive tried new ECU and config files and also pulling the dash/cluster fuse (11) and still no joy.

Really cant get very far with VCDS either as it doesnt log enough samples to see whats going on
With mine, I can connect to the ECU with ME7Logger using GUI only while the ignition is off. It can log that (attached). When I turn ignition on, or if I try to launch the program while the engine is running, no luck.
Any further hints?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ddillenger on July 31, 2014, 07:29:39 PM
Edit the cfg file to connect using SLOW 0x00


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TLS on August 02, 2014, 06:13:24 PM
Cheers.
I read this:
 connection method "double slowinit" added (helps with "instrument cluster" problem)
  To use double slowinit set in the [Communication] section of the .ecu file:
    Connect      = SLOW-0x00
    DoubleDelay  = 12           ; Possible values 1 .. 100 (delay in 100ms)
  This only allows to connect while engine not yet started.

And have amended my.ecu file so:
[Communication]
Connect      = SLOW-0x00    ; Possible values: SLOW-0x11, FAST-0x01, Double Slow-0x00
DoubleDelay  = 12           ; Possible values 1 .. 100 (delay in 100ms)
Communicate  = HM0          ; Possible values: HM0, HM2-0x01

I'll give it a go.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aef on August 03, 2014, 11:15:28 AM
Im having some issues with me7logger and my me7.5 S3 1.8t

cable is a cheap one from ebay without ftdi i think. i tried different settings without success.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TLS on August 03, 2014, 06:16:00 PM
Cheers.
I read this:
 connection method "double slowinit" added (helps with "instrument cluster" problem)
  To use double slowinit set in the [Communication] section of the .ecu file:
    Connect      = SLOW-0x00
    DoubleDelay  = 12           ; Possible values 1 .. 100 (delay in 100ms)
  This only allows to connect while engine not yet started.

And have amended my.ecu file so:
[Communication]
Connect      = SLOW-0x00    ; Possible values: SLOW-0x11, FAST-0x01, Double Slow-0x00
DoubleDelay  = 12           ; Possible values 1 .. 100 (delay in 100ms)
Communicate  = HM0          ; Possible values: HM0, HM2-0x01

I'll give it a go.

This didn't help. With key off it connects. As soon as I turn it on, it disconnects. :(


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aef on August 03, 2014, 11:05:14 PM
Have you started the car (if your car has immo in dash) and then pulling dash fuse. This should work


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: eliotroyano on August 04, 2014, 07:18:26 AM
Have you started the car (if your car has immo in dash) and then pulling dash fuse. This should work

I have seen #11 & #15 fuses are cluster related, for example in a MK4 Golf case. My doubt is: which one do you pull out? #15 only or both?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aef on August 04, 2014, 10:05:43 AM
15 will not do that much. the right display will show "fuse" instead of the miles
11 will turn of the whole dash. so 11 alone should work.

my problem was solved today.

Slow-0x00
12
HM0
56000

worked for me. i was able to start the car and the log didnt crash.
will do a test drive the other day.

125000 as described by user mil_on to use the whole k-line didnt work for me.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: SB_GLI on August 04, 2014, 02:02:07 PM
I finally dug into the issue that I was having logging my Jetta.  I could only get like 5 or samples a second and had to cut down the number of variables that I logged. 

Since I am using VisualME7Logger, ME7Logger needs to write the log to both the stdout and the file.  Writing to both was causing the issues with my car / pc combo.   This was only an issue for my jetta, as I have logged other vehicles with my PC at 20 frames per second with no issues.  If I write just to the log, or just to the stdout, it logs with no issue.  Otherwise it would just take a few samples and then puke out.

Testing with ME7Logger from the command line, it still has the same issue when trying to print to the stdout and file at the same time, so it's not VisualME7Logger related.

I added an option to disable real-time display in VisualME7Logger and now I can log 50+ variables at 20+ frames per second, I just can't see stuff as I am driving unless I go back to around 5 samples a second.  I will release this option in the near future or as needed if someone else notices this problem.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TLS on August 05, 2014, 12:29:54 AM
I'm glad to hear you got it working AEF. I don't have a fuse in spot 11. There are no pins there.
What symbol am I looking for for dash fuse?

Am I correct in saying you want me to start the car, pull the dash fuse and then try to connect?
I pulled 5 and also 15 together after having started the car. Still would not connect.
http://www.passatworld.com/forums/42-volkswagen-passat-b5-discussion/336438-b5-b5-5-passat-fuse-layout-reference.html


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aef on August 05, 2014, 01:32:20 AM
you can try it with car off and ignition on.

dash should went dark if you pull fuse 5 i think.

then you have to play with the settings:
Slow-0x00
12
HM0
56000

if you are able to connect the me7logger you can try it with dash. if this doesnt work put a killswitch into k-line to dash, maybe this will work. you are allowed to start the car, kill the kline (immo related), turn on logger :)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: gitman on September 12, 2014, 10:02:03 AM
wanted to report an issue - when I mouse over points plotted out on "Y Axis2", it does not pop up a tooltip with the X,Y, and cell values that you can see if you mouse over a point plotted out on the first "Y Axis"


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: metronet on September 28, 2014, 10:13:34 AM
Any word on this? Would be sweet to get a raspberry pi in a car to start logging based off of a switch and not need a computer in the car.

Another vote for a binary compiled for Arm processors like the RaspberryPi. It would be really cool! :D


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on November 16, 2014, 03:18:49 PM
Another vote for a binary compiled for Arm processors like the RaspberryPi. It would be really cool! :D

BUMP!

Hey setzi, if you are too busy, just release the source ;)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: fukenbroken on December 07, 2014, 10:16:04 AM
little diy. howto generate vag-com measurement groups vs variables table


C:/vw/me7logger/bin/me7info.exe C:/vw/my_ecu.bin -g >C:/vw/my_ecu.txt

legend:
path to me7info
path to your bin file
path to output file

Code:
Measgroup table for file 06A906032DR_0002.bin
Map measgroup -> result_type(variable name)  for all the sub-results

measgroup 000: 0050(tmotlin             ), 0002(rl                  ), 000E(nmotll              ), 0051(wub                 ), 0007(wdkba               ),
               0087(dmllri_w            ), 0013(dmvad_w             ), 001C(fr_w                ), 001F(rkat_w/rkaz_w       ), 0021(fra_w               )
measgroup 001: 0001(nmot                ), 0050(tmotlin             ), 001C(fr_w                ), 000D(                    )
measgroup 002: 0001(nmot                ), 0002(rl                  ), 004A(ti_b1               ), 000A(mshfm_w             )
measgroup 003: 0001(nmot                ), 000A(mshfm_w             ), 0007(wdkba               ), 0009(zwout               )
...


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: fukenbroken on December 07, 2014, 10:19:25 AM
here is mine
wideband 1.8t


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: melu on December 11, 2014, 02:39:38 PM
Is there a way to use ME7Info with a ME7.9.10?
If I try to use it, I will get the error, that the flash length is not correct, as ME7.9.10 uses a 832kB flash.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on December 11, 2014, 02:56:06 PM
Unfortunately, no.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: melu on December 12, 2014, 02:55:19 PM
It's a pity :(
I tried also with ME7.5.20, didn't work neither

Still struggling with disassemble ST10F275


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: juutasqsa on January 22, 2015, 09:47:31 AM
Hi,

I installed ME7Logger and GUI into my win7 64bit laptop and I can't get ME7Logger working.
Below error came:
can't load library ftd2xx.dll
Initialization failed, exiting ...
exiting (cause=0x1)...

Is it cause I have 64bit OS and can someone help me how to solve this problem?

Thanks in advance.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on January 22, 2015, 10:27:40 AM
I installed ME7Logger and GUI into my win7 64bit laptop and I can't get ME7Logger working.
Below error came:
can't load library ftd2xx.dll

Which FTDI driver did you install?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: juutasqsa on January 22, 2015, 10:29:00 AM
Hi,

I installed ME7Logger and GUI into my win7 64bit laptop and I can't get ME7Logger working.
Below error came:
can't load library ftd2xx.dll
Initialization failed, exiting ...
exiting (cause=0x1)...

Is it cause I have 64bit OS and can someone help me how to solve this problem?

Got help for this problem, I added that .dll into bin folder and I took away 'Boot in intelligent mode' from VCDS. Thanks Okkim, again.




Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: A4Rich on January 22, 2015, 03:28:39 PM


I had the same problem on W7 64-bit with genuine VCDS K+can cable but did get it working.  I didn't have the VCP driver from ross-tech installed fully.  Check this thread out, click (http://nefariousmotorsports.com/forum/index.php?topic=3138.0title=) and use the FTDIchip.com instructions for more guidance (note, I never couldn't get the FTDIchip driver to work).


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on January 23, 2015, 11:49:31 AM
one more minor thing

I think ldimxak_w should be {BoostCorrectFactorPID-IActual}, not {ChargeLimitPID-I}


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: 4ringpieces on January 29, 2015, 11:17:13 AM
Just checking that v1.20 is latest version?

Anyone used this with genuine vcds cable guessing it has to be in "dumb" mode to work?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on January 29, 2015, 11:26:09 AM
Just checking that v1.20 is latest version?

Anyone used this with genuine vcds cable guessing it has to be in "dumb" mode to work?


Yes and yes.

I find it is more stable with the VCP (emulated serial port) driver from ross-tech in serial mode than in native USB mode... ymmv.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: 4ringpieces on January 29, 2015, 11:40:01 AM
Cheers Nyet

Will try it first but any problems i'll swap over to the vcp driver



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: seany260 on February 01, 2015, 08:07:01 AM
Can't connect to Golf 06A906032HJ ecu, I get the error in the attached picture. it connects using the nefmoto software no problem.
i can connect to my a4 b6 without problem also.

do i need to change speeds?

sorry if this has been visited many times before but cant find anything on it.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: TLS on February 01, 2015, 09:41:57 PM
Have you tried super slow init?
Set Baud to 34k option.
Sample rates around 15/s
Load the logger
turn Accessories on
Start logging
Then turn engine on.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: seany260 on February 02, 2015, 01:09:05 AM
Have you tried super slow init?
Set Baud to 34k option.
Sample rates around 15/s
Load the logger
turn Accessories on
Start logging
Then turn engine on.
baud is at only 10k for some reason already.
I'm using the GUI to connect, can the bauds be changed using this? I know the sample rates can..


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: SB_GLI on February 06, 2015, 05:41:43 PM
baud is at only 10k for some reason already.
I'm using the GUI to connect, can the bauds be changed using this? I know the sample rates can..

Visual ME7Logger has these options.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: seany260 on February 07, 2015, 03:05:15 AM
Thanks, I'll get a play about with it later.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: wannabeS4 on February 26, 2015, 12:04:15 AM
So I am having an issue where my logs dont show up after logging. I took a couple logs tonight and when I was looking for the csv file I couldnt find them. Anybody have an idea on what is happening? 


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on February 26, 2015, 12:25:59 AM
cut and paste (not screen shot) of a dir of the cwd.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: wannabeS4 on February 26, 2015, 12:48:49 AM
Not sure what you mean by that.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on February 26, 2015, 11:06:47 AM
type "dir" in the log directory.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: wannabeS4 on February 26, 2015, 09:38:08 PM
Sorry I'm not getting this but you mean in the search bar in the log folder that comes with me7logger correct. Cause I did that and nothing came up.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on February 26, 2015, 11:52:36 PM
Are you running ME7L from command line or visualme7logger?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: wannabeS4 on February 27, 2015, 12:24:50 AM
I'm using the gui for me7logger.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: pete95zhn on February 27, 2015, 04:18:12 AM
Hello!

Who's the ME7logger guru nowadays? Someone who could help with ME7.8 logging issues?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on February 27, 2015, 10:16:16 AM
I'm using the gui for me7logger.

Where are you looking for the logs? What directory? BE SPECIFIC, you haven't provided any useful information yet..


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: KmosK04 on May 14, 2015, 10:30:38 AM
Star the log when you are in 3rd gear, ready to go WOT. Wait until it says press C to stop logging, then just take the log. Does it stop within seconds?

I face this problem. Any help please?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: golfputtputt on June 04, 2015, 08:00:25 PM
I keep getting can't load library ftd2xx.dll

Not sure what to do. I'm using the VCDS HEX+CAN cable.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: sonique on June 19, 2015, 12:37:02 PM
i have problem this file try create ecu file

Code:
ME7Info.exe "Seat leon cupra 1.8T 180HP 06A906032T 0261206
545 352761.ori" -o seat.ecu
read 1116 map entries
mapped 198 aliases
matchOpcode(0, D74XXXXX) out of bounds
Error: getOpc(0) out of range
get_dpp_addr(1) out of bounds
written 571 definitions
written output to file seat.ecu


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on June 19, 2015, 12:40:10 PM
I keep getting can't load library ftd2xx.dll

Not sure what to do. I'm using the VCDS HEX+CAN cable.

You need the VCP driver to use the logger with COMx. Otherwise, use USB mode.

Also ALWAYS INCLUDE THE CONTENT OF THE CMD WINDOW when asking for help, including the full command line you are executing.

Just saying "it doesn't work" is useless.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: grey on June 30, 2015, 03:16:37 PM
create ecu file;

C:\ME7Logger\bin>me7info.exe audi_tt.bin
read 1116 map entries
mapped 198 aliases
matchOpcode(0, D74XXXXX) out of bounds
Error: getOpc(0) out of range
get_dpp_addr(1) out of bounds
written 571 definitions
written output to file C:\ME7Logger\ecus\audi_tt.ecu

Any idea about this problem?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: sonique on June 30, 2015, 04:27:29 PM
same error my 32t file but no any answer


create ecu file;

C:\ME7Logger\bin>me7info.exe audi_tt.bin
read 1116 map entries
mapped 198 aliases
matchOpcode(0, D74XXXXX) out of bounds
Error: getOpc(0) out of range
get_dpp_addr(1) out of bounds
written 571 definitions
written output to file C:\ME7Logger\ecus\audi_tt.ecu

Any idea about this problem?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on June 30, 2015, 05:04:57 PM
Either it isn't a stock file or that binary isn't supported. Unfortunately, he never made the source code available so it cannot be fixed, as it is abandonware.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: rnagy86 on July 01, 2015, 12:55:29 AM
Either it isn't a stock file or that binary isn't supported. Unfortunately, he never made the source code available so it cannot be fixed, as it is abandonware.

Maybe he could be persuaded to do so after so many years have passed.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: seany260 on September 19, 2015, 02:06:47 PM
starting getting this error while logging a while back, anyone aware of what causes it. it bumps me off and stops logging!

thanx


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: SB_GLI on September 20, 2015, 05:47:50 AM
Try logging less variables, a smaller sample rate, or use different baud rates.  Id none of that works, try logging with your cluster fuse pulled.  I use this logger on several cars and a lot of them have issues keeping the connection.  In all most every case, pulling the cluster fuse makes it work 100%.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: 316LV on September 20, 2015, 04:22:35 PM
^ Agreed. I had the same issue until I bypassed the cluster for logging. Works flawlessly now.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: cruuz on November 10, 2015, 03:00:42 AM
hi,

is it posible with the me7logger to make RAM dumps?
E.g by using such a ecu file?:
;Name           , {Alias}                                   , Address, Size, Bitmask, {Unit},    S, I,            A,      B, Comment
dump             , {CountStartsWithOilInFuel}        , 0x380000,  65536,  0x0000, {#}       , 0, 0,            1,      0, {dump}

or is there anothe tool to make ram dumps?

br - cruuz


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aef on December 30, 2015, 04:16:55 PM
I am trying to add mibas_w to my ecu file.

I found mibas_w in 018J damos like this:
Quote
/UMP, {}, mibas_w, {indiziertes Basis-Moment}, $38252E, 514, 287, rel_uw_b100, 3, $FFFF, K;

KFZW is at $8120DD according to damos and in my file its $120DD because of the well known 800000 offset @ import.

How to add mibas_w into the existing syntax?

Quote
;Name           , {Alias}                         , Address,     Size,    Bitmask,    {Unit},    S,  I,                  A,      B,       Comment
mifa_w          , {}                                , 0x3824D6,       2,    0x0000,      {%},     0, 0,    0.00152588,      0,      {indiziertes Motormoment Fahrerwunsch}



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on December 31, 2015, 09:21:47 AM
Err, what is the problem? I don't understand the question. Fill in the required fields, done.
Code:
mibas_w                  , {}                                , 0xXXXXXX,  2,  0x0000, { }       , 0, 0,   0.00152588,      0, {indicated basic torque}


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aef on January 01, 2016, 07:36:42 AM
happy new year nyet,

thats what i did when i saw that all mi.... have the same 0.00152588.
will log and report later.

regards


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: DT on January 01, 2016, 07:48:35 AM
If you draw the conclusion that the damos is correct for your bin because KFZW line up you might be wrong. But sure, if your mifa_w from your me7logger file also match with the damos your mibas_w address is probably also correct.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: dream3R on January 01, 2016, 04:32:37 PM
Just add the offset no?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on January 01, 2016, 04:46:43 PM
1/0.0015258785*100 = 2^?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: dream3R on January 01, 2016, 05:05:00 PM
1/0.0015258785*100 = 2^?
0xFFFF!?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Rs6 on February 24, 2016, 01:42:47 PM
Hello Guys!

After lots of reading i did get ME7Logger to work on my C5 RS6  ;D

Very nice stuff and lots of data. Only problem i now have is how to read it with Excel? I always see nice and clear Excel sheets on the internet but when i open a log on excel it looks very disturbing :-[ Did lots of reading but i cant find a solution to fix this? Is it just a setting in Excel or do i have other problems?

Thanks!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: armageddon on February 24, 2016, 02:04:26 PM
look to nyet's sign  ;D

2 posts up


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Rs6 on February 24, 2016, 02:19:47 PM
look to nyet's sign  ;D

2 posts up

Do you mean the ME7.1 tuning guide? Already read that its great yes! But i cant find anything on the Excel?

I like to have it like this  ???


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on February 24, 2016, 02:20:10 PM
lol @ excel


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Rs6 on February 24, 2016, 02:44:29 PM
lol @ excel

Not good?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: 316LV on February 27, 2016, 02:09:09 PM
Not good?

Not really. As you found, it is hard to read without graphing the data. Why bother as Nyet has the solution in his sig line (as Armageddon pointed out). Use this: http://nyet.org/cars/ECUxPlot (http://nyet.org/cars/ECUxPlot). Its awesome.



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: roman_tyk on March 19, 2016, 06:51:56 AM
Dear collegues,

does anybody tried to find actual fueling corrections (variable in %) like in VCDS measure group 033?

thx in advance.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on March 19, 2016, 10:18:10 AM
fr/fr2/frm/frm2?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: roman_tyk on March 19, 2016, 02:26:05 PM
fr/fr2/frm/frm2?

looks different, maybe should i use some specific factor?
(http://s13.postimg.org/nh6x3jjyr/fr_frm.jpg) (http://postimg.org/image/nh6x3jjyr/)


Title: Logging ME7 fast and flexible t ME7Logger
Post by: RolandUsen on March 28, 2016, 04:36:58 AM
Spec C, that will require someone to custom program that into a logger.   A logger that already works. 

I believe Calvin released his source if someone wants to hop on it.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: eliotroyano on March 28, 2016, 10:01:51 AM
Friends sorry I have not readed whole thread, but exist any similar logger for MED9.1?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: h100vw on April 02, 2016, 11:32:39 PM
I keep getting can't load library ftd2xx.dll

Not sure what to do. I'm using the VCDS HEX+CAN cable.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: h100vw on April 02, 2016, 11:49:43 PM
I keep getting can't load library ftd2xx.dll

Not sure what to do. I'm using the VCDS HEX+CAN cable.

I have the same problem. The set up I have works ok on the w7 Dell I have but I recently went New Skool to W10 on a Toshiba.

I tried to post a screen shot of it but failed. The cut and paste below is what happens at the end. This is with FTDI selected.

                           
Logged data size is 103 bytes.
Really logged are 61 entries with 102 bytes.
can't load library ftd2xx.dll
Initialization failed, exiting ...
exiting (cause=0x1)...

C:\Users\Jack Bauer\Desktop\ME7 LOGGER>


*******************************************EDIT*********************************************

So in the interests of being useful. I deleted the drivers for the VCDS cable and reloaded them from a fresh download of the VCP drivers from Ross-Tech. http://www.ross-tech.com/vag-com/usb/virtual-com-port.html

The drivers wouldn't update. I had to uninstall the cable and reinstall the drivers and now ME7 logger is off again. :)

I am surprised that I needed to do this as I have been using this laptop to flash ME7 ECU with nefmoto.

But I am willing to take on the win any way.

Gavin




Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on April 02, 2016, 11:53:39 PM
VCP drivers, reinstall ftdi drivers.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Tshirt2k on April 07, 2016, 02:09:49 PM
Having a similar issue to some using this.

Can't connect to ECU with the ignition on.

Engine is a conversion but have wired in ECU and connected OBD port according to wiring diagram. Nothing else is connected in the k line.  It is direct to pin 43 on the ECU.
VCDS works. I am using Hex com serial version. I can also read and write flash via the port using MPPS.

When using the GUI or visualme7logger, I can get it to run when the ignition is off but as soon as I try with ignition on it fails. Giving error -19

Anyone know what could cause this?

I'm am using the blue ftdi cable. Not sure if it's connected but I can't connect to ECU using an elm327 with torque app.

Seems to point to wiring but with other programs able to talk to the ECU I am unsure.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: h100vw on April 10, 2016, 06:18:32 PM
Ignition on or engine running?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Tshirt2k on April 12, 2016, 09:57:07 AM
Both. If ignition is on or running. It disconnects.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Tshirt2k on April 16, 2016, 11:33:49 AM
Managed to get it working with my trusty Hex Com Vcds lead.
Connected straight away with no issues. At any baud rate except 125000

Blue cable must not work very well with it.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Lauria112 on May 26, 2016, 02:44:48 PM
Hi,
Could someone please explain what are the differences between slow-0x11 and slow-0x00 connection settings?
I'm working to get logging working on raspberry but my ecu requires slow-0x00 connection so i would need to replicate that to mmll from trichard3000

Best regards
Lauri


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: 20VTMK1 on June 07, 2016, 08:18:39 AM
Hi All ,

Could some one please assist me .

I had a laptop crash and it came back to life with windows 10 . I tried re-installing ME7 logger and kept getting the "missing FTD2XX.DLL " message.

I then down loaded the FTD2XX.dll and placed it in the library folder of ME7 logger and also in the Windows system folder .

So now the me7 logger starts up but wont write to the log file and then wont log .

Am I missing something ?

Thanks in advance


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on June 07, 2016, 11:05:48 AM
I then down loaded the FTD2XX.dll and placed it in the library folder of ME7 logger and also in the Windows system folder .

DO NOT DO THIS.

Delete any add on dlls from the me7logger dir and install the drivers properly, using the installer or the windows driver management console. You're just going to cause problems if you copy dlls around manually.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: 20VTMK1 on June 07, 2016, 12:12:47 PM
Hi Nyet ,

Thanks for the reply . I tried all the installs , even via the windows device manager , manual driver update - no luck . I even downloaded the CMD exe file from the FTDI website - no luck

I now run the GUI as admin and it works ..

I did find libME7logger.dll in the lib folder tho'



Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on June 07, 2016, 12:24:23 PM
Thanks for the reply . I tried all the installs , even via the windows device manager , manual driver update - no luck . I even downloaded the CMD exe file from the FTDI website - no luck

That is a bad sign.

Quote
I now run the GUI as admin and it works ..

That's a good sign.

Quote
I did find libME7logger.dll in the lib folder tho'

That is part of the logging software, not the driver for your cable.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: ing90 on June 14, 2016, 12:18:53 PM
Tried this soft on my ME7.4.6 on Peugeot V6, not working.
Error at connection (reason=4) . . .

Cheer ;)

I did it - 3 years later ;)

But if anyone is interested:
Connect      = FAST-0x11
Communicate  = HM0
LogSpeed     = 10400


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: telnet402m on June 18, 2016, 07:26:52 AM
Thank you all for contribution, is a great tool and can save from a lot of bad things.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: lsalt100 on October 05, 2016, 01:12:05 PM
hello loggerfuns

can you  check log.txt for find where I'm wrong?

especially:
21:34:29.054-539,1 os_sendbyte(data=75)
21:34:29.061-522,2 os_rcvbyte(timeout=50) -> 75
21:34:29.093-248,4 os_rcvbyte(timeout=100) -> 0F
received wrong inverted address 0x0F (expected 0xFE)


logger is not able to start ;-(

thanx for help



 


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: prj on October 07, 2016, 11:46:44 AM
hello loggerfuns

can you  check log.txt for find where I'm wrong?

especially:
21:34:29.054-539,1 os_sendbyte(data=75)
21:34:29.061-522,2 os_rcvbyte(timeout=50) -> 75
21:34:29.093-248,4 os_rcvbyte(timeout=100) -> 0F
received wrong inverted address 0x0F (expected 0xFE)


logger is not able to start ;-(

thanx for help



 

Start the logger with ignition turned on and engine NOT running. After it is logging start the engine.
You can not use SLOW-0x00 method with the engine running unless you patch the ECU.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: eliotroyano on July 25, 2017, 01:19:51 PM
Friends I have a question, maybe a dumb one. Ok anyway I will make it. Is there any way to convert M7Logger csv files in common csv files that could be proccesed by other 3rd party software? I have many issues processing long run logs with MegaLogViewer


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: eliotroyano on July 28, 2017, 02:59:36 PM
Friends I have a question, maybe a dumb one. Ok anyway I will make it. Is there any way to convert M7Logger csv files in common csv files that could be proccesed by other 3rd party software? I have many issues processing long run logs with MegaLogViewer

This is what I mean. Example1 is something similar to what ME7logger generates in my case. Example2 is what other 3rd party software can read. It is like unmodified CSV format. What can be done to obtain this format (like example2.csv)?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: eliotroyano on July 29, 2017, 07:22:19 AM
This is what I mean. Example1 is something similar to what ME7logger generates in my case. Example2 is what other 3rd party software can read. It is like unmodified CSV format. What can be done to obtain this format (like example2.csv)?

Sorry to ask you again but I have check ME7Logger software options and the GUIs available and I still got the same format. Anyone one have notice the same thing? any experiences?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on July 29, 2017, 09:30:56 AM
There is literally nothing wrong with the .csv format that ME7Logger outputs

It is "unmodified" csv, and unless you can be more specific about what is wrong with the format, I'm not sure what can be done.

If you are saying it is missing trailing commas, i'd say whatever parser they are using is fundamentally broken and stupid.

It is trivial to write a script to modify csv.

Perl is one way.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: eliotroyano on July 29, 2017, 12:15:20 PM
There is literally nothing wrong with the .csv format that ME7Logger outputs
It is "unmodified" csv, and unless you can be more specific about what is wrong with the format, I'm not sure what can be done.
If you are saying it is missing trailing commas, i'd say whatever parser they are using is fundamentally broken and stupid.
It is trivial to write a script to modify csv.
Perl is one way.

I understand you Nyet. This are the basic differences. Apparently ME7Logger include some spaces between values and commas that are generating me some issues.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: SB_GLI on July 29, 2017, 02:18:17 PM
what you have in example2 is exactly what happens when you open up example1 in something like excel or openoffice and save it.  It totally fucks the format.   The ME7Logger format is just fine and dandy.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: eliotroyano on July 30, 2017, 07:26:26 AM
what you have in example2 is exactly what happens when you open up example1 in something like excel or openoffice and save it.  It totally fucks the format.   The ME7Logger format is just fine and dandy.

Thanks a lot for the tip. After some research using Excel and others logs I found the same thing that you mentioned. Excel was changing the csv output format that show me with only opening it.  :o  :o  :o  :o .  Then after some some massaging of the logs I made it work with my log proccesing tool. I need to test with ECUxPlot too. Other difference is that the log I am processing is a 20min one. It is a 12Mb csv log.
Attached some pics of the tool.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Brando47 on August 20, 2017, 09:47:06 AM
Is there any chance this would work for data logging an ME1.5.5?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 20, 2017, 11:11:27 AM
Stop. Fucking. Using. Excel. Already.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: SB_GLI on August 20, 2017, 12:31:44 PM
Stop. Fucking. Using. Excel. Already.

lolz, I updated vme7l parsing so it can handle it because this is becoming more of an epidemic.  :)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on August 20, 2017, 12:34:08 PM
lolz, I updated vme7l parsing so it can handle it because this is becoming more of an epidemic.  :)

Argh. I have been trying to avoid doing that in ECUxPlot because it is impossible to predict the 8 million ways excel can screw up the csv.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: CodeTurbo on August 20, 2017, 04:34:12 PM
Hi people,
    Easy question, I haven't been able to use ME7Logger in my Golf 4 1.8T 20V AUQ.
    I have a 12.12 VCDS cable, which has an FTDI chip, should I use a KKL one?. I tryed many things, like VCP drivers from Ross-Tech, standard FTDI drivers, using ME7Logger with -f and with COM port, nothing..., it fails right away.

Thanks!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aef on August 21, 2017, 12:47:16 AM
better post a log of your problem
could be settings, could be shared k-line, could be everything


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: BlackT on August 21, 2017, 08:23:20 AM
Hi people,
    Easy question, I haven't been able to use ME7Logger in my Golf 4 1.8T 20V AUQ.
    I have a 12.12 VCDS cable, which has an FTDI chip, should I use a KKL one?. I tryed many things, like VCP drivers from Ross-Tech, standard FTDI drivers, using ME7Logger with -f and with COM port, nothing..., it fails right away.

Thanks!
I didn't manage to get work with that cable. same ftdi chip, problem is when instaling drivers for 'dump k-line'  the interface ask to instal ross tech drivers. Do you see your interface under COM ports in device menager?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: CodeTurbo on August 21, 2017, 09:35:02 AM
Thanks for your answers, here is the error I get:

ME7Logger_DIST_10072013_v1.20\bin\ME7Logger.exe -f basic.cfg

Logged data size is 59 bytes.
Really logged are 33 entries with 59 bytes.
FTDI library version 30214
can't open FTDI interface, error=3
Initialization failed, exiting ...
exiting (cause=0x1)...


As I said, I can use the cable with the VCDS software, but so far with this cable (12.12) I wasn't able to use lemminwinks, unisettings, APR V-Tuning nor ME7Logger, so I think this cable is crap but will be a KKL cable a solution?

My ECU code/version is 06A 906 032 LT


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: BlackT on August 21, 2017, 10:20:39 AM
read twice what i wrote. And read every faq thread.
Here is litle explanation.  Your laptop/PC is a destination A,your car ECU is destination B. 
FTDI FT232R is a highway, and every other chip inside interface(for HEX,CAN etc. protocols) is some sort of stop
And that is bad, KKL have only FTDI and that why is good. Same that you can read on VCDS site,link is on S4tuning wiki


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: CodeTurbo on August 21, 2017, 03:49:31 PM
Hi BlackT,
    I read what you wrote more than 2 times and also many others threads, here and there.
    Believe, if I wrote here is because nothing worked. I'm asking about KKL cable because the 12.12 didn´t exist when this thread was created and many threads not even mention exactly what cable are using, just say "cheap ebay cable", "ftdi", but not 12.12 or 409.
   I'm a SW Engineer but I'm not specialized in cars (but is my hobby) nor those low-level protocols that ECUs speaks. That is why I'm looking for real help here.

    Thanks again.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: bmw5002 on February 07, 2018, 02:40:50 PM
Any idea what would be involved with making this work for something like MED 9.1? Seems guys are already tuning that ecu... would be great to have a fast datalogger for my 2012 TTRS. :-D


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aef on June 29, 2018, 03:10:08 AM
PRJ wrote somewhere what to modify in the bin to make the logger connect with the ecu when the car is running.
I cant find the post again but this would be very useful.

There were two small changes in two spots of the file.

 ???


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: armageddon on July 02, 2018, 01:32:19 PM
PRJ wrote somewhere what to modify in the bin to make the logger connect with the ecu when the car is running.
I cant find the post again but this would be very useful.

There were two small changes in two spots of the file.

 ???

http://nefariousmotorsports.com/forum/index.php?;topic=14119.0

for rs4 k-box:

0x35FD2 - 3D 06 -> CC 00
0x77DE4 - 3D 08 -> CC 00
0x78CB6 - 3D 03 -> CC 00


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: aef on July 02, 2018, 11:05:30 PM
yes yes yes,

thank you!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: brs on October 04, 2018, 03:39:55 PM
Little help here please... I downloaded and installed winlog. I coppied the ME7L_winlog.dll and libME7Logger.dll into the Winlog directory. i opened up winlog and went to device configuration and set everything up just like in the video... 56000 baudrate 10 samplerate absolute timestamps. i even used the cfg file and dsh file provided by stetzi however when i try to load winlog it pops up and says "error initializing device: ME7logger winlog driver. Would you like to retry" also i noticed when i go to the device configuration like setzi does in the video i do not have a little plus next to the "me7logger winlog driver" that drops down all the variables being logged... can someone maybe help me figure out what i am doing wrong here?

Hi all
I have same issue,any idea ?

Regards


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tweetss4estate on November 25, 2018, 12:40:46 PM
What is the output? Just telling it can't connect or something more?
Are you referencing the right ecu characteristics file in your trace config?
If a wrong characteristics file is used, the logger could try to connect to a
wrong address.


I'm referencing the characteristics file I created from my ECUs binary.
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x11
Communicate  = HM0
LogSpeed     = 57600
[Identification]
HWNumber           = "0261206776"
SWNumber           = "1037354123"
PartNumber         = "8D0907551G"
SWVersion          = "0001"
EngineId           = "2.7l V6/5VT"

Here's the output:
Logged data size is 101 bytes.
Start connecting to ECU at 02.08.2011 17:17:17.515
try connect slow(11)
try connect slow(11)
Could not connect
=> Could not connect to ECU, exiting ...
=> Logging failed
exiting (cause=0x4)...


I can’t find the Engine ID in the 551M config files. Help please!


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on November 25, 2018, 02:34:52 PM
What do you need the EngineID for? What files did you look in?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: tweetss4estate on November 25, 2018, 04:52:13 PM
What do you need the EngineID for? What files did you look in?

Me7 logger tells me that the engine code should be “2.7T 5V xxx”, and the ecu is coded to say for example “vast file V3”. I am having difficulty copying and then changing one of my 551M config files to work on this car.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on November 27, 2018, 06:13:07 AM
ME7Info should generate the correct EngineID if you run it on the BIN you are currently running. Otherwise, you will have to hand edit the config which should work.

Unless the problem is spaces? Carriage returns? Some other character in the EngineID string? You can only really tell by hexediting the bin itself.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Khendal on February 12, 2019, 02:53:23 PM
One question...at the moment with last VCDS Genuine Cable...is it possible to use ME7Logger?  :)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on February 12, 2019, 03:01:33 PM
yes

disable intelligent mode. You will need to install the VCP driver if you want to use ME7L with a com port (more stable on SOME machines)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: vwaudiguy on February 12, 2019, 05:47:57 PM
One question...at the moment with last VCDS Genuine Cable...is it possible to use ME7Logger?  :)

Last genuine cable is the wifi one (can also use with a cable). Was told by VCDS these would not work as a pass through like the previous generation. Never tried based on this infoz.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on February 13, 2019, 10:23:37 AM
Last genuine cable is the wifi one (can also use with a cable). Was told by VCDS these would not work as a pass through like the previous generation. Never tried based on this infoz.

Sorry, I thought the poster meant the last USB version.

Yes, the wifi version will not work.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: Khendal on February 17, 2019, 02:05:02 PM
yes

disable intelligent mode. You will need to install the VCP driver if you want to use ME7L with a com port (more stable on SOME machines)


I have the last not wifi cable :) so should work.

What does intelligent mode do in VCDS? After disable...can i use like always VCDS?
Which one are the best vcp driver to install?

Thanks :)


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: nyet on February 17, 2019, 04:38:59 PM
What does intelligent mode do in VCDS? After disable...can i use like always VCDS?

It puts the cable into VCDS mode as soon as it detects any ECU. It screws up all non-vcds programs, but can speed VCDS launch time.

If you disable it, VCDS will still work

Quote
Which one are the best vcp driver to install?

As far as I know there is only one; the one from RossTech and it is super old. It isn't a must have, but some ftdi obdii programs will not work with direct usb.


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: BlackT on April 19, 2019, 12:26:32 PM
How to find mimax and mibas on ME7.5 ? What metod are you using?


Title: Re: Logging ME7 fast and flexible => ME7Logger
Post by: BlackT on April 29, 2019, 06:16:12 AM
How to find mimax and mibas on ME7.5 ? What metod are you using?
Bump