NefMoto

Hey all,

Great site here, makes me wish I had an Audi.
Anyway I have something close, a Golf R32.
I thought I would try reading the flash for fun, used a generic usb data cable, using slow init a connection was made and i was able to read ECU info but the read flash was greyed out.
Any easy way to get it dump the flash?

thanks!

You may want to attach a copy of the log file so Tony can see what is going on.  It is in c:\Users\YourUsername\AppData\Local\Nefarious_Motorsports.

edit:  I am braindead.

I tried it again this evening. Realized I should at least post the log file.

05/Dec/2010 04:12:40.797: USER: Connecting...
05/Dec/2010 04:12:41.107: USER: Connecting to address 0x01.
05/Dec/2010 04:12:43.277: USER: Slow init succeeded.
05/Dec/2010 04:12:43.286: USER: Switching to KWP2000 session.
05/Dec/2010 04:12:43.598: LOG: Sent message with service ID StartCommunication
05/Dec/2010 04:12:43.638: LOG: Received message with service ID StartCommunicationPositiveResponse
05/Dec/2010 04:12:43.645: USER: Connected
05/Dec/2010 04:12:46.167: LOG: Sent message with service ID TesterPresent
05/Dec/2010 04:12:46.203: LOG: Received message with service ID TesterPresentPositiveReponse
05/Dec/2010 04:12:46.803: USER: Reading ECU info.
05/Dec/2010 04:12:46.808: USER: Negotiating communication timings.
05/Dec/2010 04:12:46.810: LOG: Reading current communication timings.
05/Dec/2010 04:12:46.896: LOG: Sent message with service ID AccessTimingParameters
05/Dec/2010 04:12:46.923: LOG: Received message with service ID AccessTimingParametersPositiveResponse
05/Dec/2010 04:12:46.935: LOG: Reading communication timing limits.
05/Dec/2010 04:12:47.033: LOG: Sent message with service ID AccessTimingParameters
05/Dec/2010 04:12:47.075: LOG: Received message with service ID AccessTimingParametersPositiveResponse
05/Dec/2010 04:12:47.081: LOG: Requesting communication at timing limits.
05/Dec/2010 04:12:47.196: LOG: Sent message with service ID AccessTimingParameters
05/Dec/2010 04:12:47.231: LOG: Received message with service ID AccessTimingParametersPositiveResponse
05/Dec/2010 04:12:47.257: USER: Successfully changed to new communication timings.
05/Dec/2010 04:12:47.274: USER: Reading ECU identification option: ECUIdentificationScalingTable
05/Dec/2010 04:12:47.282: LOG: Sent message with service ID ReadECUIdentification
05/Dec/2010 04:12:47.307: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
05/Dec/2010 04:12:47.325: USER: Successfully read ECU identification information
05/Dec/2010 04:12:47.344: USER: Reading ECU identification option: systemSupplierECUHardwareNumber
05/Dec/2010 04:12:47.351: LOG: Sent message with service ID ReadECUIdentification
05/Dec/2010 04:12:47.375: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
05/Dec/2010 04:12:47.402: USER: Read ECU Identification systemSupplierECUHardwareNumber: 0261208344,
05/Dec/2010 04:12:47.412: USER: Successfully read ECU identification information
05/Dec/2010 04:12:47.429: USER: Reading ECU identification option: systemSupplierECUSoftwareNumber
05/Dec/2010 04:12:47.443: LOG: Sent message with service ID ReadECUIdentification
05/Dec/2010 04:12:47.458: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
05/Dec/2010 04:12:47.504: USER: Read ECU Identification systemSupplierECUSoftwareNumber: 1037369363,
05/Dec/2010 04:12:47.518: USER: Successfully read ECU identification information
05/Dec/2010 04:12:47.547: USER: Reading ECU identification option: vehicleManufacturerECUHardwareNumber
05/Dec/2010 04:12:47.557: LOG: Sent message with service ID ReadECUIdentification
05/Dec/2010 04:12:47.580: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
05/Dec/2010 04:12:47.632: USER: Read ECU Identification vehicleManufacturerECUHardwareNumber: 0x0D, 14.4.03     , 0xFF,
05/Dec/2010 04:12:47.650: USER: Successfully read ECU identification information
05/Dec/2010 04:12:47.660: USER: Reading ECU identification option: calibrationDate
05/Dec/2010 04:12:47.671: LOG: Sent message with service ID ReadECUIdentification
05/Dec/2010 04:12:47.717: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
05/Dec/2010 04:12:47.763: USER: Read ECU Identification calibrationDate: 022906032EG , 5626, 0x03000084, 0x00000000, 0x7AB6, MOTRONIC ME7.1., 1G   ,
05/Dec/2010 04:12:47.774: USER: Successfully read ECU identification information
05/Dec/2010 04:12:47.790: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber
05/Dec/2010 04:12:47.826: LOG: Sent message with service ID ReadECUIdentification
05/Dec/2010 04:12:47.846: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
05/Dec/2010 04:12:47.872: USER: Read ECU Identification calibrationEquipmentSoftwareNumber: 0x00000000,
05/Dec/2010 04:12:47.883: USER: Successfully read ECU identification information
05/Dec/2010 04:12:47.902: USER: Reading ECU info succeeded.
05/Dec/2010 04:12:50.347: LOG: Sent message with service ID TesterPresent
05/Dec/2010 04:12:50.360: LOG: Received message with service ID TesterPresentPositiveReponse
05/Dec/2010 04:12:52.870: LOG: Sent message with service ID TesterPresent
05/Dec/2010 04:12:52.892: LOG: Received message with service ID TesterPresentPositiveReponse
05/Dec/2010 04:12:55.390: LOG: Sent message with service ID TesterPresent
05/Dec/2010 04:12:55.408: LOG: Received message with service ID TesterPresentPositiveReponse
05/Dec/2010 04:12:57.670: USER: Disconnecting...
05/Dec/2010 04:12:57.681: LOG: Sent message with service ID StopCommunication
05/Dec/2010 04:12:57.700: LOG: Received message with service ID StopCommunicationPositiveResponse
05/Dec/2010 04:12:57.710: USER: Disconnected
05/Dec/2010 04:12:57.773: LOG: Closing FTDI device.
05/Dec/2010 04:12:57.782: LOG: Send receive thread now terminated.
05/Dec/2010 04:13:02.302: LOG: Closing NefMoto ME7 ECU Flasher BETA 1.6.0.0


