Pages: 1 ... 5 6 [7]
Author Topic: Open Source NefMoto ME7 ECU Flasher and Data Logger  (Read 169179 times)
R32Dude
Full Member
***

Karma: +35/-6
Offline Offline

Posts: 174



« Reply #90 on: May 05, 2021, 12:01:23 AM »

I'm trying to use this awesome program for logging. It connects and reads the ECU info no probs,  but keeps getting an error when logging.  Its an ST10 with IMMO off, on the bench. BTW ,VCDS works fine with forced kwp2000.  I don't need to flash, just need logging.

May/2021 02:48:47.487: USER: Starting variable reading.
05/May/2021 02:48:47.497: LOG: Starting DevelopmentSession diagnostic session with 10400 baud rate.
05/May/2021 02:48:47.497: USER: Starting diagnostic session.
05/May/2021 02:48:47.524: LOG: Sent message with service ID StartDiagnosticSession
05/May/2021 02:48:47.565: LOG: Received message with service ID: NegativeResponse
05/May/2021 02:48:47.565: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
05/May/2021 02:48:47.565: USER: Start diagnostic session failed, ECU reports security access is required.
05/May/2021 02:48:47.566: USER: 100% complete.
Logged
golfputtputt
Sr. Member
****

Karma: +6/-4
Offline Offline

Posts: 367


« Reply #91 on: July 12, 2021, 06:57:35 PM »

anyone manage to solve the verify checksums tab crashing for win7? github thread doesnt look like there's progress. Don't mean to be greedy.I very much appreciate this awesome piece of software. I'm not a developer so I wouldn't know where to begin solving this.

this was the event report:

Code:
Cab Id: 0

Problem signature:
P1: nefmotoecuflasher.exe
P2: 1.9.4.3
P3: 5b343238
P4: ECUShared
P5: 1.9.1.0
P6: 5b333945
P7: ee
P8: 8
P9: System.IO.FileNotFoundException
P10:
« Last Edit: July 12, 2021, 07:02:46 PM by golfputtputt » Logged
TeknoFi
Full Member
***

Karma: +1/-3
Offline Offline

Posts: 74


« Reply #92 on: November 06, 2022, 09:28:36 AM »

I have problem with Nefmoto flasher 1.9.4.3 via OBD. It refuses to write. Cable is blue kkl with 232RL and it works perfectly with other programs (writing with me7eeprom etc).
Whether the car's immo is enabled or not didn't make any difference, I tried both ways. Car is -00 Audi TT (1.8T AJQ)


Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 8N0906018AB 1.8L R4/5VT
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected

Writing ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Succesfully changed to new communication timings.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Succesfully started diagnostic session.
Negotiating communication timings.

Disconnecting because no response was received for the Tester Present message.
Disconnected
Writing ECU flash memory failed.
100% Complete.
« Last Edit: November 06, 2022, 09:34:29 AM by TeknoFi » Logged
nyet
Administrator
Hero Member
*****

Karma: +585/-148
Online Online

Posts: 12048


WWW
« Reply #93 on: November 06, 2022, 09:52:19 AM »

Is the ECU stock? Does it have a riser?
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please 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 experience.
TeknoFi
Full Member
***

Karma: +1/-3
Offline Offline

Posts: 74


« Reply #94 on: November 06, 2022, 09:54:38 AM »

Is the ECU stock? Does it have a riser?

Yes, ecu that car has come with, and no riser
Logged
nyet
Administrator
Hero Member
*****

Karma: +585/-148
Online Online

Posts: 12048


WWW
« Reply #95 on: November 06, 2022, 09:57:30 AM »

pin 121 powered up?

http://nefariousmotorsports.com/forum/index.php?topic=13149.msg107893#msg107893

Does the cable work on other ME7.5 ecus?
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please 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 experience.
JeanAwt
Full Member
***

Karma: +3/-3
Offline Offline

Posts: 70


« Reply #96 on: November 06, 2022, 10:04:00 AM »

I have problem with Nefmoto flasher 1.9.4.3 via OBD. It refuses to write. Cable is blue kkl with 232RL and it works perfectly with other programs (writing with me7eeprom etc).
Whether the car's immo is enabled or not didn't make any difference, I tried both ways. Car is -00 Audi TT (1.8T AJQ)



Hello
I am not successful either with blue kkl 232RL

I use it for vag commander 1.4

