Pages: 1 ... 7 8 [9] 10
Author Topic: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2  (Read 141096 times)
vampirelo
Jr. Member
**

Karma: +1/-1
Offline Offline

Posts: 27


« Reply #120 on: March 05, 2015, 01:05:36 AM »

Is the ECU stock? If not, bootmode it and overwrite it with a stock fie.
There is no info about changed/tuned ECU.  Undecided
And I have no stock ECU dump.
Logged
diagnosticator
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 42


« Reply #121 on: May 04, 2015, 08:40:01 PM »

@ pusher:

use KWP2000+ interface and the specific ME7edition software from AMT cartech, if you want to read the ecu on the bench, without opening it up.
Galletto is a last resort, using bootmode. Not nescessary.

Nefmoto mainly fails with ME7.5 ecu's on the bench.

Cheers,

PvL
3900 Pounds Sterling.
Logged
TLS4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 13


« Reply #122 on: June 08, 2015, 02:55:18 PM »

When I try to connect to my ECU it reports that it has connected and after a couple of seconds it disconnects with the message:
"Disconnecting because no response was received for the Tester Present message"
If I try to read the ECU before it disconnects it first reports:
"ECU reports that security access request was rejected" and then disconnects with the previous message.
I have not used the Nefmoto program previously so I may be doing somthing wrong.
I have tried to lower the baudrate to 57600 (and restarted the program and the ECU) without success.
My setup is a bit mixed with an A6 4B0907551S box, RS4 8D0907551Q software and a -98 euro S4 (which used to have a 8D0907551C box).
The cable is a cheap china blue.

Any ideas what I should try?

Here is the log file from the first test.

Code:
08-jun-2015 10:06:16.772: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
08-jun-2015 10:06:17.483: LOG: Cannot load license file, file does not exist: C:\Documents and Settings\user\Application Data\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
08-jun-2015 10:06:17.563: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
08-jun-2015 10:06:31.022: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
08-jun-2015 10:06:31.113: LOG: Opened FTDI device.
08-jun-2015 10:06:31.113: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A5026GPL Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
08-jun-2015 10:06:31.113: LOG: FTDI ChipID DLL is loaded, checking chip ID...
08-jun-2015 10:06:31.123: LOG: FTDI device chip ID: 0xF01B04DD
08-jun-2015 10:06:31.213: USER: Validated FTDI device is in dumb mode.
08-jun-2015 10:06:31.233: LOG: Starting send receive thread.
08-jun-2015 10:06:31.253: LOG: Send receive thread now started.
08-jun-2015 10:06:31.263: USER: Disconnected
08-jun-2015 10:06:31.343: LOG: Setting communication timings to defaults.
08-jun-2015 10:06:31.343: LOG: Set timing parameters to defaults.
08-jun-2015 10:06:31.353: USER: Connecting...
08-jun-2015 10:06:31.393: LOG: Setting communication timings to defaults.
08-jun-2015 10:06:31.393: USER: Starting slow init connection.
08-jun-2015 10:06:33.997: USER: Connecting to address 0x01.
08-jun-2015 10:06:36.210: USER: Slow init succeeded.
08-jun-2015 10:06:36.210: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
08-jun-2015 10:06:36.210: USER: Switching to KWP1281 session.
08-jun-2015 10:06:36.400: LOG: KWP1281 read block
08-jun-2015 10:06:36.460: LOG: KWP1281 sent block
08-jun-2015 10:06:36.781: LOG: KWP1281 read block
08-jun-2015 10:06:36.841: LOG: KWP1281 sent block
08-jun-2015 10:06:37.021: LOG: KWP1281 read block
08-jun-2015 10:06:37.081: LOG: KWP1281 sent block
08-jun-2015 10:06:37.231: LOG: KWP1281 read block
08-jun-2015 10:06:37.301: LOG: KWP1281 sent block
08-jun-2015 10:06:37.331: LOG: KWP1281 read block
08-jun-2015 10:06:37.402: LOG: KWP1281 sent block
08-jun-2015 10:06:37.402: USER: KWP1281 connect info: ¸D0907551Q  2.7l V6/5VT     G   0001 +Ö 
08-jun-2015 10:06:38.894: USER: Connecting to address 0x01.
08-jun-2015 10:06:41.107: USER: Slow init succeeded.
08-jun-2015 10:06:41.107: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
08-jun-2015 10:06:41.107: USER: Switching to KWP2000 session.
08-jun-2015 10:06:41.107: USER: Connected
08-jun-2015 10:06:43.701: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:06:43.741: LOG: Received message with service ID: TesterPresentPositiveReponse
08-jun-2015 10:06:46.214: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:06:46.264: LOG: Received message with service ID: TesterPresentPositiveReponse
08-jun-2015 10:06:48.738: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:06:50.751: LOG: Message received no replies.
08-jun-2015 10:06:50.751: LOG: Resending message. Send attempts: 2
08-jun-2015 10:06:50.771: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:06:52.774: LOG: Message received no replies.
08-jun-2015 10:06:52.774: LOG: Resending message. Send attempts: 3
08-jun-2015 10:06:52.794: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:06:54.797: LOG: Message received no replies.
08-jun-2015 10:06:54.797: LOG: Failed to send message 3 times, message send failed.
08-jun-2015 10:06:54.797: USER: Disconnecting because no response was received for the Tester Present message.
08-jun-2015 10:06:54.797: USER: Disconnected
08-jun-2015 10:06:54.907: LOG: Closing FTDI device.
08-jun-2015 10:06:54.957: LOG: Send receive thread now terminated.
08-jun-2015 10:07:38.089: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
Logged
TLS4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 13


