Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
 Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
 |
« on: January 25, 2012, 12:35:22 PM »
|
|
|
Here is version 1.9.2.3 of the NefMoto software. New in this version: - New premium feature to detect the maximum and all communication baud rates supported by the ECU.
- Improved premium feature for fast flash reading and writing to improve the speed of the full flash read and write.
- Support for falling back to slower communication baud rates if the desired rate doesn't work.
- Allow users to continue reading or writing flash memory if the memory layout validation fails.
- Better support for starting diagnostic sessions on ECUs that return unexpected error codes.
- Better support for starting communication using slow-init on ECUs that don't accept the StartCommunication message.
- Added support for verifying if flash erasing actually failed when the incorrectly ECU reports it has failed.
- Changed the file format of the ECU Info files to better handle entries that generate invalid XML.
- Crash fix for connecting in boot mode when the ECU responds incorrectly.
This version has also changed the format of the premium license files. If you had previously purchased a premium license, then the updated license file should already be waiting for you in your email inbox. If you have any problems with the new license files, or if you didn't not receive an updated license, just let me know. Attached is the installer for the NefMoto software, and as always the FTDI USB drivers if you don't already have them. You can read about the software on the wiki: http://www.nefariousmotorsports.com/wiki/index.php/NefMoto_ECU_Flashing_Software |
|
|
|
« Last Edit: February 15, 2012, 12:07:45 PM by Tony@NefMoto »
|
Logged
|
|
|
|
|
julex
|
|
« Reply #1 on: January 25, 2012, 01:48:23 PM »
|
|
|
I'll give it a spin shortly and thank you for license email.
|
|
|
|
|
Logged
|
|
|
|
Drludlow
Newbie
Karma: +0/-0
Offline
Posts: 16
|
|
« Reply #2 on: January 26, 2012, 10:58:39 AM »
|
|
|
I have yet to be successful reading from an immo car. Am i missing the point, or doing it wrong.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #3 on: January 26, 2012, 11:06:12 AM »
|
|
|
I have yet to be successful reading from an immo car. Am i missing the point, or doing it wrong.
Are you reading in the car or on the bench? Can you post your log file? |
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #4 on: January 26, 2012, 11:44:14 PM »
|
|
|
I repeated the process tonight and everything installed properly.
Thanks Tony.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #5 on: February 03, 2012, 04:04:18 PM »
|
|
|
I just added a new version updated from 1.9.2.0 to 1.9.2.1 that includes a bunch of small fixes for EDC15. You should only care about this small update if you are testing with EDC15.
|
|
|
|
|
Logged
|
|
|
|
|
sn00k
|
|
« Reply #6 on: February 04, 2012, 07:34:15 AM »
|
|
|
if i use the detect supported baudrates button, my ecu responds to 200.000+baud, which is awesome, and the flashing speed is VERY nice, BUT, if i close the program and then open it again it reverts back to 124800 since this is the highest value available in the drop down box..
..and so i need to to another detection to enable this 200.000+ baud-rate.. which is rather counter-productive since the detection takes longer time then to just flash at 124800.. is it possible to fix this so that the program remembers the last detected value for my deviceID when closing and reopening it? =)
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #7 on: February 05, 2012, 01:29:02 PM »
|
|
|
if i use the detect supported baudrates button, my ecu responds to 200.000+baud, which is awesome, and the flashing speed is VERY nice, BUT, if i close the program and then open it again it reverts back to 124800 since this is the highest value available in the drop down box..
..and so i need to to another detection to enable this 200.000+ baud-rate.. which is rather counter-productive since the detection takes longer time then to just flash at 124800.. is it possible to fix this so that the program remembers the last detected value for my deviceID when closing and reopening it? =)
It is supposed to remember the supported baud rates. There may be an issue with it resetting the detected speeds if the USB cable is not connected when the program opens. I will try to do a small update to fix this issue. |
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #8 on: February 05, 2012, 01:29:47 PM »
|
|
|
I updated the installer in the original post to version 1.9.2.2. This updated version has a few more fixes for the EDC15 guys.
|
|
|
|
|
Logged
|
|
|
|
Jacknk
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #9 on: February 10, 2012, 08:52:11 PM »
|
|
|
Will this program work with a KWP2000+? I have tried and cannot get it to connect with the ECU?
|
|
|
|
|
Logged
|
|
|
|
|
|
|
rob.mwpropane
|
|
« Reply #11 on: February 13, 2012, 05:50:30 AM »
|
|
|
Maybe this is a dumb ?, but all new releases here on out of the Nefmoto software will be Windows XP compatible? Thanks  |
|
|
|
|
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: +130/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #12 on: February 13, 2012, 02:13:01 PM »
|
|
|
Maybe this is a dumb ?, but all new releases here on out of the Nefmoto software will be Windows XP compatible? Thanks Yup, all new releases are compatible with Windows XP SP2 and later. |
|
|
|
|
Logged
|
|
|
|
New2Tune
Full Member
Karma: +3/-1
Offline
Posts: 55
|
|
« Reply #13 on: February 13, 2012, 04:40:28 PM »
|
|
|
Hi Tony,
I can't seem to get the logger working.
I've got an Audi A4 binary that is not working with Setzi's ME7Info program to find the RAM variable addresses. Does anyone know how to find these addresses in the binary itself using WinOLS or other programs?
Using another binary that does work with the ME7Info I can find a lot of references to those addresses in the code but I'm really looking for a more concentrated table. Are there other techniques people are using to find the addresses?
Thanks
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #14 on: February 13, 2012, 04:59:34 PM »
|
|
|
Right now everyone is using Setzi's ME7Logger to generate variable locations. Doing it manually is very very hard.
|
|
|
|
|
Logged
|
|
|
|
|
