Pages: 1 ... 17 18 [19] 20 21 ... 35
Author Topic: Logging ME7 fast and flexible => ME7Logger  (Read 535779 times)
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #270 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.
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
chrisp
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4


« Reply #271 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?
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #272 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*
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
professor
Sr. Member
****

Karma: +25/-0
Offline Offline

Posts: 409



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

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

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #274 on: June 23, 2013, 01:29:12 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?
Logged
Axis
Full Member
***

Karma: +4/-4
Offline Offline

Posts: 91


« Reply #275 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
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #276 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
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
Malinovsky
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #277 on: June 25, 2013, 06:32:39 AM »

thanks Smiley
Logged
kaross
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 63


« Reply #278 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.
« Last Edit: July 02, 2013, 01:06:38 PM by kaross » Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #279 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.
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
kaross
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 63


« Reply #280 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. Sad
Logged
Jrw0215
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 2


« Reply #281 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.
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #282 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.
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
Jrw0215
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 2


« Reply #283 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.
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #284 on: July 02, 2013, 02:09:36 PM »

btw cygwin bash is much better than the cosmic joke that is "cmd.exe"
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 ... 17 18 [19] 20 21 ... 35
  Print  
 
Jump to:  

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