« Reply #123 on: June 08, 2015, 02:56:15 PM »

And the second attempt:

Code:
08-jun-2015 10:08:42.522: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
08-jun-2015 10:08:42.952: LOG: Cannot load license file, file does not exist: C:\Documents and Settings\user\Application Data\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
08-jun-2015 10:08:43.032: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
08-jun-2015 10:09:14.688: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
08-jun-2015 10:09:14.768: LOG: Opened FTDI device.
08-jun-2015 10:09:14.778: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A5026GPL Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
08-jun-2015 10:09:14.778: LOG: FTDI ChipID DLL is loaded, checking chip ID...
08-jun-2015 10:09:14.788: LOG: FTDI device chip ID: 0xF01B04DD
08-jun-2015 10:09:14.878: USER: Validated FTDI device is in dumb mode.
08-jun-2015 10:09:14.898: LOG: Starting send receive thread.
08-jun-2015 10:09:14.918: LOG: Send receive thread now started.
08-jun-2015 10:09:14.928: USER: Disconnected
08-jun-2015 10:09:15.018: LOG: Setting communication timings to defaults.
08-jun-2015 10:09:15.018: LOG: Set timing parameters to defaults.
08-jun-2015 10:09:15.028: USER: Connecting...
08-jun-2015 10:09:15.068: LOG: Setting communication timings to defaults.
08-jun-2015 10:09:15.078: USER: Starting slow init connection.
08-jun-2015 10:09:17.682: USER: Connecting to address 0x01.
08-jun-2015 10:09:19.895: USER: Slow init succeeded.
08-jun-2015 10:09:19.895: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
08-jun-2015 10:09:19.895: USER: Switching to KWP1281 session.
08-jun-2015 10:09:20.096: LOG: KWP1281 read block
08-jun-2015 10:09:20.166: LOG: KWP1281 sent block
08-jun-2015 10:09:20.496: LOG: KWP1281 read block
08-jun-2015 10:09:20.566: LOG: KWP1281 sent block
08-jun-2015 10:09:20.736: LOG: KWP1281 read block
08-jun-2015 10:09:20.807: LOG: KWP1281 sent block
08-jun-2015 10:09:20.947: LOG: KWP1281 read block
08-jun-2015 10:09:21.017: LOG: KWP1281 sent block
08-jun-2015 10:09:21.047: LOG: KWP1281 read block
08-jun-2015 10:09:21.117: LOG: KWP1281 sent block
08-jun-2015 10:09:21.117: USER: KWP1281 connect info: ¸D0907551Q  2.7l V6/5VT     G   0001 +Ö 
08-jun-2015 10:09:22.619: USER: Connecting to address 0x01.
08-jun-2015 10:09:24.812: USER: Slow init succeeded.
08-jun-2015 10:09:24.812: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
08-jun-2015 10:09:24.812: USER: Switching to KWP2000 session.
08-jun-2015 10:09:24.812: USER: Connected
08-jun-2015 10:09:27.386: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:09:27.436: LOG: Received message with service ID: TesterPresentPositiveReponse
08-jun-2015 10:09:29.910: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:09:29.930: LOG: User Prompt - Title: Confirm Full Read ECU Flash Memory Message: If you are ready to read, confirm the following things:
1) You have loaded a valid memory layout for the ECU.
2) The engine is not running.
Note: Some non-standard flash memory chips may prevent reading the flash memory.

