NefMoto > Technical > Flashing and Chipping > Golf 1.8T flash problems 032AR
Pages: [1]
« previous next »
Author Topic: Golf 1.8T flash problems 032AR  (Read 7510 times)
Twin
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« on: October 01, 2015, 03:54:31 AM »
Hi

I have a vw golf 1.8T with ARZ engine, I have read the flash, first I chose the 29F800BB, Because when i try 29F400BB Says That It Appears to be a wrong Layout, then reread the flash with 400bb and all ok, but when I go to load a tuned flash, nefmoto disconnects and get the following message:

Because no response was disconecting receved tester for the present message.

And this is the LOG of nefmoto:

30/sep/2015 11:20:05.767: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
30/sep/2015 11:20:08.762: LOG: Cannot load license file, file does not exist: C:\Users\....\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
30/sep/2015 11:20:09.245: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
30/sep/2015 11:20:31.890: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
30/sep/2015 11:23:11.774: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
30/sep/2015 11:23:14.036: LOG: Cannot load license file, file does not exist: C:\Users\....\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
30/sep/2015 11:23:14.691: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
30/sep/2015 11:23:33.034: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
30/sep/2015 11:23:33.135: LOG: Opened FTDI device.
30/sep/2015 11:23:33.136: LOG: FTDI device info - Description: FT232R USB UART Serial Number: AL01BL5P Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
30/sep/2015 11:23:33.138: LOG: FTDI ChipID DLL is loaded, checking chip ID...
30/sep/2015 11:23:33.148: LOG: FTDI device chip ID: 0x7C1E8C5D
30/sep/2015 11:23:33.425: USER: Validated FTDI device is in dumb mode.
30/sep/2015 11:23:33.642: LOG: Starting send receive thread.
30/sep/2015 11:23:33.729: LOG: Send receive thread now started.
30/sep/2015 11:23:33.743: USER: Disconnected
30/sep/2015 11:23:33.932: LOG: Setting communication timings to defaults.
30/sep/2015 11:23:33.936: LOG: Set timing parameters to defaults.
30/sep/2015 11:23:33.937: USER: Connecting...
30/sep/2015 11:23:33.993: LOG: Setting communication timings to defaults.
30/sep/2015 11:23:34.002: USER: Starting slow init connection.
30/sep/2015 11:23:36.604: USER: Connecting to address 0x01.
30/sep/2015 11:23:38.814: USER: Slow init succeeded.
30/sep/2015 11:23:38.815: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
30/sep/2015 11:23:38.817: USER: Switching to KWP1281 session.
30/sep/2015 11:23:39.092: LOG: Final byte of KWP1281 message was not block end byte.
30/sep/2015 11:23:39.093: LOG: KWP1281 read block failed.
30/sep/2015 11:23:39.095: USER: Failed to read KWP1281 connect info.
30/sep/2015 11:23:40.598: USER: Connecting to address 0x01.
30/sep/2015 11:23:42.792: USER: Slow init succeeded.
30/sep/2015 11:23:42.970: LOG: KWP1281 read block
30/sep/2015 11:23:43.034: LOG: KWP1281 sent block
30/sep/2015 11:23:43.280: LOG: KWP1281 read block
30/sep/2015 11:23:43.344: LOG: KWP1281 sent block
30/sep/2015 11:23:43.519: LOG: KWP1281 read block
30/sep/2015 11:23:43.583: LOG: KWP1281 sent block
30/sep/2015 11:23:43.730: LOG: KWP1281 read block
30/sep/2015 11:23:43.794: LOG: KWP1281 sent block
30/sep/2015 11:23:43.830: LOG: KWP1281 read block
30/sep/2015 11:23:43.894: LOG: KWP1281 sent block
30/sep/2015 11:23:43.895: USER: KWP1281 connect info: 06A906032AR 1.8L R4/5VT     G   0007 *ø 
30/sep/2015 11:23:45.396: USER: Connecting to address 0x11.
30/sep/2015 11:23:47.596: USER: Slow init succeeded.
30/sep/2015 11:23:47.598: LOG: Setting Address: 0x11 KeyByte1: 0x6F KeyByte2: 0x0F
30/sep/2015 11:23:47.600: USER: Switching to KWP2000 session.
30/sep/2015 11:23:47.602: USER: Connected
30/sep/2015 11:23:50.183: LOG: Sent message with service ID TesterPresent
30/sep/2015 11:23:52.143: LOG: Message received no replies.
30/sep/2015 11:23:52.144: LOG: Resending message. Send attempts: 2
30/sep/2015 11:23:52.164: LOG: Sent message with service ID TesterPresent
30/sep/2015 11:23:54.166: LOG: Message received no replies.
30/sep/2015 11:23:54.167: LOG: Resending message. Send attempts: 3
30/sep/2015 11:23:54.187: LOG: Sent message with service ID TesterPresent
30/sep/2015 11:23:56.190: LOG: Message received no replies.
30/sep/2015 11:23:56.233: LOG: Failed to send message 3 times, message send failed.
30/sep/2015 11:23:56.238: USER: Disconnecting because no response was received for the Tester Present message.
30/sep/2015 11:23:56.241: USER: Disconnected
30/sep/2015 11:23:56.277: LOG: Closing FTDI device.
30/sep/2015 11:23:56.331: LOG: Send receive thread now terminated.
30/sep/2015 11:25:24.371: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
30/sep/2015 11:25:24.373: USER: Switching to KWP2000 session.
30/sep/2015 11:25:24.436: LOG: Opened FTDI device.
30/sep/2015 11:25:24.437: LOG: FTDI device info - Description: FT232R USB UART Serial Number: AL01BL5P Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
30/sep/2015 11:25:24.438: LOG: FTDI ChipID DLL is loaded, checking chip ID...
30/sep/2015 11:25:24.448: LOG: FTDI device chip ID: 0x7C1E8C5D
30/sep/2015 11:25:24.496: USER: Validated FTDI device is in dumb mode.
30/sep/2015 11:25:24.523: LOG: Starting send receive thread.
30/sep/2015 11:25:24.526: LOG: Send receive thread now started.
30/sep/2015 11:25:24.527: USER: Disconnected
30/sep/2015 11:25:24.564: LOG: Setting communication timings to defaults.
30/sep/2015 11:25:24.565: USER: Connecting...
30/sep/2015 11:25:24.602: LOG: Setting communication timings to defaults.
30/sep/2015 11:25:24.604: USER: Starting slow init connection.
30/sep/2015 11:25:27.208: USER: Connecting to address 0x01.
30/sep/2015 11:25:29.363: USER: Slow init succeeded.
30/sep/2015 11:25:29.364: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
30/sep/2015 11:25:29.365: USER: Switching to KWP1281 session.
30/sep/2015 11:25:29.540: LOG: KWP1281 read block
30/sep/2015 11:25:29.602: LOG: KWP1281 sent block
30/sep/2015 11:25:29.929: LOG: KWP1281 read block
30/sep/2015 11:25:29.992: LOG: KWP1281 sent block
30/sep/2015 11:25:30.169: LOG: KWP1281 read block
30/sep/2015 11:25:30.232: LOG: KWP1281 sent block
30/sep/2015 11:25:30.378: LOG: KWP1281 read block
30/sep/2015 11:25:30.442: LOG: KWP1281 sent block
30/sep/2015 11:25:30.478: LOG: KWP1281 read block
30/sep/2015 11:25:30.542: LOG: KWP1281 sent block
30/sep/2015 11:25:30.544: USER: KWP1281 connect info: 06A906032AR 1.8L R4/5VT     G   0007 *ø 
30/sep/2015 11:25:32.046: USER: Connecting to address 0x01.
30/sep/2015 11:25:34.210: USER: Slow init succeeded.
30/sep/2015 11:25:34.386: LOG: KWP1281 read block
30/sep/2015 11:25:34.450: LOG: KWP1281 sent block
30/sep/2015 11:25:34.726: LOG: KWP1281 read block
30/sep/2015 11:25:34.790: LOG: KWP1281 sent block
30/sep/2015 11:25:34.966: LOG: KWP1281 read block
30/sep/2015 11:25:35.030: LOG: KWP1281 sent block
30/sep/2015 11:25:35.176: LOG: KWP1281 read block
30/sep/2015 11:25:35.240: LOG: KWP1281 sent block
30/sep/2015 11:25:35.276: LOG: KWP1281 read block
30/sep/2015 11:25:35.340: LOG: KWP1281 sent block
30/sep/2015 11:25:35.341: USER: KWP1281 connect info: 06A906032AR 1.8L R4/5VT     G   0007 *ø 
30/sep/2015 11:25:36.843: USER: Connecting to address 0x11.
30/sep/2015 11:25:39.036: USER: Slow init succeeded.
30/sep/2015 11:25:39.039: LOG: Setting Address: 0x11 KeyByte1: 0x6F KeyByte2: 0x0F
30/sep/2015 11:25:39.041: USER: Switching to KWP2000 session.
30/sep/2015 11:25:39.042: USER: Connected
30/sep/2015 11:25:41.571: LOG: Sent message with service ID TesterPresent
30/sep/2015 11:25:43.574: LOG: Message received no replies.
30/sep/2015 11:25:43.575: LOG: Resending message. Send attempts: 2
30/sep/2015 11:25:43.595: LOG: Sent message with service ID TesterPresent
30/sep/2015 11:25:45.597: LOG: Message received no replies.
30/sep/2015 11:25:45.598: LOG: Resending message. Send attempts: 3
30/sep/2015 11:25:45.618: LOG: Sent message with service ID TesterPresent
30/sep/2015 11:25:47.621: LOG: Message received no replies.
30/sep/2015 11:25:47.623: LOG: Failed to send message 3 times, message send failed.
30/sep/2015 11:25:47.625: USER: Disconnecting because no response was received for the Tester Present message.
30/sep/2015 11:25:47.626: USER: Disconnected
30/sep/2015 11:25:47.659: LOG: Closing FTDI device.
30/sep/2015 11:25:47.712: LOG: Send receive thread now terminated.
30/sep/2015 11:27:27.106: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
01/oct/2015 12:12:34.722: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
01/oct/2015 12:12:47.124: LOG: Cannot load license file, file does not exist: C:\Users\....\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
01/oct/2015 12:12:47.140: LOG: Cannot load license file, file does not exist: C:\Users\....\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
01/oct/2015 12:12:50.135: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
01/oct/2015 12:12:50.151: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
01/oct/2015 12:13:51.527: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
01/oct/2015 12:22:30.825: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
01/oct/2015 12:36:27.697: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
01/oct/2015 12:36:29.506: LOG: Cannot load license file, file does not exist: C:\Users\....\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
01/oct/2015 12:36:29.771: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2

