NefMoto > Technical > Data Logging > Error -19 when trying to log (-8)
Pages: [1] 2
« previous next »
Author Topic: Error -19 when trying to log (-8)  (Read 21053 times)
kingkhalilz
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 123
« on: August 25, 2014, 11:15:51 PM »
Everything is chill when the ignition is on, once i start the car it stops. Same with vag com for some reason. This is what i get

-> Reading log config file C:\Documents and Settings\ABC\Desktop\Audi\ME7 loging
\logs\4B0907551K-0261206561-352740_template.cfg .... done
-> Reading ecu characteristics file C:\Documents and Settings\ABC\Desktop\Audi\M
E7 loging\ecus\4B0907551K-0261206561-352740.ecu .... done
Used Ecu definition is:
[Communication]
Connect = SLOW-0x11
Communicate = HM0
LogSpeed = 56000

[Identification]
HWNumber = "0261206561"
SWNumber = "1037352740"
PartNumber = "4B0907551K"
SWVersion = "0005"
EngineId = "2.7l V6/5VT"

Logged variables are:
#no.: name , alias , addr ,sz, bitm, S
, I, A , B, unit
#-------------------------------------------------------------------------------
-----------------------------
#001: plsol , BoostPressureDesired , 380B3B, 1, 0000, 0
, 0, 10, 0, 'mbar'
#002: plsol_w , BoostPressureDesired , 38219E, 2, 0000, 0
, 0, 0.0390625, 0, 'mbar'
#003: pvdkds_w , BoostPressureActual , 38210E, 2, 0000, 0
, 0, 0.0390625, 0, 'mbar'
#004: pvdks_w , BoostPressureActual , 382112, 2, 0000, 0
, 0, 0.0390625, 0, 'mbar'
Logged data size is 7 bytes.
Really logged are 4 entries with 7 bytes.
Start connecting to ECU at 24.08.2014 14:37:51.775
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:\Documents and Settings\ABC\Desktop\Audi\ME7 loging\logs\custom
.csv
-> Start logging (logdata size=7, 20 samples/second, 56000 baud) at 24.08.2014 1
4:37:55.368
Press ^C to stop logging
.....................Got error -19
14:38:16.895-837,2 os_sendbuf(len=3, data= 01 B7 B8)
14:38:16.903-385,4 os_rcvbyte(timeout=100) -> 01
14:38:16.904-052,5 os_rcvbyte(timeout=100) -> B7
14:38:16.904-656,2 os_rcvbyte(timeout=100) -> B8
14:38:16.919-536,3 os_rcvbyte(timeout=150) -> FE
14:38:16.920-333,3 os_rcvbyte(timeout=50) -> CF
14:38:16.971-945,8 os_rcvbyte(timeout=50) -> TIMEOUT
Got error -8
14:38:17.028-187,3 os_sendbuf(len=3, data= 01 B7 B8)
14:38:17.032-309,9 os_rcvbyte(timeout=100) -> 01
14:38:17.032-929,2 os_rcvbyte(timeout=100) -> B7
14:38:17.033-488,8 os_rcvbyte(timeout=100) -> B8
14:38:17.048-228,6 os_rcvbyte(timeout=150) -> 8C
14:38:17.064-133,7 os_rcvbyte(timeout=50) -> F3
14:38:17.115-782,5 os_rcvbyte(timeout=50) -> TIMEOUT
Got error -8
14:38:17.172-019,2 os_sendbuf(len=3, data= 01 B7 B8)
14:38:17.175-363,0 os_rcvbyte(timeout=100) -> 01
14:38:17.175-975,6 os_rcvbyte(timeout=100) -> B7
14:38:17.176-671,2 os_rcvbyte(timeout=100) -> B8
14:38:17.329-278,3 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
14:38:17.385-386,3 os_sendbuf(len=3, data= 01 B7 B8)
14:38:17.399-497,6 os_rcvbyte(timeout=100) -> 01
14:38:17.400-180,4 os_rcvbyte(timeout=100) -> B7
14:38:17.400-779,3 os_rcvbyte(timeout=100) -> B8
14:38:17.415-780,1 os_rcvbyte(timeout=150) -> FE
14:38:17.416-386,6 os_rcvbyte(timeout=50) -> FB
14:38:17.467-755,7 os_rcvbyte(timeout=50) -> TIMEOUT
Got error -8
14:38:17.524-056,4 os_sendbuf(len=3, data= 01 B7 B8)
14:38:17.526-379,9 os_rcvbyte(timeout=100) -> 01
14:38:17.526-997,9 os_rcvbyte(timeout=100) -> B7
14:38:17.527-605,5 os_rcvbyte(timeout=100) -> B8
14:38:17.684-997,8 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
14:38:17.741-290,7 os_sendbuf(len=3, data= 01 B7 B8)
14:38:17.751-468,9 os_rcvbyte(timeout=100) -> 01
14:38:17.752-239,6 os_rcvbyte(timeout=100) -> B7
14:38:17.752-829,4 os_rcvbyte(timeout=100) -> B8
14:38:17.908-929,1 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
14:38:17.966-543,7 os_sendbuf(len=3, data= 01 B7 B8)
14:38:17.974-438,0 os_rcvbyte(timeout=100) -> 01
14:38:17.975-113,8 os_rcvbyte(timeout=100) -> B7
14:38:17.975-642,9 os_rcvbyte(timeout=100) -> B8
14:38:18.129-579,2 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
14:38:18.185-775,2 os_sendbuf(len=3, data= 01 B7 B8)
14:38:18.198-467,3 os_rcvbyte(timeout=100) -> 01
14:38:18.199-022,9 os_rcvbyte(timeout=100) -> B7
14:38:18.199-533,6 os_rcvbyte(timeout=100) -> B8
14:38:18.214-332,4 os_rcvbyte(timeout=150) -> FF
14:38:18.214-896,8 os_rcvbyte(timeout=50) -> FF
14:38:18.266-140,1 os_rcvbyte(timeout=50) -> TIMEOUT
Got error -8
14:38:18.322-240,6 os_sendbuf(len=3, data= 01 B7 B8)
14:38:18.326-597,5 os_rcvbyte(timeout=100) -> 01
14:38:18.327-135,3 os_rcvbyte(timeout=100) -> B7
14:38:18.327-739,0 os_rcvbyte(timeout=100) -> B8
14:38:18.358-817,0 os_rcvbyte(timeout=150) -> FF
14:38:18.359-491,1 os_rcvbyte(timeout=50) -> FF
14:38:18.411-508,6 os_rcvbyte(timeout=50) -> TIMEOUT
Got error -8
14:38:18.467-626,9 os_sendbuf(len=3, data= 01 B7 B8)
14:38:18.470-427,6 os_rcvbyte(timeout=100) -> 01
14:38:18.471-012,8 os_rcvbyte(timeout=100) -> B7
14:38:18.471-729,7 os_rcvbyte(timeout=100) -> B8
14:38:18.624-736,0 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
=> Logging failed
exiting (cause=0x4)...

