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

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #105 on: August 17, 2010, 10:20:28 AM »
Quote from: arne_rs4 on August 17, 2010, 02:02:04 AM
Hi,

When I use S4 memory layout, it reads out and flashes OK. No errors.
In dashboard ESP and ABS lights are on. And VAG shows errors, but engine runs very fine.

Arne

Looking at your VAG errors and the NefMoto flashing log, it appears as though everything was fine with the reading and writing of the flash memory. The VAG errors indicate that the ECU coding is incorrect. Did you flash the ECU with the file from another ECU that was from a different year of car, or came with different transmission or something? The coding can be corrected via VAG-COM.
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
arne_rs4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 5
« Reply #106 on: August 17, 2010, 01:14:44 PM »
thanx for replying,

It works perfecly, only those errors. There is one good thing so, I dont have to switch off ESP like I always do Wink
Both cars are exactly same.
Via VAG? Can you help?

Arne
Logged
pvl
Sr. Member
****

Karma: +32/-1
Offline Offline

Posts: 350
« Reply #107 on: August 17, 2010, 01:29:55 PM »
@ arne :

Have a look over here :

http://www.ross-tech.com/vag-com/tour/recode_screen.html

Be sure to note-down your original code as a backup, and check with your friend's RS4 to write-down his coding and apply it to yours.
That would do the trick. There are several items that can be recoded. It works very well.
I did a imported A6 from the US for a friend over here.
Now the speedo reads KM as of odometer-value digitally instead of miles, and all other values are metric instead of imperial.

Be sure that the car is exactly the same as of options and equipment, otherwise this will not work properly.

Have fun !

Greetings,

Pascal
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #108 on: August 17, 2010, 06:28:01 PM »
Quote from: pvl on August 16, 2010, 04:22:18 PM
Hopefully i am able to test the setup on a car, as you'd recommended, but that perhaps can
take a few days. Need to find a guineypig for this.

Pascal, I had another look at your logs today. I am 99% sure your problem is caused by the ECU not being in the car. Your logs indicate that the programming mode preconditions have not been met. Currently the NefMoto flashing software only checks these when writing to the flash, and not when reading. Checking the flashing programming preconditions when reading is something I will add to the next version of the software.

Please let me know if reading or writing work when the ECU is in the car.
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
arne_rs4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 5
« Reply #109 on: August 18, 2010, 02:38:46 AM »
Thanks for help, changing Software Coding number in VAG-COM helped. No more errors.

Arne
Logged
pvl
Sr. Member
****

Karma: +32/-1
Offline Offline

Posts: 350
« Reply #110 on: August 18, 2010, 03:13:20 AM »
@ Tony :

I will report back asap.

Need to test this on a few cars firstly, and then i'll report back.

Thanks,

Pascal
Logged
BFT
Newbie
*

Karma: +3/-0
Offline Offline

Posts: 7
« Reply #111 on: August 25, 2010, 02:37:04 AM »
Cool just downloaded and will post back anything.

Great work!
Logged
s4rmm
Jr. Member
**

Karma: +4/-1
Offline Offline

Posts: 28
« Reply #112 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.
Logged
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704
« Reply #113 on: August 25, 2010, 11:20:02 AM »
Tried on a 99 UK Audi S4.

Cable is a blue Chinese ebay item.

Works fine with VCDS.

No coms with flash tool.  My car has a tune for big injectors etc by a big tuning company currently on there.

Log file:


