NefMoto

Technical => NefMoto Software => Topic started by: TCSTigersClaw on July 23, 2013, 07:24:00 AM



Title: Will not read 06A906032CN NEW BEETLE
Post by: TCSTigersClaw on July 23, 2013, 07:24:00 AM
Ok :) Its the first time I have a nefmoto issue..

I connect ,slow init as usual ,try to read full read flash (with both cheap blue and rosstech cable).

About 7% read , I got an error.I tried again and again, the same.I read e2 just in case (if there was a revo demo or something) ,but its ok.

Here are the logs .I searched about reading/receiving InvalidChecksum but .still cant find anything.

Ignoring received message that is not a response. Message service ID was EcuReset
23/Ιουλ/2013 03:25:50.321: LOG: Could not construct valid message from received data: InvalidChecksum
23/Ιουλ/2013 03:25:50.322: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x38
23/Ιουλ/2013 03:25:50.322: LOG: Could not construct valid message from received data: InvalidChecksum
23/Ιουλ/2013 03:25:50.323: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x12
23/Ιουλ/2013 03:25:50.323: LOG: Could not construct valid message from received data: InvalidChecksum
23/Ιουλ/2013 03:25:50.324: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x02
23/Ιουλ/2013 03:25:50.324: LOG: Could not construct valid message from received data: InvalidChecksum
23/Ιουλ/2013 03:25:50.325: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x12
23/Ιουλ/2013 03:25:50.325: LOG: Could not construct valid message from received data: InvalidChecksum
23/Ιουλ/2013 03:25:50.326: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x03
23/Ιουλ/2013 03:25:50.326: LOG: Could not construct valid message from received data: MessageContainsNoData
23/Ιουλ/2013 03:25:50.326: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00
23/Ιουλ/2013 03:25:50.327: LOG: Could not construct valid message from received data: MessageContainsNoData
23/Ιουλ/2013 03:25:50.327: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00
23/Ιουλ/2013 03:25:53.334: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
23/Ιουλ/2013 03:25:53.335: LOG: Flushing 192 bytes from receive buffer due to P1 ECU response inter byte time out.
23/Ιουλ/2013 03:25:53.336: LOG: Message received no replies.
23/Ιουλ/2013 03:25:53.337: LOG: Failed to send message 3 times, message send failed.
23/Ιουλ/2013 03:25:53.338: LOG: Did not receive any replies to message.
23/Ιουλ/2013 03:25:53.339: USER: Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete.
23/Ιουλ/2013 03:25:53.341: LOG: Sent message with service ID TesterPresent
23/Ιουλ/2013 03:25:53.350: LOG: Validating flashed data checksum for address range 0x00900000 to 0x00900001.
23/Ιουλ/2013 03:25:53.376: LOG: Received message with service ID: TransferDataPositiveResponse
23/Ιουλ/2013 03:25:53.377: LOG: Ignoring message with service ID TransferDataPositiveResponse because it was unsolicited
23/Ιουλ/2013 03:25:55.345: LOG: Message received no replies.
23/Ιουλ/2013 03:25:55.346: LOG: Resending message. Send attempts: 2
23/Ιουλ/2013 03:25:55.347: LOG: Sent message with service ID TesterPresent
23/Ιουλ/2013 03:25:55.369: LOG: Received message with service ID: TesterPresentPositiveReponse
23/Ιουλ/2013 03:25:55.370: LOG: Sent message with service ID StartRoutineByLocalIdentifier
23/Ιουλ/2013 03:25:55.391: LOG: Received message with service ID: StartRoutineByLocalIdentifierPositiveResponse
23/Ιουλ/2013 03:25:55.398: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier
23/Ιουλ/2013 03:25:55.419: LOG: Received message with service ID: NegativeResponse
23/Ιουλ/2013 03:25:55.420: LOG: Received negative response for service ID: RequestRoutineResultsByLocalIdentifier, with response code: BlockTransferDataChecksumError
23/Ιουλ/2013 03:25:55.421: LOG: Checksum is incorrect.
23/Ιουλ/2013 03:25:55.422: USER: Finished forcing ECU to recognize that failed read operation is complete.
23/Ιουλ/2013 03:25:55.453: USER: Reading ECU flash memory failed.


Title: Re: Will not read 06A906032CN NEW BEETLE
Post by: oldcarguy85 on July 23, 2013, 08:20:09 AM
Maybe try pulling the cluster fuse?  I have trouble flashing/reading if cluster fuse is not pulled.  There are two cluster fuses.  Pull the one that leaves the clock on but disables the gauges.


Title: Re: Will not read 06A906032CN NEW BEETLE
Post by: TCSTigersClaw on July 23, 2013, 08:40:22 AM
Well I never had issues until now..The weird thing is this car`s VIN number in e2p is all XXXXX .This is supposed to be a completely stock car.


Title: Re: Will not read 06A906032CN NEW BEETLE
Post by: TCSTigersClaw on July 23, 2013, 09:45:24 AM
ok the car has also immo off, I was too busy looking for REVO signature or something ,that I overlooked the FF`s.

Its not Revo ,so maybe another company with a locked tune that nefmoto can`t read.The problem is the car has completely stock Psi .Anyway


Title: Re: Will not read 06A906032CN NEW BEETLE
Post by: oldcarguy85 on July 24, 2013, 04:31:53 AM
Maybe it was a demo tune that goes back to "stock" after a period of time. I saw your other thread asking for an original. That's probably your best bet. Just boot mode flash it with an original. Maybe even replace the e2p just to make sure.


Title: Re: Will not read 06A906032CN NEW BEETLE
Post by: TCSTigersClaw on July 24, 2013, 08:25:05 AM
thanks , thats what I thought too .Problem is  06A906032CN.ori is very hard to find. For e2p I could flash just a generic without immo.

I found an ori from the same VAG149 family , I could try that .


Title: Re: Will not read 06A906032CN NEW BEETLE
Post by: oldcarguy85 on July 24, 2013, 11:44:04 AM
thanks , thats what I thought too .Problem is  06A906032CN.ori is very hard to find. For e2p I could flash just a generic without immo.

I found an ori from the same VAG149 family , I could try that .

Ya you might be ok.  I assume that's the 1.8T, not the 2.0 right?  I'd just be careful because the 1.8t beetle had a smaller turbo and some other changes as compared to the GTI.  Maybe it was just a smaller downpipe (iI can't remember) but i know they had some hardware differences.


Title: Re: Will not read 06A906032CN NEW BEETLE
Post by: TCSTigersClaw on July 24, 2013, 02:56:03 PM
You are right , but AWU engine supposed to have the same exact setup with the AUM -Golf engine.

The weird thing is ,that AWU nevel listed with 06A906032CN ,only with AVC..the car VIN is for an AWU engine.
Since it also has immo off , i can assume that it has changed its ECU.
Also the flash I got is a 06A906032CK ,also from a beetle ,also AVC ,it should work.

VW New Beetle (1C) Turbo 1,8 AWU 06A906032RT
VW New Beetle (1C) Turbo 1,8 AVC 06A906032CK
VW New Beetle (1C) Turbo 1,8 AVC 06A906032CN
VW New Beetle (1C) Turbo 1,8 AVC 06A906032B
VW New Beetle (1C) Turbo 1,8 AWU 06A906032HH
VW New Beetle (1C) Turbo 1,8 AWU 06A906032FT
VW New Beetle (1C) Turbo 1,8 AWU 06A906032FS
VW New Beetle (1C) Turbo 1,8 AWU 06A906032RT