C:\Documents and Settings\ABC\Desktop\Audi\ME7 loging>


She is an a6
Logged
kingkhalilz
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 123
« Reply #1 on: August 28, 2014, 12:38:04 PM »
Tried slow 0x00. Tried using nefmoto logger same thing happens when i turn car on...

Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Disconnecting because no response was received for the Tester Present message.
Disconnected

I used nefmoto to read my bin
« Last Edit: September 04, 2014, 12:58:53 PM by kingkhalilz » Logged
gitman
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 12
« Reply #2 on: September 05, 2014, 12:51:32 PM »
i have this same issue such that i have to start the logger with the key in the ignition and turned on (but the engine not started). if i try to start the logger with the engine running, then i have the same issue as the OP.
Logged
kingkhalilz
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 123
« Reply #3 on: November 01, 2014, 03:55:08 PM »
What cable you using?? Ftdi?
Logged
aef
Hero Member
*****

Karma: +69/-46
Offline Offline

Posts: 1600
« Reply #4 on: November 02, 2014, 02:39:49 AM »
easiest solution is a switch in the kline to your dash.

or drive around without dead dash via fuse Wink

there is a thread for the logger by the way... you are not the only person with this problem(s)
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640
« Reply #5 on: November 02, 2014, 03:08:43 AM »
Change samples per second to 15, and baud to 38400. Should work after that.
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
kingkhalilz
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 123
« Reply #6 on: November 02, 2014, 09:24:58 AM »
When i switched cable it worked for me. But these guys are right
Logged
aef
Hero Member
*****

Karma: +69/-46
Offline Offline

