NefMoto > Technical > Data Logging > Logging ME7 fast and flexible => ME7Logger
Pages: 1 2 3 [4] 5 6 ... 35
« previous next »
Author Topic: Logging ME7 fast and flexible => ME7Logger  (Read 535702 times)
setzi62
Full Member
***

Karma: +142/-0
Offline Offline

Posts: 249
« Reply #45 on: August 12, 2011, 07:50:39 AM »
Quote from: tobz on August 11, 2011, 06:16:42 PM
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
Logged
tobz
Full Member
***

Karma: +3/-1
Offline Offline

Posts: 60
« Reply #46 on: August 12, 2011, 07:55:37 AM »
Quote from: setzi62 on August 12, 2011, 07:50:39 AM
Quote from: tobz on August 11, 2011, 06:16:42 PM
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.
« Last Edit: August 12, 2011, 08:00:27 AM by tobz » Logged
setzi62
Full Member
***

Karma: +142/-0
Offline Offline

Posts: 249
« Reply #47 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.
Logged
tobz
Full Member
***

Karma: +3/-1
Offline Offline

Posts: 60
« Reply #48 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.
Logged
setzi62
Full Member
***

Karma: +142/-0
Offline Offline

Posts: 249
« Reply #49 on: August 12, 2011, 08:09:33 AM »
Quote from: tobz on August 12, 2011, 07:55:37 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  Wink.
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.
Logged
setzi62
Full Member
***

Karma: +142/-0
Offline Offline

Posts: 249
« Reply #50 on: August 12, 2011, 08:12:41 AM »
Quote from: 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.

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

Karma: +3/-1
Offline Offline

Posts: 60
« Reply #51 on: August 12, 2011, 09:10:40 AM »
Quote from: setzi62 on August 12, 2011, 08:09:33 AM
Quote from: tobz on August 12, 2011, 07:55:37 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  Wink.
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.
Logged
Ur-S-Sex
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 1
« Reply #52 on: August 15, 2011, 11:36:58 AM »
Any chance this program will log the AEB 1.8t P box ECUs?
Logged
s5fourdoor
Hero Member
*****

Karma: +33/-3
Offline Offline

Posts: 617
« Reply #53 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
Logged
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709
« Reply #54 on: August 16, 2011, 05:28:45 PM »
Quote from: 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


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.
Logged
TWiST
Newbie
*

Karma: +4/-0
Offline Offline

Posts: 20
« Reply #55 on: August 17, 2011, 10:26:33 PM »
I have been gone for a while, looking forward to giving this a run soon.
Logged
ThomasRS4
Guest
« Reply #56 on: August 18, 2011, 08:45:09 AM »
Quote from: 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.

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

Karma: +607/-168
Online Online

Posts: 12270


WWW
« Reply #57 on: August 18, 2011, 12:12:57 PM »
Quote from: 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?


I would like to know this too Smiley 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
Logged
ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

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 ex
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709
« Reply #58 on: August 18, 2011, 12:45:43 PM »
Quote from: nyet on August 18, 2011, 12:12:57 PM
Quote from: 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?


I would like to know this too Smiley 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 )
« Last Edit: August 18, 2011, 12:48:29 PM by phila_dot » Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Online Online

Posts: 12270


WWW
« Reply #59 on: August 18, 2011, 06:25:23 PM »
Also: a request

ldrkp
ldrki
ldrkd

Smiley
Logged
ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

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 ex
Pages: 1 2 3 [4] 5 6 ... 35
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 26, 2024, 02:09:14 PM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

    Login with username, password and session length
Search
 
Advanced Search
About Disclaimer
All Rights Reserved 2010 Nefarious Motosports
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.036 seconds with 17 queries. (Pretty URLs adds 0.005s, 0q)