|
Title: me7logger - received wrong inverted address 0x0F Post by: Sacula92 on September 15, 2016, 10:14:50 AM I can't get me7logger to log properly on my Golf IV 1.8T, when i start the engine and run me7logger it seems to be logging.
Once i drive or when i wait for a while it just stops, when i try to reconnect i get "received wrong inverted address 0x0F (see image below). I'm using the following settings in the ecu file, otherwise it does not connect at all when ignition is on: Connect = SLOW-0x00 DoubleDelay = 12 For my other Golf IV 2.0 AZJ it works fine, don't need to set SLOW-0x00 and DoubleDelay and i get no "errors". What is causing this? (http://i.imgur.com/SUu6sAN.jpg) Title: Re: me7logger - received wrong inverted address 0x0F Post by: nyet on September 15, 2016, 10:16:45 AM try unplugging cluster or cluster fuse, slower baud rate, or dedicated k-line
Title: Re: me7logger - received wrong inverted address 0x0F Post by: Sacula92 on September 16, 2016, 02:22:26 AM Okay, yesterday i tried a lower baud rate.
I found out how to get it working (not sure if it is due to the lower baudrate, will try higher baudrate later). - Turn ignition on, start me7logger, start the engine > works fine - Turn ignition off, keep the key in, turn ignition on, start me7logger > does not work (same thing) - Take key out, put key back in, turn ignition on, start me7logger, start engine > works fine Is this normal behavior? If it is not, any idea why this happens? Anyway I'm happy, i'm able to log now. Thanks. Title: Re: me7logger - received wrong inverted address 0x0F Post by: nyet on September 16, 2016, 10:05:12 AM Yea, more than a few people have reported having to do this for some reason.
I'm guessing it has something to do with not being able to *start* ME7L due to cluster/ecu interference on the k-line once the car is already running. Title: Re: me7logger - received wrong inverted address 0x0F Post by: fknbrkn on September 16, 2016, 10:24:55 AM start your engine
pull out fuse #11 connect me7l thats all Title: Re: me7logger - received wrong inverted address 0x0F Post by: vwaudiguy on September 16, 2016, 10:53:37 AM start your engine pull out fuse #11 connect me7l thats all No gear reference for me7l, no tach, speedo Possibly alternator not charging (haven't tested this, but heard it mentioned a few times) Just set me7L correctly, and the fuse removal method isn't needed. Title: Re: me7logger - received wrong inverted address 0x0F Post by: nyet on September 16, 2016, 11:05:57 AM Just set me7L correctly Which settings? Somebody should compile a list of ECUs and settings... Title: Re: me7logger - received wrong inverted address 0x0F Post by: vwaudiguy on September 16, 2016, 02:18:16 PM Which settings? Try this 19200 baud rate in the .ecu file samples per sec to 14 Title: Re: me7logger - received wrong inverted address 0x0F Post by: Sacula92 on September 19, 2016, 01:59:06 AM I prefer not having to pull any fuses.
Perhaps it also depends on what instrument cluster you have, or is that very unlikely? I'll try those settings later, thanks. @fukenbroken I also have an AUM, do you have the same ECU? If so, do you have the same problem? Title: Re: me7logger - received wrong inverted address 0x0F Post by: adam- on September 19, 2016, 04:38:27 AM Yeah, I think that's why I've got no gear reference. How do you add baud rate to the ECU file? I know you can do it in the command line, but I like the GUI. Tempted to edit the current one to add automatic revision/adjustable baud.
Title: Re: me7logger - received wrong inverted address 0x0F Post by: fknbrkn on September 19, 2016, 08:44:13 AM I prefer not having to pull any fuses. Perhaps it also depends on what instrument cluster you have, or is that very unlikely? I'll try those settings later, thanks. @fukenbroken I also have an AUM, do you have the same ECU? If so, do you have the same problem? no i has DR box. its immo2 and no problems with connection at all in fact the reason of this issues is a flash. hj and some others are not friendly to me7l |