|
rob.mwpropane
|
 |
« Reply #15 on: February 13, 2012, 05:01:43 PM »
|
|
|
Yup, all new releases are compatible with Windows XP SP2 and later.
Thanks Tony. Awesome. |
|
|
|
|
Logged
|
This has nothing to do with cars but you can see my glorifying job at, www.MWPropane.com |
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
 Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #16 on: February 15, 2012, 12:08:54 PM »
|
|
|
I just posted another small update and bumped the version number to 1.9.2.3.
The update includes a bug fix for the premium feature licensing system when used on Windows XP SP2.
|
|
|
|
|
Logged
|
|
|
|
Il Signor Zetec
Jr. Member
Karma: +0/-4
Offline
Posts: 48
|
 |
« Reply #17 on: February 17, 2012, 03:16:32 AM »
|
|
|
Hello!
I'm trying to read an ecu 1ML 906 032 of a seat leon. this ecu has inside the 95040 file of my audi S3 (putted with me7 95040 software). the car starts and run without problems. whe I want to read ecu with nefmoto software, I read ecu information and when I try to read flash file (with memory layout 29F800, 29F800BB or 29F800BT), the software go in error for IMMOBILIZER NOT AUTHENTICATED: what can I do???
|
|
|
|
|
Logged
|
|
|
|
Jacknk
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #18 on: February 21, 2012, 11:03:12 AM »
|
|
|
I'm not sure what I am doing wrong but any help would be appreciated. When I run the program it will connect with fast init but when I try to do anything the program just disappears. If I click slow inti the program disappears?  ?? Any ideas. |
|
|
|
|
Logged
|
|
|
|
|
julex
|
|
« Reply #19 on: February 21, 2012, 01:58:32 PM »
|
|
|
Check the nefmoto log file and event viewer in control panel/administrative tools for anything abnormal?
|
|
|
|
|
Logged
|
|
|
|
Jacknk
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #20 on: February 21, 2012, 02:34:29 PM »
|
|
|
I looked and did not see any errors. I am not a computer guru so not exactly sure what I am looking for. I wonder if it could be because I have the FT232BN chip instead of the FT232R chip? |
|
|
|
|
Logged
|
|
|
|
NOTORIOUS VR
Administrator
Hero Member
Karma: +58/-7
Offline
Posts: 1056
|
|
« Reply #21 on: February 27, 2012, 01:20:08 PM »
|
|
|
Does the flasher not work w/ 1.8T's?
I get the following error:
Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
100% complete.
|
|
|
|
|
Logged
|
|
|
|
carlossus
Sr. Member
Karma: +38/-0
Offline
Posts: 394
Leon Curpa Stg1+
|
|
« Reply #22 on: February 27, 2012, 02:48:08 PM »
|
|
|
Work fine with my 1.8T (AUQ).
Maybe try flashing back to stock first?
|
|
|
|
|
Logged
|
|
|
|
NOTORIOUS VR
Administrator
Hero Member
Karma: +58/-7
Offline
Posts: 1056
|
|
« Reply #23 on: February 27, 2012, 02:53:43 PM »
|
|
|
Both the current own and I are fairly certain it is stock... and the previous owner says 100% that the car was never flashed.
I will have to try a bench flash
|
|
|
|
|
Logged
|
|
|
|
NOTORIOUS VR
Administrator
Hero Member
Karma: +58/-7
Offline
Posts: 1056
|
|
« Reply #24 on: February 27, 2012, 03:25:06 PM »
|
|
|
Also just got a call from my buddy... he said the CEL came on after he drove home last night... scanned code shows something along the lines of (software programming not complete) and he says there is no boost and the car is very slow.
I never even tried a write... only read and that failed.
|
|
|
|
|
Logged
|
|
|
|
|
s5fourdoor
|
|
« Reply #25 on: February 27, 2012, 07:45:58 PM »
|
|
|
hey Tony - i believe i bricked my ecu today, not real sure. the car starts and then immediately shuts off. the check engine light and epc light flash even with the engine off yet the ignition turned to on. here's the error i'm getting from your program, which is a bit strange, because it looks like its connecting but not allowing writing. please let me know what to do from here. i've never bricked the ecu in over a year of using your software, so a bit nervous here... lol
any idea?
just checked the log and here's the output from today:
27/Feb/2012 06:19:01.591: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
27/Feb/2012 06:19:01.640: LOG: Opened FTDI device.
27/Feb/2012 06:19:01.641: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A800ecWH Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
27/Feb/2012 06:19:01.641: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Feb/2012 06:19:01.650: LOG: FTDI device chip ID: 0x3302ADF1
27/Feb/2012 06:19:01.698: USER: Validated FTDI device is in dumb mode.
27/Feb/2012 06:19:01.749: LOG: Starting send receive thread.
27/Feb/2012 06:19:01.750: LOG: Send receive thread now started.
27/Feb/2012 06:19:01.780: USER: Disconnected
27/Feb/2012 06:19:01.802: LOG: Setting communication timings to defaults.
27/Feb/2012 06:19:01.802: LOG: Set timing parameters to defaults.
27/Feb/2012 06:19:01.802: USER: Connecting...
27/Feb/2012 06:19:01.824: LOG: Setting communication timings to defaults.
27/Feb/2012 06:19:01.824: USER: Starting fast init connection.
27/Feb/2012 06:19:01.824: USER: Connecting to address 0x01.
27/Feb/2012 06:19:04.556: USER: Fast init sent, sending start communication request.
27/Feb/2012 06:19:04.596: LOG: Received message with service ID: StartCommunicationPositiveResponse
27/Feb/2012 06:19:04.596: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
27/Feb/2012 06:19:04.596: USER: Switching to KWP2000 session.
27/Feb/2012 06:19:04.597: USER: Connected
27/Feb/2012 06:19:07.073: LOG: Sent message with service ID TesterPresent
27/Feb/2012 06:19:09.076: LOG: Message received no replies.
27/Feb/2012 06:19:09.076: LOG: Resending message. Send attempts: 2
27/Feb/2012 06:19:09.095: LOG: Sent message with service ID TesterPresent
27/Feb/2012 06:19:11.098: LOG: Message received no replies.
27/Feb/2012 06:19:11.099: LOG: Resending message. Send attempts: 3
27/Feb/2012 06:19:11.117: LOG: Sent message with service ID TesterPresent
27/Feb/2012 06:19:13.120: LOG: Message received no replies.
27/Feb/2012 06:19:13.121: LOG: Failed to send message 3 times, message send failed.
27/Feb/2012 06:19:13.121: USER: Disconnecting because no response was received for the Tester Present message.
27/Feb/2012 06:19:13.122: USER: Disconnected
27/Feb/2012 06:19:13.188: LOG: Closing FTDI device.
27/Feb/2012 06:19:13.198: LOG: Send receive thread now terminated.
27/Feb/2012 06:19:32.886: LOG: Closing NefMoto VW Audi ME7 Flasher Logger1.9.2.2
also here's the log of the last flash which occured right before the issue:
27/Feb/2012 06:01:58.993: LOG: Received negative response for service ID: RequestRoutineResultsByLocalIdentifier, with response code: RoutineNotCompleteOrServiceInProgress
27/Feb/2012 06:01:58.995: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier
27/Feb/2012 06:01:59.012: LOG: Received message with service ID: RequestRoutineResultsByLocalIdentifierPositiveResponse
27/Feb/2012 06:01:59.013: LOG: Checksum is correct.
27/Feb/2012 06:01:59.014: USER: Flash checksum matches new data, flashing was successful.
27/Feb/2012 06:01:59.014: USER: Disconnecting from ECU to force it to recognize successful completion of flash write.
27/Feb/2012 06:01:59.026: USER: Writing ECU flash memory succeeded. Wrote 19 of 19 sectors in flash memory.
Flashing time was 00:00:54.
27/Feb/2012 06:02:00.245: USER: Restoring Windows sleep mode.
27/Feb/2012 06:02:00.305: USER: Disconnecting...
|
|
|
|
« Last Edit: February 27, 2012, 07:53:17 PM by nehalem »
|
Logged
|
|
|
|
NOTORIOUS VR
Administrator
Hero Member
Karma: +58/-7
Offline
Posts: 1056
|
|
« Reply #26 on: February 27, 2012, 08:59:27 PM »
|
|
|
hey Tony - i believe i bricked my ecu today, not real sure. the car starts and then immediately shuts off. the check engine light and epc light flash even with the engine off yet the ignition turned to on.
I've had that happen to me a few times.. it's always been a checksum issue... If you're using the MTX plug in, use another way to correct your files or at least check them after using the MTX-plug in |
|
|
|
|
Logged
|
|
|
|
|
s5fourdoor
|
|
« Reply #27 on: February 27, 2012, 09:31:57 PM »
|
|
|
definitely always use me7checker after the mtx-auto-write for tuner pro. this time it said no problem as usual. a strange new thing is occuring now. the throttle body is making nasty clicking noises, like its recalibrating. the epc and CEL are flashing slowly but consistently. headed out to try vagcom now, maybe clear a code or perform an adaptation of the tb, fingers crossed. any idea?
|
|
|
|
|
Logged
|
|
|
|
NOTORIOUS VR
Administrator
Hero Member
Karma: +58/-7
Offline
Posts: 1056
|
|
« Reply #28 on: February 28, 2012, 06:59:40 AM »
|
|
|
other then flashing back a different program, no.
but your experience is identical to mine, and it was always a checksum issue from the MTX plug in... WinOLS would find an invalid checksum on the file that did that to me.
I had to use my Galletto cable in boot mode to recover FWIW.
|
|
|
|
|
Logged
|
|
|
|
|
marcellus
|
|
« Reply #29 on: February 28, 2012, 08:56:56 PM »
|
|
|
I cant get the utility to read my ecm. I want to save the current tune just in case and it just gets hung up "negotiating communication timings"
LOG:
28/Feb/2012 07:55:19.898: LOG: Sent message with service ID TesterPresent
28/Feb/2012 07:55:19.913: LOG: Received message with service ID: TesterPresentPositiveReponse
28/Feb/2012 07:55:22.403: LOG: Sent message with service ID TesterPresent
28/Feb/2012 07:55:22.416: LOG: Received message with service ID: TesterPresentPositiveReponse
28/Feb/2012 07:55:24.908: LOG: Sent message with service ID TesterPresent
28/Feb/2012 07:55:24.920: LOG: Received message with service ID: TesterPresentPositiveReponse
28/Feb/2012 07:55:27.413: LOG: Sent message with service ID TesterPresent
28/Feb/2012 07:55:27.424: LOG: Received message with service ID: TesterPresentPositiveReponse
28/Feb/2012 07:55:29.917: LOG: Sent message with service ID TesterPresent
28/Feb/2012 07:55:29.929: LOG: Received message with service ID: TesterPresentPositiveReponse
28/Feb/2012 07:55:30.964: USER: Disabling Windows sleep mode.
28/Feb/2012 07:55:30.978: USER: Reading ECU flash memory.
28/Feb/2012 07:55:31.054: LOG: Reading ECU identification option: 0x9C
28/Feb/2012 07:55:31.057: LOG: Sent message with service ID ReadECUIdentification
28/Feb/2012 07:55:31.080: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
28/Feb/2012 07:55:31.094: LOG: Read ECU identification option: 0x9C
28/Feb/2012 07:55:31.094: LOG: Successfully read ECU identification information
28/Feb/2012 07:55:31.100: USER: ECU reports programming session preconditions have been met.
28/Feb/2012 07:55:31.101: USER: Negotiating communication timings.
28/Feb/2012 07:55:31.101: LOG: Reading current communication timings.
28/Feb/2012 07:55:31.107: LOG: Sent message with service ID AccessTimingParameters
28/Feb/2012 07:55:31.132: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
28/Feb/2012 07:55:31.132: LOG: Setting communication timing to defaults.
28/Feb/2012 07:55:31.137: LOG: Sent message with service ID AccessTimingParameters
28/Feb/2012 07:55:31.156: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
28/Feb/2012 07:55:31.156: LOG: Reading current communication timings.
28/Feb/2012 07:55:31.161: LOG: Sent message with service ID AccessTimingParameters
28/Feb/2012 07:55:31.212: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
28/Feb/2012 07:55:31.212: USER: Successfully changed to new communication timings.
28/Feb/2012 07:55:31.214: USER: Requesting security access.
28/Feb/2012 07:55:31.217: LOG: Sent message with service ID SecurityAccess
28/Feb/2012 07:55:31.257: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.258: LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
28/Feb/2012 07:55:31.260: USER: ECU reports that security access request was rejected.
28/Feb/2012 07:55:31.260: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
28/Feb/2012 07:55:31.261: USER: Starting diagnostic session.
28/Feb/2012 07:55:31.264: LOG: Sent message with service ID StartDiagnosticSession
28/Feb/2012 07:55:31.309: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.310: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.349: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.350: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.389: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.390: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.429: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.430: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.469: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.470: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.505: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.505: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.545: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.545: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.583: LOG: Received message with service ID: StartDiagnosticSessionPositiveResponse
28/Feb/2012 07:55:31.584: LOG: Setting communication timings to defaults.
28/Feb/2012 07:55:31.584: LOG: Set timing parameters to defaults.
28/Feb/2012 07:55:31.584: LOG: Changed diagnostic session type to: ProgrammingSession
28/Feb/2012 07:55:31.584: LOG: ECU requesting specific baud rate: 124800
28/Feb/2012 07:55:31.587: USER: Successfully started diagnostic session.
28/Feb/2012 07:55:31.588: USER: Negotiating communication timings.
28/Feb/2012 07:55:31.588: LOG: Reading current communication timings.
28/Feb/2012 07:55:31.656: LOG: Sent message with service ID AccessTimingParameters
28/Feb/2012 07:55:31.929: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:31.929: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:31.958: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:31.958: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:31.988: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:31.989: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.018: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.018: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.048: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.049: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.078: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.080: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.108: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.108: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.138: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.138: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.168: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.168: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.200: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.200: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
|
|
|
|
|
Logged
|
|
|
|
|
