NefMoto

Completely new to this so go easy , looking to take a copy of my map off the car.

I've installed the software, but it doesn't seem to be getting any info off the ecu.

Anyone care to enlighten me ??


TIA

What cable are you using? Are there any errors in the log file?

Just a cheapo KKL blue one, I have a genuine rosstech one as well.

Am I right in thinking I need to load up a XDF file in nefmoto before it will pull a copy of whats on there ??

you should be able to click on slow init, hit connect, click on KWP2000 Flashing tab, select the proper memory layout for your car, click on full read flash. This should get you a *.bin file for what is in your ECU.

I can see the file for memory layouts, but how do I work out which is right for my 06A906032HN ECU ???

Got it

 I looked in here and cross referenced it  http://www.nefariousmotorsports.com/wiki/index.php/NefMoto_ECU_Flashing_Software

I assume I drop the AM and am left with ME7 29F800 which I can see in the layout files on the program.


Nice one I'll give it another shot now

Use this http://www.nefariousmotorsports.com/wiki/index.php/NefMoto_ECU_Flashing_Software#Tested_ECUs (http://www.nefariousmotorsports.com/wiki/index.php/NefMoto_ECU_Flashing_Software#Tested_ECUs)to determine proper memory layout.

Thats what I used thanks mate

I tried reading the bin file form my ecu but I'm getting and unable to file error message.

ANy ideas or is it because the mapper locked it ??

if you have a commercial tune, they have it blocked from reading so it cannot be reproduced. Does the car still start?

Car starts fine, a small mapper not sure of origin to be honest

Request: can you change the topic of this thread to be a bit more specific?

Thanks.

Here's the log file