Thanks!
Logged
Twin
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #1 on: October 02, 2015, 08:27:02 AM »
Anyone can help me?
Logged
V8 Dave
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 6
« Reply #2 on: October 03, 2015, 03:12:16 PM »
Immo 3 ECU? I've literally just got over this problem (I've been registered here for years, and have prety much solved all my problems by reading, there is so much info here!). Have you got pin 121 on the ECU powered? I had it mssing on my bench cable and it seemed to work on my immo 2 ECU (29F400) but the first time I tried Immo 3 it refused to flash.
Logged
V8 Dave
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 6
« Reply #3 on: October 03, 2015, 03:14:07 PM »
EDIT: - interestingly, my immo 2 box was a 6032AR but has a 29F400 in it and was suppsoedly from a GTI too
Logged
_nameless
Hero Member
*****

Karma: +342/-466
Offline Offline

Posts: 2802
« Reply #4 on: October 04, 2015, 05:08:00 AM »
patch your cable with the galletto serial number from the thread that daz made "galletto with proper English" with mprog and blind write that bitch. Also with this youll have a bootmode backup if you do brick your ecu. 
Logged
Giving your mom a tuneup
Twin
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #5 on: October 04, 2015, 09:48:59 AM »
First, thanks for answering.

Quote from: V8 Dave on October 03, 2015, 03:12:16 PM
Immo 3 ECU? I've literally just got over this problem (I've been registered here for years, and have prety much solved all my problems by reading, there is so much info here!). Have you got pin 121 on the ECU powered? I had it mssing on my bench cable and it seemed to work on my immo 2 ECU (29F400) but the first time I tried Immo 3 it refused to flash.