Click OK to confirm, otherwise Cancel. Result: OK
08-jun-2015 10:09:29.930: USER: Disabling Windows sleep mode.
08-jun-2015 10:09:29.970: USER: Reading ECU flash memory.
08-jun-2015 10:09:29.990: LOG: Received message with service ID: TesterPresentPositiveReponse
08-jun-2015 10:09:30.000: LOG: Reading ECU identification option: 0x9C
08-jun-2015 10:09:30.040: LOG: Sent message with service ID ReadECUIdentification
08-jun-2015 10:09:30.090: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
08-jun-2015 10:09:30.090: LOG: Read ECU identification option: 0x9C
08-jun-2015 10:09:30.090: LOG: Successfully read ECU identification information
08-jun-2015 10:09:30.120: USER: ECU reports programming session preconditions have been met.
08-jun-2015 10:09:30.120: USER: Negotiating communication timings.
08-jun-2015 10:09:30.120: LOG: Reading current communication timings.
08-jun-2015 10:09:30.210: LOG: Sent message with service ID AccessTimingParameters
08-jun-2015 10:09:30.260: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08-jun-2015 10:09:30.260: LOG: Set timing parameters to new values.
08-jun-2015 10:09:30.260: LOG: Setting communication timing to defaults.
08-jun-2015 10:09:30.320: LOG: Sent message with service ID AccessTimingParameters
08-jun-2015 10:09:30.360: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08-jun-2015 10:09:30.360: LOG: Reading current communication timings.
08-jun-2015 10:09:30.420: LOG: Sent message with service ID AccessTimingParameters
08-jun-2015 10:09:30.470: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08-jun-2015 10:09:30.470: USER: Successfully changed to new communication timings.
08-jun-2015 10:09:30.470: USER: Requesting security access.
08-jun-2015 10:09:30.500: LOG: Sent message with service ID SecurityAccess
08-jun-2015 10:09:30.551: LOG: Received message with service ID: NegativeResponse
08-jun-2015 10:09:30.551: LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
08-jun-2015 10:09:30.551: USER: ECU reports that security access request was rejected.
08-jun-2015 10:09:30.561: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
08-jun-2015 10:09:30.561: USER: Starting diagnostic session.
08-jun-2015 10:09:30.591: LOG: Sent message with service ID StartDiagnosticSession
08-jun-2015 10:09:30.641: LOG: Received message with service ID: NegativeResponse
08-jun-2015 10:09:30.641: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08-jun-2015 10:09:30.681: LOG: Received message with service ID: NegativeResponse
08-jun-2015 10:09:30.681: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08-jun-2015 10:09:30.721: LOG: Received message with service ID: NegativeResponse
08-jun-2015 10:09:30.721: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08-jun-2015 10:09:30.761: LOG: Received message with service ID: NegativeResponse
08-jun-2015 10:09:30.761: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08-jun-2015 10:09:40.615: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:09:40.725: LOG: Message received no replies.
08-jun-2015 10:09:40.725: LOG: Resending message. Send attempts: 2
08-jun-2015 10:09:40.745: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:09:40.855: LOG: Message received no replies.
08-jun-2015 10:09:40.855: LOG: Resending message. Send attempts: 3
08-jun-2015 10:09:40.865: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:09:40.986: LOG: Message received no replies.
08-jun-2015 10:09:40.986: LOG: Failed to send message 3 times, message send failed.
08-jun-2015 10:09:40.986: USER: Disconnecting because no response was received for the Tester Present message.
08-jun-2015 10:09:40.986: USER: Disconnected
08-jun-2015 10:09:41.046: USER: Reading ECU flash memory failed.
08-jun-2015 10:09:41.146: LOG: Closing FTDI device.
08-jun-2015 10:09:41.196: LOG: Send receive thread now terminated.
08-jun-2015 10:09:49.257: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK
08-jun-2015 10:09:49.257: USER: 100% complete.
08-jun-2015 10:09:49.288: USER: Restoring Windows sleep mode.
Logged
seany260
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 115


