Print Page - NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0

Title: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Tony@NefMoto on March 17, 2012, 01:51:50 PM

This is the version 1.9.3.0 release of the NefMoto software.

Changes in this version:
-Fast data logging that works the same way as the ME7 Logger.
-User interface optimizations and improvements for data logging.
-Option to choose between three different data logging methods.
-Bug fix for negotiating communication timings that caused errors on overly picky ECUs.

Fast data logging can read up to 84 variables at a time with samples rates as high as 50 samples per second. The sample rate defaults to 10 samples per second. High sample rates can overload the ECU and cause communication disconnections. This same problem effects the ME7 Logger when attempting to read too many variables with sample rates that are too high. I recommend only logging the variables you are interested in at sample rate you need. The data logging method that this software and ME7 Logger use are non-standard and as such are able to overload the ECU if used irresponsibly.

Aside from the new fast data logging, there are two other methods for data logging in the NefMoto software. The other two methods read variables from the ECU using the standard OEM KWP2000 protocol. One of the methods reads one variable with each ECU message, and the other reads all the variables in a block of contiguous memory with each ECU message. All three methods depend on having variable definitions that specify the memory addresses of the variables in your particular ECU.

You can read about the software on the wiki: http://www.nefariousmotorsports.com/wiki/index.php/NefMoto_ECU_Flashing_Software

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: s4rmm on March 18, 2012, 06:34:31 AM

Tony,
received an error when flashing with this version. Log attached.
LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
USER: ECU reports that security access request was rejected
No problems with previous 1.9.2.3

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: All_Euro on March 23, 2012, 06:24:06 AM

Quote from: Tony@NefMoto on March 17, 2012, 01:51:50 PM

Fast data logging can read up to 84 variables at a time with samples rates as high as 50 samples per second. The sample rate defaults to 10 samples per second. High sample rates can overload the ECU and cause communication disconnections. This same problem effects the ME7 Logger when attempting to read too many variables with sample rates that are too high. I recommend only logging the variables you are interested in at sample rate you need. The data logging method that this software and ME7 Logger use are non-standard and as such are able to overload the ECU if used irresponsibly.

^^^ thanks for this, I'll double check my sample rate as ME7 Logger isn't working right since I had my Unitronic file flashed to their 2+... I'm getting timing pull values of 40*-50*... VCDS works but it so SLOW :(

I'll download your flasher/logger and give it a try this weekend :)

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Jason on March 25, 2012, 03:51:45 PM

Something I noticed, and maybe it's just this winders install being stupid, but if I read a file and want to over-write an existing file, the application hangs in the save file dialog box...

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: julex on March 26, 2012, 10:02:26 AM

Shutting your ECU due to too many variables/too high refresh rate is not fun. Happened to me, it is like hitting a brick wall when doing WOT pull... literally. You go from 0.5g to -0.2 or so in an instant. The lower the gear, the larger g change. The ECU reset within about 0.5 - 1s though and re-fires the engine so you get jerked back into the seat again almost instantaneously.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: -SlowSilverTIPJason- on March 26, 2012, 10:09:24 AM

Quote from: julex on March 26, 2012, 10:02:26 AM

How many vars/samples caused the reset? Trying to avoid this while tuning my buddies car because I know he will turn his pants brown.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Jason on March 29, 2012, 11:15:12 PM

Do we know sample rate/data rate is definitely the trigger? Out of about 40 hours of continuous logging, I've only had it happen once, and it was while cruising on the highway. The ECU recovered fast. I was using the Mark P style template and a sample rate of around 50hz.

The part I found interesting was that the instrument cluster was "dead" for about 30 seconds.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: NOTORIOUS VR on April 01, 2012, 09:49:31 AM

Anyone else have issues flashing with this or the previous version?

It will not read or write to my M-box at all... It says something about security access not allowed/granted.

I have to go back and use ver. 1.8.0.0 and all works fine.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Jason on April 01, 2012, 09:51:46 AM

I'm having no problems with 1.9.2.3. I'll go try the latest version now.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Jason on April 01, 2012, 09:59:54 AM

It's working just fine for me on my M-box.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Jason on April 01, 2012, 10:04:10 AM

Anybody else getting "no response was received for the Tester Present message" when trying to detect supported baud rates?

Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Switching to KWP2000 session.
Connected
Disabling Windows sleep mode.
Please wait while all supported baud rates are detected.
Detecting supported baud rates.
Detecting supported baud rates failed.
100% complete.
Restoring Windows sleep mode.
Disconnecting because no response was received for the Tester Present message.
Disconnected

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: julex on April 02, 2012, 01:52:43 PM

Quote from: Jason on March 29, 2012, 11:15:12 PM

It is uncertain. I've had it happen couple of times on slow rate and low amount of variables situation... Since then I log about 2x as more stuff at same rate and no problems at all. Seems like it is fairly inconsistent.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Jason on April 02, 2012, 02:09:31 PM

Quote from: julex on April 02, 2012, 01:52:43 PM

Did your cluster die completely like mine? Or did it spring back right away?

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: s5fourdoor on April 04, 2012, 08:57:37 PM

pardon my ignorance but where are the xml definition files required to use the logger?

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: masterj on April 09, 2012, 01:12:19 PM

Quick question here: Is boot mode now fully supported? I mean read and write access?

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: lulu2003 on April 12, 2012, 07:13:39 AM

tried nefmoto flasher (OBD) with a ME7.8 but no luck:

Quote

04/Apr/2012 10:45:59.609: USER: Validated FTDI device is in dumb mode.
04/Apr/2012 10:45:59.671: LOG: Starting send receive thread.
04/Apr/2012 10:45:59.703: LOG: Send receive thread now started.
04/Apr/2012 10:45:59.703: USER: Disconnected
04/Apr/2012 10:45:59.781: LOG: Setting communication timings to defaults.
04/Apr/2012 10:45:59.781: LOG: Set timing parameters to defaults.
04/Apr/2012 10:45:59.781: USER: Connecting...
04/Apr/2012 10:45:59.812: LOG: Setting communication timings to defaults.
04/Apr/2012 10:45:59.828: USER: Starting slow init connection.
04/Apr/2012 10:46:02.468: USER: Connecting to address 0x01.
04/Apr/2012 10:46:04.703: LOG: Read incorrect sync byte, guessing baud rate is actually 9600.
04/Apr/2012 10:46:04.765: LOG: Not enough key bytes, read: 0
04/Apr/2012 10:46:04.781: USER: Slow init failed.
04/Apr/2012 10:46:04.781: USER: Disconnected
04/Apr/2012 10:46:04.812: LOG: Setting communication timings to defaults.
04/Apr/2012 10:46:04.812: USER: Connecting...
04/Apr/2012 10:46:04.843: LOG: Setting communication timings to defaults.
04/Apr/2012 10:46:04.843: USER: Starting slow init connection.
04/Apr/2012 10:46:07.453: USER: Connecting to address 0x01.
04/Apr/2012 10:46:10.265: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
04/Apr/2012 10:46:10.328: LOG: Not enough key bytes, read: 0
04/Apr/2012 10:46:10.343: USER: Slow init failed.
04/Apr/2012 10:46:10.343: USER: Disconnected
04/Apr/2012 10:46:10.375: LOG: Setting communication timings to defaults.
04/Apr/2012 10:46:10.375: USER: Connecting...
04/Apr/2012 10:46:10.421: LOG: Setting communication timings to defaults.
04/Apr/2012 10:46:10.421: USER: Starting slow init connection.
04/Apr/2012 10:46:13.031: USER: Connecting to address 0x01.
04/Apr/2012 10:46:15.843: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
04/Apr/2012 10:46:15.906: LOG: Not enough key bytes, read: 0
04/Apr/2012 10:46:15.921: USER: Slow init failed.
04/Apr/2012 10:46:15.921: USER: Disconnected
04/Apr/2012 10:46:15.953: LOG: Setting communication timings to defaults.
04/Apr/2012 10:46:15.968: LOG: Closing FTDI device.

ME7L succeeds to connect to that ECU but only fails in writing to memory as a limit of the ECU image.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: LHN86 on April 14, 2012, 07:56:59 AM

I tested the new version no, with orginal ross-tech HEX+CAN. Worked nice to read out in 124800 baud and slow int.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: marcellus on April 17, 2012, 05:27:27 PM

I think my ECU is Screwed now. Please help. I just upgraded to this version of the flasher and in the process of flashing it errored out and now the ecu wont turn on.