I was actually able to dump the flash with a 1250 clone cable and Galleto via OBDII today though. It did take close to 20 minutes though. That did let me verify the software is stock.

My software "SHOULD" work with your R32.

Most likely you just need to specify a memory layout file, then the read flash button will be enabled. The next version of the software will tell you why the buttons get greyed out.

Thanks for the reply Tony.

I have tried the different flash layouts but always get the security access error.

Just sent you a PM with a link to a test release. Hopefully I just need to refine a few things in my security access protocol.

hey tony :D im interested in this test release too since i own a r32 engine...

Everything that was tested with kls has already been added to the latest 1.6.1.0 release of the software.

If that release isn't working with your R32, please send me a log file so we can sort it out.

ok great sorry didnt knew.. ill test on my r32 ecu

No worries, I'm happy someone new wants to test it out on the R32.

Dear R32 owners, 

would you both be so kind to post your vag-ecu-number / softwareversion,
so we all know which ecu's it works and which don't at the moment ?

I also have issues connecting to a R32 ecu...  it's a 022906032CN 0005.

Thanks,

PvL

I am also having trouble trying to read my VW Golf Mk4 VR6 R32 3.2 022906032EG.
And I am using NefMoto ver. 1.8.0.0.
 

Are they any changes in the new version? I cant read my 02290603 CN ECU. The memory Layout is invailable :(