Posts: 1600
« Reply #7 on: November 02, 2014, 03:16:35 PM »
Quote from: ddillenger on November 02, 2014, 03:08:43 AM
Change samples per second to 15, and baud to 38400. Should work after that.

worked for me today. great!
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640
« Reply #8 on: November 02, 2014, 04:22:09 PM »
Quote from: aef on November 02, 2014, 03:16:35 PM
worked for me today. great!

Of course it did.

I say it every day.

38400 baud

Set the baud rate to 38400.

lol
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
316LV
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 150
« Reply #9 on: January 15, 2015, 03:56:56 PM »
For anyone searching this in the future:

15 samples and 38400 didn't work for me (2002 Jetta 032HS). I tried slow init, super slow init and all combinations of speeds. Nothing did the job. From reading the ME7Logger thread I was pretty sure it was the cluster messing up communication.

So I took a DPDT switch and wired it as follows: K-line input direct from the ECU and output to the OBDII port on the center pins, then a loop on 5+6, and finally the other ends of the wires I cut on 1+2. Switch one way bypasses everything on the K-line, the opposite way and the K-line is run as normal. Installed the switch in the trim panel just above the fuse block (behind the access door) so it was out of the way yet easily usable.

Now when I want to log without issue, it is as simple as opening the fuse door and flipping the switch. Works great. I was really hoping not to have to cut wiring but apparently that is what has to be done sometimes...

Thanks to those who identified a K-line bypass as a solution! This forum is such a great resource.
Logged
Go ahead and give me negative karma... I don't care if you like what I post princess.
TLS
Full Member
***

Karma: +1/-0
Offline Offline

Posts: 62
« Reply #10 on: January 28, 2015, 08:58:29 PM »
Hi There.
Are you able to post a pic or two or a schematic to show what you did?
Trev
Logged
316LV
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 150
« Reply #11 on: January 31, 2015, 02:14:05 PM »
Quote from: TLS on January 28, 2015, 08:58:29 PM
Hi There.
Are you able to post a pic or two or a schematic to show what you did?
Trev

No problem Trev. I don't have pictures sorry but here is a schematic for you:



It is simple. All you are doing is cutting two wires. K-line from ECU to cluster and K-line to OBD2 port. Both ends of each cut get connected to the switch (1,2,3,and 4). As the picture shows 5 and 6 are just a simple loop to pass the K-line in on 4 to the OBD2 port out on 3.

Caution: I listed the cluster/OBD2 pins from memory. Check your Bentley manual to confirm wiring for your car to ensure accuracy for your application. K-line is usually grey with a white stripe and is easy to identify.

Let me know if I can make it any more clear for you, but hopefully that makes sense. I would grab some pictures but its pissing rain here and they won't really help much more if you can understand the schematic...

So far the above has worked perfectly for me. Logging and flashing are no longer an issue with the switch in 'bypass', and VCDS can communicate with all modules on the K-line with the switch in 'normal'. Tried and tested so to speak. Good luck.
Logged
Go ahead and give me negative karma... I don't care if you like what I post princess.
TLS
Full Member
***

Karma: +1/-0
Offline Offline

Posts: 62
« Reply #12 on: February 01, 2015, 09:34:48 PM »
Champion
Logged
tightmopedman9
Jr. Member
**

Karma: +0/-2
Offline Offline

Posts: 45
« Reply #13 on: October 31, 2022, 03:56:52 PM »
I had the same issue as the OP on a 2002 Audi C5 Allroad, manual transmission for what its worth. I fixed my issue by snipping the K-line right before it entered the cluster. I then spliced a wire to both cut ends and ran that to a SPST switch, which I placed next to the OBDII port. When I want to log, I turn the switch to the OFF position, leaving the cluster out of the k-line bus. When I want to read codes etc, I turn the switch to the ON position.

For my car, the K-line wire going into the cluster was at T32a/28, a green wire with red stripe. The T32a connector is the green one.
Logged
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6035
« Reply #14 on: November 01, 2022, 04:28:41 AM »
It works on pretty much all cars with SLOW-0x00.
You just have to turn ignition on, then start logging, then start engine.
If you want to start logging with the engine running, you have to apply a small patch to the bin, so it allows "upgrading" the session to KWP2000 when the engine is running.
Logged
PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
Pages: [1] 2
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 22, 2024, 04:00:48 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.042 seconds with 16 queries. (Pretty URLs adds 0s, 0q)