maybe a chip ID problem?

can you read but not write?
cable speed in the configuration maybe


do you have mprog to see the details?

I try to help but I'm just a noob and mechanic Roll Eyes
Logged
TeknoFi
Full Member
***

Karma: +1/-3
Offline Offline

Posts: 74


« Reply #97 on: November 06, 2022, 10:57:25 AM »

pin 121 powered up?

http://nefariousmotorsports.com/forum/index.php?topic=13149.msg107893#msg107893

Does the cable work on other ME7.5 ecus?

pin 121 did not exist in the wiring harness in ecu connector, was empty i.e. there is no power. Looking for schematics of autodata it should have direct connection to ignition coils' black/violet wire, but it did not.

I don't have other ecu's to try...

However, with the china-clone mpps v18 cable and its program, I can write through the obd in this situation, so I'll use it for now until I try to add pin 121.

Reading is also not possible with the nefmoto program.
Logged
BlackT
Hero Member
*****

Karma: +71/-32
Offline Offline

Posts: 1261



« Reply #98 on: November 07, 2022, 12:38:59 AM »

I have problem with Nefmoto flasher 1.9.4.3 via OBD. It refuses to write. Cable is blue kkl with 232RL and it works perfectly with other programs (writing with me7eeprom etc).
Whether the car's immo is enabled or not didn't make any difference, I tried both ways. Car is -00 Audi TT (1.8T AJQ)


Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 8N0906018AB 1.8L R4/5VT
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected

Writing ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Succesfully changed to new communication timings.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Succesfully started diagnostic session.
Negotiating communication timings.

Disconnecting because no response was received for the Tester Present message.
Disconnected
Writing ECU flash memory failed.
100% Complete.

512kb ECUs can't be write or read with nefmoto soft.
Use mpps(2 min to write)  or galleto 1260(slow 12 minute to write flash)
Logged
fever
Newbie
*

Karma: +2/-0
Offline Offline

Posts: 23


« Reply #99 on: November 07, 2022, 04:02:32 AM »

512kb ECUs can't be write or read with nefmoto soft.
Use mpps(2 min to write)  or galleto 1260(slow 12 minute to write flash)

Nefmoto is working for me with 512kb ECUs, but with "some special procedure".

- turn ignition ON and connect to ECU
- select 400BB layout and file to write
- click write and wait for it to fail with messege "A communication error was encountered while flashing. Press Cancel to abort, or OK to continue after reconnecting."
- click OK and wait for it to disconnect
- turn ignition OFF and click reconnect

It will say now "THIS-IS-THE-RAM-PROGRAM-" in KWP info, get SecurityAccessPositiveResponse and start write.

I don't even remember how I came up with this, but it works for me every time for many years...
Logged
TeknoFi
Full Member
***

Karma: +1/-3
Offline Offline

Posts: 74


« Reply #100 on: November 07, 2022, 09:58:16 AM »

Nefmoto is working for me with 512kb ECUs, but with "some special procedure".

- turn ignition ON and connect to ECU
- select 400BB layout and file to write
- click write and wait for it to fail with messege "A communication error was encountered while flashing. Press Cancel to abort, or OK to continue after reconnecting."
- click OK and wait for it to disconnect
- turn ignition OFF and click reconnect

It will say now "THIS-IS-THE-RAM-PROGRAM-" in KWP info, get SecurityAccessPositiveResponse and start write.

I don't even remember how I came up with this, but it works for me every time for many years...

Thank you, this helped.

I got the writing to succeed when I waited a good moment after that dialogue (and pressing ok), and pressed the connect fast/slow init button again. it started writing!

I also tried turning off / cycling the ignition there like you suggest, but that prevented the operation.  

however, I get "erase report failed" errors, despite that the writing goes through and no problems occur.




