Pages: [1]
Author Topic: Using VagTacho to unlock cluster for ME7  (Read 5186 times)
jcolossal
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4


« on: August 05, 2017, 07:48:38 AM »

I wasn't sure where to post this, hopefully this is correct.

Car is a Euro B5 S4 (2000).

Originally the ECU was a 551D. Flashed an Mbox over the top. 

In the past I have been able to 'unlock' (for lack of a better word) the cluster using vagtacho, which then allowed me to successfully use me7logger. Without unlocking the cluster, me7logger will not work.

It's been a number of years since I have messed with B5's, but im back at it.

I tried for many hours to get this going again tonight, but it seems that when I try to read the immob/cluster it will not work.

Can anyone give any insight into why this might be?
Logged
aef
Hero Member
*****

Karma: +70/-46
Offline Offline

Posts: 1601


« Reply #1 on: August 06, 2017, 02:16:03 AM »

What do you mean by unlock? Check immo status of your ecu with vcds. adaptions channel 91.
If immo is on you can try to start the car, pull the dash fuse, try to start logger.

Or you can turn ignition on, start logger, start car, this maybe works too.

For better support, i would recommend to post me7logger output in the correct thread.
maybe it's some configuration problem, check ecu file and edit communication settings. 
Logged
jcolossal
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4


« Reply #2 on: August 06, 2017, 04:53:53 AM »

I figured it out.

Me7 logger will not work without bypassing the cluster (or not when i have tried with the car off or on). It cannot connect.

I used vag tacho (VAG_K+CAN_Commander_v2.5) to read the immob on the cluster (vdo).

For some reason, in doing this, the k-line is now active at the port and me7 logger will work as intended.

I had the wrong com port selected in the .inti file for vagtacho (stupid mistake).

Logged
aef
Hero Member
*****

Karma: +70/-46
Offline Offline

Posts: 1601


« Reply #3 on: August 06, 2017, 05:10:26 AM »

So what have you done to the cluster in detail?
Pls help me to understand it.
Logged
4ringpieces
Full Member
***

Karma: +4/-4
Offline Offline

Posts: 232


« Reply #4 on: August 07, 2017, 05:14:40 AM »

Think he's trying to say that by reading the cluster with vagtacho is somehow stopping the cluster block?

Or is he reading the cluster epprom and then it magically stops cluster blocking.

Either way I'd be interested too as I find it's S3's that give me headaches logging.
Logged
jcolossal
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4


« Reply #5 on: August 07, 2017, 08:06:29 AM »

yes, 4rings is correct.

for whatever reason, using vagtacho to read the immo eeprom unblocks the cluster. then me7 logger will work. if i dont do this step with vagtacho, me7 logger times out and will not work.

i tried to start me7 logger and then start the car, it does not work on my car. i don't know why.

i couldn't be bothered to run a direct k-line so this is the next easiest way. next time i have the interior apart i may bypass the cluster with a new k-line.
Logged
aef
Hero Member
*****

Karma: +70/-46
Offline Offline

Posts: 1601


« Reply #6 on: August 07, 2017, 08:59:05 AM »

On my S3 AMK this works when ignition is on:

Code:
[Communication]
Connect      = SLOW-0x00 ; Possible values: SLOW-0x11, FAST-0x10
DoubleDelay  = 12
Communicate  = HM0          ; Possible values: HM0, HM2-0x10
LogSpeed     = 38400        ; Possible values: 10400, 14400, 19200, 38400, 56000, 57600, 125000

then start the car
Logged
Pages: [1]
  Print  
 
Jump to:  

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