Pages: 1 ... 5 6 [7] 8 9 ... 11
Author Topic: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2  (Read 227911 times)
Bi-turbo
Full Member
***

Karma: +1/-7
Offline Offline

Posts: 164


« Reply #90 on: September 24, 2014, 08:12:38 AM »

It flashed on fine then I went back to read ecu info

How can you force the ecu to know it's been programmed?
Logged
Bi-turbo
Full Member
***

Karma: +1/-7
Offline Offline

Posts: 164


« Reply #91 on: September 24, 2014, 09:33:01 AM »

Done a search and seems that I need to switch the ignition off and back on?

I'll have to stick a switch into the ignition wire in the bench loom.

Anything else to try?

I've put a different 95040 on it and flashed the file with galletto then tried to use nefmoto again and that's what it said
Logged
Bi-turbo
Full Member
***

Karma: +1/-7
Offline Offline

Posts: 164


« Reply #92 on: September 24, 2014, 02:15:30 PM »

One D box file works fine and brings up the part number etc when I connect.

The other D box file keeps bringing up THIS IS THE RAM

Have got switch on the ignition power. No change

Have wrote another 95040. No change

What is the actual cause?

The file itself is fine as in a can read all the maps in tunerpro and its fine, have compared the hex dumps of both files and can't see anything out of place.
Logged
Bi-turbo
Full Member
***

Karma: +1/-7
Offline Offline

Posts: 164


« Reply #93 on: September 25, 2014, 12:26:58 AM »

Could it be somthing in the flash .bin? as its a commercial tune?
Logged
turboat
Hero Member
*****

Karma: +43/-2
Offline Offline

Posts: 619


« Reply #94 on: September 25, 2014, 01:27:10 AM »

It seems likely that nef is just reading back the ecu info, which in one of your bins is set to THIS IS THE RAM. Have you diff'd the files to see where they differ? Beyond compare is a useful tool for this.

Edit - just seen Tonys comments on the other thread, seems like it's still in programming mode. What do you get if you run me7check across the file?
« Last Edit: September 25, 2014, 01:31:56 AM by turboat » Logged
Bi-turbo
Full Member
***

Karma: +1/-7
Offline Offline

Posts: 164


« Reply #95 on: September 25, 2014, 02:08:30 AM »

me7check come back as fine.

In the location of the ecu number etc in the hex dump it is correct.

Cant see how to get around it? ive read all the searched threads on here and there isnt an actual answer.
Logged
turboat
Hero Member
*****

Karma: +43/-2
Offline Offline

Posts: 619


« Reply #96 on: September 25, 2014, 02:10:29 AM »

Is this a 1.8t or 2.7t file?
Logged
Bi-turbo
Full Member
***

Karma: +1/-7
Offline Offline

Posts: 164


« Reply #97 on: September 25, 2014, 03:48:18 AM »

551D 2.7T
Logged
ddillenger
Hero Member
*****

Karma: +631/-20
Offline Offline

Posts: 5640


« Reply #98 on: September 25, 2014, 07:00:59 AM »

Once you cycle the power after the flash, it should be normal again.

This assumes you are writing with nefmoto, not MPPS.
Logged

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 experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Bi-turbo
Full Member
***

Karma: +1/-7
Offline Offline

Posts: 164


« Reply #99 on: September 25, 2014, 07:14:51 AM »

by cycling do you mean switching all power off and back on?

if so done that and still the same, flashed the file with nefmoto and galletto and both the same outcome.

as said i can put another file on and its fine but this file is causing issues but i dont know what issues
Logged
Bi-turbo
Full Member
***

Karma: +1/-7
Offline Offline

Posts: 164


« Reply #100 on: September 25, 2014, 01:26:10 PM »

It's the .bin file

Put standard on it and its fine and vcds connects and all coding is there.

Just need to search for a decent .xdf as the LDRXN in the one I have is way off

The I'll copy and paste all the relevant maps, checksum, flash and see if that's goes on ok
Logged
ddillenger
Hero Member
*****

Karma: +631/-20
Offline Offline

Posts: 5640


« Reply #101 on: September 25, 2014, 01:30:37 PM »

It's the .bin file

Put standard on it and its fine and vcds connects and all coding is there.

Just need to search for a decent .xdf as the LDRXN in the one I have is way off

The I'll copy and paste all the relevant maps, checksum, flash and see if that's goes on ok

Don't copy and paste tune. If you're here, it should be to learn. Copying things from one file into another, then wondering why it doesn't work is unacceptable. Create your own file. If you can't explain EVERY SINGLE CHANGE to a file, you're not doing it right.
Logged

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 experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Bi-turbo
Full Member
***

Karma: +1/-7
Offline Offline

Posts: 164


« Reply #102 on: September 25, 2014, 10:32:14 PM »

I no what and why things have been changed, I just need them in this ecu and the file has issues
Logged
Waltomatic
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7


« Reply #103 on: October 14, 2014, 04:22:13 PM »

Can anyone tell me why the program I correctly installed simply does not open?

Windows XP SP3 + .NET 3.5
Logged
overspeed
Sr. Member
****

Karma: +17/-4
Offline Offline

Posts: 351



« Reply #104 on: October 15, 2014, 02:44:51 PM »

Can anyone tell me why the program I correctly installed simply does not open?

Windows XP SP3 + .NET 3.5

Even if work, you canĀ“t read ME3.1 with it... as said before bootmode was not implemented yet
Logged
Pages: 1 ... 5 6 [7] 8 9 ... 11
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.021 seconds with 18 queries. (Pretty URLs adds 0.001s, 0q)