Pages: 1 ... 23 24 [25] 26 27 ... 34
Author Topic: Logging ME7 fast and flexible => ME7Logger  (Read 464601 times)
phila_dot
Hero Member
*****

Karma: +170/-11
Offline Offline

Posts: 1709


« Reply #360 on: February 11, 2014, 07:47:21 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.

No, log with factor of 1, then convert from decimal to hex or binary
Logged
terminator
Sr. Member
****

Karma: +15/-4
Offline Offline

Posts: 425


« Reply #361 on: February 13, 2014, 04:08:08 AM »

Solved. The problem was chinese KKL cable.
« Last Edit: February 13, 2014, 09:55:04 AM by terminator » Logged
carsey
Sr. Member
****

Karma: +7/-4
Offline Offline

Posts: 401


« Reply #362 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
Logged
littco
Hero Member
*****

Karma: +52/-7
Offline Offline

Posts: 903


« Reply #363 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 )
Logged
carsey
Sr. Member
****

Karma: +7/-4
Offline Offline

Posts: 401


« Reply #364 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.
Logged
SB_GLI
Hero Member
*****

Karma: +115/-10
Offline Offline

Posts: 1022


« Reply #365 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.
Logged
ddillenger
Hero Member
*****

Karma: +637/-21
Offline Offline

Posts: 5640


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

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!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
TLS
Full Member
***

Karma: +1/-0
Offline Offline

Posts: 62


« Reply #367 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?
Logged
ddillenger
Hero Member
*****

Karma: +637/-21
Offline Offline

Posts: 5640


« Reply #368 on: July 31, 2014, 07:29:39 PM »

Edit the cfg file to connect using SLOW 0x00
Logged

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!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
TLS
Full Member
***

Karma: +1/-0
Offline Offline

Posts: 62


« Reply #369 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.
Logged
aef
Hero Member
*****

Karma: +69/-46
Offline Offline

Posts: 1566


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

Karma: +1/-0
Offline Offline

Posts: 62


« Reply #371 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. Sad
Logged
aef
Hero Member
*****

Karma: +69/-46
Offline Offline

Posts: 1566


« Reply #372 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
Logged
eliotroyano
Hero Member
*****

Karma: +47/-7
Offline Offline

Posts: 796


« Reply #373 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?
Logged
aef
Hero Member
*****

Karma: +69/-46
Offline Offline

Posts: 1566


« Reply #374 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.
Logged
Pages: 1 ... 23 24 [25] 26 27 ... 34
  Print  
 
Jump to:  

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