NefMoto

Technical => Data Logging => Topic started by: vtraudt on May 20, 2020, 04:26:17 AM



Title: 2002 Golf GTI - pulling instrument fuse for logging
Post by: vtraudt on May 20, 2020, 04:26:17 AM
I need to pull the instrument cluster fuse (#11), otherwise Me7Logger is not working.
Is there a way around?
And why is it required on this car, and not on others?


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: dal on May 20, 2020, 04:52:08 AM
On my car was the same thing.
Once I saw someone here telling to connect first with Nefmoto Flasher, then use ME7Logger. Works like a charm.


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: vtraudt on May 20, 2020, 05:25:23 AM
On my car was the same thing.
Once I saw someone here telling to connect first with Nefmoto Flasher, then use ME7Logger. Works like a charm.

Leave fuse in, start Nefmoto flasher and 'connect'. Leave flasher running/open and THEN open Me7Logger and log?


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: fknbrkn on May 20, 2020, 05:52:53 AM
There is only two options - yes or no
Is it necessary to asking those basic things and not to try yourself?


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: aef on May 20, 2020, 06:06:30 AM
ignition on, logger on, car on without ignition off

is this working for you?


try this in your software
http://nefariousmotorsports.com/forum/index.php?topic=14119.msg114367#msg114367


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: vtraudt on May 20, 2020, 06:13:44 AM
There is only two options - yes or no
Is it necessary to asking those basic things and not to try yourself?

Are you trying to answer the question or only bored from being locked up? Yes or No?


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: dal on May 20, 2020, 06:29:11 AM
Leave fuse in, start Nefmoto flasher and 'connect'. Leave flasher running/open and THEN open Me7Logger and log?

Yes, leave fuse in. I Start nefmoto flasher, connect, then disconnect, close the software, then start ME7logger normal.


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: vtraudt on May 20, 2020, 07:10:46 AM
Yes, leave fuse in. I Start nefmoto flasher, connect, then disconnect, close the software, then start ME7logger normal.

Thanks, will give it a try this afternoon.


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: vtraudt on May 20, 2020, 10:43:15 AM
Yes, leave fuse in. I Start nefmoto flasher, connect, then disconnect, close the software, then start ME7logger normal.

I just tried, did not work.
Just hate driving around without rpm and speed indication.


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: BlackT on May 20, 2020, 10:44:47 AM
The only solution is to pull separate Kline from ECU


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: vtraudt on May 20, 2020, 11:58:41 AM
The only solution is to pull separate Kline from ECU

The VisualMe7Logger with live data helps when I have someone else to drive.
Wouldn't know how to pull a separate K-line from ECU (to instrument cluster), what pin to which pin?


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: BlackT on May 20, 2020, 03:38:09 PM
Climatronic, stereo, cluster, ECU, central electronic... They are all connected to OBD via K-line.  You need to pull wire from ECU to OBD direct. Or make one more OBD connector for ECU only, or put switch that discconect other stuff from K line.
If you don't know how to do it by yourself, there is a shemaric somewere on forum. In some sticky tread i think


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: aef on May 21, 2020, 04:28:53 AM
ignition on, logger on, car on without ignition off

is this working for you?


try this in your software
http://nefariousmotorsports.com/forum/index.php?topic=14119.msg114367#msg114367

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

have you tried any of this? its not necessary to use separate line or pull fuse



Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: tao13 on January 18, 2021, 07:25:47 AM
Hi all. I have the same problem on my car.
All next tried cases use same cable and same laptop.
Logger works on speed 10400 for only 10-20 seconds, with or without ignition. If i remove the instrument cluster fuse can make log at 56000.
If i make the log directly to ecu on the bench, it works at 115200 , SO ECU IS NOT A CAUSE!
I tried on 2 other cars and there don't have problem and can make log at 56000.
I got an instrument cluster from one of the car witch work at 56000 and put it in my car. NOTHING, same problem, log not work, SO IS NOT THE INSTRUMENT CLUSTER PROBLEM.
What can it be? i don't have other can slave in the car only climatronic (skoda octravia 1U2).



Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: vtraudt on January 18, 2021, 08:10:03 AM
Climatronic, stereo, cluster, ECU, central electronic... They are all connected to OBD via K-line.  You need to pull wire from ECU to OBD direct.

Are the other 'users' of the K-line 'cutting' the ECU off?
Why would running an additional cable from the ECU to the OBD change that (the other users are still connected to the K-line so we have the cluster running).

I assume other cars (A4 1.8T of similar generation?) don't have the issue. What is different?


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: nyet on January 18, 2021, 12:40:31 PM
Are the other 'users' of the K-line 'cutting' the ECU off?
because k-line is a shit standard. single wire, shared bus hack.


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: tao13 on January 18, 2021, 12:54:00 PM
I agree with you Nyet but it is the same shit to all cars and logger works on some car.


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: BlackT on January 18, 2021, 03:38:39 PM
Are the other 'users' of the K-line 'cutting' the ECU off?
Why would running an additional cable from the ECU to the OBD change that (the other users are still connected to the K-line so we have the cluster running).

I assume other cars (A4 1.8T of similar generation?) don't have the issue. What is different?

don't skip details. Read topic from begining

The only solution is to pull separate Kline from ECU

What is different from other cars I don't know. Also bad cable can make problems. I have cable that work excelent on any B6 chaiss, but it can't work on B5 and C5 on stock OBD port. Porr lattency and there is a problem

ECU is connected to cluster via W wire(not K-line) than tru cluster is going on K-line OBD port. So i depend on cluster also


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: nyet on January 18, 2021, 03:55:11 PM
I agree with you Nyet but it is the same shit to all cars and logger works on some car.



Marginal is marginal


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: tao13 on January 18, 2021, 11:09:51 PM

ECU is connected to cluster via W wire(not K-line) than tru cluster is going on K-line OBD port. So i depend on cluster also

BlackT, i wrote upstairs, i put on my car a cluster witch work with my cable to make log at 56000. So i think is not from cluster.
I tried 2 kind of cables , vag commander cable and galletto (clone). Both make problems on my car. 


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: vtraudt on January 19, 2021, 06:29:12 AM

Marginal is marginal

So running another line will improve the 'signal quality' and move (on Golf Mk4 platform only) from 'marginal' (or not working) to 'acceptable' (and working, like on other platforms)?


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: nyet on January 19, 2021, 10:15:14 AM
So running another line will improve the 'signal quality' and move (on Golf Mk4 platform only) from 'marginal' (or not working) to 'acceptable' (and working, like on other platforms)?


Running a *dedicated* line will do this (that is to say, make sure nothing else is connected on the k-line anywhere else). Or, rather, if it doesn't work, it will prove something else is wrong.


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: tao13 on January 19, 2021, 01:02:32 PM
Me7logger use k-line or CANBUS?


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: nyet on January 19, 2021, 01:07:32 PM
Me7logger use k-line or CANBUS?

k-line. No CANBUS logging on ME7.1


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: tao13 on January 19, 2021, 01:09:09 PM
I fogot to specify upstairs , my ecu is me7.5


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: nyet on January 19, 2021, 01:10:45 PM
I fogot to specify upstairs , my ecu is me7.5

Doesn't matter, me7logger uses kline due to 7.1 needing it.

No good canbus logging for me7.5 anyway.


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: tao13 on January 19, 2021, 01:37:47 PM
Thanks Nyet
Like i said on the bench the ecu works fine at 115200 with the same cable and same laptop like i use on the car.
Maybe the kline wire is bad on the obd adapter or some negative cable.
Will try to get directly a wire for logger directly from ecu but i leave the standard kline wire in circuit, because if i cut it i think cluster will not comunicate with ecu after this.


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: terminator on January 19, 2021, 03:51:48 PM
I think you can solve this problem by using the NefMoto flasher to open a diagnostic session (just press "Connect"). Only after you have done this, connect ME7Logger.


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: nyet on January 19, 2021, 04:24:24 PM
Thanks Nyet
Like i said on the bench the ecu works fine at 115200 with the same cable and same laptop like i use on the car.
Maybe the kline wire is bad on the obd adapter or some negative cable.
Will try to get directly a wire for logger directly from ecu but i leave the standard kline wire in circuit, because if i cut it i think cluster will not comunicate with ecu after this.


Add a switch to be able to swap the ecu from obd connector to stock kline


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: tao13 on January 19, 2021, 11:32:58 PM
Add a switch to be able to swap the ecu from obd connector to stock kline
I will try but first must see if the k-line in obd conector arrive from cluster or from ecu. i think it arrive from ecu to cluster and from cluster to obd conector.
Please tell me , le7logger send a one request to ecu for all selected variables or 1 request for 1 variable?
Thanks


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: nyet on January 20, 2021, 12:28:07 AM
I will try but first must see if the k-line in obd conector arrive from cluster or from ecu.


that totally doesn't matter. clip the wire from the ecu. clip the wire from the obd connecgtor. run a wire from the the ecu to the obd connector, and add a switch that switches between that wire and the kline to the harness. done.


Title: Re: 2002 Golf GTI - pulling instrument fuse for logging
Post by: tao13 on January 20, 2021, 02:57:47 AM
Thanks Nyet
Can you please tell me about reuest info sent and recived from ecu? Sincerly i try to make something with arduino and my k-line protocol not work for all pids, only few. I think what Me7logger use is other type of protocol or how it access the info from ecu. Thanks