Pages: [1]
Author Topic: Having Trouble Loggin MKiv Me7Logger  (Read 814 times)
1slicks4
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 29



« on: June 07, 2019, 06:07:26 PM »

Im trying to data log a MKIV and i keep getting this. Can someone help me understand what i am missing?


-> Reading log config file C:\ME7Logger\logs\VW_1.8T_AWP_06A906032HS_template.cfg .... done
-> Reading ecu characteristics file C:\ME7Logger\ecus\VW_1.8T_AWP_06A906032HS.ecu .... done
Used Ecu definition is:
[Communication]
Connect      = SLOW-0x11
Communicate  = HM0
LogSpeed     = 56000

[Identification]
HWNumber           = "0261207446"
SWNumber           = "1037362111"
PartNumber         = "06A906032HS"
SWVersion          = "0007"
EngineId           = "1.8L R4/5VT"

Logged variables are:
#no.: name                , alias                           , addr  ,sz, bitm, S, I,  A         ,   B, unit
#------------------------------------------------------------------------------------------------------------
#001: dlahi_w             , LambdaPID-I                     , 383AF6, 2, 0000, 1, 0, 3.05176e-005,   0, '-'
#002: dlahp_w             , LambdaPID-P                     , 382832, 2, 0000, 1, 0, 3.05176e-005,   0, '-'
#003: dwkrz_0             , IgnitionRetardCyl1              , 380A8F, 1, 0000, 1, 0,        0.75,   0, '░KW'
#004: dwkrz_1             , IgnitionRetardCyl4              , 380A90, 1, 0000, 1, 0,        0.75,   0, '░KW'
#005: dwkrz_2             , IgnitionRetardCyl2              , 380A91, 1, 0000, 1, 0,        0.75,   0, '░KW'
#006: dwkrz_3             , IgnitionRetardCyl3              , 380A92, 1, 0000, 1, 0,        0.75,   0, '░KW'
#007: fzabg_w_0           , CountMisfireCyl1                , 38185E, 2, 0000, 0, 0,           1,   0, '#'
#008: fzabg_w_1           , CountMisfireCyl4                , 381860, 2, 0000, 0, 0,           1,   0, '#'
#009: fzabg_w_2           , CountMisfireCyl2                , 381862, 2, 0000, 0, 0,           1,   0, '#'
#010: fzabg_w_3           , CountMisfireCyl3                , 381864, 2, 0000, 0, 0,           1,   0, '#'
#011: gangi               , SelectedGear                    , 3809A4, 1, 0000, 0, 0,           1,   0, 'gear'
#012: lamsbg_w            , AirFuelRatioDesired             , 381F78, 2, 0000, 0, 0, 0.000244141,   0, '-'
#013: lamsoni_w           , AirFuelRatioCurrent             , 381B2E, 2, 0000, 0, 0, 0.000244141,   0, '-'
#014: ldimn_w             , BoostPID-I-Min                  , 38234E, 2, 0000, 1, 0,       0.005,   0, '%'
#015: ldimx_w             , BoostPID-I-Max                  , 382356, 2, 0000, 1, 0,       0.005,   0, '%'
#016: ldtvm               , WastegateDutyCycle              , 380AD4, 1, 0000, 0, 0,    0.390625,   0, '%'
#017: plsol               , BoostPressureDesired            , 380A09, 1, 0000, 0, 0,          10,   0, 'mbar'
#018: plsol_w             , BoostPressureDesired            , 381E92, 2, 0000, 0, 0,   0.0390625,   0, 'mbar'
#019: pvdkds_w            , BoostPressureActual             , 381E2C, 2, 0000, 0, 0,   0.0390625,   0, 'mbar'
#020: pvdks_w             , BoostPressureActual             , 381E32, 2, 0000, 0, 0,   0.0390625,   0, 'mbar'
#021: rkrn_w_0            , KnockVoltageCyl1                , 384B5E, 2, 0000, 0, 0,   0.0195313,   0, 'V'
#022: rkrn_w_1            , KnockVoltageCyl4                , 384B60, 2, 0000, 0, 0,   0.0195313,   0, 'V'
#023: rkrn_w_2            , KnockVoltageCyl2                , 384B62, 2, 0000, 0, 0,   0.0195313,   0, 'V'
#024: rkrn_w_3            , KnockVoltageCyl3                , 384B64, 2, 0000, 0, 0,   0.0195313,   0, 'V'
#025: tans                , IntakeAirTemperature            , 380A44, 1, 0000, 0, 0,        0.75,  48, '░C'
#026: wkr_0               , IgnRetardKnockControlCyl1       , 00F9D2, 1, 0000, 0, 0,       -0.75,   0, '░KW'
#027: wkr_1               , IgnRetardKnockControlCyl4       , 00F9D3, 1, 0000, 0, 0,       -0.75,   0, '░KW'
#028: wkr_2               , IgnRetardKnockControlCyl2       , 00F9D4, 1, 0000, 0, 0,       -0.75,   0, '░KW'
#029: wkr_3               , IgnRetardKnockControlCyl3       , 00F9D5, 1, 0000, 0, 0,       -0.75,   0, '░KW'
#030: wkrdya_0            , AdaptedIgnitionAngleDynRange1   , 383204, 1, 0000, 0, 0,       -0.75,   0, '░KW'
#031: wkrdya_1            , AdaptedIgnitionAngleDynRange2   , 383205, 1, 0000, 0, 0,       -0.75,   0, '░KW'
#032: wkrdya_2            , AdaptedIgnitionAngleDynRange3   , 383206, 1, 0000, 0, 0,       -0.75,   0, '░KW'
#033: wkrdya_3            , AdaptedIgnitionAngleDynRange4   , 383207, 1, 0000, 0, 0,       -0.75,   0, '░KW'
#034: wped_w              , AccelPedalPosition              , 381C2E, 2, 0000, 0, 0,   0.0015259,   0, '% PED'
#035: zwist               , IgnitionTimingAngle             , 00FA0A, 1, 0000, 1, 0,        0.75,   0, '░KW'
#036: zwout               , IgnitionTimingAngleOverall      , 00FA0C, 1, 0000, 1, 0,        0.75,   0, '░KW'
Logged data size is 54 bytes.
Really logged are 30 entries with 54 bytes.
Start connecting to ECU at 07.06.2019 20:05:46.793
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:\ME7Logger\logs\Test Andrewlog2.csv
-> Start logging (logdata size=54, 20 samples/second, 56000 baud) at 07.06.2019 20:05:52.836
Press ^C to stop logging
Got error -8
20:05:53.312-329,3 os_sendbuf(len=3, data= 01 B7 B8)
20:05:53.315-862,7 os_rcvbyte(timeout=100) -> 01
20:05:53.315-967,2 os_rcvbyte(timeout=100) -> B7
20:05:53.316-389,0 os_rcvbyte(timeout=100) -> B8
20:05:53.467-434,2 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
20:05:53.524-938,4 os_sendbuf(len=3, data= 01 B7 B8)
20:05:53.538-101,6 os_rcvbyte(timeout=100) -> 01
20:05:53.538-228,8 os_rcvbyte(timeout=100) -> B7
20:05:53.538-682,8 os_rcvbyte(timeout=100) -> B8
20:05:53.690-491,4 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
20:05:53.747-779,2 os_sendbuf(len=3, data= 01 B7 B8)
20:05:53.762-728,1 os_rcvbyte(timeout=100) -> 01
20:05:53.762-837,4 os_rcvbyte(timeout=100) -> B7
20:05:53.763-709,7 os_rcvbyte(timeout=100) -> B8
20:05:53.917-124,1 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
20:05:53.974-962,3 os_sendbuf(len=3, data= 01 B7 B8)
20:05:53.986-830,0 os_rcvbyte(timeout=100) -> 01
20:05:53.987-051,0 os_rcvbyte(timeout=100) -> B7
20:05:53.987-669,4 os_rcvbyte(timeout=100) -> B8
20:05:54.138-471,2 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
20:05:54.195-865,5 os_sendbuf(len=3, data= 01 B7 B8)
20:05:54.210-311,0 os_rcvbyte(timeout=100) -> 01
20:05:54.210-430,3 os_rcvbyte(timeout=100) -> B7
20:05:54.210-858,9 os_rcvbyte(timeout=100) -> B8
20:05:54.362-455,1 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
20:05:54.419-962,5 os_sendbuf(len=3, data= 01 B7 B8)
20:05:54.434-372,5 os_rcvbyte(timeout=100) -> 01
20:05:54.434-587,5 os_rcvbyte(timeout=100) -> B7
20:05:54.435-494,0 os_rcvbyte(timeout=100) -> B8
20:05:54.587-026,2 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
20:05:54.644-748,4 os_sendbuf(len=3, data= 01 B7 B8)
20:05:54.658-192,4 os_rcvbyte(timeout=100) -> 01
20:05:54.658-377,7 os_rcvbyte(timeout=100) -> B7
20:05:54.658-938,1 os_rcvbyte(timeout=100) -> B8
20:05:54.809-999,1 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
20:05:54.867-370,4 os_sendbuf(len=3, data= 01 B7 B8)
20:05:54.881-842,2 os_rcvbyte(timeout=100) -> 01
20:05:54.881-978,9 os_rcvbyte(timeout=100) -> B7
20:05:54.882-840,2 os_rcvbyte(timeout=100) -> B8
20:05:55.035-185,8 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
20:05:55.093-352,5 os_sendbuf(len=3, data= 01 B7 B8)
20:05:55.105-804,2 os_rcvbyte(timeout=100) -> 01
20:05:55.105-967,0 os_rcvbyte(timeout=100) -> B7
20:05:55.106-554,7 os_rcvbyte(timeout=100) -> B8
20:05:55.258-232,0 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
20:05:55.315-702,0 os_sendbuf(len=3, data= 01 B7 B8)
20:05:55.328-982,3 os_rcvbyte(timeout=100) -> 01
20:05:55.329-516,9 os_rcvbyte(timeout=100) -> B7
20:05:55.330-340,9 os_rcvbyte(timeout=100) -> B8
20:05:55.482-168,5 os_rcvbyte(timeout=150) -> TIMEOUT
Got error -8
=> Logging failed
exiting (cause=0x4)..
Logged
1slicks4
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 29