15/Jul/2013 10:12:54.000: LOG: Opening NefMoto VW Audi ME7 ECU Flasher BETA 1.9.1.2
15/Jul/2013 10:12:54.593: LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.9.1.2
15/Jul/2013 10:13:01.564: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
15/Jul/2013 10:13:01.669: LOG: Opened FTDI device.
15/Jul/2013 10:13:01.687: LOG: FTDI device info - Description: VAG KKL Serial Number: CARL007 Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
15/Jul/2013 10:13:01.704: LOG: FTDI ChipID DLL is loaded, checking chip ID...
15/Jul/2013 10:13:01.735: LOG: FTDI device chip ID: 0x666AEED9
15/Jul/2013 10:13:01.867: USER: Validated FTDI device is in dumb mode.
15/Jul/2013 10:13:01.913: LOG: Starting send receive thread.
15/Jul/2013 10:13:01.981: LOG: Send receive thread now started.
15/Jul/2013 10:13:02.017: USER: Disconnected
15/Jul/2013 10:13:02.171: LOG: Setting communication timings to defaults.
15/Jul/2013 10:13:02.199: LOG: Set timing parameters to defaults.
15/Jul/2013 10:13:02.208: USER: Connecting...
15/Jul/2013 10:13:02.250: LOG: Setting communication timings to defaults.
15/Jul/2013 10:13:02.272: USER: Starting slow init connection.
15/Jul/2013 10:13:04.896: USER: Connecting to address 0x01.
15/Jul/2013 10:13:07.138: USER: Slow init succeeded.
15/Jul/2013 10:13:07.179: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
15/Jul/2013 10:13:07.211: USER: Switching to KWP1281 session.
15/Jul/2013 10:13:07.288: LOG: Failed to read KWP1281 block length byte.
15/Jul/2013 10:13:07.329: LOG: KWP1281 read block failed.
15/Jul/2013 10:13:07.355: USER: Failed to read KWP1281 connect info.
15/Jul/2013 10:13:08.878: USER: Connecting to address 0x01.
15/Jul/2013 10:13:11.052: USER: Slow init succeeded.
15/Jul/2013 10:13:11.061: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
15/Jul/2013 10:13:11.230: LOG: KWP1281 read block
15/Jul/2013 10:13:11.336: LOG: KWP1281 sent block
15/Jul/2013 10:13:11.603: LOG: KWP1281 read block
15/Jul/2013 10:13:11.678: LOG: KWP1281 sent block
15/Jul/2013 10:13:11.844: LOG: KWP1281 read block
15/Jul/2013 10:13:11.918: LOG: KWP1281 sent block
15/Jul/2013 10:13:12.057: LOG: KWP1281 read block
15/Jul/2013 10:13:12.171: LOG: KWP1281 sent block
15/Jul/2013 10:13:12.227: LOG: KWP1281 read block
15/Jul/2013 10:13:12.319: LOG: KWP1281 sent block
15/Jul/2013 10:13:12.348: USER: KWP1281 connect info: °6A906032HN 1.8L R4/5VT         0002 YÙ75
15/Jul/2013 10:13:14.057: USER: Connecting to address 0x11.
15/Jul/2013 10:13:16.235: USER: Slow init succeeded.
15/Jul/2013 10:13:16.258: LOG: Setting Address: 0x11 KeyByte1: 0x6F KeyByte2: 0x0F
15/Jul/2013 10:13:16.280: USER: Switching to KWP2000 session.
15/Jul/2013 10:13:16.635: LOG: Sent message with service ID StartCommunication
15/Jul/2013 10:13:16.648: USER: Sending start communication request.
15/Jul/2013 10:13:16.727: LOG: Received message with service ID StartCommunicationPositiveResponse
15/Jul/2013 10:13:16.741: LOG: Setting Address: 0x11 KeyByte1: 0x6F KeyByte2: 0x0F
15/Jul/2013 10:13:16.753: USER: Connected
15/Jul/2013 10:13:19.154: LOG: Sent message with service ID TesterPresent
15/Jul/2013 10:13:19.571: USER: Disabling Windows sleep mode.
15/Jul/2013 10:13:19.735: USER: Reading ECU flash memory.
15/Jul/2013 10:13:19.871: LOG: Reading ECU identification option: 0x9C
15/Jul/2013 10:13:21.157: LOG: Message received no replies.
15/Jul/2013 10:13:21.175: LOG: Resending message. Send attempts: 2
15/Jul/2013 10:13:21.211: LOG: Sent message with service ID TesterPresent
15/Jul/2013 10:13:23.214: LOG: Message received no replies.
15/Jul/2013 10:13:23.238: LOG: Resending message. Send attempts: 3
15/Jul/2013 10:13:23.279: LOG: Sent message with service ID TesterPresent
15/Jul/2013 10:13:25.281: LOG: Message received no replies.
15/Jul/2013 10:13:25.297: LOG: Failed to send message 3 times, message send failed.
15/Jul/2013 10:13:25.313: USER: Disconnecting because no response was received for the Tester Present message.
15/Jul/2013 10:13:25.330: USER: Disconnected
15/Jul/2013 10:13:25.478: USER: Reading ECU flash memory failed.
15/Jul/2013 10:13:25.592: LOG: Closing FTDI device.
15/Jul/2013 10:13:25.630: LOG: Send receive thread now terminated.
15/Jul/2013 10:13:27.049: USER: 100% complete.
15/Jul/2013 10:13:27.073: USER: Restoring Windows sleep mode.

Do you have a stock ECU you can try?

I don't mate, I may try and get one at some point

Spoken to the mapper in question, no security on the file, no reason why it shouldn't copy.

Tried my rosstech cable too.... No cigar !!!

Got it too read after, I did by switching the ignition as the confirmation screen comes up just before the read.

I also do have problem with ECU dump as fast/full read/write options are disable.
Nefmoto connected via obd with KWP2000 protocol, I can read ECU info an that is all I can. Nothing more.
What is going on?

Try a cheap blue china cable.They are better than the china VCDS cables.
Also original Rosstech can`t work even with "dump mode" at least I cant do it.

Fast init is for registered users only you need a license

I got mine working every time both read and write by pulling the cluster fuse.

It seems since I did that it works without pulling it each time now.

make a bench harness then try to read it , then try to read it in boot mode

My cable is cheap blue chinese sh....
Tonight I`ll try to use cable with elm327 chipset and I`ll let you know.

i can never successfully read/write my 1.8t ECU (AWW motor) without pulling cluster fuse.  Its the cluster fuse closest to the firewall.  If the gauges stop working but clock stays on you pulled the right fuse.