17/Apr/2012 04:46:15.400: LOG: Sent message with service ID TransferData
17/Apr/2012 04:46:15.444: LOG: Received message with service ID: TransferDataPositiveResponse
17/Apr/2012 04:46:15.471: LOG: Sent message with service ID TransferData
17/Apr/2012 04:46:15.516: LOG: Received message with service ID: TransferDataPositiveResponse
17/Apr/2012 04:46:15.542: LOG: Sent message with service ID TransferData
17/Apr/2012 04:46:15.586: LOG: Received message with service ID: TransferDataPositiveResponse
17/Apr/2012 04:46:15.612: LOG: Sent message with service ID TransferData
17/Apr/2012 04:46:15.614: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 64 of 65 bytes.
17/Apr/2012 04:46:15.614: LOG: Expected: 00 FB 36 47 BD 93 45 2F B2 B8 45 C0 B5 B9 01 B7 88 B8 9B 89 C3 B3 E5 42 45 89 E2 9D C5 8E 7A B9 E9 93 85 4A 45 9D 9D 43 45 E0 05 89 C3 93 B5 44 45 93 CD 01 05 C0 05 C1 ED 93 85 42 45 9D 9D 4B 45 A8 0B 49 AD 21 BB B7 7A AF B2 44 45 92 C5 4F 04 4F 43 93 45 92 4D 21 BA B7 45 C1 BD B7 09 B8 88 B9 93 87 CB 9C B5 43 4D 9D C5 0E 05 B9 E9 93 85 4A 45 9D 9D 43 45 E0 05 89 C3 B3 C5 44 45 89 C2 9D C5 8E 7A C1 0D CF E5 9C 85 43 4D 93 95 44 45 A9 03 47 A5 2E BB B6 72 A1 BA 4B 45 93 CD 41 0C 40 43 92 4D 9C 45 2E BA B6 4D CF B5 B8 09 B9 80 B7 9B 88 CB 9D BD 4D 45 2E BA B6 4D 9D C5 8E 7A B9 E9 93 85 4A 45 9D 9D 43 45 E0 05 89 C3 93 B5 44 45 93 CD 01 05 C0 05 C1 ED 93 85 42 45 9D 9D 4B 45 A8 0B 49 AD 21 BB B7 7A AF B2 44 45 92 C5 A7 04 4F 43 93 45 92 4D 21 BA B7 45 D1
17/Apr/2012 04:46:15.614: LOG: Read: 00 FB 36 47 BD 93 45 2F B2 B8 45 C0 B5 B9 01 B7 88 B8 9B 89 C3 B3 E5 42 45 89 E2 9D C5 8E 7A B9 E9 93 85 4A 45 9D 9D 43 45 E0 05 89 C3 93 B5 44 45 93 CD 01 05 C0 05 C1 ED 93 85 42 45 9D 9D 4B 00
17/Apr/2012 04:46:15.615: LOG: Clearing remaining expected echo bytes.
17/Apr/2012 04:46:17.619: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
17/Apr/2012 04:46:17.619: LOG: Flushing 1 bytes from receive buffer due to P1 ECU response inter byte time out.
17/Apr/2012 04:46:17.619: LOG: Message received no replies.
17/Apr/2012 04:46:17.619: LOG: Resending message. Send attempts: 2
17/Apr/2012 04:46:17.643: LOG: Sent message with service ID TransferData
17/Apr/2012 04:46:19.647: LOG: Message received no replies.
17/Apr/2012 04:46:19.647: LOG: Failed to read echo within time limit. Clearing remaining expected echo bytes.
17/Apr/2012 04:46:19.648: LOG: Resending message. Send attempts: 3
17/Apr/2012 04:46:19.673: LOG: Sent message with service ID TransferData
17/Apr/2012 04:46:21.676: LOG: Message received no replies.
17/Apr/2012 04:46:21.676: LOG: Failed to read echo within time limit. Clearing remaining expected echo bytes.
17/Apr/2012 04:46:21.676: LOG: Failed to send message 3 times, message send failed.
17/Apr/2012 04:46:21.677: LOG: Did not receive any replies to message.
17/Apr/2012 04:46:22.175: LOG: Sent message with service ID TesterPresent
17/Apr/2012 04:46:24.177: LOG: Message received no replies.
17/Apr/2012 04:46:24.177: LOG: Failed to read echo within time limit. Clearing remaining expected echo bytes.
17/Apr/2012 04:46:24.177: LOG: Resending message. Send attempts: 2
17/Apr/2012 04:46:24.177: LOG: Sent message with service ID TesterPresent
17/Apr/2012 04:46:26.179: LOG: Message received no replies.
17/Apr/2012 04:46:26.179: LOG: Failed to read echo within time limit. Clearing remaining expected echo bytes.
17/Apr/2012 04:46:26.179: LOG: Resending message. Send attempts: 3
17/Apr/2012 04:46:26.180: LOG: Sent message with service ID TesterPresent
17/Apr/2012 04:46:28.183: LOG: Message received no replies.
17/Apr/2012 04:46:28.183: LOG: Failed to read echo within time limit. Clearing remaining expected echo bytes.
17/Apr/2012 04:46:28.183: LOG: Failed to send message 3 times, message send failed.
17/Apr/2012 04:46:28.183: USER: Disconnecting because no response was received for the Tester Present message.
17/Apr/2012 04:46:28.183: USER: Disconnected
17/Apr/2012 04:46:28.196: LOG: Closing FTDI device.
17/Apr/2012 04:46:28.206: LOG: Send receive thread now terminated.
17/Apr/2012 04:52:18.365: LOG: User Prompt - Title: Communication Error Message: A communication error was encountered while flashing. Press Cancel to abort, or OK to continue after reconnecting. Result: OK
17/Apr/2012 04:52:18.366: USER: Waiting for user to reconnect to ECU before continuing...
17/Apr/2012 04:52:18.367: USER: Waiting for user to reconnect to ECU before continuing...
17/Apr/2012 04:52:26.059: LOG: User Prompt - Title: Confirm Cancel Operation Message: Press OK to cancel the current operation, or Cancel otherwise. Result: OK
17/Apr/2012 04:52:26.059: USER: Cancelling current operation.
17/Apr/2012 04:52:26.069: USER: Writing ECU flash memory failed.
17/Apr/2012 04:52:26.077: USER: 100% complete.
17/Apr/2012 04:52:28.213: USER: Restoring Windows sleep mode.
17/Apr/2012 04:52:34.330: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.0
17/Apr/2012 04:52:38.181: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.0
17/Apr/2012 04:52:38.274: LOG: Cannot load license file, file does not exist: C:\Users\Marcellus\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
17/Apr/2012 04:52:38.321: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.0
17/Apr/2012 04:53:50.362: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.0
17/Apr/2012 04:53:58.198: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.0
17/Apr/2012 04:53:58.268: LOG: Cannot load license file, file does not exist: C:\Users\Marcellus\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
17/Apr/2012 04:53:58.308: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.0
17/Apr/2012 04:54:05.432: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.0
17/Apr/2012 04:55:31.450: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.0
17/Apr/2012 04:55:31.540: LOG: Cannot load license file, file does not exist: C:\Users\Marcellus\AppData\Roaming\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
17/Apr/2012 04:55:31.590: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.0

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: marcellus on April 18, 2012, 12:39:37 PM

I tried Minimot (the absolute worst thing to set up for someone like me) and the EEPROM writer in bootmode. Nothing worked. I unplugged the battery over night, and was able to connect and flash with the older Version of the Flasher. I dont know what happenned. Only thing different between this time and all the other times I have been flashing was the Utility itself.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: TheDSI on April 22, 2012, 03:23:02 AM

hi, I've tried to connect to my friends audi S3 AMK with nefmoto ecu flasher with a genuine rosstech hex-usb .
when engine is not runing I can connect to ecu with slow init, fast init don't work .

Code:

21/avr./2012 05:43:54.984: LOG: Opened FTDI device.
21/avr./2012 05:43:54.984: LOG: FTDI device info - Description: Ross-Tech KII-USB Serial Number: RT000001 Device Type: FT_DEVICE_232R ID: 0x403FA24 Device Flags: 0x0
21/avr./2012 05:43:54.984: LOG: FTDI ChipID DLL is loaded, checking chip ID...
21/avr./2012 05:43:55.000: LOG: FTDI device chip ID: 0x40CFB4D9
21/avr./2012 05:43:55.046: USER: Validated FTDI device is in dumb mode.
21/avr./2012 05:43:55.062: LOG: Starting send receive thread.
21/avr./2012 05:43:55.062: LOG: Send receive thread now started.
21/avr./2012 05:43:55.062: USER: Disconnected
21/avr./2012 05:43:55.093: LOG: Setting communication timings to defaults.
21/avr./2012 05:43:55.093: USER: Connecting...
21/avr./2012 05:43:55.125: LOG: Setting communication timings to defaults.
21/avr./2012 05:43:55.140: USER: Starting fast init connection.
21/avr./2012 05:43:55.140: USER: Connecting to address 0x01.
21/avr./2012 05:43:57.921: USER: Fast init sent, sending start communication request.
21/avr./2012 05:43:59.937: LOG: Message received no replies.
21/avr./2012 05:43:59.937: LOG: Failed to send message 1 times, message send failed.
21/avr./2012 05:43:59.937: USER: Start communication request did not receive any response.
21/avr./2012 05:43:59.937: USER: Disconnected
21/avr./2012 05:43:59.968: LOG: Setting communication timings to defaults.
21/avr./2012 05:43:59.984: USER: Connecting...
21/avr./2012 05:44:00.015: LOG: Setting communication timings to defaults.
21/avr./2012 05:44:00.015: USER: Starting fast init connection.
21/avr./2012 05:44:00.015: USER: Connecting to address 0x01.
21/avr./2012 05:44:02.750: USER: Fast init sent, sending start communication request.
21/avr./2012 05:44:04.796: LOG: Message received no replies.
21/avr./2012 05:44:04.796: LOG: Failed to send message 1 times, message send failed.
21/avr./2012 05:44:04.796: USER: Start communication request did not receive any response.
21/avr./2012 05:44:04.796: USER: Disconnected
21/avr./2012 05:44:04.828: LOG: Setting communication timings to defaults.
21/avr./2012 05:44:04.843: USER: Connecting...
21/avr./2012 05:44:04.875: LOG: Setting communication timings to defaults.
21/avr./2012 05:44:04.875: USER: Starting fast init connection.
21/avr./2012 05:44:04.875: USER: Connecting to address 0x01.
21/avr./2012 05:44:07.609: USER: Fast init sent, sending start communication request.
21/avr./2012 05:44:09.625: LOG: Message received no replies.
21/avr./2012 05:44:09.625: LOG: Failed to send message 1 times, message send failed.
21/avr./2012 05:44:09.625: USER: Start communication request did not receive any response.
21/avr./2012 05:44:09.625: USER: Disconnected
21/avr./2012 05:44:09.656: LOG: Setting communication timings to defaults.
21/avr./2012 05:44:09.671: LOG: Closing FTDI device.
21/avr./2012 05:44:09.671: LOG: Send receive thread now terminated.
21/avr./2012 05:44:22.156: LOG: Opened FTDI device.
21/avr./2012 05:44:22.156: LOG: FTDI device info - Description: Ross-Tech KII-USB Serial Number: RT000001 Device Type: FT_DEVICE_232R ID: 0x403FA24 Device Flags: 0x0
21/avr./2012 05:44:22.156: LOG: FTDI ChipID DLL is loaded, checking chip ID...
21/avr./2012 05:44:22.156: LOG: FTDI device chip ID: 0x40CFB4D9
21/avr./2012 05:44:22.203: USER: Validated FTDI device is in dumb mode.
21/avr./2012 05:44:22.218: LOG: Starting send receive thread.
21/avr./2012 05:44:22.218: LOG: Send receive thread now started.
21/avr./2012 05:44:22.218: USER: Disconnected
21/avr./2012 05:44:22.250: LOG: Setting communication timings to defaults.
21/avr./2012 05:44:22.250: USER: Connecting...
21/avr./2012 05:44:22.281: LOG: Setting communication timings to defaults.
21/avr./2012 05:44:22.281: USER: Starting slow init connection.
21/avr./2012 05:44:24.937: USER: Connecting to address 0x01.
21/avr./2012 05:44:27.125: USER: Slow init succeeded.
21/avr./2012 05:44:27.125: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
21/avr./2012 05:44:27.125: USER: Switching to KWP1281 session.
21/avr./2012 05:44:27.312: LOG: KWP1281 read block
21/avr./2012 05:44:27.375: LOG: KWP1281 sent block
21/avr./2012 05:44:27.625: LOG: KWP1281 read block
21/avr./2012 05:44:27.687: LOG: KWP1281 sent block
21/avr./2012 05:44:27.765: LOG: KWP1281 read block
21/avr./2012 05:44:27.828: LOG: KWP1281 sent block
21/avr./2012 05:44:27.968: LOG: KWP1281 read block
21/avr./2012 05:44:28.031: LOG: KWP1281 sent block
21/avr./2012 05:44:28.078: LOG: KWP1281 read block
21/avr./2012 05:44:28.140: LOG: KWP1281 sent block
21/avr./2012 05:44:28.140: USER: KWP1281 connect info: ¸N0906018CH 1.8L R4/5VT     G   0005 S¬þ
21/avr./2012 05:44:29.640: USER: Connecting to address 0x01.
21/avr./2012 05:44:31.828: USER: Slow init succeeded.
21/avr./2012 05:44:32.000: LOG: KWP1281 read block
21/avr./2012 05:44:32.062: LOG: KWP1281 sent block
21/avr./2012 05:44:32.343: LOG: KWP1281 read block
21/avr./2012 05:44:32.406: LOG: KWP1281 sent block
21/avr./2012 05:44:32.593: LOG: KWP1281 read block
21/avr./2012 05:44:32.671: LOG: KWP1281 sent block
21/avr./2012 05:44:32.796: LOG: KWP1281 read block
21/avr./2012 05:44:32.859: LOG: KWP1281 sent block
21/avr./2012 05:44:32.906: LOG: KWP1281 read block
21/avr./2012 05:44:32.968: LOG: KWP1281 sent block
21/avr./2012 05:44:32.968: USER: KWP1281 connect info: ¸N0906018CH 1.8L R4/5VT     G   0005 S¬þ
21/avr./2012 05:44:34.468: USER: Connecting to address 0x11.
21/avr./2012 05:44:37.281: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
21/avr./2012 05:44:37.343: LOG: Not enough key bytes, read: 0
21/avr./2012 05:44:37.359: USER: Slow init failed.
21/avr./2012 05:44:37.359: USER: Disconnected
21/avr./2012 05:44:37.390: LOG: Setting communication timings to defaults.
21/avr./2012 05:44:37.390: USER: Connecting...
21/avr./2012 05:44:37.421: LOG: Setting communication timings to defaults.
21/avr./2012 05:44:37.437: USER: Starting slow init connection.
21/avr./2012 05:44:40.046: USER: Connecting to address 0x01.
21/avr./2012 05:44:42.218: USER: Slow init succeeded.
21/avr./2012 05:44:42.406: LOG: KWP1281 read block
21/avr./2012 05:44:42.468: LOG: KWP1281 sent block
21/avr./2012 05:44:42.812: LOG: KWP1281 read block
21/avr./2012 05:44:42.875: LOG: KWP1281 sent block
21/avr./2012 05:44:43.046: LOG: KWP1281 read block
21/avr./2012 05:44:43.109: LOG: KWP1281 sent block
21/avr./2012 05:44:43.265: LOG: KWP1281 read block
21/avr./2012 05:44:43.328: LOG: KWP1281 sent block
21/avr./2012 05:44:43.359: LOG: KWP1281 read block
21/avr./2012 05:44:43.421: LOG: KWP1281 sent block
21/avr./2012 05:44:43.421: USER: KWP1281 connect info: ¸N0906018CH 1.8L R4/5VT     G   0005 S¬þ
21/avr./2012 05:44:44.921: USER: Connecting to address 0x01.
21/avr./2012 05:44:46.734: LOG: Read incorrect sync byte, guessing baud rate is actually 9600.
21/avr./2012 05:44:46.812: LOG: Not enough key bytes, read: 0
21/avr./2012 05:44:46.828: USER: Slow init failed.
21/avr./2012 05:44:46.828: USER: Disconnected
21/avr./2012 05:44:46.843: LOG: Setting communication timings to defaults.
21/avr./2012 05:44:46.843: USER: Connecting...
21/avr./2012 05:44:46.875: LOG: Setting communication timings to defaults.
21/avr./2012 05:44:46.875: USER: Starting slow init connection.
21/avr./2012 05:44:49.484: USER: Connecting to address 0x01.
21/avr./2012 05:44:51.671: USER: Slow init succeeded.
21/avr./2012 05:44:51.875: LOG: KWP1281 read block
21/avr./2012 05:44:51.937: LOG: KWP1281 sent block
21/avr./2012 05:44:52.171: LOG: KWP1281 read block
21/avr./2012 05:44:52.250: LOG: KWP1281 sent block
21/avr./2012 05:44:52.421: LOG: KWP1281 read block
21/avr./2012 05:44:52.484: LOG: KWP1281 sent block
21/avr./2012 05:44:52.625: LOG: KWP1281 read block
21/avr./2012 05:44:52.687: LOG: KWP1281 sent block
21/avr./2012 05:44:52.734: LOG: KWP1281 read block
21/avr./2012 05:44:52.796: LOG: KWP1281 sent block
21/avr./2012 05:44:52.796: USER: KWP1281 connect info: ¸N0906018CH 1.8L R4/5VT     G   0005 S¬þ
21/avr./2012 05:44:54.312: USER: Connecting to address 0x01.
21/avr./2012 05:44:56.500: USER: Slow init succeeded.
21/avr./2012 05:44:56.687: LOG: KWP1281 read block
21/avr./2012 05:44:56.750: LOG: KWP1281 sent block
21/avr./2012 05:44:57.015: LOG: KWP1281 read block
21/avr./2012 05:44:57.078: LOG: KWP1281 sent block
21/avr./2012 05:44:57.265: LOG: KWP1281 read block
21/avr./2012 05:44:57.328: LOG: KWP1281 sent block
21/avr./2012 05:44:57.468: LOG: KWP1281 read block
21/avr./2012 05:44:57.546: LOG: KWP1281 sent block
21/avr./2012 05:44:57.578: LOG: KWP1281 read block
21/avr./2012 05:44:57.640: LOG: KWP1281 sent block
21/avr./2012 05:44:57.640: USER: KWP1281 connect info: ¸N0906018CH 1.8L R4/5VT     G   0005 S¬þ
21/avr./2012 05:44:59.171: USER: Connecting to address 0x11.
21/avr./2012 05:45:01.015: LOG: Read incorrect sync byte, guessing baud rate is actually 9600.
21/avr./2012 05:45:01.093: LOG: Not enough key bytes, read: 0
21/avr./2012 05:45:01.093: USER: Slow init failed.
21/avr./2012 05:45:01.093: USER: Disconnected
21/avr./2012 05:45:01.125: LOG: Setting communication timings to defaults.
21/avr./2012 05:45:01.140: LOG: Closing FTDI device.
21/avr./2012 05:45:01.140: LOG: Send receive thread now terminated.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: TheDSI on April 22, 2012, 03:23:58 AM

