NefMoto

Hello,

First of all I want to say a big thank you to all Nefmoto members and a special thanks to everybody who's idea was to start this awesome forum.
It's definitely a Bible for all who want to understand how to tune a car and much more.
I'm new to this forum and to tuning generally.
My current problem is that the VisualME7logger connects only when the ignition is off.

As soon as I turn the ignition on it disconnects and I get the message:

Error! Exit code:4
=>could not connect to ECU, exiting ...
exiting (cause=0x4)...


Also if I pull dash fuse on the running engine I have no problem to connect.

It would be great if anybody could help me understand what is going on.

to the car:
A3 8L AUQ Tiptronic.

to the cable:
EBAY VAG COM FTDI (BLUE CABLE)

Many thanks in Advance.

Split topic.

Known issue.

some clusters interfere with logging.

Run a separate kline to the ecu when logging or log with cluster unplugged.

Could you please tell which one is the K-Line and how to connect it to the ECU?

pin43 on the big connector because we are talking about me7 ecu

Thank you

Set connection method to SLOW-0x00.
Set the speed to the maximum that it allows.
Turn on the ignition.
Connect, start logging.

Start car.

Should work just fine on AUQ.

I just want to share my observations and experience how I manage ME7looger to get to work.

Somewhere in the forum I have read that connecting the "NefMoto VW Audi ME7 ECU Flasher", disconnecting it and than connecting the ME7logger should work.
it was explained that some IMMOS are blocking the connection and "NefMoto VW Audi ME7 ECU Flasher" is disabling it while connecting.

I have tried as described and it worked.

Interesting theory. Wish we had source code for both to fix the logger, if true.

This will maintain vfzg working on the ECU?
Because in my car I have to pull out the cluster fuse to use ME7logger. Consequence of this, the ECU dont receive vehicle speed anymore (goes from cluster do ECU). And I cant use antilag or NLS safely.

I have an A3 narrowband ME7.5 converted to wideband (032S to 032LP). I use an 032HP file (from GTI MK4), so my ECU can't communicate with the cluster (my A3 and GTI uses differents protocols).

set connection mode to 0x00 and set samples/ second to 50 ... then the line clears up and u dont need to pull fuse.

Might work, but note that some ecus don't like connection mode 0x00 either.

well it depends on the protocol, 0x00 should be the proper 5 baud init & handshake for KWP1281 which is what me7.5 uses , thats how I got the CH chip working too.

I will try this later. Hope it works. I will give an feedback.
Thanks!

Just tested this method and worked with me. \o/. I'm happy.


I'll try this method on weekend, because I'm using visualme7logger, and the GUI dont let me use 0x00 connection mode. Even if I hard change this on .ecu file, it changes on GUI.
On weekend I will try the command line me7logger.

I have a audi B4 with swaped  APU engine, 512 kb ECU, IMMO OFF, direct K-line
First I was able to start logger while engine is ON, problem is as soon I hit full throttle it really slow down logging and it stops
baud rate 56000, I log around 45 variables, 20 samples at second
Then I put ECU from audi TT, and things got even worse. It can connect sometimes at 19200 baud rate, but same thing at soon I hit full throttle it stops logging
And now it can't connect when engine is running on both ECUs, I try to log just few variables, and it continue to log while engine is running but only for few seconds then it stops
I connect OBD few cm from ECU, both ground and K-line and still it can't log while engine is on. Nefmoto can't connect too while engine is on
First log  is when engine is running and everything is OK, and second log is from today, it stops few seconds after engine is on

updates:
Same ECU different car (audi TT MK1), i put K-line direct to ECU, ground and 12 V from OBD port. I start logging while engine is off, then start engine and logger work without problems. I put sample time to 30, sometimes on 50 it break connection.
So I can confirm logger is working on 512 kb 8N090601AB ECUs also

Just be carefull about logging > 20 hz or many variables.

If the ECU load goes above 95-96% you can have "Ignition cut-off" for a split second. The ECU overloads and have to reset.  you will really feel that in your car. Its almost the same as removing the MAF sensor and hit full throttle :P

for 512Kb ecu (C ecu s4 b5), it looks like its not a problem. I can read 80 variables att 20 Hz --> The ecu load is still under 90%
For 1024kb ecu (like M/F/K for s4/rs4 b5) i dont recommend driving with 80 variables att 20 H, because ECU load will be close to 95-96%. Only do it during a pull.

For daily driving and logging, im running 30 variables att 10 Hz on my 1024Kb ecu. Never had "ignition turnoff" with this setup. I have problably over 300 hours logging in the car.