Pages: 1 ... 22 23 [24] 25 26 ... 34
Author Topic: Logging ME7 fast and flexible => ME7Logger  (Read 464635 times)
professor
Sr. Member
****

Karma: +25/-0
Offline Offline

Posts: 409



« Reply #345 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?
Logged

Seat Ibiza MK4 Cupra 1.8t 20V, stg3.
"Those 1.8T 20V machines are really tough" ©
grey
Full Member
***

Karma: +4/-1
Offline Offline

Posts: 146


« Reply #346 on: September 06, 2013, 12:06:06 PM »

Using windows 7, give to me7logger.exe admin rights and try again.

Thank you for everything  Wink
Logged
cactusgreens4
Full Member
***

Karma: +2/-0
Offline Offline

Posts: 110


« Reply #347 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?
Logged
lulu2003
Full Member
***

Karma: +11/-1
Offline Offline

Posts: 242



« Reply #348 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?

Logged
Ptyrell
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 30


« Reply #349 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
Logged
Ptyrell
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 30


« Reply #350 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
Logged
MIL_on
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 119


« Reply #351 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 Smiley

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.
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12232


WWW
« Reply #352 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.
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
MIL_on
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 119


« Reply #353 on: November 04, 2013, 03:47:19 PM »

some more info to me 7.5 logging based on todays experience  Smiley
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  Grin 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 Cheesy
Logged
titi65
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 43


« Reply #354 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 Wink
Logged
Aurélien
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 60


« Reply #355 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 ?
Logged
dantt
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 148


« Reply #356 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  Wink
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  Smiley

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


Logged
titi65
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 43


« Reply #357 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 .
Logged
automan001
Full Member
***

Karma: +47/-0
Offline Offline

Posts: 153


« Reply #358 on: February 11, 2014, 02:12:42 AM »

ME7Logger is the greatest! Cool
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.
Logged
terminator
Sr. Member
****

Karma: +15/-4
Offline Offline

Posts: 425


« Reply #359 on: February 11, 2014, 06:23:50 AM »

I'm trying with blue cable, but there is no echo from FTDI or the cable.  Sad 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...
Logged
Pages: 1 ... 22 23 [24] 25 26 ... 34
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.031 seconds with 17 queries. (Pretty URLs adds 0s, 0q)