« Reply #124 on: July 05, 2015, 07:39:36 PM »

having this issue with windows 8 x64 computer, works fine on my windows 7.
any idea why it would do this at 94%.

Bumping this post as I'm this computer full time now and it has this issue everytime I try to flash for the first time, when I select yes and it tries to flash again it works. Never seen this on my 32bit windows 7 computer.

« Last Edit: April 07, 2017, 11:57:35 PM by seany260 » Logged
macxxx
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 144


« Reply #125 on: September 10, 2015, 03:54:00 AM »

Nefmoto Flasher doesn't see my KKL cable , newest drivers installed , reinstalled everything
 - no diffrence.

It's a new cable , a good quality one , made on FTDI 231x chip , maybe that's the problem? My recent cable ( a KKL on a 232BL chip ) worked like a charm.

Info from USBVIEW:

Code:
Device Descriptor:
bcdUSB:             0x0200
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x08 (8)
idVendor:           0x0403 (Future Technology Devices International Limited)
idProduct:          0x6015
bcdDevice:          0x1000
iManufacturer:        0x01
0x0409: "FTDI"
iProduct:             0x02
0x0409: "FT231X USB UART"
0x0409: "FT231X USB UART"
iSerialNumber:        0x03
0x0409: "DA01G33D"
bNumConfigurations:   0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed:     Full
Device Address:       0x01
Open Pipes:              2

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:        Bulk
wMaxPacketSize:     0x0040 (64)
bInterval:            0x00

Endpoint Descriptor:
bEndpointAddress:     0x02  OUT
Transfer Type:        Bulk
wMaxPacketSize:     0x0040 (64)
bInterval:            0x00

Configuration Descriptor:
wTotalLength:       0x0020
bNumInterfaces:       0x01
bConfigurationValue:  0x01
iConfiguration:       0x00
bmAttributes:         0xA0 (Bus Powered Remote Wakeup)
MaxPower:             0x2D (90 Ma)

Interface Descriptor:
bInterfaceNumber:     0x00
bAlternateSetting:    0x00
bNumEndpoints:        0x02
bInterfaceClass:      0xFF
bInterfaceSubClass:   0xFF
bInterfaceProtocol:   0xFF
iInterface:           0x02
0x0409: "FT231X USB UART"
0x0409: "FT231X USB UART"

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:        Bulk
wMaxPacketSize:     0x0040 (64)
bInterval:            0x00

Endpoint Descriptor:
bEndpointAddress:     0x02  OUT
Transfer Type:        Bulk
wMaxPacketSize:     0x0040 (64)
bInterval:            0x00
« Last Edit: September 10, 2015, 03:55:45 AM by macxxx » Logged
macxxx
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 144


