Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
 Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
 |
« Reply #45 on: June 26, 2012, 11:25:08 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. |
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #46 on: June 26, 2012, 11:31:36 PM »
|
|
|
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. |
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #47 on: June 26, 2012, 11:43:25 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. 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? |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #48 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... 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
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #49 on: June 28, 2012, 01:58:43 PM »
|
|
|
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 |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #50 on: July 02, 2012, 04:38:06 PM »
|
|
|
Tony: i tried EVERYTHING. Nothing works, only bench  |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #51 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.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #52 on: July 02, 2012, 08:49:27 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? |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #53 on: July 02, 2012, 10:26:47 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? |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #54 on: July 02, 2012, 11:11:46 PM »
|
|
|
Nope. Thats the one that needs fixing.
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
automan001
Full Member
Karma: +47/-0
Offline
Posts: 153
|
|
« Reply #55 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...
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #56 on: July 03, 2012, 02:24:58 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. |
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #57 on: July 04, 2012, 10:44:46 PM »
|
|
|
|
|
|
|
|
Logged
|
|
|
|
|