when I try to start variable reading

Code:

21/avr./2012 05:48:46.187: USER: Starting variable reading.
21/avr./2012 05:48:46.203: LOG: Received message with service ID: TesterPresentPositiveReponse
21/avr./2012 05:48:46.531: LOG: Starting DevelopmentSession diagnostic session with 124800 baud rate.
21/avr./2012 05:48:46.531: USER: Starting diagnostic session.
21/avr./2012 05:48:46.562: LOG: Sent message with service ID StartDiagnosticSession
21/avr./2012 05:48:46.609: LOG: Received message with service ID: StartDiagnosticSessionPositiveResponse
21/avr./2012 05:48:46.609: LOG: Setting communication timings to defaults.
21/avr./2012 05:48:46.609: LOG: Changed diagnostic session type to: DevelopmentSession
21/avr./2012 05:48:46.609: LOG: ECU requesting specific baud rate: 124800
21/avr./2012 05:48:46.609: USER: Successfully started diagnostic session.
21/avr./2012 05:48:46.609: USER: Negotiating communication timings.
21/avr./2012 05:48:46.625: LOG: Reading current communication timings.
21/avr./2012 05:48:46.656: LOG: Sent message with service ID AccessTimingParameters
21/avr./2012 05:48:46.671: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 0 of 4 bytes.
21/avr./2012 05:48:46.671: LOG: Expected: 02 83 02 87 
21/avr./2012 05:48:46.671: LOG: Read:     00 02 00 06 
21/avr./2012 05:48:46.671: LOG: Clearing remaining expected echo bytes.
21/avr./2012 05:48:46.687: LOG: Could not construct valid message from received data: InvalidChecksum
21/avr./2012 05:48:46.687: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00
21/avr./2012 05:48:46.687: LOG: Could not construct valid message from received data: InvalidChecksum
21/avr./2012 05:50:30.453: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x06
21/avr./2012 05:50:32.484: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:32.484: LOG: Flushing 7 bytes from receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:32.484: LOG: Message received no replies.
21/avr./2012 05:50:32.484: LOG: Resending message. Send attempts: 2
21/avr./2012 05:50:32.500: LOG: Sent message with service ID AccessTimingParameters
21/avr./2012 05:50:32.500: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 0 of 4 bytes.
21/avr./2012 05:50:32.500: LOG: Expected: 02 83 02 87 
21/avr./2012 05:50:32.500: LOG: Read:     00 02 00 06 
21/avr./2012 05:50:32.500: LOG: Clearing remaining expected echo bytes.
21/avr./2012 05:50:34.515: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:34.515: LOG: Flushing 4 bytes from receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:34.515: LOG: Message received no replies.
21/avr./2012 05:50:34.515: LOG: Resending message. Send attempts: 3
21/avr./2012 05:50:34.531: LOG: Sent message with service ID AccessTimingParameters
21/avr./2012 05:50:34.531: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 0 of 4 bytes.
21/avr./2012 05:50:34.531: LOG: Expected: 02 83 02 87 
21/avr./2012 05:50:34.531: LOG: Read:     00 02 00 06 
21/avr./2012 05:50:34.531: LOG: Clearing remaining expected echo bytes.
21/avr./2012 05:50:36.531: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:36.531: LOG: Flushing 4 bytes from receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:36.531: LOG: Message received no replies.
21/avr./2012 05:50:36.531: LOG: Failed to send message 3 times, message send failed.
21/avr./2012 05:50:36.531: LOG: Did not receive any replies to message.
21/avr./2012 05:50:36.546: USER: 100% complete.
21/avr./2012 05:50:36.546: USER: Stopped reading variables.
21/avr./2012 05:50:36.546: USER: Restoring Windows sleep mode.
21/avr./2012 05:50:37.046: LOG: Sent message with service ID TesterPresent
21/avr./2012 05:50:37.046: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 0 of 4 bytes.
21/avr./2012 05:50:37.046: LOG: Expected: 02 3E 01 41 
21/avr./2012 05:50:37.046: LOG: Read:     00 3C 00 00 
21/avr./2012 05:50:37.046: LOG: Clearing remaining expected echo bytes.
21/avr./2012 05:50:39.062: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:39.062: LOG: Flushing 4 bytes from receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:39.062: LOG: Message received no replies.
21/avr./2012 05:50:39.062: LOG: Resending message. Send attempts: 2
21/avr./2012 05:50:39.078: LOG: Sent message with service ID TesterPresent
21/avr./2012 05:50:39.078: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 0 of 4 bytes.
21/avr./2012 05:50:39.078: LOG: Expected: 02 3E 01 41 
21/avr./2012 05:50:39.078: LOG: Read:     00 3C 00 00 
21/avr./2012 05:50:39.078: LOG: Clearing remaining expected echo bytes.
21/avr./2012 05:50:41.078: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:41.078: LOG: Flushing 4 bytes from receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:41.078: LOG: Message received no replies.
21/avr./2012 05:50:41.078: LOG: Resending message. Send attempts: 3
21/avr./2012 05:50:41.109: LOG: Sent message with service ID TesterPresent
21/avr./2012 05:50:41.109: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 0 of 4 bytes.
21/avr./2012 05:50:41.109: LOG: Expected: 02 3E 01 41 
21/avr./2012 05:50:41.109: LOG: Read:     00 3C 00 00 
21/avr./2012 05:50:41.109: LOG: Clearing remaining expected echo bytes.
21/avr./2012 05:50:43.109: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:43.109: LOG: Flushing 4 bytes from receive buffer due to P1 ECU response inter byte time out.
21/avr./2012 05:50:43.109: LOG: Message received no replies.
21/avr./2012 05:50:43.109: LOG: Failed to send message 3 times, message send failed.
21/avr./2012 05:50:43.109: USER: Disconnecting because no response was received for the Tester Present message.
21/avr./2012 05:50:43.109: USER: Disconnected
21/avr./2012 05:50:43.171: LOG: Closing FTDI device.
21/avr./2012 05:50:43.171: LOG: Send receive thread now terminated.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: TheDSI on April 22, 2012, 03:27:56 AM

when I try to connect slow init when engine is running

Code:

21/avr./2012 05:42:47.984: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.0
21/avr./2012 05:43:00.500: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
21/avr./2012 05:43:00.578: LOG: Opened FTDI device.
21/avr./2012 05:43:00.578: LOG: FTDI device info - Description: Ross-Tech KII-USB Serial Number: RT000001 Device Type: FT_DEVICE_232R ID: 0x403FA24 Device Flags: 0x0
21/avr./2012 05:43:00.578: LOG: FTDI ChipID DLL is loaded, checking chip ID...
21/avr./2012 05:43:00.593: LOG: FTDI device chip ID: 0x40CFB4D9
21/avr./2012 05:43:00.671: USER: Validated FTDI device is in dumb mode.
21/avr./2012 05:43:00.687: LOG: Starting send receive thread.
21/avr./2012 05:43:00.687: LOG: Send receive thread now started.
21/avr./2012 05:43:00.734: USER: Disconnected
21/avr./2012 05:43:00.750: LOG: Setting communication timings to defaults.
21/avr./2012 05:43:00.750: LOG: Set timing parameters to defaults.
21/avr./2012 05:43:00.750: USER: Connecting...
21/avr./2012 05:43:00.765: LOG: Setting communication timings to defaults.
21/avr./2012 05:43:00.781: USER: Starting slow init connection.
21/avr./2012 05:43:03.390: USER: Connecting to address 0x01.
21/avr./2012 05:43:05.593: USER: Slow init succeeded.
21/avr./2012 05:43:05.593: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
21/avr./2012 05:43:05.593: USER: Switching to KWP1281 session.
21/avr./2012 05:43:05.781: LOG: KWP1281 read block
21/avr./2012 05:43:05.843: LOG: KWP1281 sent block
21/avr./2012 05:43:06.187: LOG: KWP1281 read block
21/avr./2012 05:43:06.250: LOG: KWP1281 sent block
21/avr./2012 05:43:06.328: LOG: KWP1281 read block
21/avr./2012 05:43:06.390: LOG: KWP1281 sent block
21/avr./2012 05:43:06.531: LOG: KWP1281 read block
21/avr./2012 05:43:06.593: LOG: KWP1281 sent block
21/avr./2012 05:43:06.640: LOG: KWP1281 read block
21/avr./2012 05:43:06.703: LOG: KWP1281 sent block
21/avr./2012 05:43:06.703: USER: KWP1281 connect info: ¸N0906018CH 1.8L R4/5VT     G   0005 S¬þ
21/avr./2012 05:43:08.203: USER: Connecting to address 0x01.
21/avr./2012 05:43:10.390: USER: Slow init succeeded.
21/avr./2012 05:43:10.578: LOG: KWP1281 read block
21/avr./2012 05:43:10.640: LOG: KWP1281 sent block
21/avr./2012 05:43:10.906: LOG: KWP1281 read block
21/avr./2012 05:43:10.968: LOG: KWP1281 sent block
21/avr./2012 05:43:11.156: LOG: KWP1281 read block
21/avr./2012 05:43:11.218: LOG: KWP1281 sent block
21/avr./2012 05:43:11.359: LOG: KWP1281 read block
21/avr./2012 05:43:11.421: LOG: KWP1281 sent block
21/avr./2012 05:43:11.453: LOG: KWP1281 read block
21/avr./2012 05:43:11.531: LOG: KWP1281 sent block
21/avr./2012 05:43:11.531: USER: KWP1281 connect info: ¸N0906018CH 1.8L R4/5VT     G   0005 S¬þ
21/avr./2012 05:43:13.031: USER: Connecting to address 0x11.
21/avr./2012 05:43:15.843: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
21/avr./2012 05:43:15.906: LOG: Not enough key bytes, read: 0
21/avr./2012 05:43:15.921: USER: Slow init failed.
21/avr./2012 05:43:15.921: USER: Disconnected
21/avr./2012 05:43:15.937: LOG: Setting communication timings to defaults.
21/avr./2012 05:43:15.937: USER: Connecting...
21/avr./2012 05:43:15.968: LOG: Setting communication timings to defaults.
21/avr./2012 05:43:15.968: USER: Starting slow init connection.
21/avr./2012 05:43:18.578: USER: Connecting to address 0x01.
21/avr./2012 05:43:20.781: USER: Slow init succeeded.
21/avr./2012 05:43:20.968: LOG: KWP1281 read block
21/avr./2012 05:43:21.031: LOG: KWP1281 sent block
21/avr./2012 05:43:21.281: LOG: KWP1281 read block
21/avr./2012 05:43:21.343: LOG: KWP1281 sent block
21/avr./2012 05:43:21.531: LOG: KWP1281 read block
21/avr./2012 05:43:21.593: LOG: KWP1281 sent block
21/avr./2012 05:43:21.734: LOG: KWP1281 read block
21/avr./2012 05:43:21.796: LOG: KWP1281 sent block
21/avr./2012 05:43:21.843: LOG: KWP1281 read block
21/avr./2012 05:43:21.906: LOG: KWP1281 sent block
21/avr./2012 05:43:21.906: USER: KWP1281 connect info: ¸N0906018CH 1.8L R4/5VT     G   0005 S¬þ
21/avr./2012 05:43:23.406: USER: Connecting to address 0x01.
21/avr./2012 05:43:25.593: USER: Slow init succeeded.
21/avr./2012 05:43:25.781: LOG: KWP1281 read block
21/avr./2012 05:43:25.843: LOG: KWP1281 sent block
21/avr./2012 05:43:26.109: LOG: KWP1281 read block
21/avr./2012 05:43:26.171: LOG: KWP1281 sent block
21/avr./2012 05:43:26.359: LOG: KWP1281 read block
21/avr./2012 05:43:26.421: LOG: KWP1281 sent block
21/avr./2012 05:43:26.578: LOG: KWP1281 read block
21/avr./2012 05:43:26.640: LOG: KWP1281 sent block
21/avr./2012 05:43:26.671: LOG: KWP1281 read block
21/avr./2012 05:43:26.734: LOG: KWP1281 sent block
21/avr./2012 05:43:26.734: USER: KWP1281 connect info: ¸N0906018CH 1.8L R4/5VT     G   0005 S¬þ
21/avr./2012 05:43:28.234: USER: Connecting to address 0x11.
21/avr./2012 05:43:31.046: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
21/avr./2012 05:43:31.109: LOG: Not enough key bytes, read: 0
21/avr./2012 05:43:31.125: USER: Slow init failed.
21/avr./2012 05:43:31.125: USER: Disconnected
21/avr./2012 05:43:31.156: LOG: Setting communication timings to defaults.
21/avr./2012 05:43:31.156: USER: Connecting...
21/avr./2012 05:43:31.171: LOG: Setting communication timings to defaults.
21/avr./2012 05:43:31.171: USER: Starting slow init connection.
21/avr./2012 05:43:33.781: USER: Connecting to address 0x01.
21/avr./2012 05:43:35.968: USER: Slow init succeeded.
21/avr./2012 05:43:36.156: LOG: KWP1281 read block
21/avr./2012 05:43:36.218: LOG: KWP1281 sent block
21/avr./2012 05:43:36.484: LOG: KWP1281 read block
21/avr./2012 05:43:36.546: LOG: KWP1281 sent block
21/avr./2012 05:43:36.718: LOG: KWP1281 read block
21/avr./2012 05:43:36.781: LOG: KWP1281 sent block
21/avr./2012 05:43:36.921: LOG: KWP1281 read block
21/avr./2012 05:43:36.984: LOG: KWP1281 sent block
21/avr./2012 05:43:37.031: LOG: KWP1281 read block
21/avr./2012 05:43:37.093: LOG: KWP1281 sent block
21/avr./2012 05:43:37.093: USER: KWP1281 connect info: ¸N0906018CH 1.8L R4/5VT     G   0005 S¬þ
21/avr./2012 05:43:38.609: USER: Connecting to address 0x01.
21/avr./2012 05:43:40.859: USER: Slow init succeeded.
21/avr./2012 05:43:41.031: LOG: KWP1281 read block
21/avr./2012 05:43:41.093: LOG: KWP1281 sent block
21/avr./2012 05:43:41.375: LOG: KWP1281 read block
21/avr./2012 05:43:41.437: LOG: KWP1281 sent block
21/avr./2012 05:43:41.625: LOG: KWP1281 read block
21/avr./2012 05:43:41.687: LOG: KWP1281 sent block
21/avr./2012 05:43:41.843: LOG: KWP1281 read block
21/avr./2012 05:43:41.906: LOG: KWP1281 sent block
21/avr./2012 05:43:41.953: LOG: KWP1281 read block
21/avr./2012 05:43:42.015: LOG: KWP1281 sent block
21/avr./2012 05:43:42.015: USER: KWP1281 connect info: ¸N0906018CH 1.8L R4/5VT     G   0005 S¬þ
21/avr./2012 05:43:43.515: USER: Connecting to address 0x11.
21/avr./2012 05:43:46.328: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
21/avr./2012 05:43:46.390: LOG: Not enough key bytes, read: 0
21/avr./2012 05:43:46.406: USER: Slow init failed.
21/avr./2012 05:43:46.406: USER: Disconnected
21/avr./2012 05:43:46.421: LOG: Setting communication timings to defaults.
21/avr./2012 05:43:46.453: LOG: Closing FTDI device.
21/avr./2012 05:43:46.453: LOG: Send receive thread now terminated.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on May 07, 2012, 11:45:19 AM

I'm having problems with in car flash.

I get a security error. I'll post logs next time i try flashing.

currently, i HAVE to use the bench flasher.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Snow Trooper on May 07, 2012, 05:13:15 PM

Quote from: nyet on May 07, 2012, 11:45:19 AM

I'm having problems with in car flash.

I get a security error. I'll post logs next time i try flashing.

currently, i HAVE to use the bench flasher.

That happened to me after a recent Vcds update, I reinstalled nef, drivers and deleted all old Rosstech drivers and issue went away.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on May 07, 2012, 05:20:42 PM

Thanks ST, i'll give that a shot tonight.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on May 08, 2012, 01:16:00 PM

no joy

08/May/2012 01:10:27.947: USER: Requesting security access.
08/May/2012 01:10:27.974: LOG: Sent message with service ID SecurityAccess
08/May/2012 01:10:28.020: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.023: LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
08/May/2012 01:10:28.027: USER: ECU reports that security access request was rejected.

Code:

08/May/2012 01:10:07.880: LOG: Opened FTDI device.
08/May/2012 01:10:07.881: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A400GNA4 Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
08/May/2012 01:10:07.882: LOG: FTDI ChipID DLL is loaded, checking chip ID...
08/May/2012 01:10:07.883: LOG: FTDI device chip ID: 0xEC7BA6D5
08/May/2012 01:10:07.893: USER: Validated FTDI device is in dumb mode.
08/May/2012 01:10:07.898: LOG: Starting send receive thread.
08/May/2012 01:10:07.900: LOG: Send receive thread now started.
08/May/2012 01:10:07.900: USER: Disconnected
08/May/2012 01:10:07.915: LOG: Setting communication timings to defaults.
08/May/2012 01:10:07.915: USER: Connecting...
08/May/2012 01:10:07.932: LOG: Setting communication timings to defaults.
08/May/2012 01:10:07.933: USER: Starting slow init connection.
08/May/2012 01:10:10.533: USER: Connecting to address 0x01.
08/May/2012 01:10:12.679: USER: Slow init succeeded.
08/May/2012 01:10:12.680: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
08/May/2012 01:10:12.680: USER: Switching to KWP1281 session.
08/May/2012 01:10:12.861: LOG: KWP1281 read block
08/May/2012 01:10:12.925: LOG: KWP1281 sent block
08/May/2012 01:10:13.193: LOG: KWP1281 read block
08/May/2012 01:10:13.257: LOG: KWP1281 sent block
08/May/2012 01:10:13.435: LOG: KWP1281 read block
08/May/2012 01:10:13.499: LOG: KWP1281 sent block
08/May/2012 01:10:13.645: LOG: KWP1281 read block
08/May/2012 01:10:13.708: LOG: KWP1281 sent block
08/May/2012 01:10:13.746: LOG: KWP1281 read block
08/May/2012 01:10:13.810: LOG: KWP1281 sent block
08/May/2012 01:10:13.811: USER: KWP1281 connect info: 8D0907551M  2.7l V6/5VT     G   0002 4oTO
08/May/2012 01:10:15.311: USER: Connecting to address 0x01.
08/May/2012 01:10:17.486: USER: Slow init succeeded.
08/May/2012 01:10:17.487: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
08/May/2012 01:10:17.488: USER: Switching to KWP2000 session.
08/May/2012 01:10:17.488: USER: Connected
08/May/2012 01:10:20.037: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:20.073: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:22.554: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:22.598: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:25.072: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:25.111: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:27.499: USER: Disabling Windows sleep mode.
08/May/2012 01:10:27.549: USER: Writing ECU flash memory.
08/May/2012 01:10:27.591: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:27.593: LOG: Reading ECU identification option: 0x9C
08/May/2012 01:10:27.625: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:27.663: LOG: Sent message with service ID ReadECUIdentification
08/May/2012 01:10:27.711: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
08/May/2012 01:10:27.716: LOG: Read ECU identification option: 0x9C
08/May/2012 01:10:27.716: LOG: Successfully read ECU identification information
08/May/2012 01:10:27.736: USER: ECU reports programming session preconditions have been met.
08/May/2012 01:10:27.740: USER: Negotiating communication timings.
08/May/2012 01:10:27.740: LOG: Reading current communication timings.
08/May/2012 01:10:27.757: LOG: Sent message with service ID AccessTimingParameters
08/May/2012 01:10:27.803: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08/May/2012 01:10:27.806: LOG: Set timing parameters to new values.
08/May/2012 01:10:27.806: LOG: Setting communication timing to defaults.
08/May/2012 01:10:27.829: LOG: Sent message with service ID AccessTimingParameters
08/May/2012 01:10:27.869: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08/May/2012 01:10:27.869: LOG: Reading current communication timings.
08/May/2012 01:10:27.901: LOG: Sent message with service ID AccessTimingParameters
08/May/2012 01:10:27.943: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08/May/2012 01:10:27.944: USER: Successfully changed to new communication timings.
08/May/2012 01:10:27.947: USER: Requesting security access.
08/May/2012 01:10:27.974: LOG: Sent message with service ID SecurityAccess
08/May/2012 01:10:28.020: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.023: LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
08/May/2012 01:10:28.027: USER: ECU reports that security access request was rejected.
08/May/2012 01:10:28.031: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
08/May/2012 01:10:28.032: USER: Starting diagnostic session.
08/May/2012 01:10:28.054: LOG: Sent message with service ID StartDiagnosticSession
08/May/2012 01:10:28.090: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.091: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08/May/2012 01:10:28.130: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.131: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08/May/2012 01:10:28.170: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.171: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08/May/2012 01:10:28.210: LOG: Received message with service ID: NegativeResponse

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on May 08, 2012, 01:39:04 PM

ah interesting. on the bench i also get the same security error, but it ignores the problem and completes fine

Quote

08/May/2012 01:10:28.286: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.287: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08/May/2012 01:10:28.326: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.327: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08/May/2012 01:10:28.362: LOG: Received message with service ID: StartDiagnosticSessionPositiveResponse
08/May/2012 01:10:28.369: LOG: Setting communication timings to defaults.
08/May/2012 01:10:28.370: LOG: Set timing parameters to defaults.

when in the car, it just goes into a loop with that negative response forever.

on the bench it continues as above

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on May 08, 2012, 01:41:23 PM

Quote from: Snow Trooper on May 07, 2012, 05:13:15 PM

That happened to me after a recent Vcds update, I reinstalled nef, drivers and deleted all old Rosstech drivers and issue went away.

which drivers did you install? off of ftd site, or whatever win7 automatically installs?

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Snow Trooper on May 09, 2012, 10:56:29 AM

I use Vcds v10.8 and my custom vcp drivers. The new Ross tech drivers don't get along with much of anything it seems

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Jason on May 09, 2012, 10:59:45 AM

And the installer is rather persistent in trying to trick you into installing them.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on May 10, 2012, 01:28:15 PM

Still no joy on in car flashing.

Bench flashing works just fine...

anybody else have any advice?

Tony appears to be awol :/

I blame D3

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Jason on May 10, 2012, 01:55:41 PM

Quote from: nyet on May 08, 2012, 01:16:00 PM

Code:

08/May/2012 01:10:07.880: LOG: Opened FTDI device.
08/May/2012 01:10:07.881: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A400GNA4 Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
08/May/2012 01:10:07.882: LOG: FTDI ChipID DLL is loaded, checking chip ID...
08/May/2012 01:10:07.883: LOG: FTDI device chip ID: 0xEC7BA6D5
08/May/2012 01:10:07.893: USER: Validated FTDI device is in dumb mode.
08/May/2012 01:10:07.898: LOG: Starting send receive thread.
08/May/2012 01:10:07.900: LOG: Send receive thread now started.
08/May/2012 01:10:07.900: USER: Disconnected
08/May/2012 01:10:07.915: LOG: Setting communication timings to defaults.
08/May/2012 01:10:07.915: USER: Connecting...
08/May/2012 01:10:07.932: LOG: Setting communication timings to defaults.
08/May/2012 01:10:07.933: USER: Starting slow init connection.
08/May/2012 01:10:10.533: USER: Connecting to address 0x01.
08/May/2012 01:10:12.679: USER: Slow init succeeded.
08/May/2012 01:10:12.680: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
08/May/2012 01:10:12.680: USER: Switching to KWP1281 session.
08/May/2012 01:10:12.861: LOG: KWP1281 read block
08/May/2012 01:10:12.925: LOG: KWP1281 sent block
08/May/2012 01:10:13.193: LOG: KWP1281 read block
08/May/2012 01:10:13.257: LOG: KWP1281 sent block
08/May/2012 01:10:13.435: LOG: KWP1281 read block
08/May/2012 01:10:13.499: LOG: KWP1281 sent block
08/May/2012 01:10:13.645: LOG: KWP1281 read block
08/May/2012 01:10:13.708: LOG: KWP1281 sent block
08/May/2012 01:10:13.746: LOG: KWP1281 read block
08/May/2012 01:10:13.810: LOG: KWP1281 sent block
08/May/2012 01:10:13.811: USER: KWP1281 connect info: 8D0907551M  2.7l V6/5VT     G   0002 4oTO
08/May/2012 01:10:15.311: USER: Connecting to address 0x01.
08/May/2012 01:10:17.486: USER: Slow init succeeded.
08/May/2012 01:10:17.487: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
08/May/2012 01:10:17.488: USER: Switching to KWP2000 session.
08/May/2012 01:10:17.488: USER: Connected
08/May/2012 01:10:20.037: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:20.073: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:22.554: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:22.598: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:25.072: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:25.111: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:27.499: USER: Disabling Windows sleep mode.
08/May/2012 01:10:27.549: USER: Writing ECU flash memory.
08/May/2012 01:10:27.591: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:27.593: LOG: Reading ECU identification option: 0x9C
08/May/2012 01:10:27.625: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:27.663: LOG: Sent message with service ID ReadECUIdentification
08/May/2012 01:10:27.711: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
08/May/2012 01:10:27.716: LOG: Read ECU identification option: 0x9C
08/May/2012 01:10:27.716: LOG: Successfully read ECU identification information
08/May/2012 01:10:27.736: USER: ECU reports programming session preconditions have been met.
08/May/2012 01:10:27.740: USER: Negotiating communication timings.
08/May/2012 01:10:27.740: LOG: Reading current communication timings.
08/May/2012 01:10:27.757: LOG: Sent message with service ID AccessTimingParameters
08/May/2012 01:10:27.803: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08/May/2012 01:10:27.806: LOG: Set timing parameters to new values.
08/May/2012 01:10:27.806: LOG: Setting communication timing to defaults.
08/May/2012 01:10:27.829: LOG: Sent message with service ID AccessTimingParameters
08/May/2012 01:10:27.869: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08/May/2012 01:10:27.869: LOG: Reading current communication timings.
08/May/2012 01:10:27.901: LOG: Sent message with service ID AccessTimingParameters
08/May/2012 01:10:27.943: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08/May/2012 01:10:27.944: USER: Successfully changed to new communication timings.
08/May/2012 01:10:27.947: USER: Requesting security access.
08/May/2012 01:10:27.974: LOG: Sent message with service ID SecurityAccess
08/May/2012 01:10:28.020: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.023: LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
08/May/2012 01:10:28.027: USER: ECU reports that security access request was rejected.
08/May/2012 01:10:28.031: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
08/May/2012 01:10:28.032: USER: Starting diagnostic session.
08/May/2012 01:10:28.054: LOG: Sent message with service ID StartDiagnosticSession
08/May/2012 01:10:28.090: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.091: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08/May/2012 01:10:28.130: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.131: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08/May/2012 01:10:28.170: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.171: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08/May/2012 01:10:28.210: LOG: Received message with service ID: NegativeResponse

I had this exact same problem this morning. I had to uninstall and revert to 1.9.2.3

