NOTORIOUS VR
Administrator
Hero Member
Karma: +58/-7
Offline
Posts: 1056
|
|
« on: August 18, 2012, 07:14:02 AM »
|
|
|
I don't get why, it works perfectly fine on 2.7T's but on all 1.8T's that I've tried it on, ECUx will connect and start to log for 2-3 then just stop/freeze.
Anyone have suggestions?
|
|
|
Logged
|
|
|
|
elRey
|
|
« Reply #1 on: August 18, 2012, 06:33:04 PM »
|
|
|
no help, but I get a lot of that on my 2002 1.8T ECU also. last longer than 2-3 sec, more like 1min for me.
|
|
|
Logged
|
|
|
|
Gonzo
|
|
« Reply #2 on: August 22, 2012, 06:14:14 AM »
|
|
|
Any reason why you are using ECUx over ME7Logger?
Either way I would try logging less variables/slower.
|
|
|
Logged
|
|
|
|
NOTORIOUS VR
Administrator
Hero Member
Karma: +58/-7
Offline
Posts: 1056
|
|
« Reply #3 on: August 22, 2012, 06:16:24 AM »
|
|
|
Any reason why you are using ECUx over ME7Logger?
Either way I would try logging less variables/slower.
I suppose because it's simple/familiar... also I don't have/know any variables for the 1.8T ECU... or will the ones from the S4 work? If you have something for ME7L that will allow me to log 1.8T boxes (Wideband ECU's) would be much appreciated.
|
|
|
Logged
|
|
|
|
phila_dot
|
|
« Reply #4 on: August 22, 2012, 06:55:53 AM »
|
|
|
I suppose because it's simple/familiar... also I don't have/know any variables for the 1.8T ECU... or will the ones from the S4 work? If you have something for ME7L that will allow me to log 1.8T boxes (Wideband ECU's) would be much appreciated.
The variables will be the same. Create the *.ecu file and go from there.
|
|
|
Logged
|
|
|
|
Gonzo
|
|
« Reply #5 on: August 22, 2012, 01:41:20 PM »
|
|
|
The variables will be the same.
Create the *.ecu file and go from there.
This. Plus ME7L comes with basic config files with enough variables to get you started.
|
|
|
Logged
|
|
|
|
littco
|
|
« Reply #6 on: August 22, 2012, 01:56:39 PM »
|
|
|
Only way I found to get 1.8t to work properly with me7 logger without it crashing out is to run a pure Kline from the ecu either put a 3 way switch on the obd port and run that and normal Kline switching when logging to pure Kline.
Or make up a cable to connect your flash cable for me7 lOgger.
|
|
|
Logged
|
|
|
|
NOTORIOUS VR
Administrator
Hero Member
Karma: +58/-7
Offline
Posts: 1056
|
|
« Reply #7 on: August 22, 2012, 07:58:52 PM »
|
|
|
Really? That would suck for sure.
I am going to try ME7L next time I have access to a 1.8T... I will also try to reduce the number of things logged in ECUx and see if that helps.
I know for a fact that I've once logged a 225HP TT and it worked fine. But with the two wideband 1.8T's I've tried so far both exhibit the same issue (at first I thought it was an issue with the first car).
|
|
|
Logged
|
|
|
|
littco
|
|
« Reply #8 on: August 23, 2012, 12:27:18 AM »
|
|
|
I'm sure there is a post on this, with instructions and diagrams in how to wire it in.
I have to admit I've always logged as much as I can so maybe that is the issue, but with the pure Kline it's always allowed me to logg as much as I wanted in one go.
|
|
|
Logged
|
|
|
|
prj
|
|
« Reply #9 on: August 23, 2012, 02:47:05 AM »
|
|
|
Only way I found to get 1.8t to work properly with me7 logger without it crashing out is to run a pure Kline from the ecu either put a 3 way switch on the obd port and run that and normal Kline switching when logging to pure Kline.
Or make up a cable to connect your flash cable for me7 lOgger.
Try different settings. Try FAST-0x01, SLOW-0x11 and SLOW-0x00
|
|
|
Logged
|
|
|
|
NOTORIOUS VR
Administrator
Hero Member
Karma: +58/-7
Offline
Posts: 1056
|
|
« Reply #10 on: August 23, 2012, 06:41:15 AM »
|
|
|
^^I'll give that a try though thanks I'm sure there is a post on this, with instructions and diagrams in how to wire it in.
I have to admit I've always logged as much as I can so maybe that is the issue, but with the pure Kline it's always allowed me to logg as much as I wanted in one go.
I don't want to modify other peoples cars like that, that's the problem
|
|
|
Logged
|
|
|
|
Gonzo
|
|
« Reply #11 on: August 23, 2012, 01:01:24 PM »
|
|
|
Only way I found to get 1.8t to work properly with me7 logger without it crashing out is to run a pure Kline from the ecu either put a 3 way switch on the obd port and run that and normal Kline switching when logging to pure Kline.
Or make up a cable to connect your flash cable for me7 lOgger.
Or reduce the sample down to 15hz Or pull the cluster fuse (but then you don't know how fast you are going).
|
|
« Last Edit: August 23, 2012, 01:12:52 PM by NOTORIOUS VR »
|
Logged
|
|
|
|
NOTORIOUS VR
Administrator
Hero Member
Karma: +58/-7
Offline
Posts: 1056
|
|
« Reply #12 on: August 23, 2012, 01:13:34 PM »
|
|
|
^^ sorry about the edit... I hit modify instead of reply w/ quote. This forum software is horrible. Or reduce the sample down to 15hz Or pull the cluster fuse (but then you don't know how fast you are going).
All good suggestions, thanks. Anyone have an idea why we have this issue? Conflicting data on the K-line?
|
|
|
Logged
|
|
|
|
littco
|
|
« Reply #13 on: August 23, 2012, 02:13:14 PM »
|
|
|
^^I'll give that a try though thanks I don't want to modify other peoples cars like that, that's the problem I totally agree, it was my car so didn't matter but it's a shame it doesn't work off the bat.
|
|
|
Logged
|
|
|
|
kenmac
Full Member
Karma: +6/-0
Offline
Posts: 161
|
|
« Reply #14 on: September 07, 2012, 07:39:47 PM »
|
|
|
Anyone have an idea why we have this issue? Conflicting data on the K-line?
The cluster seems to put a lot of noise on the k-line. Pull the fuse and the k-line is silent. I almost always log this way as I don't really care about vehicle speed. You usually have a good idea of your speed based on the gear and engine sound. With cluster fuse in, I log at 10 hz max, and there must be less than 40 bytes per cycle. With the fuse out, I log at 20 hz, and many many more variables. It's almost limitless this way.
|
|
|
Logged
|
|
|
|
|