NefMoto > Technical > Flashing and Chipping > NefMoto ME7 Flashing Software Release 1.4.2.2 - UPDATED August 11
Pages: 1 ... 7 8 [9] 10
« previous next »
Author Topic: NefMoto ME7 Flashing Software Release 1.4.2.2 - UPDATED August 11  (Read 118144 times)
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #120 on: August 31, 2010, 10:56:57 AM »
Quote from: s4rmm on August 25, 2010, 08:25:13 AM
Tony,
got 3 failed attempts today, 4th succeeded. See attached log, do you know what's causing those errors?
When do you plan to release premium version with sub 40 sec flashing time?
Thanks.


I can see what is going wrong in your logs, but I have no idea why it is happening. The ECU appears to be sending back a response before the program has finished reading back in the echo. Given the way the FTDI USB chip buffers data, this shouldn't be possible. I will try to think of some ways to avoid this problem for the next release.

What ECU are you trying to flash?
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #121 on: August 31, 2010, 11:03:55 AM »
Quote from: pvl on August 30, 2010, 03:13:43 PM
Tried the nefmotoflash-tool on a Seat Cordoba Cupra 1.8T with ME7.5.  It has a 29F400BB flash. 
I wasn't able to get any contact with this box. No info, nor readout.

I think this one runs via K, then via a canbus-reroute back to K-line, when i follow Seat electrical scematics for this
specific car... It is directly programmable via the ME7-tool and a KWP2000+ box with a benchflash-cable.

Hope Tony can chime in, and fill us in about the status as of development on the software...  Dying to try out a (beta) update
from the software, and hopefully can get one of these cars read-out via the obd2-port on the car with the vag-com lead,
kwp2000+ interface or galletto 1260. You name it, i'll try it ! Wink

In the next release I am planning on adding the option to try fast-init mode, in addition to the slow-init mode that I already use. This may improve the connection issues that some ECUs are having.

If the car is using the new CAN-BUS system, then it is hard to say if flashing over the K-line is still supported. If it requires communication over the CAN-BUS, then that would require a CAN-BUS supporting USB cable, and most likely a different flashing protocol. This isn't something I want to spend time on currently.
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #122 on: August 31, 2010, 11:06:05 AM »
Quote from: elRey on August 30, 2010, 02:32:55 PM
Any chance this flash utility can be easily modified to do 29f200 based ECUs on older cars?

AEB 1.8Ts

To test it out, you would need to create a memory layout file for the 29F200 flash memory. Then just try to read or write to the ECU. The log file from that test should let us know how feasible supporting these older cars would be. If they use the KWP2000 protocol to flash and communicate over the K-Line, then it shouldn't be very hard.

I don't have an ECU to test, so you will need to test for yourself and send me the log file.
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #123 on: August 31, 2010, 11:22:59 AM »
In the next release I will be adding support for reading and clearing error codes, as well as allowing you to select between fast-init and slow-init methods of connecting. Hopefully this will fix some connection issues, as well as allow us to identify other errors that occur due to flashing.

After the next release, I am planning on adding support for license files to allow for premium features, such as fast flashing. Flash flashing only writes the memory sectors that are different, and not all sectors. This allows the flash to complete in about 45 seconds.

Ultimately, I don't want to work on the flashing tool anymore, and would rather spend my time working on data logging, map editing, and checksum correction. After I add support for licensing premium features, I plan on spending some time overhauling the user interface to allow for these other features.

You guys just keep finding too many strange connection and communication bugs when trying to flash all these obscure engine computers! Roll Eyes

All I ask is that you keep me up to date on which engine computers you have tried to flash. That way we can keep an accurate record of which ones are supported and which ones aren't.
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
s4rmm
Jr. Member
**

Karma: +4/-1
Offline Offline

Posts: 28
« Reply #124 on: August 31, 2010, 12:42:43 PM »
Quote from: Tony@NefMoto on August 31, 2010, 10:56:57 AM
Quote from: s4rmm on August 25, 2010, 08:25:13 AM
Tony,
got 3 failed attempts today, 4th succeeded. See attached log, do you know what's causing those errors?
When do you plan to release premium version with sub 40 sec flashing time?
Thanks.
I can see what is going wrong in your logs, but I have no idea why it is happening. The ECU appears to be sending back a response before the program has finished reading back in the echo. Given the way the FTDI USB chip buffers data, this shouldn't be possible. I will try to think of some ways to avoid this problem for the next release.