« Reply #126 on: September 13, 2015, 04:28:29 AM »

My cable works with vag-com , VCDS Lite , me7_95040.exe but no luck with nefmoto - what name or ID should it have to be seen by the ECU Flasher?





ok found a sollution - I bought a KKL cable based on 232R , works lika a charm Cheesy
« Last Edit: September 28, 2015, 02:22:40 PM by macxxx » Logged
Perphide
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 5


« Reply #127 on: March 31, 2016, 07:08:54 AM »

Is it possible to get a CMD-line version of this software?
Logged
nyet
Administrator
Hero Member
*****

Karma: +344/-40
Offline Offline

Posts: 8030


WWW
« Reply #128 on: March 31, 2016, 10:37:15 AM »

Is it possible to get a CMD-line version of this software?

I would LOVE to do this as well, but unfortunately, I do not have access to the source.

Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

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 experience.
Ionut
Full Member
***

Karma: +2/-3
Offline Offline

Posts: 89


« Reply #129 on: November 18, 2016, 12:38:46 PM »

Is this software supported anymore?
The premium version can write just changed memory blocks? I`m tired of writing full flash for tests (dtc, readlines, small calibration changes, etc)
How much costs the premium license?
Logged
companyman95
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 1


« Reply #130 on: January 17, 2017, 07:26:10 PM »

possible that I'm COMPLETELY retarded.... I cant seem to get the Ecu layouts to load... windows 10 laptop NefMoto's latest version. I just want to mess around with this stuff and am not sure how to get it going... help please.
Logged
phrozendub
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 5


« Reply #131 on: April 06, 2017, 10:34:23 PM »

possible that I'm COMPLETELY retarded.... I cant seem to get the Ecu layouts to load... windows 10 laptop NefMoto's latest version. I just want to mess around with this stuff and am not sure how to get it going... help please.

Post vehicle/ecu you are trying to connect to...
Logged
THANAS
Jr. Member
**

Karma: +0/-2
Offline Offline

Posts: 39

Yes.


« Reply #132 on: April 13, 2017, 02:01:05 AM »

I've used nefmoto flasher on many vehicles with success 99% of the time.  I've used various FTDI cables, one of which was listed in the recommended cables section.  However I end up with a problem on some vehicles with some of the cables:

Nefmoto Flasher get's stuck at "negotiating communication timings".  It will not progress further than this, regardless of how long I wait.  I close the program, cycle ignition and all is fine, no starting or programming not finished issues.  The common trend I find is the following:

The cable will work flawlessly at flashing the Mk4 GTi ecu (06A906032HP) - AUQ motor, but will not work on the Audi A3 1.8T (AUM) with the exact same bin layout, pretty much identical in every way to the Mk4, but it refuses to connect.  No problem on any vehicle with the cable using Me7Logger in FTDI mode.  It gives the same issue with some of the Polo GTis (06A906012M), some it works perfectly, some it gives 'negotiating communication timings' issues.  In the same breath, some cables will work perfectly will all of the above cars without hassle, same laptop, same drivers etc.

I get around it by using other tools, but I enjoy using Nefmoto flasher for its simplicity and speed.  Any ideas?
« Last Edit: April 13, 2017, 02:50:32 AM by THANAS » Logged
armageddon
Sr. Member
****

Karma: +15/-1
Offline Offline

Posts: 283


« Reply #133 on: April 13, 2017, 03:08:04 AM »

Run a direct K-line and problem solved.
Logged
fukenbroken
Hero Member
*****

Karma: +42/-3
Offline Offline

Posts: 608


mk4 1.8T AUM


« Reply #134 on: April 13, 2017, 08:23:58 AM »

set baud rate 38400
pull out cluster fuse after turning ignition on

Logged
Pages: 1 ... 7 8 [9] 10
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.029 seconds with 18 queries. (Pretty URLs adds 0.001s, 0q)