« Reply #1 on: June 07, 2019, 06:12:28 PM »

Also tried to pull his file and am not able to get his file either.

Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: °6A906032HS 1.8L R4/5VT     G01 0007

Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Reading ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
ECU reports that security access request was rejected.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00880000.
Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
Memory layout validation failed.
Starting to read data block.
Requesting upload from ECU for address range 0x00800000 to 0x00803FFF.
Request upload from ECU failed, ECU reports service is not supported. Request upload may have been disabled by aftermarket engine software.
Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete.
Finished forcing ECU to recognize that failed read operation is complete.
Reading ECU flash memory failed.
100% complete.
Logged
nyet
Administrator
Hero Member
*****

Karma: +432/-55
Online Online

Posts: 9803


WWW
« Reply #2 on: June 07, 2019, 06:13:55 PM »

Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
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.
1slicks4
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 29



« Reply #3 on: June 07, 2019, 06:19:49 PM »

Will this also stop us from logging the car as well?


Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
Logged
1slicks4
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 29



« Reply #4 on: June 07, 2019, 06:46:29 PM »

This ECU was originally tuned with EURODYNE and cloned after a ECU failed due to a 02 sensor short. Just trying to know what im up against here. Any help is much appreciated.
Logged
vwaudiguy
Hero Member
*****

Karma: +47/-35
Offline Offline