What ECU are you trying to flash?
It's 551G (euro S4). I have flashed more than ten times successfully with releases before 1.4.2.2, maybe had one or two fails too. But this release failed in 3 consecutive flashes. Using x64 Win7 and Ross-Tech cable.
Did one more test - flashed 100% but errors just before the end:

27.aug.2010 05:34:08.796: Successfully erased flash memory.
27.aug.2010 05:34:08.803: Starting data transfer.
27.aug.2010 05:34:08.807: Sent message with service ID TransferData at 05:34:08.805
27.aug.2010 05:34:08.823: Received message with service ID TransferDataPositiveResponse at 05:34:08.822
27.aug.2010 05:34:08.826: 100% complete.
27.aug.2010 05:34:08.828: Data transfer complete.
27.aug.2010 05:34:08.829: Requesting data transfer exit.
27.aug.2010 05:34:08.831: Sent message with service ID RequestTransferExit at 05:34:08.831
27.aug.2010 05:34:09.833: Read incorrect echo from ECU while sending message bytes
27.aug.2010 05:34:09.833: Expected: 01 37 38
27.aug.2010 05:34:09.834: Read:     03 7F 37
27.aug.2010 05:34:09.834: Failed to write message to FTDI device with service ID: RequestTransferExit
27.aug.2010 05:34:09.835: Read incorrect echo from ECU while sending message bytes
27.aug.2010 05:34:09.835: Expected: 01 37 38
27.aug.2010 05:34:09.836: Read:     31 01 37
27.aug.2010 05:34:09.836: Failed to write message to FTDI device with service ID: RequestTransferExit
27.aug.2010 05:34:09.837: Failed to send message 3 times, disconnecting
27.aug.2010 05:34:09.838: Disconnected
27.aug.2010 05:34:09.863: Closing FTDI device.
27.aug.2010 05:34:09.866: Restoring Windows sleep mode.
27.aug.2010 05:34:09.868: Writing ECU Flash Memory Failed.
27.aug.2010 05:35:28.072: Closing NefMoto ME7 ECU Flasher BETA 1.4.2.2
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #125 on: August 31, 2010, 01:10:00 PM »
Thanks for the update. I will try to see what changed with release 1.4.2.2.
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #126 on: August 31, 2010, 09:43:55 PM »
OK s4rmm, I think I know what is happening in your logs. It appears as though the program times out waiting for a response to the RequestTransferExit message. Then when it tries to resend the message, the resent message collides with the late response from the ECU.

I'm trying to figure out how to prevent this now. Thanks for posting the log.
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704
« Reply #127 on: September 06, 2010, 09:35:59 AM »
All other PC's I have access to are Windows XP, which isn't supported?  My laptop uses Windows 7 64bit with a Celeron® ULV Processor 743 @ 1.3GHz, so I don't think speed is an issue.  Tried again yesterday and there is just no communication, but reset my airbag lights fine via VCDS.

Could you recommend a decent cable perhaps?

Rick

Quote from: Tony@NefMoto on August 31, 2010, 10:50:33 AM
Quote from: Rick on August 26, 2010, 12:49:36 PM
Any thoughts as to why I can't connect? 

Any protection wouldn't actually stop it reading info would it?  What about the fact it's a 512KB UK ECU?

Rick

Hi Rick. Looking at your logs, I have really have no idea why you can't connect. Read protection only takes effect after the connection has been opened. Also, VAG-COM connects using the KWP1281 protocol, and my software using the KWP2000 protocol, but regardless it should still at least start the KWP1281 session and then fail to start the KWP2000 session.

What are the specs of the computer you are using? Maybe something is causing a slow down and preventing the slow init timings from being accurate. Could you try it on another computer?
Logged
elRey
Hero Member
*****

Karma: +32/-1
Offline Offline

Posts: 565
« Reply #128 on: September 06, 2010, 05:38:58 PM »
Can this software be used in boot mode?
Logged
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704
« Reply #129 on: September 07, 2010, 08:15:24 AM »
Tony,

I have been told today that the C box does not support KWP2000, only KWP1281.  Can this be supported in a future release?

Rick
Logged
s4rmm
Jr. Member
**

Karma: +4/-1
Offline Offline