Quote

Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Start communication request did not receive any response.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Start communication request did not receive any response.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Switching to KWP2000 session.
Connected
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Timing negotiation failed. Communication timings are unchanged.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Requesting flash memory erase for address range 0x00800000 to 0x00803FFF.
Failed to erase flash memory.
Sector erase reported as failed. Calculating checksum to verify erase.
Calculating flash checksum to verify if erase was successful for range: 0x00800000 to 0x00804000
Verified the memory sector was erased properly.
Requesting download to ECU for address range 0x00800000 to 0x00803FFF.
Request download to ECU succeeded.
Starting data transfer.
1% complete.
2% complete.
3% complete.
Data transfer complete.
Requesting data transfer exit.
Successfully exited data transfer.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00804000 to 0x00806000
Flash checksum matches new data, flashing is unnecessary, skipping.
5% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00806000 to 0x00808000
Flash checksum matches new data, flashing is unnecessary, skipping.
6% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00808000 to 0x00810000
Flash checksum matches new data, flashing is unnecessary, skipping.
13% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00810000 to 0x00820000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00810000 to 0x0081FFFF.
Failed to erase flash memory.
Sector erase reported as failed. Calculating checksum to verify erase.
Calculating flash checksum to verify if erase was successful for range: 0x00810000 to 0x00820000
The memory sector was NOT erased properly, will continue and attempt to write memory sector.
Requesting download to ECU for address range 0x00810000 to 0x0081FFFF.
Request download to ECU succeeded.
Starting data transfer.
13% complete.
14% complete.
15% complete.
16% complete.
17% complete.
19% complete.
19% complete.
20% complete.
22% complete.
25% complete.
25% complete.
Data transfer complete.
Requesting data transfer exit.
Successfully exited data transfer.
Calculating checksum for first memory range to determine which erase mode the ECU is using.
ECU appears to be in erase sector mode, continuing the flash process.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00820000 to 0x00830000
Flash checksum matches new data, flashing is unnecessary, skipping.
38% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00830000 to 0x00840000
Flash checksum matches new data, flashing is unnecessary, skipping.
50% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00840000 to 0x00850000
Flash checksum matches new data, flashing is unnecessary, skipping.
63% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00850000 to 0x00860000
Flash checksum matches new data, flashing is unnecessary, skipping.
75% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00860000 to 0x00870000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00860000 to 0x0086FFFF.
Failed to erase flash memory.
Sector erase reported as failed. Calculating checksum to verify erase.
Calculating flash checksum to verify if erase was successful for range: 0x00860000 to 0x00870000
Verified the memory sector was erased properly.
Requesting download to ECU for address range 0x00860000 to 0x0086FFFF.
Request download to ECU succeeded.
Starting data transfer.
76% complete.
77% complete.
78% complete.
79% complete.
80% complete.
81% complete.
82% complete.
83% complete.
84% complete.
85% complete.
86% complete.
87% complete.
Data transfer complete.
Requesting data transfer exit.
Requesting data transfer exit.
Successfully exited data transfer.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00870000 to 0x00880000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00870000 to 0x0087FFFF.
Failed to erase flash memory.
Sector erase reported as failed. Calculating checksum to verify erase.
Calculating flash checksum to verify if erase was successful for range: 0x00870000 to 0x00880000
Verified the memory sector was erased properly.
Requesting download to ECU for address range 0x00870000 to 0x0087FFFF.
Request download to ECU succeeded.
Starting data transfer.
88% complete.
89% complete.
90% complete.
91% complete.
100% complete.
Data transfer complete.
Requesting data transfer exit.
Successfully exited data transfer.
Disconnecting from ECU to force it to recognize successful completion of flash write.
Writing ECU flash memory succeeded. Wrote 11 of 11 sectors in flash memory.
Flashing time was 00:04:08.
Disconnecting...
Disconnected


even this functionality is enough and makes nefmoto a winner, but what could be the reason for those? I'm already fed up with the fact that mpps v18 is not 100% reliable, it randomly brickes the ecu, and has to be repaired via boot mode. I can't get the Galletto 1260 to work, it freezes in all operations, no matter what I try to do with it.  Undecided
« Last Edit: November 07, 2022, 10:06:37 AM by TeknoFi » Logged
nyet
Administrator
Hero Member
*****

Karma: +585/-148
Online Online

Posts: 12048


WWW
« Reply #101 on: November 07, 2022, 10:24:36 AM »

I'm not 100% sure of what is going on, but the RAM program is what runs when the flash process totally fails... its basically the ECU running in a failsafe mode (from RAM) which means if it loses power, you have a brick.

For whatever reason, NEF can get the flash process to complete when the ECU is in that failsafe mode, but NOT when it is (normally) running out of flash.

Presumably its a minor bug in nef... not sure who is qualified to debug it
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please 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 experience.
Pages: 1 ... 5 6 [7]
  Print  
 
Jump to:  

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