Posts: 1982



« Reply #5 on: June 07, 2019, 07:11:48 PM »

This ECU was originally tuned with EURODYNE and cloned after a ECU failed due to a 02 sensor short. Just trying to know what im up against here. Any help is much appreciated.

Tune/log using the Eurodyne suite.
Logged

"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
1slicks4
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 29



« Reply #6 on: June 07, 2019, 09:47:20 PM »

Tune/log using the Eurodyne suite.

Okay, Thanks for the input. We are trying to get him away from Eurodyne to be honest and looking to bring in a different tuner that is more a flash tune. The original tuner that tuned it is not available any longer and of course he was never given the file and things arent really adding up. Looks like we are gonna flash tune it but the way its looking it will likely need a new ECU!
Logged
Blazius
Hero Member
*****

Karma: +26/-20
Offline Offline

Posts: 619



« Reply #7 on: June 08, 2019, 03:02:25 AM »

Connect using 0x00 protocol. sometimes the validation fails because of the 5 byte validation ( or something like that, i forgot.) is not correct(0x4 code). I can only connnect using 0x00 and its stock ecu with ch340.
« Last Edit: June 08, 2019, 06:32:47 AM by Blazius » Logged
1slicks4
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 29



« Reply #8 on: June 08, 2019, 06:20:20 AM »

Connect using 0x00 protocol. sometimes the validation fails because of the 5 byte validation ( or something like that) is not correct(0x4 code). I can only connnect using 0x00 and its stock ecu.

I’ll give this a try.  Thanks for the info.


Its all because I own a B5 and LOVE IT!!!
Logged
SB_GLI
Hero Member
*****

Karma: +93/-7
Offline Offline

Posts: 1018


« Reply #9 on: June 10, 2019, 05:55:16 AM »

pull the cluster fuse and it will log.  MKIV's are bitches to log with the cluster
Logged
1slicks4
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 29



« Reply #10 on: June 10, 2019, 05:57:25 AM »

pull the cluster fuse and it will log.  MKIV's are bitches to log with the cluster

Thanks for the info


Its all because I own a B5 and LOVE IT!!!
Logged
Pages: [1]
  Print  
 
Jump to:  

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