Posts: 28
« Reply #130 on: September 08, 2010, 12:45:33 AM »
Quote from: Tony@NefMoto on August 31, 2010, 09:43:55 PM
OK s4rmm, I think I know what is happening in your logs. It appears as though the program times out waiting for a response to the RequestTransferExit message. Then when it tries to resend the message, the resent message collides with the late response from the ECU.

I'm trying to figure out how to prevent this now. Thanks for posting the log.
Switched back to version 1.4.1.1 and flashed couple of times without problems. Maybe this helps to analyze what's changed since that version.
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #131 on: September 09, 2010, 04:39:09 PM »
Quote from: Rick on September 07, 2010, 08:15:24 AM
Tony,

I have been told today that the C box does not support KWP2000, only KWP1281.  Can this be supported in a future release?

Rick

Rick, sorry for the slow reply. If your cable works with VCDS then it isn't the problem. At this point I don't know what is wrong with your setup. I would recommend seeing if your computer and cable can connect to another car to rule out any problem with them. That way we could localize the problem to your car.

The only other idea I have is supporting fast init. I dropped support for fast init because slow init is much more supported and works better. I will try to add back in support for fast init in the next release, or the one immediately after that.

My software starts the connection via slow init to address 0x01 which is a KWP1281 connection method. Then it closes the connection and starts another connection, which VAG ECUs respond to with a KWP2000 connection. So my software already supports connecting using KWP1281, so that isn't the problem.
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #132 on: September 09, 2010, 04:58:09 PM »
Quote from: elRey on September 06, 2010, 05:38:58 PM
Can this software be used in boot mode?

Nope this software does not work in boot mode. This software uses the KWP1281 protocol to connect, and then the KWP2000 protocol to communicate with the ECU. This allows the ECU to be flashed through the dashboard without opening the ECU up unlike boot mode.
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #133 on: September 09, 2010, 04:59:53 PM »
Quote from: s4rmm on September 08, 2010, 12:45:33 AM
Quote from: Tony@NefMoto on August 31, 2010, 09:43:55 PM
OK s4rmm, I think I know what is happening in your logs. It appears as though the program times out waiting for a response to the RequestTransferExit message. Then when it tries to resend the message, the resent message collides with the late response from the ECU.

I'm trying to figure out how to prevent this now. Thanks for posting the log.
Switched back to version 1.4.1.1 and flashed couple of times without problems. Maybe this helps to analyze what's changed since that version.

Thanks for checking that. I found what changed between 1.4.1.1 and 1.4.2.2. It turned out to be a small change in the message time outs. I have a fix for this ready, but I am just finishing the next release and so my code is all intermixed with incomplete features at the moment. I hope to have the new version released in the next couple of days.
Logged
Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
lave3k
Newbie
*

Karma: +4/-1
Offline Offline

Posts: 22
« Reply #134 on: September 10, 2010, 08:12:41 PM »
I have 03 1.8t ecu from an A4, Flashed it many times with galleto 1260 in boot mode, but wow it would be nice to leave the windshield wiper on the car while making revision!  It has a 29F800BB chip.  I'm getting some communication and timing sync, but it doesn't get past security.  I'm currently using a KII USB Ross Tech cable.  Curious if the cable is my issue or something else?  -Vista, Very fast Laptop, Good Voltage, Virus protections all disabled etc.  I also don't seem to be generating a log file?

When I attempt Read Info:

Reading ECU Info.
Switching to KWP2000 session
Connection attempt number 1.
Successfully sent slow init.
Connecting...
Connected
Starting diagnostic session.
Failed to start diagnostic session.
Disconnecting...
Reading ECU Info Failed.
Disconnected

Attempt to read Flash:

Reading ECU Flash Memory.
Disabling Windows sleep mode.
Connection attempt number 1.
Successfully sent slow init.
Connecting...
Connected
Starting diagnostic session.
Successfully started diagnostic sesion, but ECU reports security access required.
Negotiating communication timings.
Reading current communication timings.
Reading communication timing limits.
Requesting communication at timing limits.
Successfully changed to new commumication timings.
Requesting security access.
Received unknown message during security negotiation. Security negotiation failed.
Disconnecting...
Restoring Windows sleep mode.
Reading ECU Flash Memory Failed.
Disconnected




Thanks, -Dave
Logged
Pages: 1 ... 7 8 [9] 10
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 24, 2024, 01:09:26 AM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

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