If you need it let me know.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on May 10, 2012, 02:53:15 PM

yes plz thx

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Jason on May 10, 2012, 02:58:35 PM

See attached.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Badnewsmike on May 14, 2012, 08:27:32 AM

So im in a 06 2.5L jetta CAN 07K906032AQ I pulled the File using the 800 memory, modded the file check-sum and want to reload it back to the ECU and its giving me a memory error? Ive tried every memory setting Nefmoto has.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: vtraudt on June 03, 2012, 06:55:28 AM

Quote from: Tony@NefMoto on March 17, 2012, 01:51:50 PM

This is the version 1.9.3.0 release of the NefMoto software.

What is the recommended software and version for just data logging with Win7 32bit?

Title: Data Logging with 1.9.3.0
Post by: vtraudt on June 10, 2012, 02:22:16 PM

I installed 1.9.3.0 on my win32 machine.
Connected cable.
Engine running.
Found hardware KWP2000. Connected. Displayed baud rate 124800.
Click 'KWP2000 logging' tab.
Used all presets (All variables per sample, max sample rate per sec: 10.
Clicked 'start reading'
Clicked 'start recording'
About 52 seconds "Log Entries: 518 Log item: 0"
Clicked 'save log'
Saved in preset location (program files/...) names "test"
Went to file location: there is a xml file with that name, size 1kb

Now what?
- there was or is nothing to see on the Me7 screen
- playback shows nothing

Seems not data was recorded?

Car

Title: Re: Data Logging with 1.9.3.0
Post by: vtraudt on June 15, 2012, 04:53:35 AM

Quote from: vtraudt on June 10, 2012, 02:22:16 PM

How can I 'see' that data is recorded? Should there be something on the screen?

Since the cable is recognized (same cable used for data logging with other software; also used to read/write tunes (older version) to ECUs) and selected its own transfer rate, I don't think its the cable.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: marty.h on June 17, 2012, 05:09:06 AM

I cannot get this to read the map of my ecu here is the log any ideas ?

Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 8D0907551E 2.7l V6/5VT G 0002
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Disabling Windows sleep mode.
Reading all ECU info.
Starting diagnostic session.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Reading all ECU info failed.
100% complete.
Restoring Windows sleep mode.
Starting loading of info.
Cancelling loading of info.
Starting loading of info.
Cancelling loading of info.
Switching to KWP2000 session.
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 8D0907551E 2.7l V6/5VT G 0002
Slow init succeeded.
Switching to KWP2000 session.
Connected
Disconnecting because no response was received for the Tester Present message.
Disconnected
Switching to KWP2000 session.
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 8D0907551E 2.7l V6/5VT G 0002
Disabling Windows sleep mode.
Starting variable reading.
Starting diagnostic session.
Disconnecting because no response was received for the Tester Present message.
Disconnected
100% complete.
Stopped reading variables.
Restoring Windows sleep mode.
Starting loading of DTCs.
Cancelling loading of DTCs.
Switching to KWP2000 session.
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Start communication request did not receive any response.
Disconnected
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Start communication request did not receive any response.
Disconnected
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Switching to KWP2000 session.
Connected
Disabling Windows sleep mode.
Reading all ECU DTCs.
Starting diagnostic session.
Diagnostic session mode does not match requested mode.
Successfully started diagnostic session.
Diagnostic session mode does not match requested mode.
Reading all ECU DTCs failed.
100% complete.
Restoring Windows sleep mode.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Switching to KWP2000 session.
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 8D0907551E 2.7l V6/5VT G 0002
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Disconnecting because no response was received for the Tester Present message.
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 8D0907551E 2.7l V6/5VT G 0002
Connected
Disabling Windows sleep mode.
Reading all ECU info.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
0% complete.
25% complete.
50% complete.
75% complete.
100% complete.
Read 4 ECU info entries:
0x92, System Supplier ECU Hardware Number: 0261206376
0x94, System Supplier ECU Software Number: 1037350221
0x9B, Calibration Date: 8D0907551E , 0002, 0x0000164F, 0x00000000, 0x009D, 2.7l V6/5VT ,
0x9C, Calibration Equiment Software Number: 0x80030000
Restoring Windows sleep mode.
Disconnecting because no response was received for the Tester Present message.
Disconnected

Any ideas what is causing

Thanks in advance
Marty

Title: Re: Data Logging with 1.9.3.0
Post by: vtraudt on June 17, 2012, 06:31:58 AM

Quote from: vtraudt on June 15, 2012, 04:53:35 AM

Can someone post a brief 'how to' to use 1.9.3.0 for data logging purposes?
Unless its the cable, but it shows 'connecting speed'...
I don't seem to be able to figure it out. Win32 computer.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on June 20, 2012, 04:06:22 PM

Quote from: Jason on May 10, 2012, 02:58:35 PM

See attached.

Still can't flash in car.

Have to use bench flasher

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on June 21, 2012, 07:49:33 PM

Went back to old 32-bit XP laptop, with latest 1.9.3.0, no problems.

Looks like its win7 or 64-bit related.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on June 24, 2012, 09:40:41 AM

Can somebody post a known good ftdi driver for win7 64-bit that works with the nefmoto 1.9.3.0 flasher?

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on June 24, 2012, 10:19:50 AM

So i backed down to the ftdi driver tony posted in the 1.9.2.3 thread (CDM20600.zip) and now i get a different error:

Code:

24/Jun/2012 10:15:53.472: LOG: Reading current communication timings.
24/Jun/2012 10:15:53.489: LOG: Sent message with service ID AccessTimingParameters
24/Jun/2012 10:15:53.492: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 0 of 4 bytes.
24/Jun/2012 10:15:53.492: LOG: Expected: 02 83 02 87 
24/Jun/2012 10:15:53.493: LOG: Read:     00 03 00 07 
24/Jun/2012 10:15:53.493: LOG: Clearing remaining expected echo bytes.
24/Jun/2012 10:15:53.558: LOG: Could not construct valid message from received data: InvalidChecksum
24/Jun/2012 10:15:53.558: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00
24/Jun/2012 10:15:53.559: LOG: Could not construct valid message from received data: InvalidChecksum
24/Jun/2012 10:15:53.559: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x03
24/Jun/2012 10:15:53.737: LOG: Could not construct valid message from received data: InvalidChecksum
24/Jun/2012 10:15:53.738: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00
24/Jun/2012 10:15:53.739: LOG: Could not construct valid message from received data: InvalidChecksum
24/Jun/2012 10:15:53.739: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
24/Jun/2012 10:15:53.740: LOG: Could not construct valid message from received data: InvalidChecksum

Also, the flasher still works fine on the bench, this is just in car

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Tony@NefMoto on June 26, 2012, 09:54:18 AM

I'm back from the dead, sort of, and I will be working through the problems people mentioned in this thread.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Tony@NefMoto on June 26, 2012, 11:25:08 PM

Quote from: Jason on March 25, 2012, 03:51:45 PM

Something I noticed, and maybe it's just this winders install being stupid, but if I read a file and want to over-write an existing file, the application hangs in the save file dialog box...

I have already implemented a fix for this, and it will be in the next release. Thanks for pointing it out though, as it took me a long time to track this down myself. Turned out it was a problem with handling UI events on a background thread and not the main UI thread.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Tony@NefMoto on June 26, 2012, 11:31:36 PM

Quote from: Jason on April 01, 2012, 10:04:10 AM

Anybody else getting "no response was received for the Tester Present message" when trying to detect supported baud rates?

I think I know what is happening here. The ECU is not responding to one of the StartDiagnosticSession messages and that is causing the process to fail. I wrote the code assuming the ECU would always respond. I will add support for handling the case of no respose from the ECU for a particular baud rate to the next release.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Tony@NefMoto on June 26, 2012, 11:43:25 PM

Quote from: nyet on May 08, 2012, 01:16:00 PM

Code:

08/May/2012 01:10:07.880: LOG: Opened FTDI device.
08/May/2012 01:10:07.881: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A400GNA4 Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
08/May/2012 01:10:07.882: LOG: FTDI ChipID DLL is loaded, checking chip ID...
08/May/2012 01:10:07.883: LOG: FTDI device chip ID: 0xEC7BA6D5
08/May/2012 01:10:07.893: USER: Validated FTDI device is in dumb mode.
08/May/2012 01:10:07.898: LOG: Starting send receive thread.
08/May/2012 01:10:07.900: LOG: Send receive thread now started.
08/May/2012 01:10:07.900: USER: Disconnected
08/May/2012 01:10:07.915: LOG: Setting communication timings to defaults.
08/May/2012 01:10:07.915: USER: Connecting...
08/May/2012 01:10:07.932: LOG: Setting communication timings to defaults.
08/May/2012 01:10:07.933: USER: Starting slow init connection.
08/May/2012 01:10:10.533: USER: Connecting to address 0x01.
08/May/2012 01:10:12.679: USER: Slow init succeeded.
08/May/2012 01:10:12.680: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
08/May/2012 01:10:12.680: USER: Switching to KWP1281 session.
08/May/2012 01:10:12.861: LOG: KWP1281 read block
08/May/2012 01:10:12.925: LOG: KWP1281 sent block
08/May/2012 01:10:13.193: LOG: KWP1281 read block
08/May/2012 01:10:13.257: LOG: KWP1281 sent block
08/May/2012 01:10:13.435: LOG: KWP1281 read block
08/May/2012 01:10:13.499: LOG: KWP1281 sent block
08/May/2012 01:10:13.645: LOG: KWP1281 read block
08/May/2012 01:10:13.708: LOG: KWP1281 sent block
08/May/2012 01:10:13.746: LOG: KWP1281 read block
08/May/2012 01:10:13.810: LOG: KWP1281 sent block
08/May/2012 01:10:13.811: USER: KWP1281 connect info: 8D0907551M  2.7l V6/5VT     G   0002 4oTO
08/May/2012 01:10:15.311: USER: Connecting to address 0x01.
08/May/2012 01:10:17.486: USER: Slow init succeeded.
08/May/2012 01:10:17.487: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
08/May/2012 01:10:17.488: USER: Switching to KWP2000 session.
08/May/2012 01:10:17.488: USER: Connected
08/May/2012 01:10:20.037: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:20.073: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:22.554: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:22.598: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:25.072: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:25.111: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:27.499: USER: Disabling Windows sleep mode.
08/May/2012 01:10:27.549: USER: Writing ECU flash memory.
08/May/2012 01:10:27.591: LOG: Sent message with service ID TesterPresent
08/May/2012 01:10:27.593: LOG: Reading ECU identification option: 0x9C
08/May/2012 01:10:27.625: LOG: Received message with service ID: TesterPresentPositiveReponse
08/May/2012 01:10:27.663: LOG: Sent message with service ID ReadECUIdentification
08/May/2012 01:10:27.711: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
08/May/2012 01:10:27.716: LOG: Read ECU identification option: 0x9C
08/May/2012 01:10:27.716: LOG: Successfully read ECU identification information
08/May/2012 01:10:27.736: USER: ECU reports programming session preconditions have been met.
08/May/2012 01:10:27.740: USER: Negotiating communication timings.
08/May/2012 01:10:27.740: LOG: Reading current communication timings.
08/May/2012 01:10:27.757: LOG: Sent message with service ID AccessTimingParameters
08/May/2012 01:10:27.803: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08/May/2012 01:10:27.806: LOG: Set timing parameters to new values.
08/May/2012 01:10:27.806: LOG: Setting communication timing to defaults.
08/May/2012 01:10:27.829: LOG: Sent message with service ID AccessTimingParameters
08/May/2012 01:10:27.869: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08/May/2012 01:10:27.869: LOG: Reading current communication timings.
08/May/2012 01:10:27.901: LOG: Sent message with service ID AccessTimingParameters
08/May/2012 01:10:27.943: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08/May/2012 01:10:27.944: USER: Successfully changed to new communication timings.
08/May/2012 01:10:27.947: USER: Requesting security access.
08/May/2012 01:10:27.974: LOG: Sent message with service ID SecurityAccess
08/May/2012 01:10:28.020: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.023: LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
08/May/2012 01:10:28.027: USER: ECU reports that security access request was rejected.
08/May/2012 01:10:28.031: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
08/May/2012 01:10:28.032: USER: Starting diagnostic session.
08/May/2012 01:10:28.054: LOG: Sent message with service ID StartDiagnosticSession
08/May/2012 01:10:28.090: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.091: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08/May/2012 01:10:28.130: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.131: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08/May/2012 01:10:28.170: LOG: Received message with service ID: NegativeResponse
08/May/2012 01:10:28.171: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08/May/2012 01:10:28.210: LOG: Received message with service ID: NegativeResponse

The general reject to the security response is a red herring. The NefMoto software tries to negotiate security before and after starting the programming session. On almost all cars only the security negotiation after starting the programming session works. The one you are referring to is before starting the programming session, and is essentially guaranteeed to fail on all but a few types of cars.

Did the software just continually output "NegativeResonse RequestCorrectlyReceived_ResponsePending?" If so, then that means the ECU was trying to enter programming mode, but was never quite getting there for some reason. The ECU would have been trying to relocate the running code from the flash memory to RAM and was waiting until that finished. It looks like something was going on that prevented the switching to programming mode running out of RAM from finishing.

Do any other versions of the NefMoto software work for you in car?

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on June 27, 2012, 09:08:12 AM

Nope. Never got any other versions working. Tried a bunch of different drivers too.

Do you have a known good win7-64 driver?

btw 32bit xp works fine on my other laptop. I only have win7-home on the win7 lappy, so i can't do xp mode in a vm on it.

Also, see my other post about using that older ftdi driver... different error...

Code:

24/Jun/2012 10:15:53.472: LOG: Reading current communication timings.
24/Jun/2012 10:15:53.489: LOG: Sent message with service ID AccessTimingParameters
24/Jun/2012 10:15:53.492: LOG: Read incorrect echo from ECU while sending message bytes. Matched first 0 of 4 bytes.
24/Jun/2012 10:15:53.492: LOG: Expected: 02 83 02 87 
24/Jun/2012 10:15:53.493: LOG: Read:     00 03 00 07 
24/Jun/2012 10:15:53.493: LOG: Clearing remaining expected echo bytes.
24/Jun/2012 10:15:53.558: LOG: Could not construct valid message from received data: InvalidChecksum
24/Jun/2012 10:15:53.558: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00
24/Jun/2012 10:15:53.559: LOG: Could not construct valid message from received data: InvalidChecksum
24/Jun/2012 10:15:53.559: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x03
24/Jun/2012 10:15:53.737: LOG: Could not construct valid message from received data: InvalidChecksum
24/Jun/2012 10:15:53.738: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00
24/Jun/2012 10:15:53.739: LOG: Could not construct valid message from received data: InvalidChecksum
24/Jun/2012 10:15:53.739: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
24/Jun/2012 10:15:53.740: LOG: Could not construct valid message from received data: InvalidChecksum

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Tony@NefMoto on June 28, 2012, 01:58:43 PM

Quote from: nyet on June 27, 2012, 09:08:12 AM

Do you have a known good win7-64 driver?

I have always just used what FTDI has on there site: http://www.ftdichip.com/Drivers/D2XX.htm

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on July 02, 2012, 04:38:06 PM

Tony: i tried EVERYTHING. Nothing works, only bench :(

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Tony@NefMoto on July 02, 2012, 07:48:15 PM

A few other people have sent me log files. It looks like some changes I made to negotiating timing parameters in version 1.9.3.0 broke connecting for most people.

So if the NefMoto software worked for you prior to version 1.9.3.0 and doesn't anymore, and the software always fails with negotiating timing parameters, then I hope to have a fix for you in the next day or so.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on July 02, 2012, 08:49:27 PM

Quote from: Tony@NefMoto on July 02, 2012, 07:48:15 PM

So if the NefMoto software worked for you prior to version 1.9.3.0 and doesn't anymore, and the software always fails with negotiating timing parameters

Actually, thats the problem; that laptop has NEVER worked in car, even with 1.9.2.x.... so I am not sure changing it back to 1.9.2.x or earlier will help...

Should I try 1.9.1.x?

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Tony@NefMoto on July 02, 2012, 10:26:47 PM

Quote from: nyet on July 02, 2012, 08:49:27 PM

Actually, thats the problem; that laptop has NEVER worked in car, even with 1.9.2.x.... so I am not sure changing it back to 1.9.2.x or earlier will help...

Should I try 1.9.1.x?

In reply #48 in this thread on June 27, the log you posted showing the error that occurred right after accessing timing parameters should get fixed in the next release. Is there another error you are getting when you try to connect in car?

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: nyet on July 02, 2012, 11:11:46 PM

Nope. Thats the one that needs fixing.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: automan001 on July 03, 2012, 01:35:47 PM

I tried to read flash from ME7.5 ecu on the desk using this tool. There is issue with security access request while reading. I think it was assumed that user would do this while ecu is connected with instrument cluster and immo is on. I decided to turn the immo off in the ecu to avoid the problem with security. I've successfully read ecu's eeprom, turned immo off manually in the dump, recalculated check sum for modified lines and wrote modified eeprom back in boot mode using the same 95040 tools. But the Nefmoto flashing tool still tried to send authorization request after immo was really off. And it received another response from ecu that "authorization is not supported" on the unit. It recognized this as erorr and failed to read the flash. I think if it skipped the request it would be able to read the flash. Is it possible to read flash without sending auth request in case when the immo is off? If yes, is it possible to make this configurable in the tool. Like "skip auth. request" option...

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Tony@NefMoto on July 03, 2012, 02:24:58 PM

Quote from: automan001 on July 03, 2012, 01:35:47 PM

I think if it skipped the request it would be able to read the flash. Is it possible to read flash without sending auth request in case when the immo is off? If yes, is it possible to make this configurable in the tool. Like "skip auth. request" option...

Definitely possible. Can you post the log file so I can see what is happening? If you open the NefMoto software, and open the file menu, there are options to open or find the log file.

Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.0 - With Fast Data Logging
Post by: Tony@NefMoto on July 04, 2012, 10:44:46 PM

Version 1.9.3.2 is now available here: http://nefariousmotorsports.com/forum/index.php?topic=2200.0

NefMoto

Technical => NefMoto Software => Topic started by: Tony@NefMoto on March 17, 2012, 01:51:50 PM