25/Aug/2010 07:07:41.356: Opened NefMoto ME7 ECU Flasher BETA 1.4.2.2
25/Aug/2010 07:11:29.084: Reading ECU Info.
25/Aug/2010 07:11:29.112: Switching to KWP2000 session
25/Aug/2010 07:11:29.217: Opened FTDI device.
25/Aug/2010 07:11:29.218: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
25/Aug/2010 07:11:29.219: FTDI ChipID DLL is loaded, checking chip ID...
25/Aug/2010 07:11:29.221: Unable to read FTDI device chip ID
25/Aug/2010 07:11:29.274: Starting send receive thread.
25/Aug/2010 07:11:29.296: Send receive thread now started
25/Aug/2010 07:11:29.299: Connection attempt number 1.
25/Aug/2010 07:11:29.782: Connecting to address 0x01.
25/Aug/2010 07:11:32.166: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:11:32.185: Failed to send slow init.
25/Aug/2010 07:11:32.205: Connection attempt number 2.
25/Aug/2010 07:11:32.510: Connecting to address 0x01.
25/Aug/2010 07:11:34.851: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:11:34.872: Failed to send slow init.
25/Aug/2010 07:11:34.891: Connection attempt number 3.
25/Aug/2010 07:11:35.198: Connecting to address 0x01.
25/Aug/2010 07:11:37.532: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:11:37.550: Failed to send slow init.
25/Aug/2010 07:11:37.569: Connection attempt number 4.
25/Aug/2010 07:11:37.874: Connecting to address 0x01.
25/Aug/2010 07:11:40.226: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:11:40.248: Failed to send slow init.
25/Aug/2010 07:11:40.293: Connection attempt number 5.
25/Aug/2010 07:11:40.598: Connecting to address 0x01.
25/Aug/2010 07:11:43.045: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:11:43.080: Failed to send slow init.
25/Aug/2010 07:11:43.119: Connection attempt number 6.
25/Aug/2010 07:11:43.442: Connecting to address 0x01.
25/Aug/2010 07:11:45.771: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:11:45.829: Failed to send slow init.
25/Aug/2010 07:11:45.862: Closing FTDI device.
25/Aug/2010 07:13:07.738: Closing NefMoto ME7 ECU Flasher BETA 1.4.2.2
25/Aug/2010 07:14:33.178: Opened NefMoto ME7 ECU Flasher BETA 1.4.2.2
25/Aug/2010 07:14:41.414: Reading ECU Info.
25/Aug/2010 07:14:41.423: Switching to KWP2000 session
25/Aug/2010 07:14:41.515: Opened FTDI device.
25/Aug/2010 07:14:41.517: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
25/Aug/2010 07:14:41.518: FTDI ChipID DLL is loaded, checking chip ID...
25/Aug/2010 07:14:41.519: Unable to read FTDI device chip ID
25/Aug/2010 07:14:41.571: Starting send receive thread.
25/Aug/2010 07:14:41.583: Send receive thread now started
25/Aug/2010 07:14:41.585: Connection attempt number 1.
25/Aug/2010 07:14:41.952: Connecting to address 0x01.
25/Aug/2010 07:14:44.321: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:14:44.342: Failed to send slow init.
25/Aug/2010 07:14:44.363: Connection attempt number 2.
25/Aug/2010 07:14:44.668: Connecting to address 0x01.
25/Aug/2010 07:14:47.006: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:14:47.027: Failed to send slow init.
25/Aug/2010 07:14:47.049: Connection attempt number 3.
25/Aug/2010 07:14:47.356: Connecting to address 0x01.
25/Aug/2010 07:14:49.709: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:14:49.730: Failed to send slow init.
25/Aug/2010 07:14:49.755: Connection attempt number 4.
25/Aug/2010 07:14:50.060: Connecting to address 0x01.
25/Aug/2010 07:14:52.391: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:14:52.410: Failed to send slow init.
25/Aug/2010 07:14:52.431: Connection attempt number 5.
25/Aug/2010 07:14:52.735: Connecting to address 0x01.
25/Aug/2010 07:14:55.074: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:14:55.094: Failed to send slow init.
25/Aug/2010 07:14:55.113: Connection attempt number 6.
25/Aug/2010 07:14:55.417: Connecting to address 0x01.
25/Aug/2010 07:14:57.771: Failed to read sync byte. Read 0 bytes.
25/Aug/2010 07:14:57.799: Failed to send slow init.
25/Aug/2010 07:14:57.819: Closing FTDI device.
25/Aug/2010 07:15:46.029: Closing NefMoto ME7 ECU Flasher BETA 1.4.2.2
25/Aug/2010 07:19:18.637: Opened NefMoto ME7 ECU Flasher BETA 1.4.2.2
Logged
rik.vwt
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 19
« Reply #114 on: August 25, 2010, 12:28:09 PM »
Any difference between vw 1.8T 2000 ecu and 2001+, other than wideband o2 sensors.Will this software flash load my 2000 ME7 ecu? If so were would I get Maps for my vehicle?Newbie here so sorry for any inconvenience. Tongue
Logged
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704
« Reply #115 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
Logged
elRey
Hero Member
*****

Karma: +32/-1
Offline Offline

Posts: 565
« Reply #116 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?
http://www.google.com/search?hl=en&client=firefox-a&hs=axr&rls=org.mozilla%3Aen-US%3Aofficial&q=29f200+flashable&aq=f&aqi=&aql=&oq=&gs_rfai=

AM29F200AB-90SI
datasheet: http://www.alldatasheet.com/datasheet-pdf/pdf/55521/AMD/AM29F200AB-90SI.html

AEB 1.8Ts

Thanks,
Rey
« Last Edit: August 30, 2010, 04:30:38 PM by elRey » Logged
thom337
Full Member
***

Karma: +15/-1
Offline Offline

Posts: 81
« Reply #117 on: August 30, 2010, 02:39:10 PM »
I don't believe the older ECUs support flashing via K-line...perhaps Tony knows for sure.
Logged
pvl
Sr. Member
****

Karma: +32/-1
Offline Offline

Posts: 350
« Reply #118 on: August 30, 2010, 03:13:43 PM »
Hi,

Well some of them do it perfectly via the K-line. Only re-writeing the ecu. Take a look with
google and you'll see.

But at the moment a few interfaces only support this. Like Revo's one, CMD, MPPS, Byteshooter, and Frieling (M3.8.3 & M5.Cool.

The cheap interfaces won't do this,  untill there comes a hack for them. Or a new plug-in.

Let's focus on ME7 first. Too much differences already with these boxes. Tho would be happy if this could be
also included. Happy to test it also.

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.

No probs with that.

I had no time to try out Nefmotoflasher on other 1.8T's yet..   a Golf MK-IV-R32 with CN-computer also wasn't doable.
Yet i have to look into the problems with aftermarket-radio's and protected ecu's (socketed flashroms where read-out
is disabled) to see if this is the case with that specific ME7.1.1 car. More to come soon.

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

Thanks,

PvL
Logged
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3
« Reply #119 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
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
Pages: 1 ... 6 7 [8] 9 10
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 24, 2024, 01:00:47 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.033 seconds with 17 queries. (Pretty URLs adds 0.006s, 0q)