The car is a GTI 6032AR, the ECU is placed in the car and as I said before I read the flash seamlessly with 400bb, the ECU is a INMO 2, but the tachometer is a sport edition INMO 3.

you think the tachometer can be the problem?


Quote from: Marty on October 04, 2015, 05:08:00 AM
patch your cable with the galletto serial number from the thread that daz made "galletto with proper English" with mprog and blind write that bitch. Also with this youll have a bootmode backup if you do brick your ecu. 

you think the problem is the cable? because let me read the ecu? if I find another solution I'll do what you say, so also be able to use the bootmode cable ...

Thanks!
Logged
V8 Dave
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 6
« Reply #6 on: October 07, 2015, 02:24:45 AM »
This -

Code:
30/sep/2015 11:23:56.238: USER: Disconnecting because no response was received for the Tester Present message.

Was the cause of my problem before I powered pin 121. Powered up, no problems. Until then, the only way I could flash was boot mode with Galleto
Logged
_nameless
Hero Member
*****

Karma: +342/-466
Offline Offline

Posts: 2802
« Reply #7 on: October 07, 2015, 12:18:09 PM »
Also look at the 032cl flash and definition file. That is USA spec 1.8t dbw narrowband O2 and immo 2. So you can compare map addresses or straight cross flash without issue
Logged
Giving your mom a tuneup
Twin
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #8 on: October 08, 2015, 02:15:46 PM »
I could reread the flash without problems, the only difference is that this time I have given the button "read ecu info"...

In the following days I'll try to write the ecu
« Last Edit: October 08, 2015, 04:30:08 PM by Twin » Logged
V8 Dave
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 6
« Reply #9 on: October 09, 2015, 04:10:19 AM »
If this is in your daily driver, I'd strongly advise that you get a spare ECU first if you're having trouble connecting. The last thing you need to be doing is walking to work...
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #10 on: October 09, 2015, 11:05:57 AM »
Quote from: V8 Dave on October 09, 2015, 04:10:19 AM
If this is in your daily driver, I'd strongly advise that you get a spare ECU first if you're having trouble connecting. The last thing you need to be doing is walking to work...

This x 1000
Logged
ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
Twin
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #11 on: October 12, 2015, 04:49:43 AM »
Hi

The other day I finally decided to write my ecu.

At first keep doing the same, it was connected with the ecu and switched off, I got that was connected and I was able to read the flash smoothly as had not given me problems reading, I decided to write and everything works fine now.
Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 27, 2024, 09:50:06 PM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

    Login with username, password and session length
Search
 
Advanced Search
About Disclaimer
All Rights Reserved 2010 Nefarious Motosports
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.024 seconds with 17 queries. (Pretty URLs adds 0s, 0q)